Database Develop

[Q] Soft-Bricked HTC One - Want to go 100% stock again.

Solved thanks to @alray
Ok so the other day I tried going to Android 4.4 Google edition with a rom but s-off never worked. Without noticing s-on I tried installing the rom which soft bricked the phone (Starts up goes past HTC logo and flashes google logo then the screen goes blue).
I made the obvious mistake of not making a back up so I'm stuck. I have access to Bootloader & Recovery. I've tried installing RUU files but the ones I've tried so far get stuck at 7% 'Checking Header'. I'm just looking to get back to a working phone... Any help is appreciated.
If I'm missing any info you need let me know, I'm new to this...
Thanks.
More info:
I'm in Ireland, Europe.
The phone works with different sim cards (So I assume it must be unlocked).
RRU's I've tried:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
If you can give me more to try/ that are meant for my phone I would appreciate it.
I've given the bootloader menu as an attachment.
The fastboot getvar all is as follows (this is after I installed the new rom, I don't know what the original ones are):
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: (not sure if you need this)
(bootloader) imei: (not showing this to you)
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4262mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse

CorcoranM96 said:
Ok so the other day I tried going to Android 4.4 Google edition with a rom but s-off never worked. Without noticing s-on I tried installing the rom which soft bricked the phone (Starts up goes past HTC logo and flashes google logo then the screen goes blue).
I made the obvious mistake of not making a back up so I'm stuck. I have access to Bootloader & Recovery. I've tried installing RUU files but the ones I've tried so far get stuck at 7% 'Checking Header'. I'm just looking to get back to a working phone... Any help is appreciated.
If I'm missing any info you need let me know, I'm new to this...
Thanks.
More info:
I'm in Ireland, Europe.
The phone works with different sim cards (So I assume it must be unlocked).
RRU's I've tried:
RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed
If you can give me more to try/ that are meant for my phone I would appreciate it.
I've given the bootloader menu as an attachment.
The fastboot getvar all is as follows (this is after I installed the new rom, I don't know what the original ones are):
Click to expand...
Click to collapse
the ruu failed because you need s-off to use them with hboot 1.55 (require hboot downgrade to 1.44 which require s-off)
so now your best option is tu install a guru reset. Use this file
boot your phone into your custom recovery and push the file I linked above to your sd card. then install the .zip file with your custom recovery and follow instruction from the graphical user interface (aroma installer)
video tutorial here

so now your best option is tu install a guru reset.
boot your phone into your custom recovery and push the file I linked above to your sd card. then install the .zip file with your custom recovery and follow instruction from the graphical user interface (aroma installer)
Thanks @alray for the reply! I'm trying that now, I'll let you know how I get on!

@alray
This may sound silly but, do you know if I need to buy the 'On the go usb cable' like in his video? I dont think I do since he was running a 1.29.xxx (doesnt support touch screen) but I'll be running a 3.62.401.1 (he doesnt specify if I need one or not...) Just want to make sure before doing anything.
Thanks.

CorcoranM96 said:
@alray
This may sound silly but, do you know if I need to buy the 'On the go usb cable' like in his video? I dont think I do since he was running a 1.29.xxx (doesnt support touch screen) but I'll be running a 3.62.401.1 (he doesnt specify if I need one or not...) Just want to make sure before doing anything.
Thanks.
Click to expand...
Click to collapse
Move the .zip file to your fastboot/adb folder. boot your phone in recovery. then:
Code:
adb push name_of_file.zip /sdcard/
then in recovery select ''install'' and slect the zip you pushed
no need to use otg cable

@alray I'm getting 'Device not found' When I try to do anything with ADB... Any Idea of the problem?

CorcoranM96 said:
@alray I'm getting 'Device not found' When I try to do anything with ADB... Any Idea of the problem?
Click to expand...
Click to collapse
what recovery are you using? You are doing adb command in recovery right?

Solved!
alray said:
what recovery are you using? You are doing adb command in recovery right?
Click to expand...
Click to collapse
Fixed it, I just changed computer... My phone works perfectly and is returned to stock! :good:
Thanks a million @alray!

How to Update to 4.4.2 on rooted HTC ONE??

I have had my HTC ONE for about 5 months now and as soon as i got the phone i rooted it and installed Teamwin's recovery program. Today i got a notification that there is a system update (4.4.2). What steps do i need to take for updating this phone considering that its rooted and has Teamwins recovery program?

BlockABoots said:
I have had my HTC ONE for about 5 months now and as soon as i got the phone i rooted it and installed Teamwin's recovery program. Today i got a notification that there is a system update (4.4.2). What steps do i need to take for updating this phone considering that its rooted and has Teamwins recovery program?
Click to expand...
Click to collapse
if you have made no changes to the OS just install the stock recovery for your os version.
Stock recovery's
if your using custom roms you need to RUU back to stock then take the update
find your RUU here >> http://www.androidruu.com/index.php?developer=M7
use fastboot getvar all to find your phones information

Ok have used adb and this if my phones info......
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3************
(bootloader) imei: 354***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
What stock recovery image do i need to use? from the link you sent me above, recovery 2.24.401.8.img??
Will i lose all the data on my phone installing the stock recovery??

BlockABoots said:
Ok have used adb and this if my phones info......
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3**********
(bootloader) imei: 354**************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.060s
What stock recovery image do i need to use? from the link you sent me above, recovery 2.24.401.8.img??
Will i lose all the data on my phone installing the stock recovery??
Click to expand...
Click to collapse
Edit your previous post and remove serial no and IMEI
yes that's the recovery you need and no it won't erase your phone

clsA said:
Edit your previous post and remove serial no and IMEI
yes that's the recovery you need and no it won't erase your phone
Click to expand...
Click to collapse
Thanks for the pointer.
So these are the steps i need to do:
1. Download 'recovery 2.24.401.8.img'
2. Rename 'recovery 2.24.401.8.img' to 'recovery.img'
3. Place 'recovery.img' in my adb/fastboot folder (C:\Adb)
4. Open Command Prompt and navigate to your adb folder
5. Type 'adb reboot bootloader' to get into fastboot on the HTC ONE
6. And then flash the recovery img by typing 'fastboot flash recovery recovery.img'
Is the above all correct?

Yep that's it
Sent from my HTC One using Tapatalk

uarbie
clsA said:
Yep that's it
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
OK thanks, it doesnt matter than i have S-ON then?
After i type, 'fastboot flash recovery recovery.img'
its says, 'waiting for device' and just sits there, any ideas why this happens?

probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
BlockABoots said:
OK thanks, it doesnt matter than i have S-ON then?
After i type, 'fastboot flash recovery recovery.img'
its says, 'waiting for device' and just sits there, any ideas why this happens?
Click to expand...
Click to collapse

ipfreelytech said:
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
Click to expand...
Click to collapse
Ah yeah i am on Windows 8.1. I'll have to use my laptop then. What drivers do i need to be downloading?
Also can 4.4.2 be rooted yet?

I use the universal naked driver pack and usually just choose google nexus bootloader interface for the driver.
Sure, you root it the same as anything else: unlock bootloader, flash cwm/twrp recovery, flash SuperSU.zip
BlockABoots said:
Ah yeah i am on Windows 8.1. I'll have to use my laptop then. What drivers do i need to be downloading?
Also can 4.4.2 be rooted yet?
Click to expand...
Click to collapse

ipfreelytech said:
probably drivers.
check device manager and make sure you have a proper driver loaded
fastboot devices should show your device.
If your on windows 8/8.1 it has trouble with fastboot on older hboot versions. ADB works fine but fastboot doesn't work. I think newer hboot's resolve this so it will work after the update.
Might need to just use a win7 pc or VM to flash stock recovery.
Click to expand...
Click to collapse
ipfreelytech said:
I use the universal naked driver pack and usually just choose google nexus bootloader interface for the driver.
Sure, you root it the same as anything else: unlock bootloader, flash cwm/twrp recovery, flash SuperSU.zip
Click to expand...
Click to collapse
Ok have managed to flash the stock recovery back to the phone, and have update to 4.4.2. But when i turned the phone back on i had to go through all the setup process and now all my contact and text messages and apps have gone!!. I though i wasnt going to lose all my data?

Your bootloader was already unlocked? or was it locked and you just unlocked it? When you perform a bootloader unlock it does wipe the data as a "safety measure".
BlockABoots said:
Ok have managed to flash the stock recovery back to the phone, and have update to 4.4.2. But when i turned the phone back on i had to go through all the setup process and now all my contact and text messages and apps have gone!!. I though i wasnt going to lose all my data?
Click to expand...
Click to collapse

ipfreelytech said:
Your bootloader was already unlocked? or was it locked and you just unlocked it? When you perform a bootloader unlock it does wipe the data as a "safety measure".
Click to expand...
Click to collapse
It should of already been unlocked, as it was rooted and had TWRP install previously

So theres no way for me to get this stuff back then, pictures, messages, contacts etc?

Um, there's some missing information here.
Short answer, if you in fact "unlocked" the phone recently, you wiped all personal data and there is absolutely no way to go back.
There are other ways data can get erased however.
As you pointed out, the phone was likely unlocked previously. Not sure how it would have become relocked forcing you to unlock again, which you don't seem to remember doing anyway.
Also you didn't originally say you lost your pictures. Did you or didn't you? Losing texts and contacts is normal when flashing a ROM. There are backup apps for texts and most people keep their contacts in the cloud do you normally just resync and you're done.
But pictures is something else. Sounds like someone did a factory reset and/or formatted the entire /data partition in recovery.
Normally most recoveries know that when you "format" data, you are really just selectively erasing everything in /data *except* /data/media. You don't usually do an actual format. The stock recovery does not make this distinction, and even custom recoveries often have an advanced features that lets you truly format all of /data. So you might have nuked your pictures in recovery somehow, no unlocking necessary.
You need to go into more detail.
But if you are saying your pictures are gone, they're probably totally gone.
One last possibility, the version-main you posted suggests you may have been using android 4.2 originally.
But I suppose it's possible the original ROM you were using was actually 4.1. Maybe your stuff was at the top level of /data/media and never got moved to /data/media/0
This surprised quite a few people during the transition from Android 4.1 to 4.2
So *if* you didn't unlock *and* didn't totally format everything *and* your old ROM was 4.1, well.. get a file browser and have a look around. Maybe you got lucky.
Sent from my HTC One using xda app-developers app

Well before i flashed the recovery image bootloader had 'Tampered' and 'unlocked' listed at the top of the sceeen, just like it does now so im not really sure what happened. But as soon as i flashed the 'recovery 2.24.401.8.img' back onto my phone and then downloaded the 4.4.2 system update and installed it, when the phone restarted again it was like it was back to factory default in that i had to go through the whole setup screens!, so not sure whats happened.
But on closer inspection even though i have downloaded and installed system update 4.4.2, if i go in settings>about>Software information> it says im on Android version 4.3 and software number 3.62.401.1, isnt this wrong as ive updated to 4.4.2???

You have two separate issues here. You lost your data and you're not running 4.4.2
Apparently you're not worried about your data.
To get 4.4.2 you either need to a) get to a place that is so "stock" that OTA's will take you the rest of the way or b) manually flash a 4.4.2 ROM. The b) option usually requires S-OFF and a suitably recent recovery compatible with KitKat.
If you are already S-OFF of course b) is way simpler. But you're not. In fact you have HBOOT 1.56 which can make S-OFF less certain. If you can get S-OFF that's the way I would go. I personally never screw around chasing OTA's.
You may be in an awkward place right now.
Time for someone with more patience than me to get involved I guess.
Sent from my HTC One using xda app-developers app

No please don't get me wrong I am certainly worried about my lost data, especially the pictures, but from what you said I there's no real way to recover them, is that correct or is there a way at all?

Probably gone, but I would still use adb shell or a file explorer app to look in
/data/media
Your most recent personal data (the stuff you made in the last day or two, not the lost files you are looking for) will be in
/data/media/0
You're checking to see if there is useful stuff *outside* the " 0 " folder.
Don't delete anything unfamiliar (for instance if you see clockworkmod, leave that alone -it's nandroid backups). Just look for orphaned folders full of personal stuff like "DCIM" or " Music" or whatever.
Sent from my HTC One using xda app-developers app

NxNW said:
Probably gone, but I would still use adb shell or a file explorer app to look in
/data/media
Your most recent personal data (the stuff you made in the last day or two, not the lost files you are looking for) will be in
/data/media/0
You're checking to see if there is useful stuff *outside* the " 0 " folder.
Don't delete anything unfamiliar (for instance if you see clockworkmod, leave that alone -it's nandroid backups). Just look for orphaned folders full of personal stuff like "DCIM" or " Music" or whatever.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Sadly there is nothing in /data/media there are 3 folder, 0, legacy. obb and a file .htc_layout_version none hold any of my old photos . I have even tried the program, Wondershare Dr.Fone and that doesnt find any of my old photos either...so i guess there lost for ever, bugger.
I guess i need to get this phone back to stock and then try the update and see if it takes this time?, so ill need to remove the root, TWRP recovery and SuperSU?

Accidentally erased operating system on HTC One M7

Hi, i run an HTC One M7 that was originally from AT&T. I unlocked it and use it in my country. Few days ago i wanted to install the stock Android and try it. I did everything as was said - unlocked the bootloader, s-off, recovery etc. after a few hours of the stock Android experience i wanted to change it to ARHD. As i changed it a question popped out asking if i want to root my device. I answered "yes", not knowing what it means. My phone was bricked and stuck on the HTC welcome screen since yesterday. I tried a lot of differend ways of fixing it and still no results. I locked and unlocked the bootloader again, tried to install the official RUU, but it doesn't want to. I get MTP driver error when connecting to my computer.
I have "can't mount SD card" on my phone. I'm pretty desperate, but i want to fix this issue and get back my phone. This will be a lesson for me.

Skyrocker94 said:
Hi, i run an HTC One M7 that was originally from AT&T. I unlocked it and use it in my country. Few days ago i wanted to install the stock Android and try it. I did everything as was said - unlocked the bootloader, s-off, recovery etc. after a few hours of the stock Android experience i wanted to change it to ARHD. As i changed it a question popped out asking if i want to root my device. I answered "yes", not knowing what it means. My phone was bricked and stuck on the HTC welcome screen since yesterday. I tried a lot of differend ways of fixing it and still no results. I locked and unlocked the bootloader again, tried to install the official RUU, but it doesn't want to. I get MTP driver error when connecting to my computer.
I have "can't mount SD card" on my phone. I'm pretty desperate, but i want to fix this issue and get back my phone. This will be a lesson for me.
Click to expand...
Click to collapse
post your fastboot getvar all minus the serial no and IMEI so we can find the files you'll need to restore you phone

clsA said:
post your fastboot getvar all minus the serial no and IMEI so we can find the files you'll need to restore you phone
Click to expand...
Click to collapse
(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-ON
(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: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.120s
Here we go! thanks a lot!!

Skyrocker94 said:
(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-ON
(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: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.120s
Here we go! thanks a lot!!
Click to expand...
Click to collapse
download this ruu and run it, its the same version you already have / had on your phone, if you bootloader is unlocked then you will need to re-lock it first.
http://www.htc1guru.com/dld/ruu_m7_...9_10-26-1718-01l_release_356565_signed_2-exe/
with regards to your drivers problem, see FAQ 2 here: http://forum.xda-developers.com/showpost.php?p=52135024&postcount=2

Thanks a ton!!! i hope it works!!!

Skyrocker94 said:
Thanks a ton!!! i hope it works!!!
Click to expand...
Click to collapse
fastboot oem lock
relocks the bootloader to run the RUU
if you have problems with the RUU
try this / unlocking the bootloader / flashing TWRP 2.6.3.3 and sideload this Guru Reset >> http://www.androidfilehost.com/?fid=23501681358545274

It worked. Thank you very much!
"Ask and it shall be given to you"

same issue here, no more SO and stuck in HTC log
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
INFOversion: 0.5
INFOversion-bootloader: 1.57.0000
INFOversion-baseband: 4T.27.3218.14
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOversion-misc: PVT SHIP S-ON
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0710000
INFOcidnum: H3G__402
INFObattery-status: good
INFObattery-voltage: 4102mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-1f512bb6
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Thanks a lot for help, sorry for my English.

vanito said:
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
Thanks a lot for help, sorry for my English.
Click to expand...
Click to collapse
another H3G__402 you need help from @Danny201281
he has the same phone

vanito said:
Hello, help me please, i've search the RUU for restore my HTC but not are sure where's the right.
Here Original "fastboot getvar all" when device was working also w/o SO.
Thanks a lot for help, sorry for my English.
Click to expand...
Click to collapse
Well I'm H3G__001 UK. H3G__402 is Italy right? Not that it makes a difference the software is all the same.
Unfortunately there is no ruu for H3G. What exactly happened with your phone it can hopefully be fixed without the need for an ruu.
Bad flash, wiped your os? Can you access bootloader or recovery?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

Danny201281 said:
Well I'm H3G__001 UK. H3G__402 is Italy right? Not that it makes a difference the software is all the same.
Unfortunately there is no ruu for H3G. What exactly happened with your phone it can hopefully be fixed without the need for an ruu.
Bad flash, wiped your os? Can you access bootloader or recovery?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
this phone was w/o SO since i've buyed of 2 handle. was installed only a Custom Rom. i want make it S-OFF for installl anythingh for error from TWRP have done advanced wipe and have erase also this Rom whith all partition and BKP.
Phone enter in Recovery, hboot, fastboot and can flash RUU signed, (have tried with an BOX to flash Guru reset but Error becouse No signature), or if you have other Rom or other for fix this issue and after i want make S-OFF for change this Bad cid, if can help me please

vanito said:
this phone was w/o SO since i've buyed of 2 handle. was installed only a Custom Rom. i want make it S-OFF for installl anythingh for error from TWRP have done advanced wipe and have erase also this Rom whith all partition and BKP.
Phone enter in Recovery, hboot, fastboot and can flash RUU signed, (have tried with an BOX to flash Guru reset but Error becouse No signature), or if you have other Rom or other for fix this issue and after i want make S-OFF for change this Bad cid, if can help me please
Click to expand...
Click to collapse
Hi and sorry for the delayed reply, as I say there is no ruu for h3g, but it sounds as if you just need to push a compatible Rom to the phone, what is you current version of TWRP.
I do have some h3g stock nandroids, one for jb 4.3 and one for kk 4.4.2. I'll need to upload them for you and I can't do that until later this evening as I'm in work now. If you want to go s-off the jb 4.3 nandroid has worked for me everytime so would be worth a try. I'll upload it tonight and send you a link as soon as it's available.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

You're such a nice and friendly forum mate, @Danny201281
tetakpatalked from Nexus 7 flo

Danny201281 said:
Hi and sorry for the delayed reply, as I say there is no ruu for h3g, but it sounds as if you just need to push a compatible Rom to the phone, what is you current version of TWRP.
I do have some h3g stock nandroids, one for jb 4.3 and one for kk 4.4.2. I'll need to upload them for you and I can't do that until later this evening as I'm in work now. If you want to go s-off the jb 4.3 nandroid has worked for me everytime so would be worth a try. I'll upload it tonight and send you a link as soon as it's available.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
Not worry, important i can fix with you help this problem.
My version of TWRP installed now is "twrp-2.7.1.0a-m7" this device first of i Erase all had installed an VENOM Rom, not remember wich ViperOnes version, my Getvar All you have seen, i want listen to you becouse not understand good about these HTC w/o sd card.
If you can send to me this nandroid jb 4.3 and if please write also if i can flash how normal rom/Ruu or how do.... you help is very good for me :good:
wait for you link to download, please if cannot use Mega.co is good becouse here is blocked and impossible open this, Ciao:good:

vanito said:
Not worry, important i can fix with you help this problem.
My version of TWRP installed now is "twrp-2.7.1.0a-m7" this device first of i Erase all had installed an VENOM Rom, not remember wich ViperOnes version, my Getvar All you have seen, i want listen to you becouse not understand good about these HTC w/o sd card.
If you can send to me this nandroid jb 4.3 and if please write also if i can flash how normal rom/Ruu or how do.... you help is very good for me :good:
wait for you link to download, please if cannot use Mega.co is good becouse here is blocked and impossible open this, Ciao:good:
Click to expand...
Click to collapse
Ok sorry I was very busy last night. I am on this for you now, I'll post link as soon as it's ready but my upload seed is very poor
I created this nandroid using TWRP 2.6.3.3 but it should restore fine using other versions of TWRP.
Do you have adb working when in recovery mode? You will need it to push the nandroid to the device.

Danny201281 said:
Ok sorry I was very busy last night. I am on this for you now, I'll post link as soon as it's ready but my upload seed is very poor
I created this nandroid using TWRP 2.6.3.3 but it should restore fine using other versions of TWRP.
Do you have adb working when in recovery mode? You will need it to push the nandroid to the device.
Click to expand...
Click to collapse
Hello, can leave this version of TWRP: "twrp-2.7.1.0a-m7", that i've or you can suggest another version?
System not Mount, i've tryed to push in fastbootRUU but fail anythinghs i want push.
I've tryed putting phone in Recovery mode and i can see from "device manager" that have "adb android" or similar then if open can see "My Htc", if i put in normal mode, (is w/o Boot.img), i can see MTP that install/uninstall and phone how "Cd Unit external", (cannot open).
Not warry where upload it, important not use Mega.co becouse in Italy is Blocked, any other site is ok.
Please can send to me also Command for Push this Nandroid 4.3 in Recovery mode?, (i've also one dongle + sw but for Flash anythinghs requiere fastboot RUU mode), anyway i'm looking forward this Nandroid Bkp and how push in phone hooping that i can fix the phone

@vanito backup done with TWRP 2.6.3.3 is compatible with 2.7.1.0
He is asking you about ADB and using command line of your PC to push the files. Do you know how to do it? Do you have SDK installed on your PC?
tetakpatalked from N7100

vanito said:
Hello, can leave this version of TWRP: "twrp-2.7.1.0a-m7", that i've or you can suggest another version?
System not Mount, i've tryed to push in fastbootRUU but fail anythinghs i want push.
I've tryed putting phone in Recovery mode and i can see from "device manager" that have "adb android" or similar then if open can see "My Htc", if i put in normal mode, (is w/o Boot.img), i can see MTP that install/uninstall and phone how "Cd Unit external", (cannot open).
Not warry where upload it, important not use Mega.co becouse in Italy is Blocked, any other site is ok.
Please can send to me also Command for Push this Nandroid 4.3 in Recovery mode?, (i've also one dongle + sw but for Flash anythinghs requiere fastboot RUU mode), anyway i'm looking forward this Nandroid Bkp and how push in phone hooping that i can fix the phone
Click to expand...
Click to collapse
twrp 2.7.1.0 should work fine :good:
adb will only work in recovery mode. Put phone in recovery and connect usb. Then in the adb/fastboot command line type
Code:
adb devices
You should see an output of your phone's serial no. If you did it's working. You can test adb push with a Rom if you have one. Rename the Rom file to "rom.zip" and put it in your adb/fastboot folder. Then in the command line type
Code:
adb push rom.zip /sdcard
The push will take several minutes the command window will be unresponsive until it's done. When it's finished the push you should be able to Install the Rom using TWRP.
P.S. The stock nandroid is uploading to dropbox. This is ok for use in Italy?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk

@vanito you have got a real little guide for Windows by @Danny201281
In the case that you are a Linux user, it works just slightly different: in such case check my little thread about running fastboot & ADB in Ubuntu. It is posted in the Nexus 7 section but ADB works for Samsung just the same way.
tetakpatalked from Nexus 7 flo

Danny201281 said:
twrp 2.7.1.0 should work fine :good:
adb will only work in recovery mode. Put phone in recovery and connect usb. Then in the adb/fastboot command line type
Code:
adb devices
You should see an output of your phone's serial no. If you did it's working. You can test adb push with a Rom if you have one. Rename the Rom file to "rom.zip" and put it in your adb/fastboot folder. Then in the command line type
Code:
adb push rom.zip /sdcard
The push will take several minutes the command window will be unresponsive until it's done. When it's finished the push you should be able to Install the Rom using TWRP.
P.S. The stock nandroid is uploading to dropbox. This is ok for use in Italy?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
Click to expand...
Click to collapse
@Danny201281, ok i have this twrp 2.7.1.0 also and can install replace the other one i've installed:good:
Yes i've installed adb&fastboot in C: (principal directory), i use Win7 32 bit and can use also win Xp in the 2 pcs i've adb&fastboot installed.:good:
Yes, i know a little about use of these adb or fastboot, specific command for this case i can copy from this you good guide:good:
I've tested pushing "guru reset..." from fastboot yesterday but have get one Error 24, not have tested pushing via Adb command, but now i see you command above and can test this.
Sorry, i not know which Rom can push and if you can advise me about wich push is big help, (if you can post only link to Rom) for me, if possible any Rom for to make S-Off after that i fix this phone.
Yes, Dropbox i can use here if you give me access for download the Nandroid Bkp 4.3.
Last question, if push of Rom goes all ok, after i open phone in recovery and find this Rom in Sd Card, right?...then from "Install>Sd Card>Rom" swipe and will be installed right?
Ok, after i install this Rom always from recovery can install you nondroid bkp 4.3, ok?, :good:
I'm ready if can send to me link for this Rom and Link of dropbox i want try to ceck anythinghs.

[Q] Applying Backup from one phone to another

Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel

Happyhog11 said:
Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel
Click to expand...
Click to collapse
first of all post your fastboot getvar all of the phone that says this is a test device please, remove imei and serial number before posting please, sounds s-off to me, and that's a good thing.

Happyhog11 said:
Hi Guys,
This might be a little confusing but i will do my best.....About 6 months ago i bought a htc 1 m7, love it and it worked well. Then i decided to root it which was fine but then the OTA update came out so i can make phonecalls again, but i cant install it. Spur of the moment i bought another htc one m7 of ebay because i desperately needed to make and take calls. Turned up a couple of days ago and there seems to be some interesting stuff going on. Firstly i think it is a "test device" I cant remember where but somewhere it does say that its a test device in red writing.Also compared to my old phone the screen is more "brown" as if a filter is being applied. I'm guessing a non-oem screen was fitted that isn't as good quality as the original. I checked and the bootloader is locked and is working but it is still on android 4.4.2 and sense 5.0 and it says its up to date and wont move to sense 6.0.
So currently i'm looking for a way to either "un-test device" the new htc 1 m7 as im guessing that's why its not getting the new updates, or secondly is there anyway to get the ota updates on the rooted htc 1? I'm fairly good tech guy but...being my first android phone i guess you guys would call me a noob.
One other thought i had. If i could get the new phone to update to the latest update and then i rooted it, installed cmw and did a backup could i then load that backup as a recovery on my old phone? I'm not sure if that would work or not.....
Anyway hope you guys can help me out, i dont really care which phone i end up using one has a cracked screen and the other dose not look the best i just want to have the latest updates AND be able to make phonecalls...
Thanks All,
Joel
Click to expand...
Click to collapse
Ok there's a few reasons why you may not be receiving OTA updates on the first device.
The second device (test device) Sounds like it's s-off that's not something you want to fix there are many benefits to having the device s-off. As for transferring backups between devices that should be fine as long as their both of the same model id. To be sure of all this can you please post the output of
Code:
fastboot getvar all
For both devices :good:

Hi Guys
So here is the code for the old phone.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3814mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
As for the new phone, surprisingly out of the blue today it notified me it needed a update to fix the audio so i let it start downloading but my internet is awfully slow so i cant turn it off for another 4 hours. After the update is finished i will post the fastboot stuff asap
Have to look into this s-off thing some more. I have no idea what it means but it sounds interesting
Thanks Again
Joel

Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel

Happyhog11 said:
Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel
Click to expand...
Click to collapse
first of all, remove imei and serial numbers from your outputs in your 2 posts, these are 2 numbers you want to keep to yourself, the s-off phone is the better one and easier to work with, leave it s-off, don't ever go s-on, you will regret it, you can follow this very simple step by step guide to get this phone receiving updates again, all the way upto lollipop: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311 you will need to unlock the bootloader first though to do this.

Happyhog11 said:
Hi Again,
It just finished the update so here is the code for the new phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.11.980.12
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__039
(bootloader) battery-status: good
(bootloader) battery-voltage: 3969mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
You guys were right it is s-off but the bootloader is locked which is interesting. And they have the same model id so i can copy backup's between devices which is also cool.
So Danny you said there could be a number of reasons why my old htc is not getting the ota update, care to elaborate? i have the actual update file which is a zip saved on my pc, i just figured because it was rooted and has a different recovery than stock the ota would continue to fail, if there is a way to get it to work that would be awesome, as it would mean i wouldn't loose all my apps compared to restoring a backup from the second phone.
Cheers Guys,
Joel
Click to expand...
Click to collapse
Well I was first thinking maybe it was AT&T and AT&T phones only get OTA's when connected to the AT&T network but that's not the case here.
Are both devices running a the same stock rom. As they are identical you could just make a nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data. Could you maybe post a screen shot of the Settings>About>Software information screen from each of the devices?

It's not that it cant "get" the ota updates its more that it wont install.
Also I'm in Aus, as for the first phone it was bought outright through a retailer and i have no idea for the second phone(eBay guy didn't leave any history about the phone.)
I have just put cmw on the new phone so now i can do the guide posted by Seanie280672.
Will post the screenshots in a sec.
Will need your help with making a backup of just the boot and system partitions......don't know how to do that.
Joel

Okay This is the "old phone" screenshot:
https://drive.google.com/file/d/0B5yAH_RjUp-KQmU2bkJfUVlINXc/view?usp=sharing

Okay here is the screenshot for the new phone
https://drive.google.com/file/d/0B5yAH_RjUp-KcmRIUjZIOVN2TU0/view?usp=sharing
Also sorry Google drive was the quickest way to get pictures online from my laptop at the moment.
Only difference is the software number the old phone is x.x.x.7 not x.x.x.12 which im guessing is the update to fix audio.
Not sure if it is relevant but i have the file "OTA_M7_UL_K443_SENSE60_MR_Optus_AU_6.11.980.12-6.11.980.7_release_407474r14kwjhfpdkw8z4t" Thats the update file that the old phone downloaded to fix audio which would make it identical to the new phone, but alas it dose not install.
So i guess the "nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data" is still the best solution?
Thanks again i know i say that alot but could not have done this without your help!
Joel

Wait....i was of the belief that cmw was the reason i couldnt install ota's. Is that correct? If so what if i just put the original stock recovery back on the old phone(link http://forum.xda-developers.com/showthread.php?t=2158151) then let the update install and then put cmw back on..... i dont know if it will work but its another method, maybe i have this all back the front lol

Happyhog11 said:
Okay here is the screenshot for the new phone
https://drive.google.com/file/d/0B5yAH_RjUp-KcmRIUjZIOVN2TU0/view?usp=sharing
Also sorry Google drive was the quickest way to get pictures online from my laptop at the moment.
Only difference is the software number the old phone is x.x.x.7 not x.x.x.12 which im guessing is the update to fix audio.
Not sure if it is relevant but i have the file "OTA_M7_UL_K443_SENSE60_MR_Optus_AU_6.11.980.12-6.11.980.7_release_407474r14kwjhfpdkw8z4t" Thats the update file that the old phone downloaded to fix audio which would make it identical to the new phone, but alas it dose not install.
So i guess the "nandroid of the System and Boot partitions from the s-off device then restore these to the other device without loosing any user data" is still the best solution?
Thanks again i know i say that alot but could not have done this without your help!
Joel
Click to expand...
Click to collapse
Ok this may get a little complicated but I'll try to make it as clear as possible
You can use the system and Boot nandroid from the s-off device to update the Rom on the s-on device. Then make a full nandroid backup of the s-on device of System, boot and data. (so now you have a nandroid of the updated Rom with all your apps and settings) now backup the internal storage of the s-on device to your pc.
Now you can extract the firmware.zip from the OTA file and manually flash the firmware to the s-on device to update the firmware. This will require you to relock the bootloader and when you unlock the bootloader the device will be wiped (that's the reason we backup the internal storage to the pc) so you can Unlock the bootloader again restore the internal storage with your pc backup then Flash twrp and restore the nandroid and heypresto the s-on device is fully updated with Rom and Firmware. If you need further instruction on how the flash the firmware from the OTA just let me know
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
Happyhog11 said:
Wait....i was of the belief that cmw was the reason i couldnt install ota's. Is that correct? If so what if i just put the original stock recovery back on the old phone(link http://forum.xda-developers.com/showthread.php?t=2158151) then let the update install and then put cmw back on..... i dont know if it will work but its another method, maybe i have this all back the front lol
Click to expand...
Click to collapse
Yes that's correct if you flash the stock recovery you should be able to install the ota. Although if the stock Rom is modified in some way the OTA may fail to install.

Danny201281 said:
Ok this may get a little complicated but I'll try to make it as clear as possible
You can use the system and Boot nandroid from the s-off device to update the Rom on the s-on device. Then make a full nandroid backup of the s-on device of System, boot and data. (so now you have a nandroid of the updated Rom with all your apps and settings) now backup the internal storage of the s-on device to your pc.
Now you can extract the firmware.zip from the OTA file and manually flash the firmware to the s-on device to update the firmware. This will require you to relock the bootloader and when you unlock the bootloader the device will be wiped (that's the reason we backup the internal storage to the pc) so you can Unlock the bootloader again restore the internal storage with your pc backup then Flash twrp and restore the nandroid and heypresto the s-on device is fully updated with Rom and Firmware. If you need further instruction on how the flash the firmware from the OTA just let me know
---------- Post added at 04:02 PM ---------- Previous post was at 03:59 PM ----------
Yes that's correct if you flash the stock recovery you should be able to install the ota. Although if the stock Rom is modified in some way the OTA may fail to install.
Click to expand...
Click to collapse
Okay your method sounds like a fun experience, as long as your sure my data is safe . Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great

Happyhog11 said:
Okay your method sounds like a fun experience, as long as your sure my data is safe [emoji14]. Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great
Click to expand...
Click to collapse
Yeah my instruction kinda assumes you are using TWRP recovery [emoji14] no one uses CWM on HTC one anymore. TWRP if a far better recovery for best results use TWRP 2.6.3.3 other newer versions all have some bugs of some sort. 2.6.3.3 is bug free and stable :good:

Happyhog11 said:
Okay your method sounds like a fun experience, as long as your sure my data is safe . Will do a manual backup first anyway. As for the nandroid stuff tho...im allitle confused. with cmw there are not any options to what is included and excluded? or am i missing somehting......Sorry for the noob question.
And yes please i have no clue how to flash firmware, guess you just use fastboot? help would be great
Click to expand...
Click to collapse
Edit: this is possible with cmw or do i need to swap to twrp? Also as for the firmware is that just the zip called "firmware.zip" inside the ota zip? what do you do with the images inside? Shame on htc for putting a zip in a zip its just plain bad practice lol

Happyhog11 said:
Edit: this is possible with cmw or do i need to swap to twrp? Also as for the firmware is that just the zip called "firmware.zip" inside the ota zip? what do you do with the images inside? Shame on htc for putting a zip in a zip its just plain bad practice lol
Click to expand...
Click to collapse
Ok this is what I was afraid of when I said it might get complicated.
So first unfortunately I'm really not sure what CWM is and is not capable of these days I have not used it for about 4 years lol, since my galaxy ace days. Either way I would definitely recommend switching to twrp for your HTC one. Although you will need to make new nandroids if you do as TWRP is not compatible with CWM backups as far as I'm aware. TWRP allows you to backup and restore partitions separately.
You are correct about the firmware.zip inside the OTA file just extract the firmware.zip from the OTA and then you can flash the firmware.zip with fastboot. You must be sure you update the Rom before the firmware though or the phone won't boot after flashing the firmware. This is not an unrecoverable situation but will further complicate matters.
To manually update the firmware put the firmware.zip in your fastboot folder.
Boot the phone to the bootloader connected with fastboot usb. In the command window type.
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Your device will reboot to the bootloader and should now be ***RELOCKED***
Code:
fastboot oem rebootRUU
**--- Case sensative ---^^^
Your device should boot to a black screen with a Silver HTC logo. This is RUU mode. We can now flash the firmware. In the command window type
Code:
fastboot flash zip firmware.zip
The first flash will be short, and will appear to fail. Thats normal its just a pre update preparing the hboot for the firmware. The phone screen will go black then return to RUU mode. So now we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal. As long as the command window has finished its output its done. Reboot to the bootloader.
Code:
fastboot reboot-bootloader
Just for the record if the device was s-off like the other one there is never any need to relock the bootloader as s-off allows flashing while unlocked.

Okay super quick question. I'm trying to flash twrp onto one of the phones but how do i use adb/fastboot with multiple devices plugged in? cant figure it out.....the other device is being backed up.

Happyhog11 said:
Okay super quick question. I'm trying to flash twrp onto one of the phones but how do i use adb/fastboot with multiple devices plugged in? cant figure it out.....the other device is being backed up.
Click to expand...
Click to collapse
Fastboot should only see the device that's in the bootloader.
E.g if one device is booted to Android or Recovery (this will be the device your backing up) only adb should see this device.
So you can flash twrp to the other device while in the bootloader with fastboot
Code:
fastboot erase cache
fastboot flash recovery "name-of-recovery".img
fastboot reboot-bootloader

So just so I'm sure we are on the same page I'm going to:
1. System/Boot Nandroid from s-off device
2. System/Boot/Data Nandroid from s-on device
3. Backup files from s-on device to pc
4. Follow your steps flash firmware updates.
5. Copy Files back to phone
6. flash twrp back onto device
7. Restore The nandroid from step 2
8. Heypresto my s-onn phone now has the latest firmware and all my data just as before?
Hope i've got that right makes sense really

Okay so I've flashed twrp onto both phones, backup of the s-off is complete, backup of the s-off is ongoing.
This...i have to say is uber cool. Having two identical phones is going to be super fun when it comes to custom roms and backups and stuff like that, if one phone dies ill just apply the back to the other...super cool stuff

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.