Database Develop

[SOLVED] Problems receiving OTA

Hello guys,
So, i might be in a big problem, tried a lot of things. This is my last try to finally get stock again.
I will start with how it began.
When i received my phone, i updated to 4.2.2, hboot 1.54.
After long waiting 1,54 was able to get S-OFF. And i achieved S-OFF successfully --> Flashed latest firmware (3.57.401.500) and flashed the latest
ARHD (30.00).
The new firmware came out, so i wanted to flash that. Once in bootloader I saw that my phone has gone S-ON again? And it really is S-ON.
I've tried flashing the GURU thingy to reset to stock 4.2.2, stock recovery everything. But i still fail to receive the OTA.
So here i am now, hoping you guys have an solution to all this:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.57.401.500
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH35MW906757
(bootloader) imei: XXXXXXXXXXXXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3897mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6cad6811
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Did you get the popup of OTA?
However, strange that now you're s-on, maybe try to ask beaups.
p.s. For apply ota you need a locked bootloader, is yours?

Guich said:
Did you get the popup of OTA?
However, strange that now you're s-on, maybe try to ask beaups.
p.s. For apply ota you need a locked bootloader, is yours?
Click to expand...
Click to collapse
I have relocked my bootloader.
And i never received a popup for OTA, but since the international version is released, i should have it, IF i am completely stock. But i have no idea how to achieve that, since I tried most of the things already.

So, you've only to wait the popup...
Also other phone didn't get the OTA atm, but they are waiting

Guich said:
So, you've only to wait the popup...
Also other phone didn't get the OTA atm, but they are waiting
Click to expand...
Click to collapse
By other phones you mean other International models? If yes, i probably just have to wait.
But the thing is. I'm worried about that firmware that i flashed? or shouldn't i worry about that.
Thanks for the fast answers!

koenkokes said:
By other phones you mean other International models? If yes, i probably just have to wait.
But the thing is. I'm worried about that firmware that i flashed? or shouldn't i worry about that.
Thanks for the fast answers!
Click to expand...
Click to collapse
Yeah, i mean internationa models with other cid
No problem with the firmware, i think.
Maybe go s-off another time and reflash the 2.24 firmware

Guich said:
Yeah, i mean internationa models with other cid
No problem with the firmware, i think.
Maybe go s-off another time and reflash the 2.24 firmware
Click to expand...
Click to collapse
Hm, then I'll just wait another couple weeks.
And i dont think i can S-OFF now. because of my hboot 1.55 and firmware.

koenkokes said:
Hm, then I'll just wait another couple weeks.
And i dont think i can S-OFF now. because of my hboot 1.55 and firmware.
Click to expand...
Click to collapse
You can
Just check the rumrunners thread and post here the file he need for do the tool for the version main you've

Guich said:
You can
Just check the rumrunners thread and post here the file he need for do the tool for the version main you've
Click to expand...
Click to collapse
And how can I find a link to the corresponding RUU and/or firmware ota package?

koenkokes said:
And how can I find a link to the corresponding RUU and/or firmware ota package?
Click to expand...
Click to collapse
Check also this thread
Edit:
ops sorry, i forgot you've the 2.24 rom installed.

Yeah the thing is.
Stock 4.2.2 rom installed.
Stock 4.2.2 radio
stock kernel.
Unofficial firmware from mike: 3.57.xxx
Hboot 1.55
S-ON
So i'm still not sure IF i can receive OTA. Time will tell i guess.

koenkokes said:
Yeah the thing is.
Stock 4.2.2 rom installed.
Stock 4.2.2 radio
stock kernel.
Unofficial firmware from mike: 3.57.xxx
Hboot 1.55
S-ON
So i'm still not sure IF i can receive OTA. Time will tell i guess.
Click to expand...
Click to collapse
Seems, you've to wait, but i don't know
However, you can always re-unlock your bootloader, flash a 3.57 rom based and send the file to beaups

Guich said:
Seems, you've to wait, but i don't know
However, you can always re-unlock your bootloader, flash a 3.57 rom based and send the file to beaups
Click to expand...
Click to collapse
Will look into it, thanks man.

Update:
Relocked my bootloader, flashed stock recovery, and i received the new 4.3 update.
Now im on firmware 3.62. Managed to S-OFF.
Removed Tampered, and got my device back to LOCK. Seems everything worked perfectly, and there are no traces that i messed with my device

Out of curiosity are you planning on going back to s-on?
I'm hboot 1.55 stock Rom, stock recovery and firmware updated from 1.44 to 1.55 via various ota's. Is it safe to s on from this?

stovie_steve said:
Out of curiosity are you planning on going back to s-on?
I'm hboot 1.55 stock Rom, stock recovery and firmware updated from 1.44 to 1.55 via various ota's. Is it safe to s on from this?
Click to expand...
Click to collapse
I think it would be safe, but why would you? Some devices even ship with S-OFF right out the factory, so doing it for warranty reasons would be useless. But then again, each country handles this differently.

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

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!!!

[Q] Old hboot on Lollipop

Hi,
I have reinstall my m7 to old ROM with Android 4.1.1 and didn't do all stages OTA updates but recover backup with Lollipop. Everything is going fine but now I have hboot 1.5.4 instead 1.61. Could it cause any problem in the future? Should I install latest hboot? (where to find it?)
I have a stock rom htc one, wwe, s-off, rooted.

At this time i don't think so except if you try modding. But when htc rolls out the new sense update maybe you will have some troubles.

VoynichJimmy said:
At this time i don't think so except if you try modding. But when htc rolls out the new sense update maybe you will have some troubles.
Click to expand...
Click to collapse
I wanna stay with a stock rom. But considering to keep system up to date. What is the solution then? Should I go to rom version down and upgrade to current android 5.02 and then recover backup? Or is there a place on the network where I can find the original stock hboot 1.61 and install it via fastboot? (I've tried, didn't found)

badzi0r said:
I wanna stay with a stock rom. But considering to keep system up to date. What is the solution then? Should I go to rom version down and upgrade to current android 5.02 and then recover backup? Or is there a place on the network where I can find the original stock hboot 1.61 and install it via fastboot? (I've tried, didn't found)
Click to expand...
Click to collapse
There is no stock hboot 1.61 yet but if you want check this: http://forum.xda-developers.com/htc-one/development/hboot-modified-hboot-1-60-7-15-401-1-t3006222
But i am still confused about your case dude !! People are trying to upgrade and you are downgrading ? Hope you know what/where you are doing ?

VoynichJimmy said:
There is no stock hboot 1.61 yet
Click to expand...
Click to collapse
Yes there is.
https://www.androidfilehost.com/?fid=95916177934533541
stock 1.61 can also be extracted from these files:
https://www.androidfilehost.com/?fid=95916177934534374
https://www.androidfilehost.com/?fid=95916177934534383
https://www.androidfilehost.com/?fid=95916177934534503
@badzi0r post the output of "fastboot getvar all" before going any further. Remove imei and serialno before posting.

VoynichJimmy said:
But i am still confused about your case dude !! People are trying to upgrade and you are downgrading Hope you know what/where you are doing
Click to expand...
Click to collapse
I'm not downgrading. As I said in my first post. After crashing my HTC I have installed all from the beginning, hboot 1.44, rom with android 4.1.1, etc... then I have made OTA update to 1 version up, and then I have restored whole system (Lollipop) from backup made by TWRP. So now I have now Lollipop with hboot 1.54 but I would prefer have the updated to 1.61.
I hope it's clear now
BTW, can anyone look at my bootloader screen and confirm that not only hboot is outdated? How about the radio, etc...?

badzi0r said:
I'm not downgrading. As I said in my first post. After crashing my HTC I have installed all from the beginning, hboot 1.44, rom with android 4.1.1, etc... then I have made OTA update to 1 version up, and then I have restored whole system (Lollipop) from backup made by TWRP. So now I have now Lollipop with hboot 1.54 but I would prefer have the updated to 1.61.
I hope it's clear now
BTW, can anyone look at my bootloader screen and confirm that not only hboot is outdated? How about the radio, etc...?
Click to expand...
Click to collapse
HTC never updates hboot by itself.
If you don't have latest firmware, then you don't have latest hboot, radio, adsp, touch driver, WiFi driver, modem files, etc....
In other words, don't just update your hboot and expect to be fully up to date.
Update your full firmware.

badzi0r said:
I have installed all from the beginning, hboot 1.44, rom with android 4.1.1, etc... then I have made OTA update to 1 version up, and then I have restored whole system (Lollipop) from backup made by TWRP
Click to expand...
Click to collapse
And why not updating all the way up to lollipop? You will not be able to take ota updates with your phone in this state. Your firmware version and software version must match. Its not only the hboot version, like said above.

alray said:
And why not updating all the way up to lollipop? You will not be able to take ota updates with your phone in this state. Your firmware version and software version must match. Its not only the hboot version, like said above.
Click to expand...
Click to collapse
I didn't have stock rom with lollipop and been to lazy to do one by one all that OTA updates, so after two I've restored the twrp backup.
(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.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxx
(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: 4099mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.062s
Click to expand...
Click to collapse
What you suggest now?

RUU is not working for my M7.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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