I'm new to flash and RUU 's
I'm a little confused, even reading guides .
I would leave my htc one as stock and make updates over the air .
I value help for this.
Currently my OS is ViperOne6.2.1 and my recovery is TRWP 2.6.3.3
--------------
UNLOCKED
S -OFF
--------------
> fastboot getvar all
( bootloader ) version: 0.5
( bootloader ) version- bootloader : 1.56.0000
( bootloader ) version- baseband : 4A.23.3263.28
( bootloader ) version- cpld : None
( bootloader ) version- microp : None
( bootloader ) version- main: 4.20.707.7
( bootloader ) version- misc : PVT SHIP S -OFF
( bootloader ) SerialNo : xxxxxxxxxxxxx
( bootloader ) imei : xxxxxxxxxxxxxx
( bootloader ) meid : 00000000000000
( bootloader ) product : m7_u
( bootloader ) platform: HBOOT - 8064
( bootloader ) modelid : PN0711000
( bootloader ) cidnum : HTC__044
( bootloader ) battery- status : good
( bootloader ) battery- voltage : 3790mV
( bootloader ) partition - layout : Generic
( bootloader ) security : off
( bootloader ) build -mode : SHIP
( bootloader ) boot -mode: fastboot
( bootloader ) commitno - bootloader : dirty - 59adc32b
( bootloader ) hbootpreupdate : 11
( bootloader ) gencheckpt : 0
I downloaded the
"RUU Zip M7_U_JB_50_hTC_Asia_WWE_1.29.707.4_R_Radio_4A.14.3250.13_10.33.1150.01_release_312087_signed_2_4_decrypted.zip"
and
"Guru_Reset_M7_3.63.707.4.zip"
but not sure if that's correct.
And now , what are the specific steps for my case ?
I really appreciate any help
Thank you!
Site is back up now, look for your rom, you want to look for ?.??.707.?
you will need to look for stock rom guru reset roms, yours is in this list, make sure MID and CID etc match first, also check the file size, although the site is working, im still having problems downloading a file from the site, it says its finished and should be 780mb but is only downloading 45mb
http://www.htc1guru.com/downloads/stock-rom-downloads/
The details are:
Guru Reset M7 3.63.707.4
File Size: 1.1 GiB - Downloads: 27498
MD5: 6aba67e56889124c4ab5188bba15a569
Comments: Stock Asia/India (World Wide English) ROM 3.63.707.4 with graphical aroma installer. Includes the ability to flash the Stock Recovery and also Stock Radio.
Future OTA Updates will work when available.
modelid: PN0711000
modelid: PN0714000
cidnum: HTC__044
cidnum: HTC__038
Copy the file to your phone, easiest way is to rename it to rom.zip, and then flash it in recovery as you would do with any other rom, if you want your phone to be completely stock then select flash radio and recovery in the installer.
Seanie280672 said:
Site is back up now, look for your rom, you want to look for ?.??.707.?
you will need to look for stock rom guru reset roms, yours is in this list, make sure MID and CID etc match first, also check the file size, although the site is working, im still having problems downloading a file from the site, it says its finished and should be 780mb but is only downloading 45mb
http://www.htc1guru.com/downloads/stock-rom-downloads/
The details are:
Guru Reset M7 3.63.707.4
File Size: 1.1 GiB - Downloads: 27498
MD5: 6aba67e56889124c4ab5188bba15a569
Comments: Stock Asia/India (World Wide English) ROM 3.63.707.4 with graphical aroma installer. Includes the ability to flash the Stock Recovery and also Stock Radio.
Future OTA Updates will work when available.
modelid: PN0711000
modelid: PN0714000
cidnum: HTC__044
cidnum: HTC__038
Copy the file to your phone, easiest way is to rename it to rom.zip, and then flash it in recovery as you would do with any other rom, if you want your phone to be completely stock then select flash radio and recovery in the installer.
Click to expand...
Click to collapse
Good afternoon, Seannie!
I did exactly as mandated by the rules.
The phone was relocked and as "Not Tampered". Without the superuser.
When I tried to update it over the air, accused the phone that I'm using a modified version and can not update the system. = [
andrekerplunk said:
Good afternoon, Seannie!
I did exactly as mandated by the rules.
The phone was relocked and as "Not Tampered". Without the superuser.
When I tried to update it over the air, accused the phone that I'm using a modified version and can not update the system. = [
Click to expand...
Click to collapse
Did you flash the stock recovery when you installed the ROM ? there should of been 2 tick boxes, 1 says flash stock radio and the other says flash stock recovery just before the rom installs, I selected both when I ran it.
Seanie280672 said:
Did you flash the stock recovery when you installed the ROM ? there should of been 2 tick boxes, 1 says flash stock radio and the other says flash stock recovery just before the rom installs, I selected both when I ran it.
Click to expand...
Click to collapse
Yes, I marked them both! And...
you could try this, when you download the OTA, select install later, then plug you phone into your computer, and find the OTA on your internal storage, its just a zip file, open it with something like WinRAR and look for Firmware.zip, open that and extract recovery.img, you will see other things in there too like HBOOT etc, just ignore those, you only want the recovery for now.
Place the recovery that you just extracted into your fastboot folder and reboot your phone to fastboot mode, then flash it:
fastboot flash recovery recovery.img
It may be that the rom you flashed just has an out of date recovery in it and needs updating.
Once your phone is back on, check for updates again and see if it will install.
The trouble with OTAs is everything must be the same, if anything is disabled or missing that the OTA wants to update then it will fail, most of the time its down to an out of date recovery.
---------- Post added at 08:06 PM ---------- Previous post was at 07:19 PM ----------
You could always try manually updating if the above fails, link below is for the OTA, and the instruction on how to install it are at the top of the page.
OTA M7 U K44 SENSE55 MR HTC Asia WWE 4.20.707.7-3.63.707.4 Release 350432vv58wn1jy1a88n9h
Download
http://www.htc1guru.com/dld/ota_m7_...-63-707-4_release_350432vv58wn1jy1a88n9h-zip/
Instructions at the top of the page here:
http://www.htc1guru.com/downloads/ota-downloads/
The first set of numbers is what your rom will be updated too: 4.20.707.7
The second set of numbers is the rom version you are currently running: 3.63.707.4
K44 SENSE55 this bit means you will get KitKat 4.4 with Sense 5.5
Seanie280672 said:
you could try this, when you download the OTA, select install later, then plug you phone into your computer, and find the OTA on your internal storage, its just a zip file, open it with something like WinRAR and look for Firmware.zip, open that and extract recovery.img, you will see other things in there too like HBOOT etc, just ignore those, you only want the recovery for now.
Place the recovery that you just extracted into your fastboot folder and reboot your phone to fastboot mode, then flash it:
fastboot flash recovery recovery.img
It may be that the rom you flashed just has an out of date recovery in it and needs updating.
Once your phone is back on, check for updates again and see if it will install.
The trouble with OTAs is everything must be the same, if anything is disabled or missing that the OTA wants to update then it will fail, most of the time its down to an out of date recovery.
---------- Post added at 08:06 PM ---------- Previous post was at 07:19 PM ----------
You could always try manually updating if the above fails, link below is for the OTA, and the instruction on how to install it are at the top of the page.
OTA M7 U K44 SENSE55 MR HTC Asia WWE 4.20.707.7-3.63.707.4 Release 350432vv58wn1jy1a88n9h
Download
http://www.htc1guru.com/dld/ota_m7_...-63-707-4_release_350432vv58wn1jy1a88n9h-zip/
Instructions at the top of the page here:
http://www.htc1guru.com/downloads/ota-downloads/
The first set of numbers is what your rom will be updated too: 4.20.707.7
The second set of numbers is the rom version you are currently running: 3.63.707.4
K44 SENSE55 this bit means you will get KitKat 4.4 with Sense 5.5
Click to expand...
Click to collapse
With this "Guru_Reset_M7_3.63.707.4" my software number is 3.63.707.3 not 3.63.707.4
Should I try anyway?
andrekerplunk said:
With this "Guru_Reset_M7_3.63.707.4" my software number is 3.63.707.3 not 3.63.707.4
Should I try anyway?
Click to expand...
Click to collapse
That's strange ????, you are s-off right ?
That's probably the mis-match you are getting.
Seanie280672 said:
That's strange ????, you are s-off right ?
That's probably the mis-match you are getting.
Click to expand...
Click to collapse
Yes, I'm s-off
Also found it strange when downloading something and another appears.
Now I do not know what to do, since I have not the correct stock file.
3.63.707.3 = M7_UL (4g)
3.63.707.4 = M7_U (Non 4G)
Is your phone the 4g version or the non 4g version ? your output in the first post says non 4g (M7_U), but im wondering if at some point you changed your firmware to do that, don't want you flashing the 4g firmware if you don't have the 4g phone, it may brick it.
Seanie280672 said:
3.63.707.3 = M7_UL (4g)
3.63.707.4 = M7_U (Non 4G)
Click to expand...
Click to collapse
i'm M7U but guruRESET send me a wrong. I don't understand. And Now? =T
andrekerplunk said:
i'm M7U but guruRESET send me a wrong. I don't understand. And Now? =T
Click to expand...
Click to collapse
Yes, lots of people having the same problem in India, here is how to fix it: http://forum.xda-developers.com/showthread.php?t=2669217
Post 5 has the answer, you will have to download the RUU zip they linked and flash that instead, its for your MID and CID, I already checked, you will probably have to put TWRP recovery back on your phone first to flash that zip, you should get working OTA's then, but if you don't then refer to post 8 and what he did to get OTA's
Seanie280672 said:
Yes, lots of people having the same problem in India, here is how to fix it: http://forum.xda-developers.com/showthread.php?t=2669217
Post 5 has the answer, you will have to download the RUU zip they linked and flash that instead, its for your MID and CID, I already checked, you will probably have to put TWRP recovery back on your phone first to flash that zip, you should get working OTA's then, but if you don't then refer to post 8 and what he did to get OTA's
Click to expand...
Click to collapse
And how I install this rom 'RUU Zip M7_U_JB_50_hTC_Asia_WWE_1.29.707.4_R_Radio_4A.14.3250.13_10.33.1150.01_release_312087_signed_2_4_decrypted.zip"
Now I do not have TWRP, my bootloader say LOCK, s-off, hboot 1:44
Can you guide me?
andrekerplunk said:
And how I install this rom 'RUU Zip M7_U_JB_50_hTC_Asia_WWE_1.29.707.4_R_Radio_4A.14.3250.13_10.33.1150.01_release_312087_signed_2_4_decrypted.zip"
Now I do not have TWRP, my bootloader say LOCK, s-off, hboot 1:44
Can you guide me?
Click to expand...
Click to collapse
It shouldn't matter that your bootloader is locked as you are s-off.
Just download TWRP, put your phone in fastboot mode and then fastboot flash recovery (filename).zip to flash the new recovery, then transfer the rom RUU zip to your phone and flash it in recovery as normal.
Seanie280672 said:
It shouldn't matter that your bootloader is locked as you are s-off.
Just download TWRP, put your phone in fastboot mode and then fastboot flash recovery (filename).zip to flash the new recovery, then transfer the rom RUU zip to your phone and flash it in recovery as normal.
Click to expand...
Click to collapse
where I download TRWP
andrekerplunk said:
where I download TRWP
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/m7
Download 2.6.3.3 then put it in your fastboot folder on your computer and rename it to recovery.img for ease later on
Reboot your phone into fastboot mode
Then plug into your computer, it should now say fastbootUSB on your phone
Then open command promt, easiest way is inside your fastboot folder on your computer, hold control + shift + right mouse click and select open command window here
then type fastboot flash recovery recovery.img and press enter (it only take a few seconds)
reboot your phone and copy the rom RUU zip to the phone storage
When finished, uplug your phone from the computer and boot to recovery
select wipe first and swipe to factory reset
then select install and choose the rom RUU zip in the list, swipe to begin the install.
Seanie280672 said:
http://techerrata.com/browse/twrp2/m7
Download 2.6.3.3 then put it in your fastboot folder on your computer and rename it to recovery.img for ease later on
Reboot your phone into fastboot mode
Then plug into your computer, it should now say fastbootUSB on your phone
Then open command promt, easiest way is inside your fastboot folder on your computer, hold control + shift + right mouse click and select open command window here
then type fastboot flash recovery recovery.img and press enter (it only take a few seconds)
reboot your phone and copy the rom RUU zip to the phone storage
When finished, uplug your phone from the computer and boot to recovery
select wipe first and swipe to factory reset
then select install and choose the rom RUU zip in the list, swipe to begin the install.
Click to expand...
Click to collapse
ok...but...
"Updating partition details...
Formatting Cache using make_ext4fs function
Wiping data without wiping /data/media...
Done.
Updating partition details...
Installing '/sdcard/ruuasia.zip'...
Cheching for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip '/sdcard/ruuasia.zip'
Updating partition details...
Failed"
oh pants, I was hoping we wouldn't have to do it this way, its a bit more complicated, put your phone in fastboot mode and put rom RUU.zip in your fastboot folder on your computer and open a command promt.
From fastboot you need to first re-lock your bootloader
fastboot oem lock
Once locked it will boot back into bootloader
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip (filename).zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
Make sure device is still in ruu mode(black HTC screen).
now simply reflash the rom.zip
fastboot flash zip (filename).zip
Let it run and it should finish this time
It will reboot to a fully stock build.
just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
---------- Post added at 11:28 PM ---------- Previous post was at 11:00 PM ----------
I have to go offline now, but i'll check up on you in the morning, but this should work for you now as long as you follow those instructions.
Seanie280672 said:
oh pants, I was hoping we wouldn't have to do it this way, its a bit more complicated, put your phone in fastboot mode and put rom RUU.zip in your fastboot folder on your computer and open a command promt.
From fastboot you need to first re-lock your bootloader
fastboot oem lock
Once locked it will boot back into bootloader
fastboot oem rebootRUU
Now your booted to the black HTC screen. Make sure your Rom.zip file is in your adb/fastboot folder
fastboot flash zip (filename).zip
This takes a couple minutes and you will most likely get a error
(pre-hboot update: please flush immediately)
Make sure device is still in ruu mode(black HTC screen).
now simply reflash the rom.zip
fastboot flash zip (filename).zip
Let it run and it should finish this time
It will reboot to a fully stock build.
just remember, anytime you get a "flush immediately" error, just make sure your still in ruu mode and reflash the zip.
---------- Post added at 11:28 PM ---------- Previous post was at 11:00 PM ----------
I have to go offline now, but i'll check up on you in the morning, but this should work for you now as long as you follow those instructions.
Click to expand...
Click to collapse
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]WP,rcdata,0
(bootloader) ...... Successful
OKAY [218.237s]
finished. total time: 257.516s
thats ok...but the green line not complete in phone!
What do I do?
when its finished it should reboot itself, but I did read somewhere that the progress bar doesn't reach the top, just leave it to do its thing, but looks good so far, its working, you should get OTA's now and matching firmware, if the OTA's don't work have a look at post 8 in that thread I linked earlier on how to fix it.
Related
This guide is for Canadian HTC One Bell Rogers Telus users who need to go back to stock firmware for warranty after flashing custom recovery/rom. If you have installed Open EU, Google, Dev, ATT, or any other kind of RUU, see post #2.
Requirements:
1. Your HBOOT is 1.55.
2. You received OTA to JB 4.3 from Rogers Bell Telus
3. Your main version is 3.x.661.x, 3.x.666.x, 3.x.631.x,
4. Some working knowledge of ADB/Fastboot.
Steps to restore stock:
1. Download your respective nandroid backup from below:
Rogers Nandroid: Stock_JB_4.3_ROGER001_TWRP_3.22.631.1.zip - http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-roger001-3-22-631-1-zip/
Bell Nandroid: Stock_JB_4.3_BM___001_TWRP_3.23.666.1.zip - http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-bm___001-3-23-666-1-zip/
Telus Nandroid: Stock_JB_4.3_TELUS001_TWRP_3.22.661.1.zip - http://goo.gl/sYoqei
Telus RUU ZIP: http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Run fastboot oem rebootRUU.
Then, flash the RUU with the command fastboot flash zip filename
Click to expand...
Click to collapse
2. Download latest TWRP from: http://techerrata.com/browse/twrp2/m7
3. Reboot your device in fastboot and flash TWRP recovery. I used 2.6.3.0.
4. Reboot into recovery and do a backup of what you have working now (very important)
5. Boot back into OS
6. Unzip the nandroid backup folder and copy it to your \\SDCARD\TWRP\BACKUPS\######\somefolder\
7. Reboot back into TWRP, and restore the nandroid file
8. Reboot, your phone should be booting into your carrier firmware
9. Root
10. S-Off: Rumrunner thread, link: http://forum.xda-developers.com/showthread.php?t=2488772
11. Verify all is WORKING OK, then flash stock recovery, Link: http://goo.gl/2Kntxz
12. Remove *Tempered* from boot thread, link: http://forum.xda-developers.com/showthread.php?t=2477792
13. Unroot from SuperSU app.
14. S-On if you must, highly NOT suggested. command: fastboot oem writesecureflag 3
15. All should be good now.
Click to expand...
Click to collapse
** I am working from theory, and NOT actual experience with this **
Guide for HBOOT 1.44 (4.1.2) & those on DEV/GPE/ATT/INTL RUU based firmwares
Bell: 1.29.666.5 - http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
Rogers: 1.29.631.4 - http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-roger001-1-29-631-4-2013-06-03-zip/
Telus: 1.29.661.5 - http://www.htc1guru.com/dld/m7-twrp-nandroid-backup-cid-telus001-1-29-661-5-rar/
Stock Recovery for 1.44 HBOOT: http://goo.gl/Yzkwtl
1.44 HBOOT (S-Off required): http://d-h.st/qfc
Assumptions:
1. You have S-Off
2. You have 1.44 HBOOT
3. You know how to use fastboot/adb commands.
Steps to revert to 4.1.2 HTC One:
1. Install earliest possible RUU for Dev edition.. 1.29.1540.3 http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb_50_brightstarus_wwe_1-29-1540-3-zip/
Make sure your CID is 11111111 and MID is PN0712000.
1a. If it fails to install, install the 1.44 HBOOT from above: fastboot flash zip hboot.zip and then re-flash the DEV zip file as fastboot flash zip devruu.zip
2. Install recovery. CWM for Bell & Rogers, TWRP for Telus. Do a backup from custom recovery (mostly to generate a backup path to use in step 4)
3. Reboot back into OS
4. Unzip the nandroid backup folder and copy it to your \\SDCARD\TWRP\BACKUPS\######\somefolder\ or \\data\media\clockworkmod\ .... (I am hazy on the path detail for CWM) You may need to use ES File Explorer to move the folder around if cwm is using 0\clockworkmod folder.
5. Reboot into recovery, select restore, and restore the nandroid file.
6. You should be booting into the earliest HTC OS for Rogers, Bell, Telus. (Your fastboot getvar all will still say 1.29.1540.3, this will change after an OTA)
7. Change your CID to Rogers001, BM___001, or TELUS001 accordingly in fastboot.
8. If you are rooted, either unroot supersu, or flash this file unroot-flashable.zip from recovery: http://goo.gl/JBmJVQ
9. Install stock recovery from fastboot http://goo.gl/Yzkwtl. Do a factory reset to verify that recovery has installed. You should NOT see CWM or TWRP during reset process.
10. Reboot back into OS and check for OTA, your OTA should come through and install itself, your fastboot getvar all should now result in the correct 1.29.x.17 main version.
11. At this time, you are stock, with S-Off and unlocked bootloader. If you want to continue further to lock bootloader and S-ON, start from step 9 in post 1.
Click to expand...
Click to collapse
Miscellaneous tips and tricks:
If you can NOT mount /sdcard in recovery
Download your Non-Canadian recoveries from: http://d-h.st/users/guich/?fld_id=29380#files or http://forum.xda-developers.com/showthread.php?t=2545227
Download Canadian 1.55 HBOOT recovery: http://goo.gl/2Kntxz
Make sure you're in the bootloader go into fastboot and make sure the downloaded image is in the same folder as your fastboot.
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot-bootloader
Go into bootloader and then choose Factory Reset - let that finish running <<< Important!
Phone will go out and start bootlooping. Now power off and go back to bootloader mode:
Go into fastboot
fastboot flash recovery <custom recovery>.img
fastboot erase cache
fastboot reboot-bootloader
Now you can go into custom recovery and you should be good to go now.
Click to expand...
Click to collapse
Radio/Modem files
Radio for Bell/Rogers/Telus for 3.x.x.x firmware (hboot 1.55): http://forum.xda-developers.com/showpost.php?p=46513020&postcount=12 - Tested
Radio fro Bell/Rogers/Telus for 1.x.x.x firmware (hboot 1.44): http://forum.xda-developers.com/showpost.php?p=45360195&postcount=5 - Not Tested
Click to expand...
Click to collapse
Thanks for the help! was looking for the nandroid back ups. will check back when you have the 1.44 written up. Is there a way i can upgrade my hboot to 1.55 from 1.44 in order to use the nandroid in post 1. If load the 1.29 nandroid my touch screen wont work and i need to go buy a otg cable in order to accept whats on the screen.
Thank You so much!!
I've been searching for the ROGERS RUU or Nandroid all day, new to Android so I didn't think of making a "nandroid" backup before flashing ROMs, but you saved me mate
Cheers!
Rogers htc one stuck on fastboot screen
Rogers htc one stuck on fastboot screen.
What have you tried so far? How did it get stuck?
Stuck on fastboot
SaHiLzZ said:
What have you tried so far? How did it get stuck?
Click to expand...
Click to collapse
Before following your instructions today, i relocked the bootloader and tried few exe and zip ruu yesterday. After that its stuck on fastboot screen.
What's the output of fastboot getvar all ?
SaHiLzZ said:
What's the output of fastboot getvar all ?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.631.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3983mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
1. Unlock boot loader and download rogers nandroid and unzip.
2. Flash TWRP
3. Boot into TWRP
4. Run a fake backup. If it fails.. Got a SD card issue, let me know so I can guide you through it.
5. On computer type adb devices. Should come back with device in recovery mode
6. AD
6. Adb shell, then CD SDCARD, CD TWRP, CD BACKUP, note the path
7. Adb push rogersback \SDCARD\TWRP\BACKUPS\######\somefolder
Rogers Htc One stock rom
Thanks Sahilzz, I fixed it. Everything is back to normal. I was able to bring it back to stock rom.
Thanks a lot.
how do I install CWM I have twrp recovery. When I tried to install it. It said on CMD, but the phone keeps rebooting
Retry. Sometimes it takes a few tries for recovery to stick. Are you following post #2?
What's your fastboot getvar all output?
HELP! Blue screen, can't get past bootloader
I tried installing an OTA update that came through and now I am stuck on a blue screen. I can get to bootloader and fastboot but nothing I do can get past that. I want to return to stock or even just flash another ROM but I can't as my computer won't recognize the phone either. My HTC One is unlocked, S-On, TWRP recovery and HBOOT 1.44 . I've tried doing a fastboot getvar all but as I said, the computer won't recognize the phone so command prompt just sits there.
Move to a windows 7 machine and retry. Can't help if fastboot/adb doesn't work
SaHiLzZ said:
This guide is for Canadian HTC One Bell Rogers Telus users who need to go back to stock firmware for warranty after flashing custom recovery/rom. If you have installed Open EU, Google, Dev, ATT, or any other kind of RUU, see post #2.
Requirements:
1. Your HBOOT is 1.55.
2. You received OTA to JB 4.3 from Rogers Bell Telus
3. Your main version is 3.x.661.x, 3.x.666.x, 3.x.631.x,
4. Some working knowledge of ADB/Fastboot.
Steps to restore stock:
1. Download your respective nandroid backup from below:
Rogers Nandroid: Stock_JB_4.3_ROGER001_TWRP_3.22.631.1.zip - http://goo.gl/7702AM
Bell Nandroid: Stock_JB_4.3_BM___001_TWRP_3.23.666.1.zip - http://goo.gl/hw7Bj7
Telus Nandroid: Missing..
2. Download latest TWRP from: http://techerrata.com/browse/twrp2/m7
3. Reboot your device in fastboot and flash TWRP recovery. I used 2.6.3.0.
4. Reboot into recovery and do a backup of what you have working now (very important)
5. Boot back into OS
6. Unzip the nandroid backup folder and copy it to your \\SDCARD\TWRP\BACKUPS\######\somefolder\
7. Reboot back into TWRP, and restore the nandroid file
8. Reboot, your phone should be booting into your carrier firmware
9. Root
10. S-Off: Rumrunner thread, link: http://forum.xda-developers.com/showthread.php?t=2488772
11. Remove *Tempered* from boot thread, link: http://www.htc1guru.com/guides/guru-bootloader-reset/ OR http://forum.xda-developers.com/showthread.php?t=2477792
12. Verify all is WORKING OK, then flash stock recovery, Link: http://goo.gl/2Kntxz
13. S-On if you must, highly NOT suggested. command: fastboot oem writesecureflag 3
14. All should be good now.
Click to expand...
Click to collapse
Noob here
Step 9 says root.....what do you mean bu it?
Thanks
Install custom recovery, and root...
SaHiLzZ said:
Install custom recovery, and root...
Click to expand...
Click to collapse
Thanks......when should i relock bootloader?
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
ClydeWinux said:
Hey guys I badly need help!!! I was able to convert my HTC One GSM to Google Edition just last week, but today I want to restore it to its factory ROM so I can also restore the warranty. Now the problem became visible when I tried to flash a stock ROM (not the GPE ROM). Listed below are the problems I am facing at the moment:
1. Stuck in FASTBOOT USB, and cannot boot to ROM.
2. Can't boot to recovery. Everytime I highlight and select recovery the phone just shows up the "Google" logo, then vibrates, then back fastboot USB.
3. Factory Reset not working, again shows up "Google" then restarts to fastboot usb mode.
4. I ran cmd in sdk-tools, typed in "fastboot devices", and my phone is detected. But when I type "adb devices", my phone is not listed.
5. I tried flashing CWM or TWRP through fastboot in cmd but the reply is"remote: signature verify fail", as wellas flashing a RUU for my device.
6. On bootloader is written:
*** TAMPERED ***
*** RELOCKED ***
M7_UK PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.33250.14
OpenDSP-v30.120.3274.0520
OS-2.14.1700.15
eMMC-boot 2048MB
Guys I really badly need help to fix my phone. I don't wanna spend for repairs or throw it in the garbage. I am very sure there's a way to fix this and get it to work, but I am rookie in android as I've been an iOs user for a couple of years.
Click to expand...
Click to collapse
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Harish_Kumar said:
try flashing the appropriate firmware files for an particular RUU before flashing RUU n check?
Click to expand...
Click to collapse
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
ClydeWinux said:
Yes I have tried flashing the appropriate RUU file but in CMD it returns "remote: signature verify fail"
Click to expand...
Click to collapse
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Harish_Kumar said:
not RUU...i am talking about firmware files
for instance if you are about to flash an 4.3 sense 3.22 rom..flash its firmware in RUU mode before flashing the actual RUU
Click to expand...
Click to collapse
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
ClydeWinux said:
Oh my, are the firmware files included inside the RUU.zip? or should I download the firmware files separately? @Harish_Kumar
Click to expand...
Click to collapse
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Harish_Kumar said:
RUU Zip will be encrypted..you cant extract files from it
you have to download firmware files seperately...you can find them in android development section
check here -> http://forum.xda-developers.com/showthread.php?t=2182823
I almost forgot... you should be S-off in order to flash the firmware
and even RUU Flashing requires S-off
Click to expand...
Click to collapse
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
ClydeWinux said:
Ok I have flashed the firmware for my phone and now it's on 3.58.1700.5. Should I download a RUU.zip version 3.58.1700.5 and flash it on my phone? because until now I can't flash CWM or TWRP. @Harish_Kumar
Click to expand...
Click to collapse
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
56562336461
Harish_Kumar said:
arent you able to flash custom recovery like CWM or TWRP even after flashing firmware files? if everything's right you should be able to
Click to expand...
Click to collapse
Everytime I tried to flash custom recovery (CWM/TWRP) in cmd it returns "remote: signature verify fail", I used command "fastboot flash recovery cwm.img". And now I tried to load up recovery from menu, and it's stuck on a 'dead-android-icon-with-exclamation-error' logo. @Harish_Kumar
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode and in RUU mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
awer25 said:
Hi All,
I'm a noob when it comes to this stuff, but I've learned a lot over the last day. I soft bricked my HTC One Developer Edition while trying to do the most recent OTA update to 4.4.
What happens:
When booting normally, it goes initially to the normal white HTC screen, then to a "pink" screen (it's mostly pink, but it's really just messed up graphics), then goes to the HTC One loading screen (except BEATS is blue instead of red). Then it just freezes on that loading screen.
I can boot into the bootloader and recovery (currently TWRP, but was stock when doing the OTA update)
What I've tried:
I've used Fastboot to flash TWRP, so that part is good. Within TWRP, I've wiped the cache, system, Dalvik.
I've tried using Fastboot to flash the RUU Zip file (first one in the list here) in both Windows and OSX, while in "FASTBOOT USB" mode. Each time, it starts sending, but around 43-44 secs it fails with "remote:not allowed: For reference, the top of the bootloader screen says TAMPERED, then UNLOCKED. I'm running HBOOT 1.55 and have S-ON (but unlocked bootloader). OS shows 3.22.1540.1
I can't get past the remote:not allowed issue, and I'm not such an expert to know what to try next. Can anyone please give me some tips on what to do next? I've tried searching, but I don't know what exactly to search for.
Thank you all!
Click to expand...
Click to collapse
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
alray said:
Please post the output of ''fastboot getvar all'' minus your IMEI and serial no. And please post the commands your were using to flash the ruu.zip or a screenshot of your command prompt
Click to expand...
Click to collapse
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
Click to expand...
Click to collapse
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
awer25 said:
Thanks! The command prompt was fastboot flash zip rom.zip (I renamed it to that). For TWRP it was fastboot flash recovery recovery.img
GETVAR is attached.
EDIT: I added the command prompt and fail as well.
Click to expand...
Click to collapse
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on. Whit s-on you can only flash signed ruu.
and btw did you enter ruu mode before ''fastboot flash zip rom.zip'' ?
Thank you for that explanation. I got into RUU mode by doing fastboot oem rebootRUU, which took me to a black screen with silver HTC. That may not be RUU mode...I'm just guessing.
---------- Post added at 07:52 PM ---------- Previous post was at 07:51 PM ----------
There is a 3.22.1540.1 RUU.exe on htcdev.com you could use to restore your phone. But it will not work using windows 8.1. what is your computer OS?
edit: Wait, there is also a 3.22.1540.1 ruu.zip on htcdev.com so try it first.
fastboot oem rebootRUU
fastboot flash zip <name_of_file>.zip
fastboot flash zip <name_of_file>.zip
fastboot reboot
Click to expand...
Click to collapse
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
awer25 said:
Amazing! Thanks - I'll try this and let you know how it goes. I have Windows 8.1, but with fastboot and a zip file it should work, right? If not, I have a Windows 7 laptop at home.
Click to expand...
Click to collapse
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
alray said:
yes ruu.zip should work flawlessly with windows 8.1. but do not attempt the ruu.exe with 8.1, will work fine on 7.
Click to expand...
Click to collapse
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
awer25 said:
I saw that I already had the 3.22.1540.1 zip file on my computer, so I tried. It got a lot further, but still failed with a remote:not allowed (see attached pic).
My next tries will be to re-download the file and try again, and if that fails, to try the RUU.exe file on the Windows 7 laptop. Is this correct, or is there something else I should try?
I'm leaving work now, so I won't be able to answer for another hour or so but thank you for your help thus far!
Click to expand...
Click to collapse
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
alray said:
ok, first you can't flash that ruu you linked above (first in the list) because its a decrypted ruu. Decrypted ruu.zip require s-off and you are s-on.
Click to expand...
Click to collapse
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
alray said:
the ruu you have from the link you posted above is DECRYPTED it will not work with s-on!!!
And does the phone was in ruu mode? I don't see any ''fastboot oem rebootRUU'' from your screenshot...
Click to expand...
Click to collapse
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
awer25 said:
Sorry I didn't explain better - the file I meant was the one from HTCDevs - I downloaded it a while ago when I had a different issue. I just renamed it to rom1 or whatever. Is this then the correct file?
Also, the phone was not in RUU mode - it was in regular fastboot mode ("FASTBOOT USB"). I'll try again in RUU mode.
Click to expand...
Click to collapse
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
alray said:
you can not flash ruu with fastboot. you MUST reboot phone in ruu mode using ''fastboot oem rebootRUU'' it will then reboot with a black screen and the htc logo. so:
Code:
fastboot oem rebootRUU
fastboot flash zip name_of_ruu.zip
fastboot flash zip name_of_ruu.zip <------ yes again!
fastboot reboot
When in ruu mode you'll have a screen similar to this:
then proceed with ''fastboot flash zip...................''
Click to expand...
Click to collapse
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
awer25 said:
Ok, I booted into RUU mode and flashed the file twice as per your instructions. Both times it failed. Screenshot is attached. (I even tried it a 3rd time but it still failed with the same message)
Also, I renamed the zip file to rom1.zip just to make typing it easier, but it is the file from HTCDevs, "3.22.1540.1 Developer Edition", Zip (not RUU).
Thank you!
Click to expand...
Click to collapse
Try the ruu.exe on windows 7.
alray said:
Try the ruu.exe on windows 7.
Click to expand...
Click to collapse
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
awer25 said:
Ok, I tried it on the Windows 7 laptop and got another error (155 - unknown error). Pic is attached. It was in RUU mode btw.
I'm currently downloading the older 1.29.xx version (Android 4.1) and will try again with that.
Just for my own knowledge - how many "parts" (partitions?) of the system are there? As in, there's the recovery partition, the "main" ROM, etc. Are those the only two? I only ask because I wonder if I messed up something in another part that makes the phone think it's not the Developer Edition? (the errors seem to point to using the wrong image, but I got it directly from HTCDevs and have now tried both the RUU and Zip versions.
Click to expand...
Click to collapse
I got it! I had to relock my bootloader for some reason. Then, the Windows RUU installed fine.
Thank you alray for your help!
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
-marco- said:
Is being stuck at the booting screen (Htc one with beats audio (red color)) same as this scenario ? Is it soft bricked or boot looped or what's it called?
I'm S-off, rooted, stock rom, hboot is 1.56 w/ CWM. At some point the phone just rebooted on its own (I was even in a different place at that time!!!) and got stuck forever at that screen. Rebooting would just make it get stuck there again. bootloader, custom recovery all work.
what do?
Click to expand...
Click to collapse
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
awer25 said:
Mine did get stuck there, but after a weird messed up pink screen (and the Beats text was blue, not red for some reason). If I was in your boat, I'd just flash a fresh rom and be done.
Click to expand...
Click to collapse
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3867mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s
-marco- said:
thanks !
but which one? And how?
also getvar !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
finished. total time: 0.066s
Click to expand...
Click to collapse
-marco- said:
I am at work in the office and at some point I look at my phone and I see it rebooted on its own. now it's stuck forever on the HTC one beats audio loading screen.
I didn't even touch anything before. Tried to reboot but it just gets stuck there.
Click to expand...
Click to collapse
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
nkk71 said:
1- Please also post a screenshot of bootloader.
2- So you're on completely stock ROM?
3- are you able to enter recovery?
4- have you simply tried "fastboot erase cache" and tried booting?
Click to expand...
Click to collapse
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
-marco- said:
Thanks man!
Let's get this started:
1- done, see attached.
2- yes, up to latest OTA but i was rooted.
3- yes , CWM
4- done, still gets stuck at the same screen.
now: million $ question - is there a way to get out of this stupid problem without having to lose any data at all ? one gets quite sick at having to wipe and restore backups everytime there's a booting problem with the phone. i remember with the SGS2 i just had to reflash with odin the rom i was using and boom, back in order!
Click to expand...
Click to collapse
Well first I would recommend you update recovery to TWRP
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
since they are more compatible when flashing 4.4 ROMs (make sure to check MD5 on the files, that site doesn't play nice with download managers!)
Code:
[B]fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader[/B]
-> enter recovery
Second, in TWRP, make a nandroid backup, you may need it later *** (please check below)
Third, put a ROM on the phone (in custom recovery):
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HT34xxxxxxxx recovery <- you need to be in recovery
[B]adb push <name of rom>.zip /sdcard/[/B] <- this will take about 5 mins without any progress
and install the ROM, don't select WIPE during installation, and you should have your million $ question solved... all apps, data, etc should be there, but if you get apps crashing it's because of the "dirty-flash"
As to which ROMs you can use for the above procedure, there's is a 100% stock version of 4.19.401.9 here: http://forum.xda-developers.com/showthread.php?t=2224752
I'm personally using ARHD 52.0 from here: http://forum.xda-developers.com/showthread.php?t=2183023 (stock but with improvements, and rooted)
I haven't checked if there's a 100% stock 4.20.707.6 ROM around, so you could do some googling and see.
Hope that helps
*** once you've done the backup, you can try wiping "data, cache, dalvik", and then restore the nandroid... sometimes that works
if not keep the nandroid, as it has all the information, and you can use Nandroid Manager (in play store) to extract individual information, if need be.
Good Luck
Hello guys,
I have an HTC One S-ON and I want to try the new ROM with 4.4.3. In order to use those new ROMs, all the developers recommended to update first the firmware. Sadly, many of you have an S-OFF phone where are lots of tutorials that can help you. So, I've read a lot and made a short tutorial. If anyone of you can help me if a confirmation or not of this will be great and could help me to upgrade my phone to the latest firmware!!!
How to flash?
(bootloader needs to be relocked)
1.Re-lock your bootloader (this will most probably wipe content of your device)(Type in “fastboot oem lock”)
2.Copy downloaded .zip(from this site https://www.androidfilehost.com/?fid=23622183712460395) to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
3.Re-name .zip file to firmware.zip
4.Open command prompt
5.Boot your device in fastboot mode (vol down + power ===> fastboot)
6.Connect device to the PC
7.In command prompt cd to fastboot.exe location
8.Make sure you have correct modeid and cidnum (type: fastboot getvar all)(I've checked my phone with apk CID Getter and saw that I have modelid: PN0710000 and cidnum: HTC__032 and I think it is ok to flash the firmware)
9.Type: fastboot oem lock (if your device is not relocked yet)
10.Type: fastboot oem rebootRUU and wait for device to reboot(Is there a RUU file that should I download? This is the only trick part that I don't understand . I found this the latest http://www.htc1guru.com/dld/ruu_m7_u...igned_2-1-exe/ RUU file..but I'm not sure what to do with or if I really have to use it )
11.Type: fastboot flash zip firmware.zip and wait for process to complete
12.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
13.Type: fastboot flash zip firmware.zip and wait for process to complete
14.Type: fastboot reboot
15.Unlock your bootloader and flash custom recovery if you are going to use custom ROM(Like the usual way using http://www.htcdev.com/bootloader and after that to change the stock Recovery with TWRP)
I hope I've understand everything and all will be right!
Thanks @mike1986. for the beginning tutorial. I've just updated it in order to uderstand the whole process.
Floare said:
Hello guys,
I have an HTC One S-ON and I want to try the new ROM with 4.4.3. In order to use those new ROMs, all the developers recommended to update first the firmware. Sadly, many of you have an S-OFF phone where are lots of tutorials that can help you. So, I've read a lot and made a short tutorial. If anyone of you can help me if a confirmation or not of this will be great and could help me to upgrade my phone to the latest firmware!!!
How to flash?
(bootloader needs to be relocked)
1.Re-lock your bootloader (this will most probably wipe content of your device)(Type in “fastboot oem lock”)
2.Copy downloaded .zip(from this site https://www.androidfilehost.com/?fid=23622183712460395) to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
3.Re-name .zip file to firmware.zip
4.Open command prompt
5.Boot your device in fastboot mode (vol down + power ===> fastboot)
6.Connect device to the PC
7.In command prompt cd to fastboot.exe location
8.Make sure you have correct modeid and cidnum (type: fastboot getvar all)(I've checked my phone with apk CID Getter and saw that I have modelid: PN0710000 and cidnum: HTC__032 and I think it is ok to flash the firmware)
9.Type: fastboot oem lock (if your device is not relocked yet)
10.Type: fastboot oem rebootRUU and wait for device to reboot you will see a black screen with a silver HTC logo(Is there a RUU file that should I download? This is the only trick part that I don't understand . I found this the latest http://www.htc1guru.com/dld/ruu_m7_u...igned_2-1-exe/ RUU file..but I'm not sure what to do with or if I really have to use it )
11.Type: fastboot flash zip firmware.zip and wait for process to complete
12.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
13.Type: fastboot flash zip firmware.zip and wait for process to complete
14.Type: fastboot reboot
15.Unlock your bootloader and flash custom recovery if you are going to use custom ROM(Like the usual way using http://www.htcdev.com/bootloader and after that to change the stock Recovery with TWRP)
I hope I've understand everything and all will be right!
Click to expand...
Click to collapse
Basically the flashing the firmware steps when you are S-ON or S-OFF are the same. The only difference is if you are S-ON you must have a locked bootloader, the firmware version must be the same or higher and it must be signed.
Step 10 - You want the device in RUU mode to accept the firmware.
Step 11 - The flashing of the firmware the first time is to set up the device to accept the firmware. It should fail the first time.
Step 12/13 - Exact same code as step 11
majmoz said:
Basically the flashing the firmware steps when you are S-ON or S-OFF are the same. The only difference is if you are S-ON you must have a locked bootloader, the firmware version must be the same or higher and it must be signed.
Step 10 - You want the device in RUU mode to accept the firmware.
Step 11 - The flashing of the firmware the first time is to set up the device to accept the firmware. It should fail the first time.
Step 12/13 - Exact same code as step 11
Click to expand...
Click to collapse
@majmoz Thank you very much for your help! I did it in the end! I was calm and the target was hit..like I could say!
The moderators could close this thread. Thank you guyz for your hard work!
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.
Well... There is one thing you could do.
squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!". All night it was restarting until the battery was dead this morning. Volume up and power work, and give 5 fails to mount the sd card. Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada. It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Is there anything else I can do with it? or is it just a paperweight now?
Thanks.
Click to expand...
Click to collapse
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
2.Flash a custom recovery.
You flash a custom recovery like this using fastboot.
Code:
fastboot flash recovery <recoveryName>.img
3.Use TWRP to copy the ROM zip file to your internal storage.
4.Do a nandroid backup.
5.Do an advanced wipe (Wipe data, system, cache and dalvik cache partitions).
6.Do a factory reset (Wipe Data/Factory reset).
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
7.Flash your preferred ROM.
8.Tell me if it worked and enjoy!
squidstings said:
I have a 2 year old Rogers M7. Not unlocked and never rooted.
Yesterday it was fine one moment, then a few seconds later, without me even touching it, it showed a picture of the phone with a red triangle with a "!".
Click to expand...
Click to collapse
This screen is the stock recovery main page.
Volume up and power work, and give 5 fails to mount the sd card.
Click to expand...
Click to collapse
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
It seemed to reset ok, but HTC sync doesn't recognize it except for a couple seconds while it's starting up.
Click to expand...
Click to collapse
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
Is there anything else I can do with it? or is it just a paperweight now?
Click to expand...
Click to collapse
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant
Click to expand...
Click to collapse
Yes rogers are M7_UL too.
so you can just go ahead and root your phone then flash a ROM of your choice.
Click to expand...
Click to collapse
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
-Windows computer (WIndows 8.1 is fine).
Click to expand...
Click to collapse
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
7.Flash the ROM's kernel using fastboot.
Code:
fastboot erase cache
then
Code:
fastboot flash boot <imageName>.img
Click to expand...
Click to collapse
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.
alray said:
This screen is the stock recovery main page.
You'll always get this "sd card mount fail" 5 times when revealing the stock recovery menu, its normal on the M7, there is no sd card to mount.
Code:
Spoke to HTC online tech, we went through a couple things and her last option was to manually install the ROM but refused to help when it was learned that I live in Canada.
Can you post the output of "fastboot getvar all" or at least post all the info you see in your bootloader menu.
Uninstall HTC Sync, you don't want this thing to interact with the phone while fixing it. Don't uninstall drivers, just HTC sync.
There is a RUU for Rogers to brings your phone back to stock but first, post your "fastboot getvar all" so we can make sure it will flash fine on your phone.
@The Android Manual Just for your information my friend:
Yes rogers are M7_UL too.
There is a RUU for Rogers, would recommend to wait for OP's phone info to see if he can use it and keep his phone locked & stock... unless he prefer a custom rom over stock
It depends, fastboot commands won't work on Win 8.1 if his hboot is 1.44 as explained here
Won't hurt but not needed (unlike some other htc's phone). Kernel partition (boot) isn't secured on the M7 which mean boot.img can be flashed in recovery if the bootloader is unlocked (s-off not needed). For this reason, all custom roms you'll find here will flash their own kernel automatically at the same time you flash the rom.
Click to expand...
Click to collapse
The last HTC device that lasted 3 years with me was the One X (my AT&T M7 either got bricked or had battery issue) and I never tried to get it S-OFF'ed since I really did no't see any use for it back in the day plus its screen was having problems anyway. This is new knowledge for me thanks!
and to the OP, if you need more help the quote button is your friend.
Good luck!
The Android Manual said:
The last HTC device that lasted 3 years with me was the One X
Click to expand...
Click to collapse
Wow mine (Tegra version) only lasted 13 months, had the infamous wifi issue (repaired myself) , overheat issue and motherboard finally died. I was very reluctant to buy htc again but finally I'm very satisfied with my M7.
Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.
squidstings said:
Sorry, stomach flu
no idea what "fastboot getvar all" is.
I've already done the factory reset and wipe with the HTC tech, no improvement.
I'm not sure what info you need.
Click to expand...
Click to collapse
You can try the Roger's RUU in this post. You will need to follow the instructions in the OP. I believe in your case, since there is no 6.xx version for Roger's you can go directly to the Lollipop version.
The Android Manual said:
Can you still boot into the bootloader? or when you do the button combo it just shows that "!" ? I believe your phone is similar to the international variant so you can just go ahead and root your phone then flash a ROM of your choice. Follow the steps I'll be listing below. Do these at your OWN RISK.
Prerequisites
-Working adb and fastboot. If you don't have them you can try using this.
-Your preferred custom ROM.
-Windows computer (WIndows 8.1 is fine).
-Your phone with a good amount of battery in it.
Unlocking and flashing process
1.Unlock your bootloader using HTC Dev.
Click to expand...
Click to collapse
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.
squidstings said:
I went to the site, HTCDev but my pc wouldn't allow me to do anything stating the certificate was unacceptable.
Click to expand...
Click to collapse
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.
alray said:
Looks like an issue with your web browser or something related with your internet option. You might want to try another browser or to adjust your browser security settings.
Click to expand...
Click to collapse
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
squidstings said:
I use firefox. I'll try another browser. which would you recommend? Chrome or IE
herre's my getvar info
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main: 5.11.631.8
version-misc: PVT SHIP S-ON
serialno:xxxx
imei:xxxx
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum: ROGER001
battery-status: good
battery-voltage: 3778mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM? is one custom and the other carrier generated?). I managed to get the identifier token last night, but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.
mb_guy said:
I have the same phone. Like @majmoz suggested I would flash the Rogers lolipop ruu zip from the link in his thread. You want the 7.17.631.7. Note you must use htc fastboot the link is in the post also. Flashing the RUU will erase all data, if you don't have a backup of the sdcard you may want to unlock bootloader flash twrp recovery so you can copy to PC, then relock bootloader and flash ruu.
Click to expand...
Click to collapse
I downloaded the ruu from the link on XDA but the .zip won't extract.
squidstings said:
Thanks for the advice. I believe I've downloaded that RUU already ( sorry, what's the difference between RUU and ROM?
Click to expand...
Click to collapse
A RUU stands for Rom Update Utility. Its an official file from HTC that flashes many partitions like the system partition (the rom/OS), the recovery partition, bootloader, radio partition, touch drivers, IR drivers...... well all partitions that are not specific to your phone and that will make it stock again. The only partition that are not flashed when using a RUU are those containing unique info about your phone like the MFG partition containing your IMEI number, Serial number, Date of manufactures etc.
A rom is only the /system partition flashed using a custom recovery. So when you flash a ROM (eiither custom or stock) you only flash the system partition and all other are kept like they was before the flash.
but the phone's never been set to allow usb debugging. will that cause issues with flashing? I'm not worried about losing anything, it's going to my son, so better clean.
Click to expand...
Click to collapse
You don't need usb debugging when flashing a RUU. USB debuging is only needed to use ADB commands when booted in the OS. A RUU is flashed using FASTBOOT commands when booted in the bootloader.
squidstings said:
I downloaded the ruu from the link on XDA but the .zip won't extract.
Click to expand...
Click to collapse
This is explained in the same post from where you have downloaded the file.... You might want to read the OP of the thread you are downloading files from :good: Not trying to be rude btw but lack of reading can sometime makes the situation worst. so just for you here it is again: The ruu are encrypted so they can't be extracted or opened and don't need to be, only flash it on your phone.
This is a collection of lollipop ruu.zip files for our beloved htc one m7 801.
I cannot test all of these files so any feedback will be welcome.
Also I have no responsibility if you phone explodes after flashing any of these files, I am just the uploader.
As many in this thread, ask about zip corruption, zip are not corrupted they are encrypted and can't open normally , they need decryption check md5 and dont try to unzip them
Click to expand...
Click to collapse
and instruction how to flash the ruu are posted just below these warnings, just click on the "show more" button.
---------- Post added at 05:12 PM ---------- Previous post was at 04:54 PM ----------
@squidstings
Might be easier to just unlock the bootloader, flash a recovery and then a rom like suggested at post #2
Youv said you already have your identifier token, go ahead and submit it to htcdev.com/bootloader (must create and account first). They will reply with an e-mail containing a file named Unlock_code.bin. Download and save the file in the same folder where you have adb and fastboot installed on your computer.
Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.
Then boot your phone in bootloader, make sure "fastboot usb" is shown in red (if not select the FASTBOOT option)
Open a terminal window from the same folder where you have adb and fastboot on your computer.
Type:
Code:
fastboot oem flash unlocktoken Unlock_code.bin
don't forget the capital U at Unlock_code.bin, fastboot and adb commands are case sensitive.
You should now see a screen asking if you want to unlock the phone, select YES (use volume up/down and power button)
The phone should then reboot to bootloader after performing a factory reset. Once done, confirm that your bootloader screen shows ***UNLOCKED*** and post back here, I'll post the isntruction how to flash the recovery.[/QUOTE]
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
C:\Android>
I did read everything. got a bit confused by different methods and files suggested (maybe just different wording for the same proceedure?). I've been looking for ROMs and RUUs all day. after I've fixed this phone (hopefully) i want to root my m7.
squidstings said:
Thanks for the explanations.
Tried that. and got a command error
C:\Android>fastboot oem flash unlocktoken Unlock_code.bin
... (bootloader) [ERR] Command error !!!
OKAY
Execution time is 3(ms)
Click to expand...
Click to collapse
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired
alray said:
Sorry my bad here, its not "fastboot oem flash unlocktoken Unlock_code.bin"
Its "fastboot flash unlocktoken Unlock_code.bin" (remove "oem")
Full instructions are available at htcdev.com/bootloader, you might want to double-check the commands there since it looks like i'm a little tired
Click to expand...
Click to collapse
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!
squidstings said:
I'm sorry. been reading so much about ROMs and RUUs that I forgot that I already unlocked the bootloader. I downloaded the 7.17.631.7.zip from the collection threat on here but it doesn't seem to work. sorry for the wasted time. SOOO sorry!
Click to expand...
Click to collapse
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.
mb_guy said:
Think you're still confused with ROMs and RUUs.
Roms are what you'll find in the dvelopment forms and require custom recovery like twrp and bootloader unlocked. Roms likely just replace the system partition.
Ruu are total phone restore to stock, it will delete data and replace the phones recovery, system, data and boot partitions. To flash you require the bootloader locked, when the phone is S-on..
So if you want to flash the ruu 7.17.631.7 you need to relock the bootloader (fastboot oem lock), once you have that done, check for the latest OTA 7.17.631.35 and apply while you still have stock recovery. Then if you want a custom recovery like twrp again, unlock the bootloader (hope you kept the unlock token from before) @alray gave you the adb command a post or two above. Then flash the recovery.
Hope this helps.
Click to expand...
Click to collapse
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.
squidstings said:
Now I'm completely confused. I thought I was unlocking it in order to bring it back from brickdom. I do understand RUU's and ROMs. It doesn't matter what I decide to put on it. My son would probably enjoy a rooted phone even if he knows nothing about it. The phone's a few years old so something as fast as it used to be would be enjoyed by him.
Click to expand...
Click to collapse
Ok, let me try again.
If you want to flash a rom,
1) unlocked bootloader (you have)
2) Flash custom recovery like twrp (I don't see that you have done this) so may be easier to go the ruu route.
3) Use custom recovery to install rom. I like the arhd ones
If you want to flash the RUU
1) relock the bootloader
2) flash the ruu, once this is done and the phone rebooted and running it will be at 7.17.631.7, go to settings about and check for system updates. You should receive an OTA which is 7.17.631.35. Install it.
3) You can leave the phone like this, or re-unlock the bootloader and flash a custom recovery like twrp. This will give you the ability to do nandroid backups, root the phone or install custom roms if you want.
Either method should work, the choice is yours
Hope this is clearer.