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 !

As if I'd never touched it

Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe

smartiejoe said:
Is there a way to make it so my HTC One is back to complete factory settings. I want it back as if I'd never touched it. Unrooted, locked, S-ON, HTC Sence, stock firmware, etc.
I'm not so great at all this stuff, so some simple instructions rather than just a tonne of links would be great! Eg. flash this, do this, install this recovery, etc.
Thanks,
Joe
Click to expand...
Click to collapse
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI

alray said:
Maybe you should start by describing what you did to your phone? Also post the output of fastboot getvar all except IMEI
Click to expand...
Click to collapse
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(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: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s

smartiejoe said:
First off, it is rooted, has twrp recovery, a 4.4 GPE ROM and is S-OFF.
I'll get the fastoobt getvar all results for you.
C:\Minimal ADB and Fastboot>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.16.3250.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.17.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT368W908963
(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: 3661mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae095083bf
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.

alray said:
you want to return it to stock like if you had never touched it.. So you want stock software, locked bootloader and S-ON ? If you are not sending your phone for a repair under warranty, I'll recommend you to keep unlocked bootloader and S-OFF or at least locked bootloader but S-OFF. Do you want to be on latest stock version? If yes then its almost impossible to s-off again on hboot 1.56.
What is your goal to restore your phone back to 100% stock?
Also need to know what operating system is on your computer.
Click to expand...
Click to collapse
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.

smartiejoe said:
Just in case I do need to send it off for repair or replacement, I don't want a tampered device. Just don't want that risk. I'm running WIndows 7.
Click to expand...
Click to collapse
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.

S-OFF is a gift and should never be taken for granted. If you throw it away it may not be available to you again.
S-ON is an operation I would defer until I learned that I actually *need* to send in the phone to someone who cares if it is S-ON or not.
S-ON is always the last step in any "going back to stock " process, the very last thing before the phone leaves your possession. And even then the step is usually optional. Warranty repair people often don't care, eBay doesn't care, it's just really rare that there is *any* actual benefit.
Sent from my HTC One using xda app-developers app

alray said:
You should keep s-off unless really necessary, not ''just in case''. If you need to send your phone for repair in the future, with s-off, you'll be able to remove the tampered flag and s-on again before sending it back to repair. But atm turning back S-ON is the risk you should not take imo.
Again if you go back to stock and update your phone to the latest version then it will be very difficult or even not possible to s-off again.
Im waiting your decision to guide you.
Click to expand...
Click to collapse
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible. Decent battery life, decent speed, and not too much hassle to return to complete stock if necessary.
I'll take your advice on what you think is best!

smartiejoe said:
Okay, I think I'll stick with S-OFF, I just want a really stable build, as close to stock as possible.
Click to expand...
Click to collapse
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
smartiejoe said:
not too much hassle to return to complete stock if necessary.
Click to expand...
Click to collapse
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.

alray said:
You can use the stock RUU for your phone version, so you'll be 100% stock rom but with s-off and unlocked bootloader
Easy to do with S-OFF
So you can use the latest RUU for your phone which you can find here
this will make your phone 100% stock (except s-off and unlocked bootloader). This will wipe everything on your phone so be sure to backup your media and personal data before on your computer.
download the exe file (about 1.5Gb)
plug your phone to your computer ( I assume your htc drivers are already installed correctly, if yes, your device is listed as ''My HTC'' in windows device manager)
launch the ruu.exe and follow instructions.
Click to expand...
Click to collapse
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe

smartiejoe said:
Hi there,
I downloaded the RUU and ran it and followed all instructions but it encounters an error every time. It doesn't give any information on what the error is, it just stays on the silver HTC logo and the software says it has failed. It doesn't get stuck in a bootloop though.
Thanks,
Joe
Click to expand...
Click to collapse
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551

alray said:
MD5 check the ruu file and make sure it match, if not download it again.
MD5: 9ad4111ce86981e3dffcce6d9ee80551
Click to expand...
Click to collapse
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?

smartiejoe said:
Hi,
I redownloaded it and ran it and it has been stuck on "0/5 sending" for the last 20 minutes or so, the interface says the whole process should take 10 minutes, is this normal?
Click to expand...
Click to collapse
have you checked md5?
Maybe you could try another usb cable or another usb port

alray said:
have you checked md5?
Maybe you could try another usb cable or another usb port
Click to expand...
Click to collapse
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further

smartiejoe said:
I checked MD5 and that was all fine, I'm using a different port and now it sits on "updating (1/5) Checking Header..." for ages and I've not yet seen it move any further
Click to expand...
Click to collapse
Try another usb cable. You could also try the 1.28.401.7 ruu

alray said:
Try another usb cable. You could also try the 1.28.401.7 ruu
Click to expand...
Click to collapse
I just read somewhere that hboot 1.44 might be needed, and I have 1.54. So I shall flash 1.44 and see if it works then!
EDIT: When trying to flash hboot 1.44 it won't even send the 501kb zip file, even through a brand new usb cable. Updating drivers now to see if that works

[Q] HTC One M7 firmware help!

Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!

When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?

aooga said:
When does it fail mounting system? When flashing a ROM in TWRP or flashing an RUU?
Click to expand...
Click to collapse
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.

olimoh8464 said:
it seems to be both. I try to flash RUU via fastboot and I get a signature fail. So I try to flash a ROM to the phone and it says failed to mount system. I put the items on a usb and tried it but get an 'unable to unzip' error. Its a bit above me to be honest. Thank you so much for helping.
Click to expand...
Click to collapse
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...

Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?

olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
... run it from desktop while phone in bootloader. no need to run boot image ...

olimoh8464 said:
When you say run the RUU to you mean the RUU from the desktop or directly from the phone? How do I know if I have the correct RUU? the closest one I could find was for O2 and the radio was the same down to the last digit being different. Sorry for sounding stupid but it is a lot to take in for such a noob. I read that I need to flash a boot recovery image and then run the RUU is that right?
Click to expand...
Click to collapse
RUU must match your CID number.
I add you here link to a good thread:
http://forum.xda-developers.com/showthread.php?t=2358738
tetakpatalked from Nexus 7 flo

Devilish_Angel said:
... buddy when bootloader is unlocked and phone s-on, no ruu will work. now for ruu to flash you need to relock the bootloader and then run ruu. it will surely flash :victory: ...
Click to expand...
Click to collapse
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk

Thank you for the advice and the link! I will go try this now and let you know how I get on!

aooga said:
This is wrong. You can flash the ruu that mathches the cid and mid of your phone even with a locked bl.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
... did i say something different than what you are saying ...

@aooga Angel's point was S-On, I think.
tetakpatalked from the legendary i9000

olimoh8464 said:
Hey guys,
Sorry if I am in the wrong place for this question but I am completely stuck. I recently bought a HTC One M7 which was rooted. I did not know this when I was buying it. The new update came out and my phone asked me to update. I hit yes. My phone switched off and didn't come back on. After extensive research I got it back on to find the following:
1) It was rooted
2)Bootloader started up and TWRP is on the phone
3) There is now nothing on the phone. No firmware or packages at all
4) When I try to flash anything I get the error message: can't mount to system. I can mount to everything else ok just not internal storage.
I am unsure what recovery image and RUU to use. The phone (I was told was unlocked) was O2(Giffgaff).
Details are:
***Tampered***
***Unlocked***
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
Radio-4A.21.3263.04
OpenDSP-v32.120.724.0909
OS-3.62.206.1
eMMC-boot 2048MB
Oct 18 2013, 00:29:38. 0
IMAGE CRC
rpm: 0xC5567FC
sbl1: 0x9FE7A28C
sbl2: 0XA915A4DD
sbl3: 0xB221B6BB
tz: 0XCCD5DF62
radio: 0XEFA42613
hboot: 0xC174663B
boot: 0x94C89910
recovery: 0x59BF6CD
system: 0xFF83AB1
Any help at this stage would be greatly appreciated! I am about to just give up and bin it...
Thanks in advance!
Click to expand...
Click to collapse
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app

Devilish_Angel said:
... did i say something different than what you are saying ...
Click to expand...
Click to collapse
Uh..yeah. You said:
when bootloader is unlocked and phone s-on, no ruu will work
Click to expand...
Click to collapse

bored_stupid said:
Post a fastboot getvar all
RUU.exe files or ROM Update Utility files are executable files that run on Windows PC
RUU.zip files are simply the same as above but rather than using a Windows exe file to run them, they are packaged in a zip file that can be flashed in Fastboot mode
The RUU has to match your CID/MID. If your S-On, the RUU as to be same version or higher
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?

olimoh8464 said:
Thanks! Is there any way you could tell me the correct RUU to download? I will post a fastboot getvar all after work this evening. I tried one that I thought was right but when I click to run it as administrator I get prompted with the normal are you sure? click yes and nothing happens. It just doesn't run. Tried downloading it again but still nothing. Any ideas?
Click to expand...
Click to collapse
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
Yeah no problems. Off to work myself now, but will post correct link if any and possible other solutions.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
C:\Users\milo\Desktop\Newest>fastboot getvar all
(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.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(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!
finished. total time: 0.047s

OMG My phone literally did the same exact thing today!! I woke up, a few things were force closing so I decided that I would just reboot the phone...... Big mistake, once I did that, the phone just stayed in the booting up animation. So I figured hey what ever ill just reflash the ROM in TWRP.......Nope, couldn't boot into recovery either, the phone would flash the TWRP screen then just reset itself. Again, I thought no biggie ill just reinstall TWRP. This (again) proved to be useless, after multiple (successful) install's the phone still refused to boot into TWRP. So I finally got CWM to install, a noticed a few things at the bottom of the screen about something not being mounted properly, I didn't pay that much attention to it, i just wanted my phone back at that point. I tried to wipe my phone for a fresh flash, but as soon as the wipe began the phone reset itself. At this point I was on the brink of throwing this thing into the torrential down-pour that god decided to place in my city.
Next I tried to install Viper ROM because I knew it had a wipe functionality built into it's Aroma installer. Went through all the checklists got to the start install screen, clicked next, and then began to wipe......... and then reset again........
So finally I got TWRP reinstalled, and go install a fresh ROM and and immediately met with a screen full of : "Unable to Mount XXXXXXX" (Picture attached). So then I figure alright well my last resort has to be to use a RUU. Found this nice little thread (http://forum.xda-developers.com/showthread.php?t=2316726) and decided to use the FUU (4.19.401.11 Full Wipe). Unfortunately all that did was move my HBoot from 1.4 (or something like that) to 1.5 (or something like that), put the tamper flag back, and bring back the annoying red text at the bottom of the phone at boot (the thing about development build, blah blah blah). I reinstalled TWRP yet again hoping for the best, but still nothing. It cant seem to mount anything (what ever that means).
So now im here, stuck using my old One X. Any suggestions or answers or criticism would be very much appreciated.
Thank you!!!!!

olimoh8464 said:
C:\Users\milo\Desktop\Newest>fastboot getvar all
(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.62.206.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA366W900013
(bootloader) imei: 3578640********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3965mV
(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!
finished. total time: 0.047s
Click to expand...
Click to collapse
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app

bored_stupid said:
This is the RUU.exe you require. Run from PC
http://www.htc1guru.com/dld/ruu_m7_..._10-38r-1157-04l_release_353143_signed_2-exe/
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks

olimoh8464 said:
Thanks for that! I have downloaded it and tried to run it but it doesn't open? I get the loading message after I click run as administrator but nothing happens. Do I need HTC sync installed or deleted for this?
Thanks
Click to expand...
Click to collapse
Did you check the MD5
4961fdbbadba53c9640f3638f56faec1
When you say nothing happens.. Doesn't it even try to run?
Sent from my HTC One using XDA Premium 4 mobile app

So confused - OTA Updates & Rooted/Modified M7 - please help!

Hi all,
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
What I've tried:
Getting S-OFF (no luck whatsoever with any tools)
Flashing stock recovery and kernel
Flashing stock recovery and kernel and applying the OTA manually via recovery
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update.
Someone, please guide me in the right direction! Step by step maybe?
Keep in mind there is no way I can't get S-OFF.
Huge thanks to anyone that can help. I'd be eternally in your debt!!

SmokinWaffle said:
My girlfriend has a HTC One M7, currentley Rooted with an Unlocked bootloader, Bulletproof Kernel, CWM Recovery, S-On (can't get S-OFF no matter what I try) and running the stock 4.4.2 Sense ROM that came with the phone.
She wants to install an OTA update, obviously this won't work with the phone in it's current state. I've got experience with all of this with my Note II, but the M7 is just a whole different can of worms.
Click to expand...
Click to collapse
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
What I've tried:
Getting S-OFF (no luck whatsoever with any tools) Any error message when trying to S-OFF? You must use the correct tool for your hboot version (probably firewater) + combination of the correct rom + kernel
Flashing stock recovery and kernel --> You must have stock recovery for ota, ota will not install using a custom one.
Flashing stock recovery and kernel and applying the OTA manually via recovery --> appyling the ota manually from stock recovery require s-off
Click to expand...
Click to collapse
I've read everything on here and nothing seems to go in. She just wants to be able to install OTA updates, even if it means unrooting her phone permanently as this will happen each time there is an OTA update
Click to expand...
Click to collapse
.
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Keep in mind there is no way I can't get S-OFF.
Click to expand...
Click to collapse
still not sure about this, unless you get the "whelp" message from firewater...
post the output of fastboot getvar all except the imei number and serialno

alray said:
I suppose the phone is trying to apply to ota update and then show a red triangle with an exclamation mark inside?
Click to expand...
Click to collapse
Yep!
alray said:
http://forum.xda-developers.com/showpost.php?p=52894276&postcount=9
http://forum.xda-developers.com/showpost.php?p=53151895&postcount=23
Click to expand...
Click to collapse
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
alray said:
still not sure about this, unless you get the "whelp" message from firewater...
Click to expand...
Click to collapse
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
alray said:
post the output of fastboot getvar all except the imei number and serialno
Click to expand...
Click to collapse
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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(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: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.

SmokinWaffle said:
Yep!
Interesting. I don't have the phone with me at the moment and it's late but I'll try to do the POWERUP + VOL tomorrow at some point, I'll get her to try stock recovery + kernel then do it and see what it's stopping at.
Didn't get that message, just keeps going indefinetley or stops, and doesn't S-OFF. Tried Firewater, Revone, RumRunner, if there is another then I've almost certainly tried it, followed all the guides including the one that flashed Android Revolution...no idea..
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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: [I]XXXXXXXXXXXX[/I]
(bootloader) imei: [I]XXXXXXXXXXXXXXX[/I]
(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: 3798mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
Thanks for the prompt reply, really appreciate it and any help you can give.
Click to expand...
Click to collapse
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752

alray said:
your version-main? (rom version) Go in settings --> About --> Software info --> Rom version
maybe there is a ruu you could use to restore the phone(4.19.401.9), if it match your version
---------- Post added at 04:40 PM ---------- Previous post was at 04:35 PM ----------
you can also flash the stock 5.11.401.10 rom, recovery and firmware available on ARHD website
http://android-revolution-hd.blogspot.ca/p/android-revolution-hd-mirror-site-var.html
http://forum.xda-developers.com/showthread.php?t=2224752
Click to expand...
Click to collapse
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
I'm guessing the ARHD steps are to try to get S-OFF?

SmokinWaffle said:
4.19.401.11
What exactly is the function of the RUU? I can't seems to get my head around it..
Click to expand...
Click to collapse
forget the ruu, your phone version is higher than the ruu. flashing a ruu (4.11.401.10) with a lower version than on your phone(4.11.401.11) require s-off.
I'm guessing the ARHD steps are to try to get S-OFF?
Click to expand...
Click to collapse
No, this is the latest stock rom(5.11.401.10) for your phone model (MID: PN0710000 and CID:HTC__001) including android 4.4.2 and sense 6.0
You can flash this stock odexed rom(5.11.401.10) from custom recovery, then flash the stock recovery(5.11.401.10) over the custom one and your phone will be stock and ready to take future ota update. You may also want to update firmware to 5.11.401.10

So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved

SmokinWaffle said:
So after flashing that rom and stock recovery, ota would be ready to roll? Would the kernel matter?
Click to expand...
Click to collapse
stock kernel in included in the rom (boot.img) so if you don't flash any other kernel it should be fine.
What's the purpose / Difference of firmware and how is it updated? On my note II it was just choose a rom choose a kernel and off you go. This is so much more involved
Click to expand...
Click to collapse
firmware is all the low level code required for your phone hardware to works with the software (OS)
when speaking about HTC phone, firmware.zip include HBOOT(bootloader), BOOT(kernel), Recovery, Radio and some other stuff. if you want your phone to be 100% stock you need both stock rom + stock firmware to match the same version i.e 5.11.501.10
normally, the firmware is updated at the same time the rom version is updated (from an ota update) If you flash a rom, the rom will be updated but not the firmware.
Updating the firmware manually can be dangerous is you don't know what you are doing and flashing the wrong file. You can update firmware using this command from bootloader (with the correct firmware.zip package in the same folder you have adb and fastboot):
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
also it looks like flashing a 5.x.xxx.x firmware over a 3.x.xxx.x firmware will brick your phone. from what i see, your phone should be on a 4.x.401.x version at the moment, so it theory it should be fine.

Fails on:
>>>setting permissions
set_metadata_recursive: some changes failed
E:Error in /data/media/0/one_5.11.401.10_odexed.zip
(status 7)
Tried 3 different versions of cwm. Bad rom download?
Thinking about it I just re read your above post, could it be because the firmware isn't matched? I read your 'it should be fine' as 'dont update the firmware' not 'its fine to update' which I think is what you meant...
Firmware is 4.19.401.11 however the rom is 5.11.401.10. Can't believe I overlooked this, guess firmware needs to be 5.11.401.10 for the rom to take?

SmokinWaffle said:
Tried 3 different versions of cwm. Bad rom download?
Click to expand...
Click to collapse
No you are using CWM thats the problem. always use TWRP 2.6.3.3

alray said:
No you are using CWM thats the problem. always use TWRP 2.6.3.3
Click to expand...
Click to collapse
Huh?
Is this a requirement of ARHD or....?
Just seems odd
Edit: success!! All seems to work. Thank you. She's overjoyed!!!

GPE no OTA update from 5.0.2 to 5.1

So I noticed that 5.1 came out for the GPE M7 around 2 months ago and I still haven't received my OTA update. Interestingly, all the articles I see mention it being an update for 5.0.1.... my GPE is on 5.0.2. Is that why I never received the update? If not, did I just miss it and they stopped pushing it or something? Where can I go from here to get the update OTA or otherwise? 5.0.2 has been horribly buggy from the start and my device is getting worse and worse as time goes on. I really need this update!
fyi, I did already post in the beginners thread and got no replies so I figured it may warrant its own thread.
Thanks!

mkid89 said:
So I noticed that 5.1 came out for the GPE M7 around 2 months ago and I still haven't received my OTA update. Interestingly, all the articles I see mention it being an update for 5.0.1.... my GPE is on 5.0.2. Is that why I never received the update? If not, did I just miss it and they stopped pushing it or something? Where can I go from here to get the update OTA or otherwise? 5.0.2 has been horribly buggy from the start and my device is getting worse and worse as time goes on. I really need this update!
fyi, I did already post in the beginners thread and got no replies so I figured it may warrant its own thread.
Thanks!
Click to expand...
Click to collapse
flash the 5.1 gpe ruu, will update your phone and set everything back to stock, backup your files before.

alray said:
flash the 5.1 gpe ruu, will update your phone and set everything back to stock, backup your files before.
Click to expand...
Click to collapse
Is that my only option now? Why did I not get the OTA update that others did?

mkid89 said:
Is that my only option now? Why did I not get the OTA update that others did?
Click to expand...
Click to collapse
Are you 100% stock gpe rom or not?
Post the output of "fastboot getvar all" (remove imei / sn before posting)

I bought this device used on ebay so I'm not 100% sure the history of it. I bought it as a GPE device and it even came with the google branded box (not a carrier box). I also received the 5.0.2 update OTA so it seems legit.
I'm at work right now and they disable the USB ports on our PCs here but I can run the adb command later if still necessary.

mkid89 said:
I bought this device used on ebay so I'm not 100% sure the history of it. I bought it as a GPE device and it even came with the google branded box (not a carrier box). I also received the 5.0.2 update OTA so it seems legit.
I'm at work right now and they disable the USB ports on our PCs here but I can run the adb command later if still necessary.
Click to expand...
Click to collapse
Afaik, there never was any 5.0.2 version for GPE, only 5.0.1 and then updated to 5.1
Yep post the "fastboot getvar all" later when you can, meanwhile go in settings --> about --> software info --> more. what is the build number?

I'm definitely on 5.0.2. Says so in the same section. I also don't see any information on an update for 5.0.2 for GPE M7 so I have no idea how I got it OTA.
Build #: LRX22G.H100 release-keys

alray said:
Post the output of "fastboot getvar all" (remove imei / sn before posting)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.100
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1c33e16c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s

mkid89 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.100
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3833mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1c33e16c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
Click to expand...
Click to collapse
Strange, first time I see 5.11.1700.100. I know 5.11.1700.3 which is 5.0.1 and 6.04.1700.6 for 5.1.
And the ota update for 5.1 is from 5.0.1 to 5.1 (from LRX22C to LMY47O)
Is the bootloader still locked and no tampered flag? Maybe you should s-off the phone and update manually to 5.1

alray said:
Is the bootloader still locked and no tampered flag? Maybe you should s-off the phone and update manually to 5.1
Click to expand...
Click to collapse
still says "*** LOCKED ***" and says "M7_UL PVT SHIP S-ON RH" right below
So did I end up with some leaked OTA update or something that wasn't actually supposed to go out? Maybe that explains why my phone is so buggy now.
If I s-off and manually update I will lose everything right since there is no update from 5.0.2 to 5.1?

So I've managed to unlock the phone, installed custom recovery but I can't get S-Off which I believe is needed to flash the stock RUU back on.
Rumrunner and moonshine both fail... probably because my phone is on some weird rom/kernel that no one has ever planned for.
Is there a way to get S-Off without these utilities? Is there a different way to get back to a stock GPE RUU with OTA that doesn't require S-Off?
I thought about maybe flashing the 5.1 GPE rom and then trying to use rumrunner on that. After getting S-Off, I'd revert back to a stock GPE RUU setup to have OTA updates and hope I don't end up with this 5.0.2 update again. What do you guys think? At this point I'm almost considering just flashing the GPE+ rom and not worrying about OTA updates. I'd just hate to have to lose all my stuff every time I need to update the rom (if the developer even decides to continue updating it)

mkid89 said:
So I've managed to unlock the phone, installed custom recovery but I can't get S-Off which I believe is needed to flash the stock RUU back on.
Rumrunner and moonshine both fail... probably because my phone is on some weird rom/kernel that no one has ever planned for.
Is there a way to get S-Off without these utilities? Is there a different way to get back to a stock GPE RUU with OTA that doesn't require S-Off?
I thought about maybe flashing the 5.1 GPE rom and then trying to use rumrunner on that. After getting S-Off, I'd revert back to a stock GPE RUU setup to have OTA updates and hope I don't end up with this 5.0.2 update again. What do you guys think? At this point I'm almost considering just flashing the GPE+ rom and not worrying about OTA updates. I'd just hate to have to lose all my stuff every time I need to update the rom (if the developer even decides to continue updating it)
Click to expand...
Click to collapse
You could try cm10 and firewater to get s-off
Sent from my HTC One using Tapatalk

king_david43 said:
You could try cm10 and firewater to get s-off
Click to expand...
Click to collapse
Why CM10 and not CM11? Is firewater just known to work for sure on 10?

mkid89 said:
Why CM10 and not CM11? Is firewater just known to work for sure on 10?
Click to expand...
Click to collapse
It worked for me on cm10 when I got a replacement m7 back in December
Sent from my HTC One using Tapatalk

king_david43 said:
It worked for me on cm10 when I got a replacement m7 back in December
Click to expand...
Click to collapse
Thanks! Just to confirm so I don't go through the whole process only to hit a wall again... Is this the ROM you are referring to? http://forum.xda-developers.com/showthread.php?t=2272945
nvm, the download link on that doesn't even work. I'll just get it off the CM site unless you have a better suggestion.

mkid89 said:
Thanks! Just to confirm so I don't go through the whole process only to hit a wall again... Is this the ROM you are referring to? http://forum.xda-developers.com/showthread.php?t=2272945
nvm, the download link on that doesn't even work. I'll just get it off the CM site unless you have a better suggestion.
Click to expand...
Click to collapse
Yeah you can find them here https://download.cyanogenmod.org/?device=m7ul
Sent from my HTC One using Tapatalk

mkid89 said:
Rumrunner and moonshine both fail...
Click to expand...
Click to collapse
king_david43 said:
You could try cm10 and firewater to get s-off
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, try it yourself, you'll be redirected to sunshine website:
http://firewater-soff.com/
On hboot 1.54 you can try Rumrunner or Sunshine

Thanks for the info. I had actually figured that out on my own as soon as I started working on it. lol
I ended up paying for Sunshine and it worked even on my 5.0.2 rom so there was no need to switch over to CM.
Once I was S-Off, I was able to flash the non-rooted GPE RUU following the instructions here. Booted into it and it's currently downloading the proper update file via OTA LMY47O.H6
I still have no idea how I ended up with a 5.0.2 OTA update on a completely stock phone...