Hola amigo como están, tengo un HTC ONE M7 con las siguientes Caracteristicas
Hi fellas, i have an HTC ONE M7 with the next characteristcs
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei: xxxx
(bootloader) meid: xxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: BS_US002
(bootloader) battery-status: good
(bootloader) battery-voltage: 4023mV
(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
I was SuperCID but i load a wrong RUU and convert to BS_US002, i do a Wipe(MyError) and the phone stuck in the lock screen and turn off in 4 minutes, when i unlock it only show the HTC logo with the white background
Im S-ON because i missclicked the option S-ON in toolkit and i cannot revert
Every time i want to change the CID:
<bootloader> [JAVACARD_ERR] SD/USBDISK Init errorOkay [0.00s]finished. total time: 0.00s
Soooo i dont have any choice? there is not RUU for :
(bootloader) modelid: PN0731000
(bootloader) cidnum: BS_US002
Bayronavz said:
Hola amigo como están, tengo un HTC ONE M7 con las siguientes Caracteristicas
Hi fellas, i have an HTC ONE M7 with the next characteristcs
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 1.13.41.0702
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.28.605.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei: xxxx
(bootloader) meid: xxxx
(bootloader) product: m7_wlv
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0731000
(bootloader) cidnum: BS_US002
(bootloader) battery-status: good
(bootloader) battery-voltage: 4023mV
(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
I was SuperCID but i load a wrong RUU and convert to BS_US002, i do a Wipe(MyError) and the phone stuck in the lock screen and turn off in 4 minutes, when i unlock it only show the HTC logo with the white background
Im S-ON because i missclicked the option S-ON in toolkit and i cannot revert
Every time i want to change the CID:
<bootloader> [JAVACARD_ERR] SD/USBDISK Init errorOkay [0.00s]finished. total time: 0.00s
Soooo i dont have any choice? there is not RUU for :
(bootloader) modelid: PN0731000
(bootloader) cidnum: BS_US002
Click to expand...
Click to collapse
You can't change the CID with S-ON, it can only be done with S-OFF.
Your first mistake was trying to convert your m7_wlv variant using M7_UL variant RUU/CID. Only convert phone that are M7_U or M7_UL using M7_U or M7_UL RUU/CID/MID.
Second error (and maybe fatal) was to set back S-ON with the wrong CID. With this combination of CID, MID and Version-main, you can not flash any RUU or Firwamre.zip to unbrick your phone since it will fail at the CID check.
Is your bootloader locked or unlocked? If its unlocked you are lucky: Flash a verizon twrp recovery then a verizon stockish rom and achieve s-off again using sunshine s-off and change your CID back to the original one so you can flash the Verizon RUU and fix your phone.
If your bootloader is locked, you are now the owner of an expensive paperweight: there is nothing to do since Verizon phones aren't allowed to be bootloader unlocked using htcdev.com which is the only possible method to unlock the bootloader of a phone that isn't booting to the OS.
alray said:
You can't change the CID with S-ON, it can only be done with S-OFF.
Your first mistake was trying to convert your m7_wlv variant using M7_UL variant RUU/CID. Only convert phone that are M7_U or M7_UL using M7_U or M7_UL RUU/CID/MID.
Second error (and maybe fatal) was to set back S-ON with the wrong CID. With this combination of CID, MID and Version-main, you can not flash any RUU or Firwamre.zip to unbrick your phone since it will fail at the CID check.
Is your bootloader locked or unlocked? If its unlocked you are lucky: Flash a verizon twrp recovery then a verizon stockish rom and achieve s-off again using sunshine s-off and change your CID back to the original one so you can flash the Verizon RUU and fix your phone.
If your bootloader is locked, you are now the owner of an expensive paperweight: there is nothing to do since Verizon phones aren't allowed to be bootloader unlocked using htcdev.com which is the only possible method to unlock the bootloader of a phone that isn't booting to the OS.
Click to expand...
Click to collapse
Yes im in unlock mode, where i can find a verizon stockish rom?
Bump
alray said:
You can't change the CID with S-ON, it can only be done with S-OFF.
Your first mistake was trying to convert your m7_wlv variant using M7_UL variant RUU/CID. Only convert phone that are M7_U or M7_UL using M7_U or M7_UL RUU/CID/MID.
Second error (and maybe fatal) was to set back S-ON with the wrong CID. With this combination of CID, MID and Version-main, you can not flash any RUU or Firwamre.zip to unbrick your phone since it will fail at the CID check.
Is your bootloader locked or unlocked? If its unlocked you are lucky: Flash a verizon twrp recovery then a verizon stockish rom and achieve s-off again using sunshine s-off and change your CID back to the original one so you can flash the Verizon RUU and fix your phone.
If your bootloader is locked, you are now the owner of an expensive paperweight: there is nothing to do since Verizon phones aren't allowed to be bootloader unlocked using htcdev.com which is the only possible method to unlock the bootloader of a phone that isn't booting to the OS.
Click to expand...
Click to collapse
Today i flash a Nusense Rom for my verizon, but when i unlocked it show again the white logo screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Related
hi my friends .... plz i need your help with my mobile HTC One M7 which had no system and stuck in fastboot and i want to bring it again to stock rom but i didn't find the correct RUU for my device ..... i am from iraq and bought it from there. my cid HTC_j15 and i have s-on
please help me all the information you want about the device is listed below :
bootloader screen:
TAMPERED
RELOCKED
M7_U PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4A.17.3250.14
openDSP-v31.120.274.0617
OS-1.00.000.0
eMMC-boot 2048MB
Aug 9 2013, 16:20:20.0
FASTBOOT GETVAR ALL
(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: 1.00.000.0
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35XW913355
(bootloader) imei: 354435051934115
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks so much for help
meedo85 said:
hi my friends .... plz i need your help with my mobile HTC One M7 which had no system and stuck in fastboot and i want to bring it again to stock rom but i didn't find the correct RUU for my device ..... i am from iraq and bought it from there. my cid HTC_j15 and i have s-on
please help me all the information you want about the device is listed below :
bootloader screen:
RELOCKED
(bootloader) version-bootloader: 1.54.0000
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
thanks so much for help
Click to expand...
Click to collapse
you need to S-Off, then you can use:
RUU.EXE http://www.htc1guru.com/dld/ruu_m7_..._10-33-1150-01_release_311663_signed_2_4-exe/
or
RUU.ZIP http://www.htc1guru.com/dld/ruu-zip...0-01_release_311663_signed_2_4_decrypted-zip/
this will not work without S-Off !!
i can help you
if you have QQ You can add my QQ990128461
reckoning annosto
thanx my friend for help but i have a problem that i can't s-off my device because there is no system i wiped it previously so i can't enable usb debugging from inside ... what is the solution in your opinion please ....
best regards
meedo85 said:
thanx my friend for help but i have a problem that i can't s-off my device because there is no system i wiped it previously so i can't enable usb debugging from inside ... what is the solution in your opinion please ....
best regards
Click to expand...
Click to collapse
you need to unlock bootloader, and install a custom ROM,
get a new unlock token from HTCdev, and unlock bootloader. you won't be able to do anything with S-On and a relocked bootloader
PS: unless you can find a RUU.EXE for modelid: PN0711000 & cidnum: HTC__J15 which is 3.xx or higher
I have to sent in my one because aof warranty.
Now my problem is, that I don't become my phone on o2 stock.
- I downloaded this (RUU M7 UL K44 SENSE55 MR O2 UK 4.20.206.16 Radio 4A.23.3263.28 10.38r.1157.04L Release 353143 Signed 2) RUU from http://forum.xda-developers.com/showthread.php?t=2428276
- I relocked my bootloader
- I change my CID to O2___102
And after the RUU is sending the files I became the message that the RUU is not right for my phone.
What can I do? Please help
ChronoWerX said:
I have to sent in my one because aof warranty.
Now my problem is, that I don't become my phone on o2 stock.
- I downloaded this (RUU M7 UL K44 SENSE55 MR O2 UK 4.20.206.16 Radio 4A.23.3263.28 10.38r.1157.04L Release 353143 Signed 2) RUU from http://forum.xda-developers.com/showthread.php?t=2428276
- I relocked my bootloader
- I change my CID to O2___102
And after the RUU is sending the files I became the message that the RUU is not right for my phone.
What can I do? Please help
Click to expand...
Click to collapse
post the output of ''fastboot getvar all'' minus IMEI/SN
alray said:
post the output of ''fastboot getvar all'' minus IMEI/SN
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
ChronoWerX said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4316mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Have you removed the tampered flag from the bootloader and set it back to locked (not relocked) for warranty? This ruu will probably take you to hboot 1.56 and you'll get stuck with a tampered flag if you s-on again.
For the RUU, I don't understand why it didn't worked, you have the correct CID and MID and your phone is s-off, so it should work. Maybe @nkk71 know why?
alray said:
Have you removed the tampered flag from the bootloader and set it back to locked (not relocked) for warranty? This ruu will probably take you to hboot 1.56 and you'll get stuck with a tampered flag if you s-on again.
For the RUU, I don't understand why it didn't worked, you have the correct CID and MID and your phone is s-off, so it should work. Maybe @nkk71 know why?
Click to expand...
Click to collapse
Oh yes thanks I forget this. For information I used the dark bootloader from here
ChronoWerX said:
Oh yes thanks I forget this. For information I used the dark bootloader from here
Click to expand...
Click to collapse
Don't ever S-ON with a moded hboot, You will brick your phone!
alray said:
Don't ever S-ON with a moded hboot, You will brick your phone!
Click to expand...
Click to collapse
Ok thx, hboot is now stock, its locked and tampered is removed, test now ruu again
Edit: It worked. It was the modded HBOOT ... Thanks man
alray said:
Have you removed the tampered flag from the bootloader and set it back to locked (not relocked) for warranty? This ruu will probably take you to hboot 1.56 and you'll get stuck with a tampered flag if you s-on again.
For the RUU, I don't understand why it didn't worked, you have the correct CID and MID and your phone is s-off, so it should work. Maybe @nkk71 know why?
Click to expand...
Click to collapse
unfortunately it seems i may have a vague idea, unfortunately, ... stay away from those "RUU_M7_UL_K44_SENSE55_MR...." something doesn't seem right there!! (especially with S-On!!!)
EDIT: above statement seems inaccurate!!
nkk71 said:
unfortunately it seems i may have a vague idea, unfortunately, ... stay away from those "RUU_M7_UL_K44_SENSE55_MR...." something doesn't seem right there!! (especially with S-On!!!)
Click to expand...
Click to collapse
Oh read too late ... all worked here. Especially S-ON
ChronoWerX said:
Oh read too late ... all worked here. Especially S-ON
Click to expand...
Click to collapse
Glad to hear, what I really meant you will most likely not be able to install/flash these ROMs with S-On, with S-Off yes.... but their packaging seems a bit off, so people with S-On are going to have a hard time installing/flashing them
PS: did you just go S-Off to S-On on hboot 1.56?
how many times have you rebooted?
nkk71 said:
Glad to hear, what I really meant you will most likely not be able to install/flash these ROMs with S-On, with S-Off yes.... but their packaging seems a bit off, so people with S-On are going to have a hard time installing/flashing them
PS: did you just go S-Off to S-On on hboot 1.56?
how many times have you rebooted?
Click to expand...
Click to collapse
- locked bootloader
- install ruu ... i think 2 or 3 reboots
- s-on with fastboot command
- 2 reboots to see if all works
ChronoWerX said:
- locked bootloader
- install ruu ... i think 2 or 3 reboots
- s-on with fastboot command
- 2 reboots to see if all works
Click to expand...
Click to collapse
you should only go back s-on on hboot 1.44-1.54. The tampered flag will probably comes on again on hboot 1.55+.
alray said:
you should only go back s-on on hboot 1.44-1.54. The tampered flag will probably comes on again on hboot 1.55+.
Click to expand...
Click to collapse
No it worked
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gesendet von meinem HTC One_M8 mit Tapatalk
Hi
I had installed my stock rom from guru reset Guru Reset M7 2.24.161.1 for my CID:VODAP001
Before doing ota i had relocked bootloader and s-on
Heres my details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: H
(bootloader) imei: 3
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3881mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.074s
I now have unlocked bootloader with twrp installed. I can also s-off if i need to
How do i do ota on the stock rom without bootlooping. This was the second time i tried and same bootloop.
Is it due to s-on the boot.img doesnt flash so will it work with s-off?
Any help welcome
Thanks
hasan291 said:
Hi
I had installed my stock rom from guru reset Guru Reset M7 2.24.161.1 for my CID:VODAP001
Before doing ota i had relocked bootloader and s-on
Heres my details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: H
(bootloader) imei: 3
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3881mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.074s
I now have unlocked bootloader with twrp installed. I can also s-off if i need to
How do i do ota on the stock rom without bootlooping. This was the second time i tried and same bootloop.
Is it due to s-on the boot.img doesnt flash so will it work with s-off?
Any help welcome
Thanks
Click to expand...
Click to collapse
As you are S-off, change your CID to HTC__001 that's 2 x "_ _" not one, without the space, CID is always 8 characters
then run this RUU, you will have to lock your bootloader for the RUU to work, BUT NEVER S-ON, EVER!!!!
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
In the long run it will work out better for you. if it doesn't work, I have a Vodafone backup you can use, I used to be on Vodafone UK too and used this method to debrand my phone, best move I ever made, I now also get all OTA's from HTC servers long before VODAP001 being on HTC__001.
Seanie280672 said:
As you are S-off, change your CID to HTC__001 that's 2 x "_ _" not one, without the space, CID is always 8 characters
then run this RUU, you will have to lock your bootloader for the RUU to work, BUT NEVER S-ON, EVER!!!!
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
In the long run it will work out better for you. if it doesn't work, I have a Vodafone backup you can use, I used to be on Vodafone UK too and used this method to debrand my phone, best move I ever made.
Click to expand...
Click to collapse
Thanks
Ok so with S-OFF, change CID and then that RUU
Well i was planning on selling the phone so wanted full stock everything
So should i change cid or not. will there be any proof of cid change
hasan291 said:
Thanks
Ok so with S-OFF, change CID and then that RUU
Well i was planning on selling the phone so wanted full stock everything
So should i change cid or not. will there be any proof of cid change
Click to expand...
Click to collapse
yes first change CID, next lock bootloader, DO NOT S-ON under any circumstances, then run the RUU
Nope non at all, if you sell it, doesn't matter which network or sim card the buyer puts in it, they will still get OTAs, they will probably prefer an unbranded phone to a Vodafone branded phone, I know I would.
Greetings
i have an htc one with the following details :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34XW914782
(bootloader) imei: 354439052352400
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(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
tried the following ruu files :
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.exe
error 155
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
fastboot crashed
i also tried the following guru reset files
Guru_Reset_M7_1.26.502.15.zip
this is an at&t one and for some reason the touch didnt respond and i couldnt unlock the screen
Guru_Reset_M7_2.24.401.8.zip
this is the one that worked and this is an asia one
how do i get back fully to stock and get the updates
thank you
empreror said:
Greetings
i have an htc one with the following details :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT34XW914782
(bootloader) imei: 354439052352400
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3828mV
(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
tried the following ruu files :
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.exe
error 155
RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe
fastboot crashed
i also tried the following guru reset files
Guru_Reset_M7_1.26.502.15.zip
this is an at&t one and for some reason the touch didnt respond and i couldnt unlock the screen
Guru_Reset_M7_2.24.401.8.zip
this is the one that worked and this is an asia one
how do i get back fully to stock and get the updates
thank you
Click to expand...
Click to collapse
Your s-on their is no RUU you can use without getting s-off
SunShine S-Off
http://theroot.ninja/
in the mean time you can flash my Guru_Reset to get your phone working
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
Flash it with TWRP 2.6.3.3 or 2.8.4.0
http://techerrata.com/browse/twrp2/m7
thank you so much
can i get the updates from htc if it relocked the bootloader ?
clsA said:
Your s-on their is no RUU you can use without getting s-off
SunShine S-Off
http://theroot.ninja/
in the mean time you can flash my Guru_Reset to get your phone working
Guru_Reset_M7_5.12.502.2_clsA.zip
http://www.androidfilehost.com/?fid=23501681358545274
Flash it with TWRP 2.6.3.3 or 2.8.4.0
http://techerrata.com/browse/twrp2/m7
Click to expand...
Click to collapse
@clsA lol, all you see through these help forums when there is a new update is, how do I return to stock because I didn't do a backup and im s-on, and I messed with my phone without thinking about how to fix it if it went wrong.
empreror said:
thank you so much
can i get the updates from htc if it relocked the bootloader ?
Click to expand...
Click to collapse
AT&T has not released an update that I know of
Seanie280672 said:
@clsA lol, all you see through these help forums when there is a new update is, how do I return to stock because I didn't do a backup and im s-on, and I messed with my phone without thinking about how to fix it if it went wrong.
Click to expand...
Click to collapse
Yeah it keeps us on are toes
empreror said:
thank you so much
can i get the updates from htc if it relocked the bootloader ?
Click to expand...
Click to collapse
Don't need relock
Stock recovery and unmodified system files are enough
Seanie280672 said:
@clsA lol, all you see through these help forums when there is a new update is, how do I return to stock because I didn't do a backup and im s-on, and I messed with my phone without thinking about how to fix it if it went wrong.
Click to expand...
Click to collapse
clsA said:
Yeah it keeps us on are toes
Click to expand...
Click to collapse
And we will see a lots of "im stock on this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
screen after installing OTA" threads very soon
alray said:
And we will see a lots of "im stock on this
screen after installing OTA" threads very soon
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2791123
yatindroid said:
http://forum.xda-developers.com/showthread.php?t=2791123
Click to expand...
Click to collapse
So you are ready :good:
My htc one m7 is on some type of gray screen while converting this to Google play edition i would like to get this problem solved
I am new to these root type of stuff so any info would help thanks...........
I tried to change my mid by following this steps: http://forum.xda-developers.com/showthread.php?t=2322820
but it stopped at the step of grey screen.
what should i do?
My phone details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT ENG S-OFF
(bootloader) serialno: FA36FS900006
(bootloader) imei: ***************
(bootloader) meid: **************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3765mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
snahad007 said:
My htc one m7 is on some type of gray screen while converting this to Google play edition i would like to get this problem solved
I am new to these root type of stuff so any info would help thanks...........
I tried to change my mid by following this steps: http://forum.xda-developers.com/showthread.php?t=2322820
but it stopped at the step of grey screen.
what should i do?
My phone details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.39.2000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.10
(bootloader) version-misc: PVT ENG S-OFF
(bootloader) serialno: FA36FS900006
(bootloader) imei: ***************
(bootloader) meid: **************
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3765mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: ENG
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: 080b6f61
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
First thing you should have done was to read the moderator warnings at post #1 of that thread you have linked. This guide is dangerous for your phone and there are now really easier and safer way to do this without any risk for your phone like explained in the OP and be me if you read the last pages of that thread.
2nd, your phone is a Sprint CDMA variant (M7WLS). You can't flash a M7_UL RUU (like the GPE version) on a M7WLS. The WLS variant doesn't have the same partition layout and modem as the M7_UL. So on your Sprint phone you can only flash sprint RUU. Converting your phone by changing the MID is only possible for the M7_U and M7_UL version.
3rd The gray screen is actually the eng hboot. Like explained in that guide, you can still use fastboot commands there to change your MID. But since this guide doesn't apply to your phone, what you need to do now is to reflash your stock bootloader over the eng bootloader which will get you out of this mess.
4th If you don't get fastboot connectivity at the gray screen, its probably because you didn't read the warning at post #2 neither. You have to use Windows 7 since newer versions of windows can't detect the phone on hboot 1.44 and below (the eng hboot is 1.39....)
alray said:
First thing you should have done was to read the moderator warnings at post #1 of that thread you have linked. This guide is dangerous for your phone and there are now really easier and safer way to do this without any risk for your phone like explained in the OP and be me if you read the last pages of that thread.
2nd, your phone is a Sprint CDMA variant (M7WLS). You can't flash a M7_UL RUU (like the GPE version) on a M7WLS. The WLS variant doesn't have the same partition layout and modem as the M7_UL. So on your Sprint phone you can only flash sprint RUU. Converting your phone by changing the MID is only possible for the M7_U and M7_UL version.
3rd The gray screen is actually the eng hboot. Like explained in that guide, you can still use fastboot commands there to change your MID. But since this guide doesn't apply to your phone, what you need to do now is to reflash your stock bootloader over the eng bootloader which will get you out of this mess.
4th If you don't get fastboot connectivity at the gray screen, its probably because you didn't read the warning at post #2 neither. You have to use Windows 7 since newer versions of windows can't detect the phone on hboot 1.44 and below (the eng hboot is 1.39....)
Click to expand...
Click to collapse
Thanks a lot..... It worked successfully!