Database Develop

stock rom download?

I've installed CM7 but when I wanted to recover to my originele sense 3 rom, the phone would not boot. So my question is if I can download the stock rom from my Incredible S?

Method01 said:
I've installed CM7 but when I wanted to recover to my originele sense 3 rom, the phone would not boot. So my question is if I can download the stock rom from my Incredible S?
Click to expand...
Click to collapse
yes you can. however your bootloader will change.so are you s-off by xtc clip or software hack?
here are the roms:
http://forum.xda-developers.com/showthread.php?t=1033922

ajeya said:
yes you can. however your bootloader will change.so are you s-off by xtc clip or software hack?
here are the roms:
http://forum.xda-developers.com/showthread.php?t=1033922
Click to expand...
Click to collapse
Thanks. Which one i have to choose? Bought it in Europe and it is unbranded
I did it like here:
http://forum.xda-developers.com/showthread.php?t=1337105
And for going back to the stock rom, do I need to flash some things again or is it just factory reset + install from zip file?
http://forum.xda-developers.com/showpost.php?p=18079795&postcount=1 so that is the method to get the phone
back like new?
Or is it this topic I have to follow: http://forum.xda-developers.com/showthread.php?t=1359555

Gave it a try.. Wit the RUU method it always gave an error on my desktop and a security and update fail on my phone
So i copied the PG32IMG.zip on my sdcard and bootloader found the file.
Then in the right top corner is see some kind of status bar en when it is full, nothing happens. The phone didn't ask for any update.
What now

nobody who can help plz?

Method01 said:
Gave it a try.. Wit the RUU method it always gave an error on my desktop and a security and update fail on my phone
So i copied the PG32IMG.zip on my sdcard and bootloader found the file.
Then in the right top corner is see some kind of status bar en when it is full, nothing happens. The phone didn't ask for any update.
What now
Click to expand...
Click to collapse
OK, in reading through your posts, it sounds like you currently have HBOOT version 2.00.0000 Unlocked on your phone. That version is not going to let you install an older RUU/PG32IMG.zip file. You will have to flash the Sense 3.0 /3.08.405.3 RUU to get rid of CM7.

tpbklake said:
OK, in reading through your posts, it sounds like you currently have HBOOT version 2.00.0000 Unlocked on your phone. That version is not going to let you install an older RUU/PG32IMG.zip file. You will have to flash the Sense 3.0 /3.08.405.3 RUU to get rid of CM7.
Click to expand...
Click to collapse
That's correct.
I used the P32IMG.zip from:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
That is already the right one, not?
When I use the RUU installer on pc it says I'll update from image version 2.30.405.1 to 3.08.405.3
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.08.405.3
(bootloader) serialno: HT12TTD09339
(bootloader) imei: 355301040658406
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3768mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse

Method01 said:
That's correct.
I used the P32IMG.zip from:
RUU_VIVO_SENSE30_S_HTC_WWE_3.08.405.3_Radio_20.4802.30.0822U_3822.10.08.28_M_release_227170_signed.exe
That is already the right one, not?
When I use the RUU installer on pc it says I'll update from image version 2.30.405.1 to 3.08.405.3
Click to expand...
Click to collapse
Yes that is the right one. Everything looks good.

tpbklake said:
Yes that is the right one. Everything looks good.
Click to expand...
Click to collapse
Strange thing is that I always tried with that one and it didn't update..

Method01 said:
Strange thing is that I always tried with that one and it didn't update..
Click to expand...
Click to collapse
OK, since you have the HBOOT in an UNLOCKED state, the PG32IMG.zip/RUU will not update. You need to go into FASTBOOT mode and relock the HBOOT and then you can flash the PG32IMG.zip file.
Here's a link:
http://rootzwiki.com/topic/9322-how-to-relocked-hboot-htc-root-method/

tpbklake said:
OK, since you have the HBOOT in an UNLOCKED state, the PG32IMG.zip/RUU will not update. You need to go into FASTBOOT mode and relock the HBOOT and then you can flash the PG32IMG.zip file.
Here's a link:
http://rootzwiki.com/topic/9322-how-to-relocked-hboot-htc-root-method/
Click to expand...
Click to collapse
it worked!
thank you very much !

stuck in boot mode

hi guys, I am stuck in boot mode after removing cyanogen mod, I have tried installing the RUU.exe but it will not complete - I think the reason for this is that S-ON. I can't seem to find a solution to achieve S-off anywhere without having to be into the phones OS.
I have tried pushing the rom to my phone but I just keep getting 'no device found'
The usb recognises the phone but the adb commands do not work at all
any further info suggested would be massively appreciated.
edit:
got adb commands working by following this guide
(not allowed to post links yet)

progress so far:
I have managed to sideload a relevant ROM but it has now been saying 'installing update' for quite a while and I am not sure whether to touch it
on another note, the image verification thing on this forum is very, very annoying.

ok so I sideloaded a ROM and it aborted the installation, totally at a loss now

grantymc said:
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
Click to expand...
Click to collapse
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.

alray said:
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
Click to expand...
Click to collapse
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W914634
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b0a25cb2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

grantymc said:
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
Click to expand...
Click to collapse
Ruu.zip are not installed with a custom recovery/sideloaded!! It must be flashed via fastboot ruu mode. Anyway this ruu is not for your phone, its a .401 base and you need a .61 base ruu of same version or higher than 3.63.61.1 but afaik there is no ruu for your phone... BTW the 1.20.401.1 ruu is a pre-release version without OTA updates so it a bad idea to use it.
grantymc said:
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
Click to expand...
Click to collapse
Either because of a bad rom/download or because your recovery version is outdated. Flash twrp 2.6.3.3 or 2.6.3.4. Also clear cache every time your flash something and md5 check your roms/recovery before you flash them.
grantymc said:
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
Click to expand...
Click to collapse
S-OFF is not require to flash a custom rom like CM only if you want to convert your phone using a ruu not intended for your version.

[Q] Restoring 100% to stock, not working as it should...

Hi guys,
First of all, I did read all the topics conserning to RUU, S-On/S-Off, rumrunner, moonshine, firewater, revone, and so on but I can't seem to figure out how to properly do this.
Currently the HTC is running MIUI v5 4.5.16 JB4.2. But for warranty it has to go back to the store and I want to restore it to completly stock ROM etc. without any evidence I had a custom ROM running.
What I did was, follow the steps to unlock the bootloader, flash a custom recover (TWRP v2.6.3.0) and finally root it after MIUI was flashed.
The info you guys prolly need are as followed:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: .................
(bootloader) imei: ................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.038s
Click to expand...
Click to collapse
I tried to get S-Off but I keep getting strange errors on all of the given methods. This should work somehow I guess but how? Can somebody give me some kind of "roadmap" how to do it properly?
Currently fastboot shows:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014,15:58:33.0
Click to expand...
Click to collapse
At the moment I'm downloading "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.exe". But I already noticed that if I turn S-On (fastboot oem lock) then the phone is stuck in fast boot mode...
Thanks!

I think S-off is danger may u brick ur phone, it's better to leave it

ahmed blue said:
I think S-off is danger may u brick ur phone, it's better to leave it
Click to expand...
Click to collapse
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ...................
(bootloader) imei: ....................
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".

BETA911 said:
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
Click to expand...
Click to collapse
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.

Seanie280672 said:
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Click to expand...
Click to collapse
Well... It said it had a OTA update (like before) to 4.3 and I downloaded it. Reboot, installed, reboot --> bootloop. Now it's "HTC - quietly brilliant", black screen for couple of seconds and reboot to start from HTC logo again...
It's really beginning to piss me of.
But anyway, thanks for the help! A TWRP backup of 161 would be nice, then I'll install that one. The servers at htc1guru are giving me headache, speed is only between 50 and 250 kb/sec! I tried to download more then once but they keep failing on me when they reach bigger sizes and at this speed it's really really annoying to start over again...
Does "M7 CWM Nandroid Backup CID VODAP102 1.29.161.7" work for me? I guess not because it's 1.29 and I already have a higher version so it will give me the touchscreen issues?
To be honest, if this phone finally makes it to the store for repair I hope they can't repair it and let me choose an other phone. I had multiple Android phones the past years (with sometimes more then 2-3 different roms per week) and never had any of these long stretching problems!

The problem your having with the ota sounds like whilst you were installing the guru reset file, you must select to wipe data and also install stock recovery, it will fail without stock recovery.

Well, I did select to install the stock recovery and stock radio in the aroma installer. So I'm out of clues why it's giving me so much problems...
EDIT:
I unlocked the bootloader again and flashed TWRP. I'll try with your Vodafone image once you have time to share it with me. Already big thanks for the help!

here's the backup, you will need to extract the zip file and put the folder named backup into SDCARD/TWRP/BACKUPS/"your device serial number/
https://drive.google.com/uc?export=download&confirm=5940&id=0B_nEcSZr5peRZnpMSHRPRjlzX2c
This will put you on Vodafone 4.4.2 with sense 5.5, however you cant send your phone back until you have got rid of those 2 flags in the bootloader, only way to do that is s-off.
Ignore the folder called recovery, its just TWRP recovery to flash.
After installing, download the stock recovery from the link below and flash it to get OTAs
http://d-h.st/Cyq
Hit the thanks button please.

Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.

BETA911 said:
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
Click to expand...
Click to collapse
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom

alray said:
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
Click to expand...
Click to collapse
I know. I tried to get s-off but none of the given tools succeeded. They all complete their full cycle and eventually after the last reboot I go and check the state and it still says s-on... Then I did read I need a proper ROM so the tools can work (better). I tried to install ARHD like you mention, but after flashing it was stuck in a bootloop again. Clearing the cache and davlik didn't solve it.
At the moment I only need to know if it's safe to update to the new 5.16.161.2 update while it's unlocked... I got TWRP installed but I know I have to flash the stock recovery in order to make the update work. But I'm afraid I'm going to brick it again if I lock it again, as I don't know if it's needed to let the update complete without any errors.

RUU is not working for my M7.

I have an AT&T M7 flashed with Cyanogenmod 10 that I would like to restock. I've tried the RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2, but that is not working.
I mean it starts to run and then after asking for aproval it desapears.
I also tried the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2, and this one runs but at the end it says that is not compatible with my phones firmware.
This is the phone info:
M7_UL PVT SHIP S-OFF RH
CID-CWS_001HBOOT-1. 56. 0000
RADIO-4T. 24. 3218. 09
OpenDSP-v32. 120. 274. 0909
OS-4. 18. 502. 7
eMMC-boot 2048MB
Jan 28 2014, 09: 32: 41. 0
What is the simpliest way to go back to stock?
Thanks in advance.
Getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s

chiquito3 said:
I have an AT&T M7 flashed with Cyanogenmod 10 that I would like to restock. I've tried the RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2, but that is not working.
I mean it starts to run and then after asking for aproval it desapears.
I also tried the RUU_M7_UL_JB_50_Cingular_US_1.26.502.12_Radio_4A.14.3250.13_10.33.1150.01_release_318450_signed_2, and this one runs but at the end it says that is not compatible with my phones firmware.
This is the phone info:
M7_UL PVT SHIP S-OFF RH
CID-CWS_001HBOOT-1. 56. 0000
RADIO-4T. 24. 3218. 09
OpenDSP-v32. 120. 274. 0909
OS-4. 18. 502. 7
eMMC-boot 2048MB
Jan 28 2014, 09: 32: 41. 0
What is the simpliest way to go back to stock?
Thanks in advance.
Getvar:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4284mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s
Click to expand...
Click to collapse
you need to downgrade your hboot to 1.44 to flash 1.26.502.12

alray said:
you need to downgrade your hboot to 1.44 to flash 1.26.502.12
Click to expand...
Click to collapse
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.

chiquito3 said:
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.
Click to expand...
Click to collapse
use the 1.44 hboot from the .401 version.

chiquito3 said:
Thanks a lot for your response! Actually my real intention is not to go back to 1.26.502.12, but to go back to the latest stock available. Is just that the 4.18.502.7 RUU did not work for me.
If downgrading will solvwe my problem where do I get a copy of the 1.44 hboot for AT&T. I do not find one with the 502 identification.
Click to expand...
Click to collapse
Did you check the md5 of the 4.15.502.7 ruu you downloaded?
Also if you have HTCsync installed then uninstall it. Doesn't do any favours when using ruu's :good:

I've downloaded the file from 2 different sources and the resilt is the same.
Sent from my SM-G900T using Tapatalk

chiquito3 said:
I've downloaded the file from 2 different sources and the resilt is the same.
Sent from my SM-G900T using Tapatalk
Click to expand...
Click to collapse
Is the RUU quiting after you accept the license agreement , if so, its a windows error not an RUU error, read and do the fix below:
http://forums.androidcentral.com/htc-evo-4g-lte/363796-can-t-install-4-3-ruu-windows-7-8-1-a.html
post 18 fixed the problem for me, you need to download and install all one at a time with a reboot in-between each one, do not use windows update to update any of them.

Seanie280672 said:
Is the RUU quiting after you accept the license agreement , if so, its a windows error not an RUU error, read and do the fix below:
http://forums.androidcentral.com/htc-evo-4g-lte/363796-can-t-install-4-3-ruu-windows-7-8-1-a.html
post 18 fixed the problem for me, you need to download and install all one at a time with a reboot in-between each one, do not use windows update to update any of them.
Click to expand...
Click to collapse
Seems that you are right. I tried all the suggestions here but none of them worked on my PC. So Idecided to try on my laptop. The thing is that the RUU did run well but unfotunately it ends with an error 170 usb connection error.
The laptop recognizes the phone well so I cant understand the reason for the error.

chiquito3 said:
Seems that you are right. I tried all the suggestions here but none of them worked on my PC. So Idecided to try on my laptop. The thing is that the RUU did run well but unfotunately it ends with an error 170 usb connection error.
The laptop recognizes the phone well so I cant understand the reason for the error.
Click to expand...
Click to collapse
make sure the computer recognises the phone whilst the phone is both booted and in the bootloader with fastbootUSB showing on the phone screen.

Seanie280672 said:
make sure the computer recognises the phone whilst the phone is both booted and in the bootloader with fastbootUSB showing on the phone screen.
Click to expand...
Click to collapse
Ok guys I did it thanks to your help.
Now what is the prefered rooting method and should I take the OTA or not?

chiquito3 said:
Ok guys I did it thanks to your help.
Now what is the prefered rooting method and should I take the OTA or not?
Click to expand...
Click to collapse
yes take the OTA's, if you dont like the new Lollipop you can always just flash the RUU again to get back to the older versions as your s-off.
after you've done the OTA's, to root, just flash twrp recovery: http://dl.twrp.me/m7/twrp-2.8.5.0-m7.img and then flash the superSU zip from within TWRP recovery: http://download.chainfire.eu/696/SuperSU, complete root setup once the phone has started back up by opening superSU from your app drawer.

Seanie280672 said:
yes take the OTA's, if you dont like the new Lollipop you can always just flash the RUU again to get back to the older versions as your s-off.
after you've done the OTA's, to root, just flash twrp recovery: http://dl.twrp.me/m7/twrp-2.8.5.0-m7.img and then flash the superSU zip from within TWRP recovery: http://download.chainfire.eu/696/SuperSU, complete root setup once the phone has started back up by opening superSU from your app drawer.
Click to expand...
Click to collapse
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.

chiquito3 said:
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.
Click to expand...
Click to collapse
There is no lollipop for at&t yet, should be released soon
http://www.htc.com/us/go/htc-software-updates/#device-content

chiquito3 said:
I updated it but it only updated to 4.4.2. There was no Lollipop update. I think that there is no officail AT&T Lollipop update.
Click to expand...
Click to collapse
alray said:
There is no lollipop for at&t yet, should be released soon
http://www.htc.com/us/go/htc-software-updates/#device-content
Click to expand...
Click to collapse
Yes during the Uh Oh announcement / interview they said they were shooting for an April 1'st update for AT&T M7

clsA said:
Yes during the Uh Oh announcement / interview they said they were shooting for an April 1'st update for AT&T M7
Click to expand...
Click to collapse
And I'm longing for that moment! Thanks again.
Since I did change the stock recovery to TWRP just for rooting the phone, could I still take the OTA upgrade or does it have to be done manually?
I also installed Xposed Framework and some HTC Modules.

chiquito3 said:
And I'm longing for that moment! Thanks again.
Since I did change the stock recovery to TWRP just for rooting the phone, could I still take the OTA upgrade or does it have to be done manually?
I also installed Xposed Framework and some HTC Modules.
Click to expand...
Click to collapse
you will have to return the phone to full stock to take an OTA update

clsA said:
you will have to return the phone to full stock to take an OTA update
Click to expand...
Click to collapse
I did something bad to the phone and would like to go back to stock can I use the RUU again and how? Because I tried and it gives a fastboot error a few seconds after starting. The RUU is actually a downgrade.
I was trying to mod the Weather widget to transparent and I ended without the widget and the phone goes to black and takes too long to come back to light the screen.
the error is htc.fastboot.exe has stopped working

chiquito3 said:
I did something bad to the phone and would like to go back to stock can I use the RUU again and how? Because I tried and it gives a fastboot error a few seconds after starting. The RUU is actually a downgrade.
I was trying to mod the Weather widget to transparent and I ended without the widget and the phone goes to black and takes too long to come back to light the screen.
the error is htc.fastboot.exe has stopped working
Click to expand...
Click to collapse
you can use my Guru_Reset to return to stock 5.x
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
If you want to keep custom recovery choose no to stock recovery during install and yes to Root

clsA said:
you can use my Guru_Reset to return to stock 5.x
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
If you want to keep custom recovery choose no to stock recovery during install and yes to Root
Click to expand...
Click to collapse
Thanks again for your reply!
How do I flash this one? can it be done through costum recovery?

chiquito3 said:
Thanks again for your reply!
How do I flash this one? can it be done through costum recovery?
Click to expand...
Click to collapse
Yes you flash it in TWRP same as a rom

HTC One M7 Stock Recovery Backup

Hi Guys
Im new here so I hope I wont mess things up too bad, by posting something in the wrong place or something like that
I have a question about my Htc One M7 and I have been googling all day and either there is no easy solution or I am not able to find it...
So hopefully you can help me
My Htc One is at the moment completely stock. All I did was unlocking the bootloader as described by the htc-dev website.
I want to make a backup of my Stock Recovery, before I flash a custom one.
I tried to use this Guide: http://forum.xda-developers.com/showthread.php?t=2265618 to achieve that.
In step 7/8 it states ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)") that I should be able to boot a recovery without flashing it. But it also says that it might not work with higher hboots.
It seems that it wont work with my Hboot 1.56
Now my actual question: Is there any way to make a backup of the 100% Stock Recovery?
And please dont give me a link where i can download one, i would like to create a backup myself
If you find anything that is wrong with this post (spelling, location or somthing), please let me know.
Thank you for your help

hahamuntz said:
Hi Guys
Im new here so I hope I wont mess things up too bad, by posting something in the wrong place or something like that
I have a question about my Htc One M7 and I have been googling all day and either there is no easy solution or I am not able to find it...
So hopefully you can help me
My Htc One is at the moment completely stock. All I did was unlocking the bootloader as described by the htc-dev website.
I want to make a backup of my Stock Recovery, before I flash a custom one.
I tried to use this Guide: http://forum.xda-developers.com/showthread.php?t=2265618 to achieve that.
In step 7/8 it states ("In the Command Prompt type following command: fastboot boot recovery.img (this command might not with newer hboots)") that I should be able to boot a recovery without flashing it. But it also says that it might not work with higher hboots.
It seems that it wont work with my Hboot 1.56
Click to expand...
Click to collapse
You can only use the "fastboot boot recovery.img" command on hboot 1.44. So if you absolutely want to backup the stock recovery using this method you'll need s-off in order to downgrade your hboot so you can boot a custom recovery without flashing it to dump the stock one, not very convenient... Stock recovery can be extracted from the ota update zip file of the same version your phone is running, this is the method used by everyone if their stock recovery.img is not already available to download here on xda.
Now my actual question: Is there any way to make a backup of the 100% Stock Recovery?
Click to expand...
Click to collapse
Yes but not convenient at all like said above, I already did it once, just because the ota update zip file was encrypted and so it was impossible to extract the recovery directly from the ota so I had to pull it directly from the phone: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
And please dont give me a link where i can download one, i would like to create a backup myself
Click to expand...
Click to collapse
Can't give you any link to download your recovery anyway since we don't know what firmware version your phone is running.

alray said:
You can only use the "fastboot boot recovery.img" command on hboot 1.44. So if you absolutely want to backup the stock recovery using this method you'll need s-off in order to downgrade your hboot so you can boot a custom recovery without flashing it to dump the stock one, not very convenient... Stock recovery can be extracted from the ota update zip file of the same version your phone is running, this is the method used by everyone if their stock recovery.img is not already available to download here on xda.
Yes but not convenient at all like said above, I already did it once, just because the ota update zip file was encrypted and so it was impossible to extract the recovery directly from the ota so I had to pull it directly from the phone: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
Can't give you any link to download your recovery anyway since we don't know what firmware version your phone is running.
Click to expand...
Click to collapse
Thank you for your quick answer
It doesn't have to be this way, I just want to create my own backup of Stock Rom and Stock Recovery. If their is a way to extract it from an ota update, I would gladly use this method. Do you know a good guide, that explains how to do that? And could I do that with the current version of Android running on the Phone? Update sounds like I would have to update it first?

hahamuntz said:
Thank you for your quick answer
It doesn't have to be this way, I just want to create my own backup of Stock Rom and Stock Recovery. If their is a way to extract it from an ota update, I would gladly use this method. Do you know a good guide, that explains how to do that? And could I do that with the current version of Android running on the Phone? Update sounds like I would have to update it first?
Click to expand...
Click to collapse
To extract the stock recovery from an update update, simply open the zip file, inside you'll find another zip file named "firmware.zip" open that one and extract the recovery.img file.
what is your firmware version? "fastboot getvar version-main"

alray said:
To extract the stock recovery from an update update, simply open the zip file, inside you'll find another zip file named "firmware.zip" open that one and extract the recovery.img file.
what is your firmware version? "fastboot getvar version-main"
Click to expand...
Click to collapse
Im running 4.19.401.11
How do I get the ota.zip file? Is there a way to extract that from my Phone?

hahamuntz said:
Im running 4.19.401.11
How do I get the ota.zip file? Is there a way to extract that from my Phone?
Click to expand...
Click to collapse
You can get the ota zip file when downloading an update and selecting "install later". Once the download is completed, connect your phone to your computer and copy the ota zip file from your download folder to your computer. Once the update is installed, the ota zip file is deleted form the phone so you can't extract the update from the phone since its already installed.
You can find the ota update file for your version (from 4.19.401.9 to 4.19.401.11) here: https://www.androidfilehost.com/?fid=95747613655045071
Or directly download the 4.19.401.11 stock recovery here: https://www.androidfilehost.com/?fid=95864024717070740 which is the same exact recovery installed on your phone.

alray said:
You can get the ota zip file when downloading an update and selecting "install later". Once the download is completed, connect your phone to your computer and copy the ota zip file from your download folder to your computer. Once the update is installed, the ota zip file is deleted form the phone so you can't extract the update from the phone since its already installed.
Click to expand...
Click to collapse
I think i did it. Thank you very much!
there is the firmware folder with 9 .img files in it seems to be right, altough I can't open the zip folder directly (it says error- Folder invalid), but it worked when I extracted the Folder...
The 9 .img files are about 100 MB, is that right?
And could I apply the same update to my second HTC One M7( running a rooted Stock with Android 5.0.2), to get it back to Stock Rom and Recovery?
What do I have to check to make sure they are compatible?

hahamuntz said:
I think i did it. Thank you very much!
there is the firmware folder with 9 .img files in it seems to be right, altough I can't open the zip folder directly (it says error- Folder invalid), but it worked when I extracted the Folder...
The 9 .img files are about 100 MB, is that right?
Click to expand...
Click to collapse
The stock recovery should be around 12MB not 100MB,
And could I apply the same update to my second HTC One M7( running a rooted Stock with Android 5.0.2), to get it back to Stock Rom and Recovery?
What do I have to check to make sure they are compatible?
Click to expand...
Click to collapse
No, this recovery is only for 4.19.401.11 and that update file is for patching 4.19.401.09 to 4.19.401.11 only.

alray said:
The stock recovery should be around 12MB not 100MB, .
Click to expand...
Click to collapse
Sorry i didn't say that well... All of the .img files in this folder together are about 100 MB.
The Recovery itself is only 12 MB, so it seems fine
alray said:
No, this recovery is only for 4.19.401.11 and that update file is for patching 4.19.401.09 to 4.19.401.11 only.
Click to expand...
Click to collapse
Okay, but if I would install the update and make a Nandroid backup of the updated Rom, would I be able to install that Nandroid backup also on the second Phone?
And would I be able to use the recoverybackup I received out of the OTA.zip to restore the first Phone to StockRecovery if I flashed a custom Recovery after I updated?

hahamuntz said:
Sorry i didn't say that well... All of the .img files in this folder together are about 100 MB.
The Recovery itself is only 12 MB, so it seems fine
Click to expand...
Click to collapse
Yes that seems fine.
Okay, but if I would install the update and make a Nandroid backup of the updated Rom, would I be able to install that Nandroid backup also on the second Phone?
If I understand correctly, you'll update phone #1 then make a nandroid backup
And would I be able to use the recoverybackup I received out of the OTA.zip to restore the first Phone to StockRecovery if I flashed a custom Recovery after I updated?
Click to expand...
Click to collapse
I'm not sure if I should answer this one before knowing the details (fastboot getvar all) of the second phone and knowing what is your goal exactly. That might only brings more confusion and there might be easier solution to restore your phone than creating a backup from device A and restoring it to B...
But yes its possible, you want to make sure your recovery version, software version and firmware version match together. E.G You don't want to restore a 4.19.401.11 software backup on a phone running a different firmware version and the recovery version must also match. So if phone B is 7.19.401.22 firmware you want to restore a 7.19.401.22 software and a 7.19.401.22 stock recovery. If you have updated phone A from 4.19.401.11 to 7.19.401.22 and then make a backup of it, you should be fine restoring that backup on phone B. Any mismatch between version will prevent installation of ota updates and in some case you can have drivers issues.

alray said:
I'm not sure if I should answer this one before knowing the details (fastboot getvar all) of the second phone and knowing what is your goal exactly. That might only brings more confusion and there might be easier solution to restore your phone than creating a backup from device A and restoring it to B...
But yes its possible, you want to make sure your recovery version, software version and firmware version match together. E.G You don't want to restore a 4.19.401.11 software backup on a phone running a different firmware version and the recovery version must also match. So if phone B is 7.19.401.22 firmware you want to restore a 7.19.401.22 software and a 7.19.401.22 stock recovery. If you have updated phone A from 4.19.401.11 to 7.19.401.22 and then make a backup of it, you should be fine restoring that backup on phone B. Any mismatch between version will prevent installation of ota updates and in some case you can have drivers issues.
Click to expand...
Click to collapse
First Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Second Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3869mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
What I wanna do is to use the first phone to create my own Backup of ROM and Recovery to get the second phone to the newest Version of stock.
Is this possible with these pair of Phones?
And could you recommend me a good website were I could learn what all these variables mean? an were I could learn more about this topic?

hahamuntz said:
First Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4287mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Second Phone:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3869mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
What I wanna do is to use the first phone to create my own Backup of ROM and Recovery to get the second phone to the newest Version of stock.
Click to expand...
Click to collapse
Well the second phone can simply be updated to the latest version by flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30 which is the latest version.
The first phone can also be updated to the latest version by flashing the 7.19.401.2 firmware first and then doing the same thing, flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30. Simple and easy unlike what you are trying to do
And could you recommend me a good website were I could learn what all these variables mean? an were I could learn more about this topic?
Click to expand...
Click to collapse
Here is the essential:
(bootloader) version-bootloader: This is your bootloader version, sometime called hboot
(bootloader) version-baseband: This is your radio version, radio is the software that controls the reception/transmission. Different carriers/region will requires different radio version because of different infrastructures.
(bootloader) version-main: This is your firmware version, the firmware is the code that make possible the interaction between the software and the hardware.
(bootloader) serialno: Serial number of your phone, don't share this number on the forum
(bootloader) imei: IMEI number is a unique number identifier for GSM networks, for example if your phone is declared lost/stolen or linked to unpaid bills, this number will be added to an international blacklist and you won't be able to use your phone on any carrier worldwide. Don't share this number on the forum.
(bootloader) meid: MEID is the same as IMEI but for CDMA phones, on GSM phone you don't have an MEID (only showing 0)
(bootloader) product: This is your product code, M7_UL means its a M7, U = GSM, L= LTE so its a M7 GSM/LTE
(bootloader) modelid: Model ID (MID) is a little like the product code but more specific to your region. For example, PN0710000 = M7_UL Europe. PN0712000 is also a M7_UL but for North America (all Canadian carriers, USA's AT&T, Google Play Edition and US developer edition)
(bootloader) cidnum: CID is the carrier / region ID
(bootloader) security: Security ON/OFF. Read about s-on/s-off here

alray said:
Well the second phone can simply be updated to the latest version by flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30 which is the latest version.
The first phone can also be updated to the latest version by flashing the 7.19.401.2 firmware first and then doing the same thing, flashing the 7.19.401.22 ruu and then taking one ota update to 7.19.401.30. Simple and easy unlike what you are trying to do
Click to expand...
Click to collapse
How would I know if these are compatible?
I would rather not use some download from the Internet because I afraid that somebody messed it up and I won't get the 100% Stock, maybe even an infected one. (Is this even a rational fear? )
That's why I am trying to create all the necessary resources myself, so I can be sure that they are alright. Also I learn much more if I do it step by step instead of just flashing a Rom from the web.
For example how do I check if a Rom is compatible with my device?
alray said:
(bootloader) serialno: Serial number of your phone, don't share this number on the forum
(bootloader) imei: IMEI number is a unique number identifier for GSM networks, for example if your phone is declared lost/stolen or linked to unpaid bills, this number will be added to an international blacklist and you won't be able to use your phone on any carrier worldwide. Don't share this number on the forum.
Click to expand...
Click to collapse
Is the other stuff save to share?

hahamuntz said:
How would I know if these are compatible?
I would rather not use some download from the Internet because I afraid that somebody messed it up and I won't get the 100% Stock, maybe even an infected one. (Is this even a rational fear? )
Click to expand...
Click to collapse
Not really since the RUU are offical (from HTC) and also they are encrypted with HTC private key .The 7.19.401.22 ruu was uploaded by me as you can see here. :good: So there is nothing to fear. Then the 7.19.401.30 ota update will come directly from HTC's servers so again, nothing to fear.
That's why I am trying to create all the necessary resources myself, so I can be sure that they are alright.
Click to expand...
Click to collapse
No offense, but these ruu are probably more reliable than what you are trying to do + easier to achieve your goal.
Also I learn much more if I do it step by step instead of just flashing a Rom from the web.
Click to expand...
Click to collapse
+1 for learning
For example how do I check if a Rom is compatible with my device?
Click to expand...
Click to collapse
First you have a M7_UL (GSM variant) so make sure you are only flashing M7 GSM stuff (rom, recovery, kernel etc). Also read the rom thread to see if you have all the pre-requisite before flashing a rom, for example, lollipop roms requires at least a 7.xx.xxx.x firmware to work correctly so it would work fine on phone B but not on phone A. Another example: CyanogenMod roms requires at least TWRP recovery 2.7.1.1, using anything below that will not work. Thats why you should always read the first post of the thread from the rom you want to flash before proceeding. If you are unsure after reading, better to ask questions instead of (soft) bricking,

So can I flash the 7.19.401.22 from you directly on phone B? And then update over the official server? Then Phone B is completely stock and with the newest version?
If understood the whole s-off/ s-on that you posted, I only can flash the official RUUs on Phone B with s-on?
I think after that I understood everything for now thank you very much!
Do you have a good source where I can read about this whole topic? I need something like an encyclopedia with explanations, that are not completely basic but easy enough for me to understand

hahamuntz said:
So can I flash the 7.19.401.22 from you directly on phone B? And then update over the official server? Then Phone B is completely stock and with the newest version?
Click to expand...
Click to collapse
Yes you can and btw the ruu is not from me, I have uploaded it but its an official RUU from HTC.
If understood the whole s-off/ s-on that you posted, I only can flash the official RUUs on Phone B with s-on?
Click to expand...
Click to collapse
You can also flash the RUU on Phone A but you will need to update its firmware first since its too old to accept the 7.19.401.2 ruu
Do you have a good source where I can read about this whole topic? I need something like an encyclopedia with explanations, that are not completely basic but easy enough for me to understand
Click to expand...
Click to collapse
About what? flashing RUU?
Btw, you'll find instructions how to flash the ruu here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (see post #1)

I meant to ask if it is correct that I can only Flash official RUUs while on S-On?
I mean something like a collection of Information about all the terms used around flashing and rooting.
At the moment I just google everything I don't understand/know, but I would like to understand it all completely. Is there something like a guide, that doesn't only say " Do this and then do that" but also explains why I should do this and what exactly I am doing.

alray said:
Btw, you'll find instructions how to flash the ruu here: http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 (see post #1)
Click to expand...
Click to collapse
Thanks, can I flash everything from there that has my CID? Or do I have to look out for something else?
And while I am doing this, could I switch from Sense to the Google Play Edition on Phone B?

hahamuntz said:
Thanks, can I flash everything from there that has my CID? Or do I have to look out for something else?
Click to expand...
Click to collapse
As long as the rom you want to flash is for a M7_UL you should be able to flash it, CID is more important when you want to flash a RUU.
And while I am doing this, could I switch from Sense to the Google Play Edition on Phone B?
Click to expand...
Click to collapse
Using a custom GPE rom yes its possible, using a GPE RUU no because the phone is S-ON and flashing the GPE ruu would requires to change the phone CID/MID (s-off needed)

alray said:
As long as the rom you want to flash is for a M7_UL you should be able to flash it, CID is more important when you want to flash a RUU.
Click to expand...
Click to collapse
So could I flash this Rom, although it says its for Gsm or would I lose my ability to use lte?
(http://forum.xda-developers.com/htc-one/development/rom-google-play-edition-lollipop-v1-00-t2963927)
Is this even the correct Rom if I want the complete stock gpe? And if flash the unrooted version would I be able to root it in a second step (Easier for me to learn the stuff, then just flashing a rooted Rom)
alray said:
Using a custom GPE rom yes its possible, using a GPE RUU no because the phone is S-ON and flashing the GPE ruu would requires to change the phone CID/MID (s-off needed)
Click to expand...
Click to collapse
I think I understood it wrong... I thought the Ruu is a part of a Rom? Used to verify if it is official or not?
Do you know a collection of Information about all the terms used around flashing and rooting.
At the moment I just google everything I don't understand/know, but I would like to understand it all completely. Is there something like a guide, that doesn't only say " Do this and then do that" but also explains why I should do this and what exactly I am doing.