Hi, I got the HTC one m7 unlocked with the software 3.22.1540.1 android 4.3 sense 5
I try to update to 4.06.1540.3 which is sense 5.5 android 4.4.2 and the phone download the update without problems... But when it's updating the phone show me a red triangle and go back to the previous version so it's rebooted.
This it's the OTA that I'm trying to update :
OTA_M7_UL_K44_SENSE55_MR_BRIGHTSTARUS_WWE_4.06.1540.3-3.22.1540.1_R4_Releasy_344323lyoy5hbg6lts5b9r.zip
Any help?
jonagua said:
Hi, I got the HTC one m7 unlocked with the software 3.22.1540.1 android 4.3 sense 5
I try to update to 4.06.1540.3 which is sense 5.5 android 4.4.2 and the phone download the update without problems... But when it's updating the phone show me a red triangle and go back to the previous version so it's rebooted.
This it's the OTA that I'm trying to update :
OTA_M7_UL_K44_SENSE55_MR_BRIGHTSTARUS_WWE_4.06.1540.3-3.22.1540.1_R4_Releasy_344323lyoy5hbg6lts5b9r.zip
Any help?
Click to expand...
Click to collapse
You probably have some missing /system files or /data/preload files, thats why the recovery shows you a red triangle with an exclamation mark when attempting to update. In this case you could use a RUU or a guru reset tom to reset your phone to 100% stock and then apply ota updates. Flashing a RUU will wipe everything on your phone, so if its a problem for you, make sure to backup everything on your phone before.
please post the output of "fastboot getvar all" except the IMEI and SERIALNO to confirm what ruu or guru reset tom you'll need
alray said:
You probably have some missing /system files or /data/preload files, thats why the recovery shows you a red triangle with an exclamation mark when attempting to update. In this case you could use a RUU or a guru reset tom to reset your phone to 100% stock and then apply ota updates. Flashing a RUU will wipe everything on your phone, so if its a problem for you, make sure to backup everything on your phone before.
please post the output of "fastboot getvar all" except the IMEI and SERIALNO to confirm what ruu or guru reset tom you'll need
Click to expand...
Click to collapse
thank's @alray
ok here it is: model pn07120
tempered
unlocked
m7_ul. pvt ship s-on rh
hboot-1.55.0000
radio-4a.20.3263.16
opendsp-v32.120.274.0909os-
eMMC-boot 2048MB
Sep 17 2013,00:02.53.0
jonagua said:
thank's @alray
ok here it is: model pn07120
tempered
unlocked
m7_ul. pvt ship s-on rh
hboot-1.55.0000
radio-4a.20.3263.16
opendsp-v32.120.274.0909os-
eMMC-boot 2048MB
Sep 17 2013,00:02.53.0
Click to expand...
Click to collapse
then use the guru reset rom here:http://www.htc1guru.com/dld/guru_reset_m7_3-22-1540-1-zip/ copy it to your internal storage (/sdcard) and flash it using a custom recovery (twrp 2.6.3.3 preferred) When installing, select the option to to flash stock recovery, stock radio. do not choose to root. then you should be able to install ota updates. If you wish to s-off the phone, do it now, before updating, its easier to do on lower version.
@alray
ok but i have to root first right? and then recovery.
i got problems too with the stock recovery, i tried to flash the ota but it reboot every time that i try to go to ''apply from internal storage''
i'll let you know later how goes...
millions thanks
jonagua said:
@alray
ok but i have to root first right? and then recovery.
Click to expand...
Click to collapse
no need to root.
flash twrp 2.6.3.3 recovery
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in the custom recovery and install the guru reset rom, you'll get a grapichal user interface to asist you during the installation (aroma installer) When prompted to choose, select "stcok recovery", "stock radio" and don't select to "root".
when the installation finishes, reboot your phone normally and do the ota updates (6 updates to do for latest version 6.07.1540.1).
i got problems too with the stock recovery, i tried to flash the ota but it reboot every time that i try to go to ''apply from internal storage''
Click to expand...
Click to collapse
you can not flash ota manually from stock recovery if your phone is S-ON. Only with S-OFF
alray said:
no need to root.
flash twrp 2.6.3.3 recovery
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then boot in the custom recovery and install the guru reset rom, you'll get a grapichal user interface to asist you during the installation (aroma installer) When prompted to choose, select "stcok recovery", "stock radio" and don't select to "root".
when the installation finishes, reboot your phone normally and do the ota updates (6 updates to do for latest version 6.07.1540.1).
you can not flash ota manually from stock recovery if your phone is S-ON. Only with S-OFF
Click to expand...
Click to collapse
ok i didn't know...
now i'm going to donwload the android SDK to flash the recovery. i let you know later how goes
Hi again @alray
So I can do S-OFF and flash the OTA with my stock recovery instead of change the recovery and flash the Guru.
I will waiting your recommendation
Thanks
Sent from my HTC One using XDA Free mobile app
jonagua said:
Hi again @alray
So I can do S-OFF and flash the OTA with my stock recovery instead of change the recovery and flash the Guru.
I will waiting your recommendation
Thanks
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
for now you can not flash the ota even if you have s-off. There is some missing files in your OS and this must be fixed 1st. The guru reset will fix that, and it will relfash stock recovery over the custom one and you'll be able to flash ota then.
S-OFF is not needed to recover from your situation, however, if you want your phone to be s-off, do it now. Chances to achieve s-off decreases with every updates. WIth s-off you'll have more options to recover from a similar situation in the future.
And btw, new ota updates can no more be flashed manually, even with s-off because they are now encrypted (starting with the 6.07.1540.1 ota)
alray said:
for now you can not flash the ota even if you have s-off. There is some missing files in your OS it this must be fixed 1st. The guru reset will fix that, and it will relfash stock recovery over the custom one and you'll be able to flash ota then.
S-OFF is not needed to recover from your situation, however, if you want your phone to be s-off, do it now. Chances to achieve s-off decreases with every updates. WIth s-off you'll have more options to recover from a similar situation in the future.
And btw, new ota updates can no more be flashed manually, even with s-off because they are now encrypted (starting with the 6.07.1540.1 ota)
Click to expand...
Click to collapse
Thank's i really appreciate your help!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi @alray
I'm here again jus to let you know that I flash the GURU and !yes! I Could update my phone. I received 4 updates and the last one it's 5.11.1540.9 with sense 6 which I running now. I don't know why I don't receive the others but anyway everything it's working excellent.
Sent from my HTC One using XDA Free mobile app
jonagua said:
Hi @alray
I'm here again jus to let you know that I flash the GURU and !yes! I Could update my phone. I received 4 updates and the last one it's 5.11.1540.9 with sense 6 which I running now. I don't know why I don't receive the others but anyway everything it's working excellent.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Your not alone having issue receiving the last update (6.07.1540.1). If you absolutely want this update, you can reflash a custom recovery, flash the 6.07.1540.1 nandroid backup posted in the dev edtition update thread + the 6.07.1540.1 firmware. Latest updates is mainly security fixes, not much different from 5.11.1540.9. you might want to wait a little more and see if the update is pushed to your phone in the next few weeks.
alray said:
Your not alone having issue receiving the last update (6.07.1540.1). If you absolutely want this update, you can reflash a custom recovery, flash the 6.07.1540.1 nandroid backup posted in the dev edtition update thread + the 6.07.1540.1 firmware. Latest updates is mainly security fixes, not much different from 5.11.1540.9. you might want to wait a little more and see if the update is pushed to your phone in the next few weeks.
Click to expand...
Click to collapse
Ok, I'm going to wait a little more. If it's just security fixes I can wait.
Sent from my HTC One using XDA Free mobile app
jonagua said:
Ok, I'm going to wait a little more. If it's just security fixes I can wait.
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Hi @alray
I finally received the ota 6.07.1540.1 and as you said it's just security fixes. Now I'll waiting for android version 4.4.4 or android L.
Thanks
Sent from my HTC One using XDA Free mobile app
Related
Hi, My HTC ONE M7 is SIM unlocked but with Vodafone firmware, it is rooted on stock firmware 4.2.2 Rom version is 2.24.161.1 hboot 1.54.0000, I want to return it to unrooted state, could someone point me in the right direction thanks.
HTC One CID: VODAP102 OS(2.24.161.1) Death to Stock
granv said:
Hi, My HTC ONE M7 is SIM unlocked but with Vodafone firmware, it is rooted on stock firmware 4.2.2 Rom version is 2.24.161.1 hboot 1.54.0000, I want to return it to unrooted state, could someone point me in the right direction thanks.
Click to expand...
Click to collapse
i Also have HTC One 4.2.2 Jerry Beam CID: VODAP102 *Death*
OS: 2.24.161.1
Anyone help me to upload Stock firmware to recovery
My Device Detail is Below
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v31.120.274.0617
OS-2.24.161.1
eMMC-boot 2048MB
Jun 23 2013, 03:49:03.0
granv said:
Hi, My HTC ONE M7 is SIM unlocked but with Vodafone firmware, it is rooted on stock firmware 4.2.2 Rom version is 2.24.161.1 hboot 1.54.0000, I want to return it to unrooted state, could someone point me in the right direction thanks.
Click to expand...
Click to collapse
Hi, I have a nandroid backup of this buried on my phone however as an extreme noob I do not know how to extract
granv said:
Hi, My HTC ONE M7 is SIM unlocked but with Vodafone firmware, it is rooted on stock firmware 4.2.2 Rom version is 2.24.161.1 hboot 1.54.0000, I want to return it to unrooted state, could someone point me in the right direction thanks.
Click to expand...
Click to collapse
Did you get a resolution for this?
I too am on hboot 1.54 with S-ON and CID=VODAP001 and i'd like to be able to go back to Stock so I can get OTA updates.
OK Guys
Please read mikes thread here:
http://forum.xda-developers.com/showthread.php?t=2265618
It will help you to do all you need :victory::victory:
Please try the search option before posting, as most issues have been asked and resolved in the past
good luck
L0rdNels0n said:
OK Guys
Please read mikes thread here:
http://forum.xda-developers.com/showthread.php?t=2265618
It will help you to do all you need :victory::victory:
Please try the search option before posting, as most issues have been asked and resolved in the past
good luck
Click to expand...
Click to collapse
Well iam stuck with the same, trying find ruu or stock version for my htc. I tried to flash stock dump it fails as the cid doesnt match.
Can some one advice, details of my device
Cid:vodap001
S-on
Device : PN0710000
Boot loader 1.54.0000
2.24.161.1
Thanks
L0rdNels0n said:
OK Guys
Please read mikes thread here:
http://forum.xda-developers.com/showthread.php?t=2265618
It will help you to do all you need :victory::victory:
Please try the search option before posting, as most issues have been asked and resolved in the past
good luck
Click to expand...
Click to collapse
Hi L0rdNels0n, thanks for the help but i'm not quite sure where you are directing us to in Mike1986's thread? If i have understood correctly because we are S-ON with hboot 1.54 and CID=VODAP001 we are unable to flash firmware or return to stock unless someone has an RUU or nandroid for CID=VODAP001. SuperCID doesnt work because we are S-ON and we cant S-OFF because we are on hboot 1.54 (Revone doesnt work). Is that not correct?
I know we can flash ROMs and use a different 'recovery' but we cant update firmware or return the handset to stock Vodaphone.
Have I not understood something?
Mine was originally VODAP001 and I am also looking for a way to go back to Vodafone stock because I am planning to return the phone (i have that awful red/blue noise when taking pictures in low light conditions).
This is my current setup (running mike's 4.3 ROM).
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I suppose I also need to downgrade my firmware to x.xx.161.x
Any ideas?
Yup Im in the same boat, need to return my phone to htc for repair but need to return it to stock.
any of you teo sort it out im in the same boat. would like any advice appreciate it
Grathite said:
any of you teo sort it out im in the same boat. would like any advice appreciate it
Click to expand...
Click to collapse
you may wanna check my guide , and adjust to your needs: http://forum.xda-developers.com/showthread.php?t=2541082
post there if you have any issues
Any updates on this?
I am guessing that there are still people who want to recover their device to Vodafone for warranty repairs, is there any more info on a file that can be used (& how) for the UK Vodafone ROM?
Cheers
Martin
still no RUU? i can only find a nandroid for Vodafone Germany -.-
Cactus_Punch said:
still no RUU? i can only find a nandroid for Vodafone Germany -.-
Click to expand...
Click to collapse
if you're talking about this one: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-vodap102-1-29-161-7-7z/
it should work for UK also:
Code:
ro.aa.modelid=[B]PN0710000[/B]
ro.aa.cidlist=[B]VODAP001[/B],VODAP102,VODAPE17,VODAP405,VODAP304,VODAPD18,VODAP120,VODAP110
nkk71 said:
if you're talking about this one: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-vodap102-1-29-161-7-7z/
it should work for UK also:
Code:
ro.aa.modelid=[B]PN0710000[/B]
ro.aa.cidlist=[B]VODAP001[/B],VODAP102,VODAPE17,VODAP405,VODAP304,VODAPD18,VODAP120,VODAP110
Click to expand...
Click to collapse
I'm using this that you wrote in another thread
if that is the right one for you, and you stay S-Off, then:
"1- extract the "firmware.zip" package and put it in your adb folder; you'll need it later
2- download and install this (using CWM or TWRP): http://www.htc1guru.com/dld/guru_res...-24-161-1-zip/
select WIPE, unselect ROOT, unselect "stock recovery"
3- use either the Guru Bootloader Reset method (mentioned in the guide), or if you are comfortable with adb:
http://forum.xda-developers.com/show....php?t=2477792 (if you need to remove TAMPERED)
http://forum.xda-developers.com/show....php?t=2475914 (IF you need to set LOCKED)
(the above adb commands work in custom recovery)
4- flash firmware.zip, you extracted earlier:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
you should now be back at stock."
I'm installing the zip and selected wipe but its stuck at 0% D:
Edit: reloaded it and unchecked restore stock radio its installing now
Cactus_Punch said:
I'm using this that you wrote in another thread
if that is the right one for you, and you stay S-Off, then:
"1- extract the "firmware.zip" package and put it in your adb folder; you'll need it later
2- download and install this (using CWM or TWRP): http://www.htc1guru.com/dld/guru_res...-24-161-1-zip/
select WIPE, unselect ROOT, unselect "stock recovery"
3- use either the Guru Bootloader Reset method (mentioned in the guide), or if you are comfortable with adb:
http://forum.xda-developers.com/show....php?t=2477792 (if you need to remove TAMPERED)
http://forum.xda-developers.com/show....php?t=2475914 (IF you need to set LOCKED)
(the above adb commands work in custom recovery)
4- flash firmware.zip, you extracted earlier:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
you should now be back at stock."
I'm installing the zip and selected wipe but its stuck at 0% D:
Edit: reloaded it and unchecked restore stock radio its installing now
Click to expand...
Click to collapse
had nothing to do with radio, aroma installer sometimes just hangs.
and yep that method works too
and when you flash the firmware.zip it will also restore the radio.
nkk71 said:
had nothing to do with radio, aroma installer sometimes just hangs.
and yep that method works too
and when you flash the firmware.zip it will also restore the radio.
Click to expand...
Click to collapse
Awesome mega thanks!
---------- Post added at 05:22 PM ---------- Previous post was at 04:40 PM ----------
nkk71 said:
had nothing to do with radio, aroma installer sometimes just hangs.
and yep that method works too
and when you flash the firmware.zip it will also restore the radio.
Click to expand...
Click to collapse
I finished doing all those steps I still get "This is a test device" messages any idea?
Cactus_Punch said:
Awesome mega thanks!
---------- Post added at 05:22 PM ---------- Previous post was at 04:40 PM ----------
I finished doing all those steps I still get "This is a test device" messages any idea?
Click to expand...
Click to collapse
Because of s-off, disregard msg.
Sent from my HTC One using Tapatalk
OTA update nightmare, am I rooted or not??
Hello,
I've had a real nightmare with this so wondering if you guys could help.
I rooted my phone no probs. I then installed elementalX, no probs. (S-on and still is now) OTA update needs installing, so I thought I'll just put the stock recovery on and install the update, then revert to TWRP all cocky like.
FAIL. So I blame the custom kernel and try uninstalling it, or installing over it with the stock Kernel from htcdev.
Then realise I might have screwed something up using the kernel developer kernel??!! Kernel version currently states:
3.4.10-g40b189c
[email protected] #1
SMP PREEMPT
Flash stock recovery on phone (don't ask me which but I switching between that and TWRP no probs). I panick and disable SuperSu, but it carries on. I delete it using ESfile explorer (giving root permissions to deleting it), its still there. I re-lock the bootloader. I flash the version of the firmware.zip on this thread which is compatible with my VODAP001 (even if it wasn't I'm still s-on, so it won't do anything at worst) it flashes fine, fastboot reboot. Then I try installing the OTA and after a quarter of the install progress I get red triangle and "!". ADB.exe see's my phone as unauthorised, but the phone behaves as if it's rooted still?!
ALL I WANT TO DO IS INSTALL THIS BLOODY OTA UPDATE!! So I can forget about it again. I am currently on 6.12.161.8 the new one is .9. Or is it really that important? Should I freeze "SYSTEM Updates MUC" or similar using Titanium?
Any help would be much appreciated, thanks in advance :good:
mofoofighter said:
Hello,
I've had a real nightmare with this so wondering if you guys could help.
I rooted my phone no probs. I then installed elementalX, no probs. (S-on and still is now) OTA update needs installing, so I thought I'll just put the stock recovery on and install the update, then revert to TWRP all cocky like.
FAIL. So I blame the custom kernel and try uninstalling it, or installing over it with the stock Kernel from htcdev.
Then realise I might have screwed something up using the kernel developer kernel??!! Kernel version currently states:
3.4.10-g40b189c
[email protected] #1
SMP PREEMPT
Flash stock recovery on phone (don't ask me which but I switching between that and TWRP no probs). I panick and disable SuperSu, but it carries on. I delete it using ESfile explorer (giving root permissions to deleting it), its still there. I re-lock the bootloader. I flash the version of the firmware.zip on this thread which is compatible with my VODAP001 (even if it wasn't I'm still s-on, so it won't do anything at worst) it flashes fine, fastboot reboot. Then I try installing the OTA and after a quarter of the install progress I get red triangle and "!". ADB.exe see's my phone as unauthorised, but the phone behaves as if it's rooted still?!
ALL I WANT TO DO IS INSTALL THIS BLOODY OTA UPDATE!! So I can forget about it again. I am currently on 6.12.161.8 the new one is .9. Or is it really that important? Should I freeze "SYSTEM Updates MUC" or similar using Titanium?
Any help would be much appreciated, thanks in advance :good:
Click to expand...
Click to collapse
your missing system files from unlocking the bootloader, OTA will never work unless you RUU back to stock or find a Guru reset that includes the priv-app system folder that got deleted during unlock.
when the OTA fails you can hold volume up and tap power to see what file is missing / changed
Hi Everyone,
I'm on ROGERS, I've unlocked my bootloader, rooted, and enabled S-OFF with rumrunner, all my device info is listed below. I simply would like to know how can I update to the latest OTA 4.4.2. from Rogers. What are the exact steps I need to follow, and what files to flash if that's what I need to do? I prefer keeping root and without losing any data if possible.
Android 4.3
HTC Sense version 5.0
Software Number = 3.22.631.1
TWRP v2.6.3.0
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-ROGER001
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.22.631.1
eMMC-boot 2048MB
Sep 17 2013, 00:07:12.0
Thanks in advance for any assistance you can provide, or even just pointing me to the correct thread.
sqleinstein said:
Hi Everyone,
I'm on ROGERS, I've unlocked my bootloader, rooted, and enabled S-OFF with rumrunner, all my device info is listed below. I simply would like to know how can I update to the latest OTA 4.4.2. from Rogers. What are the exact steps I need to follow, and what files to flash if that's what I need to do? I prefer keeping root and without losing any data if possible.
Android 4.3
HTC Sense version 5.0
Software Number = 3.22.631.1
TWRP v2.6.3.0
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-ROGER001
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.22.631.1
eMMC-boot 2048MB
Sep 17 2013, 00:07:12.0
Thanks in advance for any assistance you can provide, or even just pointing me to the correct thread.
Click to expand...
Click to collapse
Are you getting the ota notification?
If so I think all you need to do is flash stock recovery, redownload the ota and install.
If you don't have the stock recovery, there is a Telus 3.22.631.1 RUU posted, I extracted the recovery from it and installed. Worked fine for me.
sqleinstein said:
Hi Everyone,
I'm on ROGERS, I've unlocked my bootloader, rooted, and enabled S-OFF with rumrunner, all my device info is listed below. I simply would like to know how can I update to the latest OTA 4.4.2. from Rogers. What are the exact steps I need to follow, and what files to flash if that's what I need to do? I prefer keeping root and without losing any data if possible.
Android 4.3
HTC Sense version 5.0
Software Number = 3.22.631.1
TWRP v2.6.3.0
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-OFF RH
CID-ROGER001
HBOOT-1.55.0000
RADIO-4A.20.3263.16
OpenDSP-v32.120.274.0909
OS-3.22.631.1
eMMC-boot 2048MB
Sep 17 2013, 00:07:12.0
Thanks in advance for any assistance you can provide, or even just pointing me to the correct thread.
Click to expand...
Click to collapse
This is the exact same situation as me...have you solved this yet?
---------- Post added at 01:59 AM ---------- Previous post was at 01:52 AM ----------
mb_guy said:
Are you getting the ota notification?
If so I think all you need to do is flash stock recovery, redownload the ota and install.
If you don't have the stock recovery, there is a Telus 3.22.631.1 RUU posted, I extracted the recovery from it and installed. Worked fine for me.
Click to expand...
Click to collapse
Can you explain how you did this? I am in the same situation as the OP and would love to figure this out. Also, I'm pretty sure the Telus stock recovery is 3.22.661.1 correct? Where did you download it? Sorry for all the questions but I would love to figure this out and update my phone.
Thanks in advance for any help!!
eightdown said:
This is the exact same situation as me...have you solved this yet?
---------- Post added at 01:59 AM ---------- Previous post was at 01:52 AM ----------
Can you explain how you did this? I am in the same situation as the OP and would love to figure this out. Also, I'm pretty sure the Telus stock recovery is 3.22.661.1 correct? Where did you download it? Sorry for all the questions but I would love to figure this out and update my phone.
Thanks in advance for any help!!
Click to expand...
Click to collapse
download the rogers ruu.zip here then extract the recovery.img file to your adb/fastboot folder. then
fastboot flash recovery recovery.img
fastboot reboot-bootloader
alray said:
download the rogers ruu.zip here then extract the recovery.img file to your adb/fastboot folder. then
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Great, thanks for your help. Another question though (forgive my ignorance), I have heard that the OTA will fail if certain files are missing from the phone (even flashlight, calculator etc...which were missing after i rooted), should i be worried about this?
*EDIT* Further to my previous questions, how exactly do you extract the recovery.img? Is it something different that unzipping the file?
eightdown said:
Great, thanks for your help. Another question though (forgive my ignorance), I have heard that the OTA will fail if certain files are missing from the phone (even flashlight, calculator etc...which were missing after i rooted), should i be worried about this?
Click to expand...
Click to collapse
The ota will md5 cheksum target files to be updated/patched. So if i.e flashlight.apk is to be updated and the apk does't exist anymore, then the md5 checksum will fail and the update will be aborted. (you will probably see this pic in recovery)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this is the case you'll probably need to restore to 100% stock before applying ota (like i'm doing now, deleted some system files and now im unable to update to 4.4.2. Had to restore to stock then apply ota)
eightdown said:
*EDIT* Further to my previous questions, how exactly do you extract the recovery.img? Is it something different that unzipping the file?
Click to expand...
Click to collapse
nothing different, just ''unzip''
alray said:
The ota will md5 cheksum target files to be updated/patched. So if i.e flashlight.apk is to be updated and the apk does't exist anymore, then the md5 checksum will fail and the update will be aborted. (you will probably see this pic in recovery)
If this is the case you'll probably need to restore to 100% stock before applying ota (like i'm doing now, deleted some system files and now im unable to update to 4.4.2. Had to restore to stock then apply ota)
Click to expand...
Click to collapse
Again, thanks for your help, i really appreciate it. I've been researching for the past couple days and it seems like i just get more and more confused.
Can the 100% stock be flashed through TWRP? I'm assuming root is lost this way so the stock recovery would have to be flashed through fastboot?
alray said:
nothing different, just ''unzip''
Click to expand...
Click to collapse
I'm on a mac so i'm not sure if this does something different but after extracting, i don't see the recovery.img file, i see a recovery.log file though.
eightdown said:
Again, thanks for your help, i really appreciate it. I've been researching for the past couple days and it seems like i just get more and more confused.
Can the 100% stock be flashed through TWRP? I'm assuming root is lost this way so the stock recovery would have to be flashed through fastboot?
Click to expand...
Click to collapse
Try to apply ota with stock recovery before. maybe returning to 100% will not be needed.
recovery is always flashed from fastboot, not related to root access.
fastboot flash recovery recovery.img
fastboot reboot-bootloader
if it fail and you want to restore to 100% stock, then follow SaHiLzZ guide for canadian users you can find in my signature. (don't forget to give him a ''thanks'' if you found his guide helpful)
eightdown said:
I'm on a mac so i'm not sure if this does something different but after extracting, i don't see the recovery.img file, i see a recovery.log file though.
Click to expand...
Click to collapse
Sry you also have to unzip the firmware.zip
unzip the ruu, then unzip the firmware.zip, the recovery.img should be there.
hope its help
alray said:
Try to apply ota with stock recovery before. maybe returning to 100% will not be needed.
recovery is always flashed from fastboot, not related to root access.
fastboot flash recovery recovery.img
fastboot reboot-bootloader
if it fail and you want to restore to 100% stock, then follow SaHiLzZ guide for canadian users you can find in my signature. (don't forget to give him a ''thanks'' if you found his guide helpful)
Sry you also have to unzip the firmware.zip
unzip the ruu, then unzip the firmware.zip, the recovery.img should be there.
hope its help
Click to expand...
Click to collapse
When i unzip the file you linked previously, this is what i see
No firmware.zip. The file was called "Stock_JB_4.3_ROGER001_TWRP_3.22.631.1_htc_one_m7.zip"
I feel like a jerk for continuing to bother you but the help your giving me is also making me feel better about all this, so again, thanks!
alray said:
download the rogers ruu.zip here then extract the recovery.img file to your adb/fastboot folder. then
fastboot flash recovery recovery.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Didn't think there was an actual Rogers RUU available. At least I couldn't find one. That's why I used the Telus one.
http://d-h.st/Fv8
mb_guy said:
Didn't think there was an actual Rogers RUU available. At least I couldn't find one. That's why I used the Telus one.
http://d-h.st/Fv8
Click to expand...
Click to collapse
eightdown said:
When i unzip the file you linked previously, this is what i see
No firmware.zip. The file was called "Stock_JB_4.3_ROGER001_TWRP_3.22.631.1_htc_one_m7.zip"
I feel like a jerk for continuing to bother you but the help your giving me is also making me feel better about all this, so again, thanks!
Click to expand...
Click to collapse
Sry mate, linked you a nandroid backup file! use that ruu file @mb_guy linked. Telus recovery is the same as rogers, so you can proceed with this.
alray said:
Sry mate, linked you a nandroid backup file! use that ruu file @mb_guy linked. Telus recovery is the same as rogers, so you can proceed with this.
Click to expand...
Click to collapse
Sorry, I also worded it wrong, it is just the Telus recovery.img
alray said:
Sry mate, linked you a nandroid backup file! use that ruu file @mb_guy linked. Telus recovery is the same as rogers, so you can proceed with this.
Click to expand...
Click to collapse
mb_guy said:
Sorry, I also worded it wrong, it is just the Telus recovery.img
Click to expand...
Click to collapse
So am I wrong to assume that if i use the Rogers Nandroid backup, then extract the recovery.img from the Telus file, flash it in, i should be ok to OTA? I guess i'll see what happens if i do so!
eightdown said:
So am I wrong to assume that if i use the Rogers Nandroid backup, then extract the recovery.img from the Telus file, flash it in, i should be ok to OTA? I guess i'll see what happens if i do so!
Click to expand...
Click to collapse
I thought your rom was still stock, so likely all you need from the nandroid is the missing apps (calc and flashlight) not sure if the ota cares if they are missing. I would just try recovery first and see what happens
eightdown said:
So am I wrong to assume that if i use the Rogers Nandroid backup, then extract the recovery.img from the Telus file, flash it in, i should be ok to OTA? I guess i'll see what happens if i do so!
Click to expand...
Click to collapse
just flash the recovery.img linked above. then try to apply the ota. if it fail then use that rogers nandroid to restore to stock following instructions from sahilzz guide in my signature
alray said:
just flash the recovery.img linked above. then try to apply the ota. if it fail then use that rogers nandroid to restore to stock following instructions from sahilzz guide in my signature
Click to expand...
Click to collapse
ok, i will just try the stock recovery and then OTA. Hope it works. One more question though (sorry haha), after i unzip the RUU, do i have to rename the recovery_signed.img to recovery.img or is it ok as is?
eightdown said:
ok, i will just try the stock recovery and then OTA. Hope it works. One more question though (sorry haha), after i unzip the RUU, do i have to rename the recovery_signed.img to recovery.img or is it ok as is?
Click to expand...
Click to collapse
you can rename it what you want
fastboot flash recovery <name_of_recovery_file_here>.img
fastboot reboot-bootloader
mb_guy said:
I thought your rom was still stock, so likely all you need from the nandroid is the missing apps (calc and flashlight) not sure if the ota cares if they are missing. I would just try recovery first and see what happens
Click to expand...
Click to collapse
alray said:
just flash the recovery.img linked above. then try to apply the ota. if it fail then use that rogers nandroid to restore to stock following instructions from sahilzz guide in my signature
Click to expand...
Click to collapse
Just an update guys (again, thanks for all your help, I really appreciate it!!): I flashed in the Telus recovery and tried the OTA with my stock ROM and unfortunately, it didn't work (I got the picture with the red triangle). I guess there was too much modified with my system.
I reflashed TWRP and then flashed the Roger's Nandroid after which I then flashed the Telus recovery again and decided to try the OTA. It worked! Phone updated to 4.4.2 so I flashed in TWRP and SuperSU and all is well. Rooted, Unlocked and S-OFF on stock 4.4.2.
One issue that did arise (which i also saw when i flashed ARHD 51) was now I can't file transfer on my Mac. It still works on a Windows based computer but HTC Sync and Android File Transfer both crash on my Mac.
:good:Anyway, thanks again for your help guys!:good:
Big Thanks to mb_guy and alray!
I want to thank mb_guy and alray for thier help.
Here are the steps that what worked for me.
1) I flashed the telus recovery_3.22.661.1_R3_signed.img
2) I was then able to apply the OTA from Rogers.
3) I re-flashed the latest twrp recovery
4) Re-applied chainfire's Super Su
Thanks again everyone!
Here we have the RUU for the Sprint HTC One 4.06.651.4!!! This RUU is for the Sprint One ONLY to restore your phone back to stock. If you are S-ON, you MUST relock your bootloader prior to using this RUU.
HUGE Thanks to the dude who hooked me up, you're awesome!
credit to @-viperboy- for decrypting, thanks!
***IMPORTANT NOTE*** you must first update your hboot to 1.56 to flash this 4.06 RUU, see full firmware below ( I recommend being s-off before doing so)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to use:
-Download Sprint_HTC_One_m7wls_4.06.651.4_RUU.zip
-extract zip to a folder on your pc
-boot into bootloader (various ways)
-using fastboot, type this cmd: fastboot oem lock this will relock the bootloader (S-ON ONLY)
-from pc, run ARUWizard.exe from the extracted folder. it will run the RUU utility & flash back to stock
DEVs, here is the Decrypted version!
Sprint_HTC_One_m7wls_4.06.651.4_RUU_decrypted.zip
These new RUU's now have the system.img split into 3 imgs. You must combine prior to extracting. Copy all 3 to a folder, then...
Use this cmd for Windows:
copy /b system_1.img + system_2.img + system_3.img newsystem.img
Use this cmd for Linux:
cat system_1.img system_2.img system_3.img > newsystem.img
credit to @-viperboy- for the cmds, thanks!
Here is the extracted Firmware:
Full Firmware from RUU (fastboot flashable): http://www.androidfilehost.com/?fid=23329332407568410
Modified Firmware w/ Radio....removed hboot, boot, recovery (fastboot flashable): http://www.androidfilehost.com/?fid=23329332407574146
some basic instructions for flashing the modified firmware....
-rename firmware to firmware.zip
-copy firmware.zip to your sdk folder
-boot into bootloader
-plug in usb
-select fastboot option (screen should say fastboot usb)
-type Fastboot oem rebootRUU
-when u see the black screen w/ HTC, type Fastboot flash zip firmware.zip
-when it's done, type Fastboot reboot
Here's a nice video from @thoughtlesskyle showing you how to flash the firmware:
Stock Rooted Romz Made From The RUU
Sprint_One_Stock_Rooted_Deodexed_4.06.651.4.zip
MD5 5603e630ddffc29a9dd20c96867c1853
Sprint_One_Stock_Rooted_Odex_4.06.651.4.zip
MD5 022aad5e626f08ea6899d7390320324c
Unsecure boot img. init.d support, data/app support
If you get the Side by Side Configuration error while using the RUU you need to install Microsoft Visual C++
Great work gents
Sent from my Nexus 7
If I were to do the Ruu and im s-off with hboot 1.55 will it update me to 1-56 hboot and still have s-off. I read on a thread that by flashimg the Ruu will eliminate my phone not able to update profile and prl. I jhave been having issues in updating my profile with code 1233, currently in Bad Boyz Rom 1.0 4.06
Sent from my HTCONE using xda app-developers app
Thank you for offering this option so soon, it's greatly appreciated and saves so much time!
Sent from my HTCONE using Tapatalk
there have been reports of the RUU not unzipping, I have re-upped... http://www.androidfilehost.com/?fid=23329332407573774
Will come in handy, thanks O.M.J.!
Sent from my HTCONE
This is what I get every time. After following this guide I am normally able to use fastboot/adb just fine.
I am on rumrunner hboot 1.55.5555
Let me know what other info I can provide.. Please help!
Edit:
I ran the utility on my XP computer, and it gave me a little more info: "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
Is the RUU different than the OTA?
numus said:
Is the RUU different than the OTA?
Click to expand...
Click to collapse
Are you asking me?
numus said:
Is the RUU different than the OTA?
Click to expand...
Click to collapse
The end result are the same.
The OTA will update the the version of android you are on and keepall of your data intact
The RUU will wipe everything on your phone and reset it as it was when it was brand new but with the latest version of android or the version of the RUU you are using.
---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------
systemshock869 said:
This is what I get every time. After following this guide I am normally able to use fastboot/adb just fine.
I am on rumrunner hboot 1.55.5555
Let me know what other info I can provide.. Please help!
Edit:
I ran the utility on my XP computer, and it gave me a little more info: "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
Click to expand...
Click to collapse
Can you confirm the windows 8.1 drivers are installed?
benny3 said:
The end result are the same.
The OTA will update the the version of android you are on and keepall of your data intact
The RUU will wipe everything on your phone and reset it as it was when it was brand new but with the latest version of android or the version of the RUU you are using.
---------- Post added at 03:19 AM ---------- Previous post was at 03:18 AM ----------
Can you confirm the windows 8.1 drivers are installed?
Click to expand...
Click to collapse
Thanks... knew that part but was wondering why anyone would rebase based on the RUU then.
numus said:
Thanks... knew that part but was wondering why anyone would rebase based on the RUU then.
Click to expand...
Click to collapse
when u install an OTA, alot of files are "patched", RUU is just cleaner. When I diffed the 4.06 dump against the RUU, most of the files were binary equal but there were 250+ that were not.
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
no more simultaneous voice + LTE
O.M.J said:
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
Click to expand...
Click to collapse
i updated to kit kat and now I don't have simultaneous voice and LTE which I used to have...anyone else notice this? I know that simultaneous voice and 3G was never an option(unlike the EVO 4G LTE) but I always had simultaneous LTE + Voice...this sucks!!
O.M.J said:
OP updated with 4.06 firmware, which includes the radio & much more that were not in the OTA....this will be especially handy for users that are on older versions of JB that need to get caught up.
Click to expand...
Click to collapse
I'm trying to run the RUU but I am getting an error 158. The installer runs and gets my phone to the black HTC screen then it fails. After exiting the installer my phone does a reboot and I'm back into my ROM (Bad Boys 4.4.2 v1.1). My phone is running unlocked HBOOT 1.44 and is S-OFF. Any ideas? Searching has netted some hits on other device forums but nothing terribly helpful for the One specifically. Should I take the Rom.zip out of the 4_06_651_4 folder and try to flash it with fastboot? If so is that ok to do unlocked or do I need to do an oem lock first?
jaybombz said:
This is exactly what I'm trying to do but I am getting an error 158. The installer runs and gets my phone to the black HTC screen then it fails. After exiting the installer my phone does a reboot and I'm back into my ROM (Bad Boys 4.4.2 v1.1). My phone is running unlocked HBOOT 1.44 and is S-OFF. Any ideas? Searching has netted some hits on other device forums but nothing terribly helpful for the One specifically. Should I take the Rom.zip out of the 4_06_651_4 folder and try to flash it with fastboot? If so is that ok to do unlocked or do I need to do an oem lock first?
Click to expand...
Click to collapse
You run this RUU from your PC not fastboot.
BD619 said:
You run this RUU from your PC not fastboot.
Click to expand...
Click to collapse
Understood, apologies if my post wasn't clear. When running the RUU installer from my PC I get an error 158. I was asking if anyone knows what is causing this/how to fix it or if I can work around it by manually running fastboot flash zip rom.zip and if that was safe to do unlocked.
Thanks for your help!
Unless I am mistaken, you have to relock your bootloader to run the RUU.
jaybombz said:
Understood, apologies if my post wasn't clear. When running the RUU installer from my PC I get an error 158. I was asking if anyone knows what is causing this/how to fix it or if I can work around it by manually running fastboot flash zip rom.zip and if that was safe to do unlocked.
Thanks for your help!
Click to expand...
Click to collapse
sevarious said:
Unless I am mistaken, you have to relock your bootloader to run the RUU.
Click to expand...
Click to collapse
OP says only if you're S-ON so I thought you didn't have to if you are S-OFF.
Hi
I'm S-OFF, CWM 6.0.4.8 and have relocked Bootloader with Guru Reset.
CID: VODAP001
modelid: PN0710000
I went back to stock using Guru Reset M7 2.24.161.1 (correct version for my CID) to get all the firmware updates before going back to CM11 but my OTA updates fail when they start to install:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How can I get them to install please?
hal_chase said:
Hi
I'm S-OFF, CWM 6.0.4.8 and have relocked Bootloader with Guru Reset.
CID: VODAP001
modelid: PN0710000
I went back to stock using Guru Reset M7 2.24.161.1 (correct version for my CID) to get all the firmware updates before going back to CM11 but my OTA updates fail when they start to install:
How can I get them to install please?
Click to expand...
Click to collapse
run the Guru reset again and choose to install stock recovery this time
clsA said:
run the Guru reset again and choose to install stock recovery this time
Click to expand...
Click to collapse
Doesn't make any difference (still fails), what else can I do?
I reset to stock using all the options in Guru Reset M7 2.24.161.1, tried the OTA and it failed with the same error.
I then assumed it had failed because my bootloader was unlocked so I flashed CWM, then flashed Guru Bootloader Reset and set it to Remove Tampered and Relock Bootloader.
I do not intend staying on Stock, all I want is updated firmware (old firmware is causing me issues on CM11) so maybe there is another non disruptive way of updating the firmware?
hal_chase said:
Doesn't make any difference (still fails), what else can I do?
I reset to stock using all the options in Guru Reset M7 2.24.161.1, tried the OTA and it failed with the same error.
I then assumed it had failed because my bootloader was unlocked so I flashed CWM, then flashed Guru Bootloader Reset and set it to Remove Tampered and Relock Bootloader.
I do not intend staying on Stock, all I want is updated firmware (old firmware is causing me issues on CM11) so maybe there is another non disruptive way of updating the firmware?
Click to expand...
Click to collapse
they will fail with custom recovery
clsA said:
they will fail with custom recovery
Click to expand...
Click to collapse
So, does having an unlocked bootloader not break OTA's then?
I'm 99% sure I tried OTA updates the second my phone reverted to stock using Guru Reset but I'll run it again just to be sure.
hal_chase said:
So, does having an unlocked bootloader not break OTA's then?
I'm 99% sure I tried OTA updates the second my phone reverted to stock using Guru Reset but I'll run it again just to be sure.
Click to expand...
Click to collapse
with s-off you can manually flash the OTA your self ...from stock recovery
clsA said:
with s-off you can manually flash the OTA your self ...from stock recovery
Click to expand...
Click to collapse
I've been unable to find an OTA for VODAP001 CID.
I'm just running Guru Reset again now so will let you know about the OTA
hal_chase said:
I've been unable to find an OTA for VODAP001 CID.
I'm just running Guru Reset again now so will let you know about the OTA
Click to expand...
Click to collapse
Well after the Guru Reset you could capture the OTApkg.zip and upload it for others in the future.
clsA said:
Well after the Guru Reset you could capture the OTApkg.zip and upload it for others in the future.
Click to expand...
Click to collapse
I've managed to get one OTA but the second one (4.19.161.11 - 4.4.2) keeps saying download unsuccessful (corrupted), tried it about 9 times now.
Would I be able to flash OTA M7UL K44 SENSE60 Vodafone UK 5.16.161.2-4.19.161.11 release_379920 or would it fail on a CID mismatch?
hal_chase said:
I've managed to get one OTA but the second one (4.19.161.11 - 4.4.2) keeps saying download unsuccessful (corrupted), tried it about 9 times now.
Would I be able to flash OTA M7UL K44 SENSE60 Vodafone UK 5.16.161.2-4.19.161.11 release_379920 or would it fail on a CID mismatch?
Click to expand...
Click to collapse
you can't skip from 3.x to 5.x if that's your question
clsA said:
you can't skip from 3.x to 5.x if that's your question
Click to expand...
Click to collapse
I'll be more specific shall I?
Is it possible to flash OTA updates with stock recovery via ADB or will they fail due to a CID mismatch?
hal_chase said:
I'll be more specific shall I?
Is it possible to flash OTA updates with stock recovery via ADB or will they fail due to a CID mismatch?
Click to expand...
Click to collapse
you just copy the ota.zip to your phone, boot to stock recovery and flash it from their ...no adb involved
Boot to the bootloader and choose recovery
Wait a second and press power and vol up
Wait for the menu then choose to install from phone storage
Click to expand...
Click to collapse
clsA said:
you just copy the ota.zip to your phone, boot to stock recovery and flash it from their ...no adb involved
Click to expand...
Click to collapse
Cool, thanks.
All I'm trying to do here is get the latest firmware the quickest way possible, then I'm going back to CM11, I've got no interest in sticking with Sense.
If there's a quicker way of achieving this instead of flashing JB 4.2, JB 4.3, JB 5.0, K 4.4 (Sense 5), K 4.4 (Sense 6) then that would be perfect.
clsA said:
you just copy the ota.zip to your phone, boot to stock recovery and flash it from their ...no adb involved
Click to expand...
Click to collapse
I've tried this method to flash an updated Superuser.zip and I got 'Installation Aborted', I also tried it with JB 4.3 (Vodafone UK 3.63.161.6-2.24.161.1) and got 'installation Aborted'
What am I doing wrong please?
delete Dp
hal_chase said:
I've tried this method to flash an updated Superuser.zip and I got 'Installation Aborted', I also tried it with JB 4.3 (Vodafone UK 3.63.161.6-2.24.161.1) and got 'installation Aborted'
What am I doing wrong please?
Click to expand...
Click to collapse
Well you sure can't flash supersu from stock recovery.
Flash the ota again.
Wait I thought you said you already took the first ota?
Sent from my HTC One using Tapatalk 4
clsA said:
Well you sure can't flash supersu from stock recovery.
Flash the ota again.
Wait I thought you said you already took the first ota?
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
The handset took an OTA (conventionally) then I tried to flash the 4.3/Sense 5.5 OTA which failed a couple of times. I've now managed to flash 4.3/Sense 5.5 so am going to try KK 4.4/Sense 5.5 then KK4.4/Sense 6
My carrier keeps trying to send me 4.2 as a proper OTA for some reason, this is failing as the phone is already on 4.3
I think I am making (slow) progress. The quicker I can get away from stock the better
Hi!
I've spent the last few days trying to restore my M7 to mostly stock.
I had TWRP recovery installed. Relocked the bootloader so I could run the RUU and now have a phone that gets stuck at the bootmenu.
The RUU says I'm using an incompatible RUU for my phone, and trying to push the rom.zip (extracted from the RUU) using adb gives me the following error: remote 02 data length is too large.
The phone is S-On, Relocked and on hboot 1.44.
I attached an image of the bootmenu.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any suggestions? Thanks in advance.
arthurrrr said:
Hi!
I've spent the last few days trying to restore my M7 to mostly stock.
I had TWRP recovery installed. Relocked the bootloader so I could run the RUU and now have a phone that gets stuck at the bootmenu.
The RUU says I'm using an incompatible RUU for my phone, and trying to push the rom.zip (extracted from the RUU) using adb gives me the following error: remote 02 data length is too large.
The phone is S-On, Relocked and on hboot 1.44.
I attached an image of the bootmenu.
Any suggestions? Thanks in advance.
Click to expand...
Click to collapse
If your trying to go back to 100% Stock you need the device to be s-off, if you just want Stock Software that should be achievable. Please can you post the output from command
Code:
fastboot getvar all
Please remove imei and serial numbers before posting. Your on hboot 1.44 so the chances of finding an RUU are good depending on your cid, mid and version main.
Your device won't boot because you have relocked your bootloader, you can't boot a custom Rom or recovery while relocked.
You will need it to be relocked to run an RUU though so you may aswell leave it that way until we know if there is an RUU you can use or not. If not you will need to unlock to flash a stock Rom.
Danny201281 said:
If your trying to go back to 100% Stock you need the device to be s-off, if you just want Stock Software that should be achievable. Please can you post the output from command
Code:
fastboot getvar all
Please remove imei and serial numbers before posting. Your on hboot 1.44 so the chances of finding an RUU are good depending on your cid, mid and version main.
Your device won't boot because you have relocked your bootloader, you can't boot a custom Rom or recovery while relocked.
You will need it to be relocked to run an RUU though so you may aswell leave it that way until we know if there is an RUU you can use or not. If not you will need to unlock to flash a stock Rom.
Click to expand...
Click to collapse
Thanks a lot for your quick reply!
I will give you the output of the getvar command when I get home (at work now).
My cid is HTC__E11 and model id is PN0710000.
The RUU is ran is: RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1.
I believe my version main to be around 1.2 or something (this is wat the RUU installer says i believe?).
I'll give you all the info when I get home.
Thanks again.
arthurrrr said:
Thanks a lot for your quick reply!
I will give you the output of the getvar command when I get home (at work now).
My cid is HTC__E11 and model id is PN0710000.
The RUU is ran is: RUU M7 UL K44 SENSE55 MR HTC Europe 4.19.401.9 R Radio 4A.23.3263.28 10.38r.1157.04L Release 353069 Signed 2-1.
I believe my version main to be around 1.2 or something (this is wat the RUU installer says i believe?).
I'll give you all the info when I get home.
Thanks again.
Click to expand...
Click to collapse
Easy fix that RUU will work for you but you will need to flash a firmware update first. Again this will require you to be relocked so leave it that way.
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/2.24.401.8.zip
http://xda7.androidrevolution.org/db_mirror/Firmware/HTC/HTC_One/401/3.62.401.1.zip
Download these 2 firmware packages and place them in your fastboot folder. Then flash them in RUU mode.
Code:
fastboot oem rebootRUU
--- *case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip 2.24.401.8.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip 2.24.401.8.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Repeat the process for the 3.62.401.1 firmware.
2.24.401.8 first followed by 3.62.401.1. Then run the ruu.exe on your pc while the device is connected to fastboot usb in the bootloader
Danny201281 said:
Easy fix that RUU will work for you but you will need to flash a firmware update first. Again this will require you to
Download these 2 firmware packages and place them in your fastboot folder. Then flash them in RUU mode.
Code:
fastboot oem rebootRUU
--- *case sensitive ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip 2.24.401.8.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip 2.24.401.8.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Repeat the process for the 3.62.401.1 firmware.
2.24.401.8 first followed by 3.62.401.1. Then run the ruu.exe on your pc while the device is connected to fastboot usb in the bootloader
Click to expand...
Click to collapse
Thanks mate! Looks very promising, going to try it out tonight!
I'll let you know how it worked out
Hi. Before iam gonna create new post I have to ask here .
I have exactly same issue however I am on the latest hboot and firmware
S-ON
My hboot is : 1.57
Firmware : 6.09.401.10
Currently on CyanogenMod 11 but I would like to revert to stock and root my Phone to use XPOSED
thanks in advance
Sent from my One using XDA Free mobile app
arthurrrr said:
Thanks mate! Looks very promising, going to try it out tonight!
I'll let you know how it worked out
Click to expand...
Click to collapse
The reason the RUU failed is to do with HTC, for some reason they decided the kitkat RUU's should only work with hboot 1.55 or 1.56. Flashing those 2 firmwares will bring your device up to hboot 1.55 and the ruu should restore your device to stock with hboot 1.56 Kitkat 4.4.2 Sense 5.5. And you should be able to take ota updates up to the latest firmware and Rom.
If you've ever thought about going s-off it may be better to do it now before updating your firmware though. Once your on the latest firmware there is only one method to achieve s-off and it cost $25.
Where as revone should work for you with hboot 1.44. And it's free to use, But that's your decision to make. :good:
Danny201281 said:
The reason the RUU failed is to do with HTC, for some reason they decided the kitkat RUU's should only work with hboot 1.55 or 1.56. Flashing those 2 firmwares will bring your device up to hboot 1.55 and the ruu should restore your device to stock with hboot 1.56 Kitkat 4.4.2 Sense 5.5. And you should be able to take ota updates up to the latest firmware and Rom.
If you've ever thought about going s-off it may be better to do it now before updating your firmware though. Once your on the latest firmware there is only one method to achieve s-off and it cost $25.
Where as revone should work for you with hboot 1.44. And it's free to use, But that's your decision to make. :good:
Click to expand...
Click to collapse
Thanks, I need S-Off if i want to reset my counter and change Relocked to Locked and get my warranty back right?
Maybe I'll do that before updating the hboot to 1.55. After that, I can just follow the stept above?
Thanks for the heads up.
arthurrrr said:
Thanks, I need S-Off if i want to reset my counter and change Relocked to Locked and get my warranty back right?
Maybe I'll do that before updating the hboot to 1.55. After that, I can just follow the stept above?
Thanks for the heads up.
Click to expand...
Click to collapse
Yes to preserve your warranty you will need s-off to go back to 100% Stock. You should be able to get s-off with this toolkit http://forum.xda-developers.com/showthread.php?t=2364445
I'm not normally a fan of toolkits like this, but this is the easiest way to s-off hboot 1.44 that I know of :good:
Once your s-off you can update without fear of being stuck with s-on or a $25 fee not that I think Sunshine app isn't worth $25 but if you can do it for free now then may as well :good:
Danny201281 said:
Yes to preserve your warranty you will need s-off to go back to 100% Stock. You should be able to get s-off with this toolkit http://forum.xda-developers.com/showthread.php?t=2364445
I'm not normally a fan of toolkits like this, but this is the easiest way to s-off hboot 1.44 that I know of :good:
Once your s-off you can update without fear of being stuck with s-on or a $25 fee not that I think Sunshine app isn't worth $25 but if you can do it for free now then may as well :good:
Click to expand...
Click to collapse
Hmm it seems to be impossible to push revone since it the device doesnt boot up. Can i push and run revone in fastboot?
Edit: managed to find my unlock.bin file from htcdev. Unlocked it again. Device does not boot but i can get to recovery now. However, pushing the file gives the No file or directory error.
arthurrrr said:
Hmm it seems to be impossible to push revone since it the device doesnt boot up. Can i push and run revone in fastboot?
Edit: managed to find my unlock.bin file from htcdev. Unlocked it again. Device does not boot but i can get to recovery now. However, pushing the file gives the No file or directory error.
Click to expand...
Click to collapse
No you need a Rom on the phone to s-off. You can push this reset.zip using a custom recovery. http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Download it and put it in your fastboot folder and rename it rom.zip boot your phone to custom recovery. And push the Rom either with the toolkit or with adb command
Code:
adb push rom.zip /sdcard
Then you should be able to flash the Rom to your phone from recovery.
In the aroma installer choose options.
Stock Recovery = No
Stock radio = yes
Root = yes
Danny201281 said:
No you need a Rom on the phone to s-off. You can push this reset.zip using a custom recovery. http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Download it and put it in your fastboot folder and rename it rom.zip boot your phone to custom recovery. And push the Rom either with the toolkit or with adb command
Code:
adb push rom.zip /sdcard
Then you should be able to flash the Rom to your phone from recovery.
In the aroma installer choose options.
Stock Recovery = No
Stock radio = yes
Root = yes
Click to expand...
Click to collapse
Everything worked out! Really appreciate your time and effort!
Thanks Danny :good:
arthurrrr said:
Everything worked out! Really appreciate your time and effort!
Thanks Danny :good:
Click to expand...
Click to collapse
Your welcome, good to hear you got it sorted :good:
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
sonic_boom said:
Hi. Before iam gonna create new post I have to ask here .
I have exactly same issue however I am on the latest hboot and firmware
S-ON
My hboot is : 1.57
Firmware : 6.09.401.10
Currently on CyanogenMod 11 but I would like to revert to stock and root my Phone to use XPOSED
thanks in advance
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
Unfortunately there is no RUU you can use with s-on. You can flash the Stock Rom from this thread with TWRP. http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
And then flash the Stock Recovery http://d-h.st/6JL
That will get you back to stock and able to receive OTA updates :good:
Danny201281 said:
Your welcome, good to hear you got it sorted :good:
---------- Post added at 10:56 PM ---------- Previous post was at 10:47 PM ----------
Unfortunately there is no RUU you can use with s-on. You can flash the Stock Rom from this thread with TWRP. http://forum.xda-developers.com/htc-one/development/rom-4-4-3-sense-6-6-09-401-5-100-stock-t2854300
And then flash the Stock Recovery http://d-h.st/6JL
That will get you back to stock and able to receive OTA updates :good:
Click to expand...
Click to collapse
MAN you are superStar !! its actually working , just wondering, is there any point to relock my bootloader ? so if i flash stock recovery i should be able to get OTA etc ?
sonic_boom said:
MAN you are superStar !! its actually working , just wondering, is there any point to relock my bootloader ? so if i flash stock recovery i should be able to get OTA etc ?
Click to expand...
Click to collapse
Your Welcome :highfive:
No need to relock your bootloader, That's only for flashing RUU's or Firmware. Just flash the Stock rom and Recovery and your good to go. :good: