To anyone who wants a challenge....
First: I installed twrp in preparing for flashing a custom rom.
2nd: Format/wiped sys/dalvik/cache
3rd: when trying to flash recieved error: remote not allowed!
4th: received the advice to relock then unlock again and that would fix the error problem.
5th: relocked bootloader... (has always been S-on)
6th: felt I had been denied, critical, need to know information.... fastboot ver was 1.55 and no longer able to unlock. Is there a fix for this yet? Can anyone please help me? I will compensate for time if needed.... I feel I have tried everything and read a couple hundred pages of threads on the subject but seems no one has answered the same question or has had different variables.
7th: Begging for help.... PLEASE!!!
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4035mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thank you in advance to any suggestions or information!!
Bda714
[email protected]
bda714 said:
To anyone who wants a challenge....
First: I installed twrp in preparing for flashing a custom rom.
2nd: Format/wiped sys/dalvik/cache
3rd: when trying to flash recieved error: remote not allowed!
4th: received the advice to relock then unlock again and that would fix the error problem.
5th: relocked bootloader... (has always been S-on)
6th: felt I had been denied, critical, need to know information.... fastboot ver was 1.55 and no longer able to unlock. Is there a fix for this yet? Can anyone please help me? I will compensate for time if needed.... I feel I have tried everything and read a couple hundred pages of threads on the subject but seems no one has answered the same question or has had different variables.
7th: Begging for help.... PLEASE!!!
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4035mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thank you in advance to any suggestions or information!!
Bda714
[email protected]
Click to expand...
Click to collapse
why can't you unlock at htcdev like everyone else ?
really.....?
clsA said:
why can't you unlock at htcdev like everyone else ?
Click to expand...
Click to collapse
Do you really think I would be asking for help if it were that easy?? When I flash unlock token it says writing and OK but does nothing....
bda714 said:
To anyone who wants a challenge....
First: I installed twrp in preparing for flashing a custom rom.
2nd: Format/wiped sys/dalvik/cache
3rd: when trying to flash recieved error: remote not allowed!
4th: received the advice to relock then unlock again and that would fix the error problem.
5th: relocked bootloader... (has always been S-on)
6th: felt I had been denied, critical, need to know information.... fastboot ver was 1.55 and no longer able to unlock. Is there a fix for this yet? Can anyone please help me? I will compensate for time if needed.... I feel I have tried everything and read a couple hundred pages of threads on the subject but seems no one has answered the same question or has had different variables.
7th: Begging for help.... PLEASE!!!
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4035mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Thank you in advance to any suggestions or information!!
Bda714
[email protected]
Click to expand...
Click to collapse
@nkk71 same problem here.. These are Dev edition One's.
Sent from my HTC One using Tapatalk
bda714 said:
To anyone who wants a challenge....
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
Click to expand...
Click to collapse
clsA said:
why can't you unlock at htcdev like everyone else ?
Click to expand...
Click to collapse
bda714 said:
Do you really think I would be asking for help if it were that easy?? When I flash unlock token it says writing and OK but does nothing....
Click to expand...
Click to collapse
Well, it's not bricked, BUT you pretty much can't do anything at the moment!
For anybody reading this: STOP flashing a US Dev Edition firmware 4.06.1540.x on your non-Dev Edition phones with a relocked bootloader and S-On, chances of HTCdev getting to unlock bootloader again is close to zero, or really zero.
(please anybody feel free to correct me)
I don't know if this is due to updated hboot, or what HTCdev unlock generator takes into account, but if for example it takes into account CID and firmware, then your firmware .1540. is not "stock"; for CWS__001 it should be a .502. firmware.
So what are the options: wait for an ATT OTA 4.06 (or above) to be released extract the firmware.zip in it (which is signed) and flash that, then try to get an unlock token and hope it works.
I'm sorry this is not the answer you're looking for, but unfortunately it's the only I have. Maybe someone else has a better idea.
EDIT: since US-Dev Edition is supposed to be unlocked anyway, has anybody tried "fastboot oem unlock"??
EDIT 2: try it in both normal mode and in "fastboot oem rebootRUU" mode.
^^ doesn't work
nkk71 said:
Well, it's not bricked, BUT you pretty much can't do anything at the moment!
For anybody reading this: STOP flashing a US Dev Edition firmware 4.06.1540.x on your non-Dev Edition phones with a relocked bootloader and S-On, chances of HTCdev getting to unlock bootloader again is close to zero, or really zero.
(please anybody feel free to correct me)
I don't know if this is due to updated hboot, or what HTCdev unlock generator takes into account, but if for example it takes into account CID and firmware, then your firmware .1540. is not "stock"; for CWS__001 it should be a .502. firmware.
So what are the options: wait for an ATT OTA 4.06 (or above) to be released extract the firmware.zip in it (which is signed) and flash that, then try to get an unlock token and hope it works.
I'm sorry this is not the answer you're looking for, but unfortunately it's the only I have. Maybe someone else has a better idea.
EDIT: since US-Dev Edition is supposed to be unlocked anyway, has anybody tried "fastboot oem unlock"??
EDIT 2: try it in both normal mode and in "fastboot oem rebootRUU" mode.
Click to expand...
Click to collapse
I don't mess with any of that unless I'm s-off, so i won't be testing it anytime soon
Related
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.039s
Pls pls help.Thank You.
erinar88 said:
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.039s
Pls pls help.Thank You.
Click to expand...
Click to collapse
Couldn`t work as you are S-On. I think you`re stuck bro afaik. Maybe someone else knows a solution. Good luck.
That's odd. It shouldn't have run at all since you can't downgrade using a RUU without s-off. It should have prompted a RUU error noting that you were on a later version.
Is your phone rooted and unlocked yet? Did you do anything to it besides run the RUU?
Can't you just use fastboot to push a custom recovery and then sideload a custom or stock ROM?
AllAboutTheCore said:
Can't you just use fastboot to push a custom recovery and then sideload a custom or stock ROM?
Click to expand...
Click to collapse
Looks like his only option. Surprised that the RUU wiped his device before getting the error.
There's no way to downgrade hboot with s-on atm.
I'm gonna be 'that guy'... What the heck were you doing flashing an RUU on S-on with 'limited IT knowledge'...
There's a reason RUUs aren't released. It's to prevent this.
On a side note I would try another RUU download. Where are you getting the error at? What's the phone doing?
Sent from my HTC One using Tapatalk 4 Beta
I'm wondering now. Did you actually try to fastboot flash the 1.44 WWE firmware.zip in RUU mode despite being s-on? Because if you really did that, the phone is dead. You're getting a signature error because the phone is s-on and you managed to corrupt something important. Being s-on, I doubt there is any way to fix it.
An expensive lesson, but maybe you'll be more careful next time. Gaining s-off isn't worth bricking your phone.
This is confusing as the official RUU's (exe's and zips) will simply not allow you to downgrade the hboot or to flash an older version of the firmware without having s-off so my thoughts are exactly the same as iElvis.
I cannot see how you managed to do what you did.
So questions....
Are you running a custom recovery?
Is your bootloader locked or unlocked?
Have you tried holding vol down and power for about 15 to 30 seconds to see if you can get into the bootloader?
Did you do something like reboot into bootloader, fastboot oem rebootRUU and then fastboot flash zip firmware.zip?
TELL US the exact steps you went through so we can try to help you and worst case scenario you have bricked your phone.
I am having a similar problem only i have S-off but i cant find the right RUU or the right recovery.img to fastboot it .
If you have rumrunner_HTC_0.5.0.zip you could gain s-off very easy .
erinar88 said:
I just bought a HTC one and when i try to downgrade the HBOOT from v1.54 to v1.44 by flashing RUU M7 ul asia wwe....... (i was stupid enough to do that)It deleted everything on the phone which included the factory os and prompt a window reading signature error.Now I cant boot up the phone.Can anyone help me please?Here is the getvar all.And also my IT knowledge is limited.
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35........
(bootloader) imei: 3..............
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3968mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(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.039s
Pls pls help.Thank You.
Click to expand...
Click to collapse
Sorry m8. Hate to break it to you but I accidentally did this too and I've found no solution for it. Ended up buying a new One...... I don't think there is a fix for this at all.
Sent from my HTC One using xda app-developers app
This the problem .
I have rooted my one but removed the software , it has s-on and relocked bootloader .
TWRP is no longer on the phone .
HBoot is 1.54000
Cid is GGOGL001
I sthere a sollution for this problem ?
Peter.henssen said:
This the problem .
I have rooted my one but removed the software , it has s-on and relocked bootloader .
TWRP is no longer on the phone .
HBoot is 1.54000
Cid is GGOGL001
I sthere a sollution for this problem ?
Click to expand...
Click to collapse
can you unlock your bootloader via htcdev? or fastboot oem unlock?
post your fastboot getvar all minus imei/sn
No to both questions , i cannot confirm the unlock confirmation .
Fastboot oem unlock doesnt work .
alray said:
can you unlock your bootloader via htcdev? or fastboot oem unlock?
post your fastboot getvar all minus imei/sn
Click to expand...
Click to collapse
Peter.henssen said:
No to both questions , i cannot confirm the unlock confirmation .
Fastboot oem unlock doesnt work .
Click to expand...
Click to collapse
post your fastboot getvar all
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Peter.henssen said:
c:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4274mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
you can tru to restore with a ruu.zip
It boots into the google screen but no further , i can get into the bootloader .
alray said:
post your fastboot getvar all
is your still booting?
Click to expand...
Click to collapse
Peter.henssen said:
It boots into the google screen but no further , i can get into the bootloader .
Click to expand...
Click to collapse
maybe you could try to restore with a ruu.
http://www.htc1guru.com/dld/ruu-zip-m7_google-edition_4-4_3-58-1700-5-zip/
Stuck
Hi I was wondering if anyone can help. I am Stuck in Bootloader with S 0on and relocked also is there anything i can do? does anyone have RUU for 4.4 5.5 sense?
gerry8 said:
Hi I was wondering if anyone can help. I am Stuck in Bootloader with S 0on and relocked also is there anything i can do? does anyone have RUU for 4.4 5.5 sense?
Click to expand...
Click to collapse
Hi gerry, just received your pm. Can you post an updated ''fastboot getvar all'' and describe the situation a little more (what rom are you on, what recovery/version and what you did before you wre stuck in bootloader)
alray said:
Hi gerry, just received your pm. Can you post an updated ''fastboot getvar all'' and describe the situation a little more (what rom are you on, what recovery/version and what you did before you wre stuck in bootloader)
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA41ES902933
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3442mV
(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
@alray Here it is I was S off unlocked and flashed Viper Rom. It wouldnt reboot so I tried to go back to Stock and for some reason I relocked and S on. I have no recovery cant get to it. I tried old RUU but wont work. cause i read cant downgrade. reboot phone goes straight to Bootloader
gerry8 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 1.13.41.0109_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA41ES902933
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3442mV
(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
@alray Here it is I was S off unlocked and flashed Viper Rom. It wouldnt reboot so I tried to go back to Stock and for some reason I relocked and S on. I have no recovery cant get to it. I tried old RUU but wont work. cause i read cant downgrade. reboot phone goes straight to Bootloader
Click to expand...
Click to collapse
your Verizon you have to s-off to do anything (unlock bootloader)
go back and get s-off instructions for Verizon
clsA said:
your Verizon you have to s-off to do anything (unlock bootloader)
go back and get s-off instructions for Verizon
Click to expand...
Click to collapse
@clsA i cant get out of bootloader. I am stuck how can i achieve s off and unlock bootloader from there
gerry8 said:
@clsA i cant get out of bootloader. I am stuck how can i achieve s off and unlock bootloader from there
Click to expand...
Click to collapse
Okay, before I can help, I'll need to know some more info. How did this happen, what were you doing, were you flashing an ruu? Let's get that taken care of before we can help you.
Truth6199 said:
Okay, before I can help, I'll need to know some more info. How did this happen, what were you doing, were you flashing an ruu? Let's get that taken care of before we can help you.
Click to expand...
Click to collapse
read post 11
he's pretty much screwed unless he can flash a RUU
clsA said:
read post 11
he's pretty much screwed unless he can flash a RUU
Click to expand...
Click to collapse
I didn't even see that post. Man oh man. If he can't flash an ruu, he is really screwed...
screwed
Does anyone have the kit kat RUU for Verizon..... Since i am dead in the water lol
gerry8 said:
Does anyone have the kit kat RUU for Verizon..... Since i am dead in the water lol
Click to expand...
Click to collapse
just keep an eye on the Verizon forums it will show up their first
Thanks
clsA said:
just keep an eye on the Verizon forums it will show up their first
Click to expand...
Click to collapse
@clsA Thank you
@clsA any update on ruu 4.4
Sent from my GT-P3113 using XDA Premium 4 mobile app
Hi Guys,
I have been reading around the forum but cant seem to find the answer to my problem. Or the suggestions are going over my head, so hope you can help.
I have a stock htc one m7 that is unrooted but it is sim unlocked. Went to bed with the phone working and then woke up with it stuck on the htc boot screen.
Things I have tried:
- get into HBOOT (which i can), then try recovery. This just reboots the phone to the white htc screen or screen just goes off.
- try and hard reset from hboot, but this does the same and either turns the screen black or reboots.
Both times i have left the phone for a while to see if it is up to anything but nothing happens.
I read about clearing the cache, but I could not get my head around the guides I read, so is there an idiots guide (I usually pretty good with tech stuff but not done much to do with phones etc)
Or any other suggestions. I use my phone for work so would be nice to get it working again without wiping it but most of the stuff should be back up anyway.
Thanks
Tom
From what I have tried I guess I should now try and flash the RRU?
The phone is on UKs EE network, as it is not rooted do I need to flash it with their branded rom or not? If so where can I get that from.
Thanks
Tommy_G5 said:
From what I have tried I guess I should now try and flash the RRU?
The phone is on UKs EE network, as it is not rooted do I need to flash it with their branded rom or not? If so where can I get that from.
Thanks
Click to expand...
Click to collapse
Do you have an sdk installed on your pc for adb/fastboot? If so can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting :good:
Danny201281 said:
Do you have an sdk installed on your pc for adb/fastboot? If so can you post the output of
Code:
fastboot getvar all
Please remove your imei and serial number before posting :good:
Click to expand...
Click to collapse
Just downloading sdk now but I used another program i found on my travels. Is this all the info you need?
C:\toolkit>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
If you need other info ill post it when sdk is downloaded and installed
Thanks for your help!
Tommy_G5 said:
Just downloading sdk now but I used another program i found on my travels. Is this all the info you need?
C:\toolkit>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.16.61.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXX
(bootloader) imei: XXXXXXXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4017mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
If you need other info ill post it when sdk is downloaded and installed
Thanks for your help!
Click to expand...
Click to collapse
Yep that's what we wanted, unfortunately there's no ruu for your phone
If you've got warranty on the device I would send it in for repair.
If you don't have warranty you gonna need to unlock the bootloader to do anything with it. If your gonna do it go here www.htcdev.com register an account and go to the Unlock My Bootloader section of the site and follow the instructions to unlock :good:
Ok. I will do that.
So once the bootloader is unlocked, what is my solution? installing a different Ruu? Or installing a different Rom (or are they the same thing)
Thanks
Tom
Tommy_G5 said:
Ok. I will do that.
So once the bootloader is unlocked, what is my solution? installing a different Ruu? Or installing a different Rom (or are they the same thing)
Thanks
Tom
Click to expand...
Click to collapse
Once your Unlocked you can flash a Custom or Unbranded Stock Rom. To be able to use RUU's you will need to go s-off. As your on hboot 1.57 the only way to s-off is Sunshine app. But this costs $25 to use. So I would just go with flashing a Custom Recovery and ROM for the time being. :good:
Unlocking the bootloader void warranty. If you have none, then proceed. In my opinion, your phone has suffered hardware failure and will not be recoverable, hence warranty.
Thanks
Thanks for the help guys. Turns out its still under warranty which is good news. I know with other custom roms you can use adb to retrive info off the device.
Any chance I can do the same, as most of the stuff is backed up except some photos ( last couple of months worth).
If not Ill get over it but just in case.
Thanks for your help so far.
Tom
Hello all XDA members,
I am looking for the correct RUU.exe for my HTC One M7. Its on Vodafone UK (VODAP001) and HBOOT 1.61.000 and is S-On. I have already relocked the bootloader and flashed the stock recovery back. I have found and tried many RUU.zip from here and HTC but I have learned that as I am S-on I am unable to go this route. This HTC One m7 was running a custom ROM and TWRP but since I am giving it my Father I needed it back to stock and ready to receive any OTA updates that Vodafone throw out.
Thank you all
Andrew
worf105 said:
Hello all XDA members,
I am looking for the correct RUU.exe for my HTC One M7. Its on Vodafone UK (VODAP001) and HBOOT 1.61.000 and is S-On. I have already relocked the bootloader and flashed the stock recovery back. I have found and tried many RUU.zip from here and HTC but I have learned that as I am S-on I am unable to go this route. This HTC One m7 was running a custom ROM and TWRP but since I am giving it my Father I needed it back to stock and ready to receive any OTA updates that Vodafone throw out.
Thank you all
Andrew
Click to expand...
Click to collapse
Can you please post the output of "fastboot getvar all" (hide your imei and sn before posting)
Will be easier to point you the correct RUU.
Btw is KatKiss 5.1 working fine? Haven't played with my tf101 for a while!
Thank you for your quick reply and as requested here is the output to fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Sxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4154mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-92aee636
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Kind Regards,
Andrew
Btw is KatKiss 5.1 working fine? Haven't played with my tf101 for a while!
Click to expand...
Click to collapse
Yes Lollipop 5.1 is working great and I have had no problems. Hopefully TimDuru will be presenting Marshmallow soon for the TF101
worf105 said:
Thank you for your quick reply and as requested here is the output to fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.18.161.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: Sxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4154mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-92aee636
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Kind Regards,
Andrew
Click to expand...
Click to collapse
The latest RUU for that version is 7.18.161.21. Since your phone is S-ON you can only flash RUU that are the same version or higher than your actual version (7.18.161.30). There is a way to bypass this. Go to this thread and read at the end of my post (post #2) under "how to downgrade with s-on". Once done and your version-main is showing 7.18.161.2 instead of 7.18.161.30 , flash the 7.18.161.21 RUU using instructions of post #1 (RUU file is at post #2). Don't forget to use the fastboot version provided at post #1, the normal fastboot version won't work to flash a lollipop RUU.
worf105 said:
Yes Lollipop 5.1 is working great and I have had no problems. Hopefully TimDuru will be presenting Marshmallow soon for the TF101
Click to expand...
Click to collapse
Its amazing how this dev is still supporting this device, will try to update :good:
Thank you alray
Will let you know how I get on with your instructions.
Ye TimDuru has done a great job in supporting the TF101. If he never I would have bought another tablet years ago.
Kindest Regards,
Andrew
I worked a treat, thank you alray for your expert help in this matter.
Gratefully yours,
Andrew
worf105 said:
I worked a treat, thank you alray for your expert help in this matter.
Gratefully yours,
Andrew
Click to expand...
Click to collapse
You're welcome :good:
alray said:
The latest RUU for that version is 7.18.161.21. Since your phone is S-ON you can only flash RUU that are the same version or higher than your actual version (7.18.161.30). There is a way to bypass this. Go to this thread and read at the end of my post (post #2) under "how to downgrade with s-on". Once done and your version-main is showing 7.18.161.2 instead of 7.18.161.30 , flash the 7.18.161.21 RUU using instructions of post #1 (RUU file is at post #2). Don't forget to use the fastboot version provided at post #1, the normal fastboot version won't work to flash a lollipop RUU.
Its amazing how this dev is still supporting this device, will try to update :good:
Click to expand...
Click to collapse
hi do you can helme whith my HTC wls RUU :crying:
jhon8500 said:
hi do you can helme whith my HTC wls RUU :crying:
Click to expand...
Click to collapse
Yes, what is the problem?
alray said:
Yes, what is the problem?
Click to expand...
Click to collapse
okay thanks for replying I have a htc one m7 wls I tried to install a rom of cyanogen but I could not install it I decided to return my htc to s-on with the intention of reinstalling the rom stock of factory but I could not find it the intetnado install by SDK but I get the error "error: device '(null)' not found" and by means of the installer of the ruu by means of .exe says it is not appropriate if you can help me I would appreciate this,
this information of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33YS901134
(bootloader) imei:xxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3841mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
jhon8500 said:
okay thanks for replying I have a htc one m7 wls I tried to install a rom of cyanogen but I could not install it I decided to return my htc to s-on with the intention of reinstalling the rom stock of factory but I could not find it the intetnado install by SDK but I get the error "error: device '(null)' not found" and by means of the installer of the ruu by means of .exe says it is not appropriate if you can help me I would appreciate this,
this information of my device:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33YS901134
(bootloader) imei:xxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3841mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Sorry for the delayed answer.
First, going back S-ON wasn't required and it's also a bad move. Having S-OFF can help a lot when troubleshooting your phone. I don't know what cyanogenmod rom version you tried to install (cyanogenmod roms are so old) but are you sure the one you tried was compatible with the M7_WLS variant? This phone variant will only work with custom roms made specifically for this variant and must also be flashed with a custom recovery compatible with WLS . Just saying because this is the most common error made by people having this phone variant.
Now, what ruu version are you trying to install? The one you need is 6.23.651.10 and can be found here:
http://dl3.htc.com/application/RUU_...99.2143463114.1556074529-999987239.1556074529
Don't forget that since you went back S-ON you now must have a locked or re-locked bootloader to install a RUU. It won't install if it's unlocked.
If not already done, you can re-lock your bootloader using fastboot from a command window using this single command:
Code:
fastboot oem lock
then install the RUU
trying to unlock bootloader . .been seeing help about going to HTCDEV from 2+ years ago but it wont allow me to get anything from there so I dont know where to go next.
All help is appreciated.
Can you post here an "fastboot getvar all" ?
lucyr03 said:
Can you post here an "fastboot getvar all" ?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.13.41.1209
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.22.605.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA396S904562
(bootloader) imei: 990004282109721
(bootloader) meid: 99000428210972
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: VZW__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4164mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
AKiiBA said:
trying to unlock bootloader . .been seeing help about going to HTCDEV from 2+ years ago but it wont allow me to get anything from there so I dont know where to go next.
All help is appreciated.
Click to expand...
Click to collapse
You can't unlock the Verizon HTC one using HTCDev.com, it will throw you the error code 160 which basically mean that your MID is not allowed to be bootloader unlocked. This MID was blocked form htcdev.com on August 23rd, 2013. The only way to unlock it yourself will requires you to purchase a Sunshine S-OFF license for $25 USD. Keep in mind that Sunshine S-OFF requires an already rooted phone to work on Lollipop and because you can't root your phone (because of the impossibility to unlock the bootloader) you'll have to achieve temp root before using Sunshine. Once done your phone will be bootloader unlocked and S-off and you'll be able to root it permanently, flash the rom/recovery of your choice, if desired (as long as it's compatible with the Verizon variant).
The temp root trick is explained somewhere in the Verizon HTC One Forum, in the General section.
Edit: Here https://forum.xda-developers.com/ve...root-root-method-bl-unlock-5-0-x-ota-t3122099
Yep.. Didn't want to go that route but guess I gotta.
Thanks alot for the help guys:good: