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.
Related
hello, where can i download the 4.19.401.8 ruu.exe?? i've rooted my 4.4.2 and want to go back to stock... i'm not into it and can't make it work.. please help me.
cabasse_tronic said:
hello, where can i download the 4.19.401.8 ruu.exe?? i've rooted my 4.4.2 and want to go back to stock... i'm not into it and can't make it work.. please help me.
Click to expand...
Click to collapse
There is no 4.19.401.8 RUU available.
post your ''fastboot getvar all'' minus imei/sn
cabasse_tronic said:
hello, where can i download the 4.19.401.8 ruu.exe?? i've rooted my 4.4.2 and want to go back to stock... i'm not into it and can't make it work.. please help me.
Click to expand...
Click to collapse
why not just leave your device as it is and flash a custom 4.19 rom?
most of the posts in this thread are from people who have screwed up their device trying to relock and RUU.
I've allready locked the device, stock recovery.. but still can't det rid of the root.. and it doesn't even run.. from the begining it didn't.. said su binary.. bla bla bla...
this is fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH3xxxxxxxxx
(bootloader) imei: 3594xxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4297mV
(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.046s
the new thing that i've seen is that the HTC Flashlight ain't installed on my phone anymore..
Please help me get it back to stock.. like is fresh out of the box.. if you can help me, i'll replay ASAP here in order to make things go faster. thanks in advice to all of you guys.
Kill me if i'm wrong... i S-OFF the device, downgrade h-boot, then i can flash the RUU for my phone.. the one on the androidruu.com .. right??
cabasse_tronic said:
Kill me if i'm wrong... i S-OFF the device, downgrade h-boot, then i can flash the RUU for my phone.. the one on the androidruu.com .. right??
Click to expand...
Click to collapse
Yes that should do the trick. Flash the correct ruu for your MID and CID
big problem.. can't S-OFF... tried all methodes.. none work. i've got that little root on my phone but ain't working.. please
cabasse_tronic said:
big problem.. can't S-OFF... tried all methodes.. none work. i've got that little root on my phone but ain't working.. please
Click to expand...
Click to collapse
Have you tried Rumrunner? If yes, what errors it's giving you?
checking for updates....... ERROR: cannot check for updates
managed to S-OFF using firewater, after installing a custom rom.. in this moment i'm confused if going back to stock (s-on, etc, etc) or keeping the AHD soft.. it has with 200mb more free ram.. guys.. give me a hint
cabasse_tronic said:
managed to S-OFF using firewater, after installing a custom rom.. in this moment i'm confused if going back to stock (s-on, etc, etc) or keeping the AHD soft.. it has with 200mb more free ram.. guys.. give me a hint
Click to expand...
Click to collapse
If you installed ARHD 51 keep it, it's better than stock
Uxepro said:
If you installed ARHD 51 keep it, it's better than stock
Click to expand...
Click to collapse
i like it.. but on my mind is stock.. i've got problems with my old phone (htc one x) with custom rom, but it was carier dependent and wouldn't recieve OTAs
Have you tried flashing the RUU your device came with? Then OTA update to latest
now i'm on custom rom, S-OFF, Unlocked, Rooted and hboot downgraded (1.44) so at this point i can flash the ruu.exe for my htc one (x.401.x.x) but still i don't know if i'll manage to get it back to the Cosmote rom (had some cool programs installed on it)..
cabasse_tronic said:
now i'm on custom rom, S-OFF, Unlocked, Rooted and hboot downgraded (1.44) so at this point i can flash the ruu.exe for my htc one (x.401.x.x) but still i don't know if i'll manage to get it back to the Cosmote rom (had some cool programs installed on it)..
Click to expand...
Click to collapse
if you want to go back to stock and you have s-off and 1.44 hboot then the only thing you need to do is to download and run the 1.28.401.7 ruu.exe from htc1guru.com
it will wipe your phone and restore to stock rom and stock recovery. you will still be s-off. Just don't forget that if you want to remove the tempered flag, you should do it before the ruu
alray said:
if you want to go back to stock and you have s-off and 1.44 hboot then the only thing you need to do is to download and run the 1.28.401.7 ruu.exe from htc1guru.com
it will wipe your phone and restore to stock rom and stock recovery. you will still be s-off. Just don't forget that if you want to remove the tempered flag, you should do it before the ruu
Click to expand...
Click to collapse
is there a problem if i keep my phone s-off for warranty???
cabasse_tronic said:
managed to S-OFF using firewater, after installing a custom rom.. in this moment i'm confused if going back to stock (s-on, etc, etc) or keeping the AHD soft.. it has with 200mb more free ram.. guys.. give me a hint
Click to expand...
Click to collapse
How did you get firewater to work? Which steps? I seems to have the same getvar info as you, but I can't get it to work...
Thanks!
I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
snebojsa said:
I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
Click to expand...
Click to collapse
If you have a file manager with root access you can look at your /system/build.prop and look under ro.aa.romver will give you which version you have.
snebojsa said:
I tried to find my firmware version but when i type gatvar all in fastboot there is nothing in version-main field. How can I find my firmware version?
Click to expand...
Click to collapse
which HBOOT version do you have, its missing off your output ?
at the moment based on your modelid and your cidnum you have something along the lines of a 401 firmware, need the HBOOT version to determine which exact version though.
majmoz said:
If you have a file manager with root access you can look at your /system/build.prop and look under ro.aa.romver will give you which version you have.
Click to expand...
Click to collapse
Seanie280672 said:
which HBOOT version do you have, its missing off your output ?
at the moment based on your modelid and your cidnum you have something along the lines of a 401 firmware, need the HBOOT version to determine which exact version though.
Click to expand...
Click to collapse
At build.prop under ro.aa.romver is 1.54.401.5
My hboot is 1.57. Phone was officially updated to Sense6 and hboot 1.57, if it helps. Then I unlocked and s-offed it and install custom rom.
My question is this:
I looked this thread: http://forum.xda-developers.com/showthread.php?t=2485651 (Firmware with modified HBOOT, (No Red warning))
There is lot of files for specific firmware versions,
6.06.401.1
5.11.1540.9
4.19.401.11
4.19.401.9
4.19.401.8
4.19.1540.4
3.62.401.1 etc...
but there is nothing for my firmware. Am I missing something?
snebojsa said:
At build.prop under ro.aa.romver is 1.54.401.5
My hboot is 1.57. Phone was officially updated to Sense6 and hboot 1.57, if it helps. Then I unlocked and s-offed it and install custom rom.
My question is this:
I looked this thread: http://forum.xda-developers.com/showthread.php?t=2485651 (Firmware with modified HBOOT, (No Red warning))
There is lot of files for specific firmware versions,
6.06.401.1
5.11.1540.9
4.19.401.11
4.19.401.9
4.19.401.8
4.19.1540.4
3.62.401.1 etc...
but there is nothing for my firmware. Am I missing something?
Click to expand...
Click to collapse
Your firmware is 5.11.401.??, you can flash any of those firmwares above, but never go s-on, they will lead to an instant brick due to modified hboot
Or see here for original firmwares http://forum.xda-developers.com/showthread.php?t=2316726
Seanie280672 said:
Your firmware is 5.11.401.??, you can flash any of those firmwares above, but never go s-on, they will lead to an instant brick due to modified hboot
Or see here for original firmwares http://forum.xda-developers.com/showthread.php?t=2316726
Click to expand...
Click to collapse
How do you know my firmware version, I can't see it?
So, if I want someday to go back s-on (for warranty) I could flash back original hboot and then go to s-on? But I don't think I will flash this modified hboot, it is only for removing red warning text that is seen only when reboot phone, don't bother me that much to mess around with possibly risky staff.
snebojsa said:
How do you know my firmware version, I can't see it?
So, if I want someday to go back s-on (for warranty) I could flash back original hboot and then go to s-on? But I don't think I will flash this modified hboot, it is only for removing red warning text that is seen only when reboot phone, don't bother me that much to mess around with possibly risky staff.
Click to expand...
Click to collapse
I can tell by your cid, mid and hboot version
Seanie280672 said:
I can tell by your cid, mid and hboot version
Click to expand...
Click to collapse
Ok, but on that site with modified hboots there is no 5.11.401 firmware? Newest Firmware is 6.06.401.1 and previously was 5.11.1540.9. If I updated my phone with officially update, like I was, suppose i would have 6.06.401.1?
snebojsa said:
Ok, but on that site with modified hboots there is no 5.11.401 firmware? Newest Firmware is 6.06.401.1 and previously was 5.11.1540.9. If I updated my phone with officially update, like I was, suppose i would have 6.06.401.1?
Click to expand...
Click to collapse
Use the other site I linked if you want official firmware, your current one is on there, the next update that's not been released yet will have 6.06.401.1 in it.
Seanie280672 said:
Use the other site I linked if you want official firmware, your current one is on there, the next update that's not been released yet will have 6.06.401.1 in it.
Click to expand...
Click to collapse
Yes, I see it, thanks for informations :good:
Same issue and confused (more than usual)
My version main is empty as well and I can't figure it out.
build.prop/ro.aa.romver=1.54.401.5
Downloads\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.01.20.0515
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: 12312313123
(bootloader) imei: 12345613456123
(bootloader) meid: 123456123456
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4117mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.085s
UNLOCKED
M7_WLS PVT HIP S-OFF RH
CID-SPCS_001
HBOOT-1.57.0000
RADIO -1.01.20.0512
OpenDSP -v32-120.284.0909
OS-
Currently running ViperOne 6.2.1. Tried 7.0 last night but things were a bit funky and didn't have enough time to sort 'em all out. Thought firmware might be an issue, and it seems a bigger issue than I originally thought.
Any and all help appreciated
Version-main empty is TWRP issue, you have to re-flash firmware and flash fixed twrp version. I moved from M7 to M8 so I forgot where to find those files, you have to search it.
On M8 I had the same problem, flashing firmware and fixed twrp solved it. Also, when tried latest Viper rom I was on old firmware and had some odd issues, but since flashed new firmware everything is fine.
Hope I helped you.
OK, so if someone could please confirm or correct me... Being S-Off, I can flash latest M7 FW (6.0.xxx, I think?), then latest TWRP, then re-flash Viper, etc? All without having to unlock, etc, again? Think I'm also going to get custom H-boot (latest Firewater) to rid myself of the dreaded red text. Anyone know, or think, of any issues with that?
Many thanks for any and all assistance.
Sent from my HTCONE using XDA Free mobile app
toad6386 said:
OK, so if someone could please confirm or correct me... Being S-Off, I can flash latest M7 FW (6.0.xxx, I think?), then latest TWRP, then re-flash Viper, etc? All without having to unlock, etc, again? Think I'm also going to get custom H-boot (latest Firewater) to rid myself of the dreaded red text. Anyone know, or think, of any issues with that?
Many thanks for any and all assistance.
Sent from my HTCONE using XDA Free mobile app
Click to expand...
Click to collapse
use the instructions here it works Great
http://forum.xda-developers.com/showthread.php?t=2758956
you can use his files or your own
clsA said:
use the instructions here it works Great
http://forum.xda-developers.com/showthread.php?t=2758956
you can use his files or your own
Click to expand...
Click to collapse
Sorry, I may be noobing out a bit :silly: and venturing outside the Sprint specific forums (couldn't find same issue there), but first link sent me to AT&T ROM thread, which alsi pointed to another thread for firmware which listed several modelid's, none of which matched mine of PN0720000.
I guess I'll keep on looking for firmware for Sprint. I do see that I should be good to go after flashing new FW and recovery and do not have to unlock again, etc.
Thanks! :good:
toad6386 said:
Sorry, I may be noobing out a bit :silly: and venturing outside the Sprint specific forums (couldn't find same issue there), but first link sent me to AT&T ROM thread, which alsi pointed to another thread for firmware which listed several modelid's, none of which matched mine of PN0720000.
I guess I'll keep on looking for firmware for Sprint. I do see that I should be good to go after flashing new FW and recovery and do not have to unlock again, etc.
Thanks! :good:
Click to expand...
Click to collapse
yeah sorry that's my bad ..i totally missed the Sprint part of your thread
clsA said:
yeah sorry that's my bad ..i totally missed the Sprint part of your thread
Click to expand...
Click to collapse
Hey, no worries. You've helped. I didn't make it clear I Sprint. I'm more used to the 3VO forum where there wasn't hardly anything BUT Sprint. I suppose that's what confuses me about this one, with all the variants. Thanks again! :thumbup:
Sent from my HTCONE using XDA Free mobile app
Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance
sheppy1 said:
Hi Everyone,
Okay so I have spent the last 3 hours following various guides in order to restore my ViperOne ROM HTC One M7 to a stock HTC ROM along with locking the bootloader again, everything I've tried has failed though. I'm wondering if anyone here can help me as I need to sell this phone ASAP but can't do that until I restore to stock.
Anyway, the bootloader was unlocked using the HTCDev website and I then installed the custom ROM after that. The Bootloader version appears to be 1.57, not sure if that actually matters.
I tried locking the bootloader which worked and then tried to restore using the O2 UK RUU which failed (The app just crashes at the same point every time).
So I'd really appreciate any help from you guys
Thanks in advance
Click to expand...
Click to collapse
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.
majmoz said:
Post a fastboot getvar all with the imei and serialno removed. I am guessing that the RUU you ran was for an earlier version and unless you are S-OFF you can only run RUUs that are same OS version or higher.
You will need to use this guide to return to stock.
Click to expand...
Click to collapse
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks
sheppy1 said:
Hi! Sorry for the late reply, please find below the output that you requested:
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__001
battery-status: good
battery-voltage: 3811mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
You were correct, I was trying to boot a lower version. I heard that people have had luck using Firewater to S-OFF with CM11 installed. It didn't help me though. Anything you might be able to suggest would be a massive help! Thanks
Click to expand...
Click to collapse
Based on your getvar all you have a Int'l (.401) phone not an O2 UK branded phone. You will need to follow the directions of this site for stock rom 5.11.401.10 and you should be back whole. You can get the stock firmware if you need it from this site: http://xda7.androidrevolution.org/db_mirror/Firmware/index.php?dir=HTC%2FHTC_One%2F401%2F Just select the 5.11.401.10 firmware.
For S-OFF, you need to be as close to stock as you can. If you are getting "whelp not able to S-OFF" then you might look at Sunshine S-OFF, but there is a price use it.
I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?
sheppy1 said:
I realised that I had the international version shortly after posting my information back to you in this thread. Okay so I'm not really interested in getting S-OFF, I only wanted it to be able to use the RUU to restore to stock. So if I just follow method 1 from the post you linked me too, will I be back to get back to stock sense? I assume that I would still see "relocked" and "tampered" in my bootloader?
Thanks for all your help so far!
That worked a charm!!! I'm back on stock FW!!! Thank you! One thing though, will the person I sell the phone too be able to get software updates in future?
Click to expand...
Click to collapse
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.
majmoz said:
If you have stock rom, stock recovery & stock firmware, he/she should be able to get OTA assuming you did not put a custom recovery or root after flashing the stock fw.
Click to expand...
Click to collapse
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?
sheppy1 said:
That's great news! Would the fact that I ran the stock FW recovery zip from your link mean that I no longer have TWRP on my phone or do I have to do something else to get rid of that too?
Click to expand...
Click to collapse
Yes, you will have stock recovery, stock radio and stock hboot.
majmoz said:
Yes, you will have stock recovery, stock radio and stock hboot.
Click to expand...
Click to collapse
Thanks for all your help!
Should my bootloader still say "tampered"?
sheppy1 said:
Should my bootloader still say "tampered"?
Click to expand...
Click to collapse
Yes, you would have to be S-OFF to reset it.
Okay thank you! Was just thinking that something sill wasn't back to stock so thought I'd check
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?
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...