Hi,
I now read 10h Threads, searched with google, but i can't find a Solution. I have a HTC One M7 which is bircked after the last update of Vodafone. I can enter Bootloader and the phone starts in Storage Encryption Mode, but i can't unlock the bootloader, can't start Recovery with adb, RUU.exe does not work now i have no more idea how i can fix the problem.
(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.51
(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: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4058mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Maybe you have an idea?
Krid86 said:
Hi,
I now read 10h Threads searched with google, but i can't find a Solution. I have a HTC One M7 which is bircked after the last update of Vodafone. I can enter Bootloader and the phone starts in Storage Encryption Mode, but i can't unlock the bootloader, can't start Recovery with adb, RUU.exe does not work now i have no more idea how i can fix the problem.
(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.51
(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: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4058mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Maybe you have an idea?
Click to expand...
Click to collapse
flash the 7.18.161.51 ruu.zip
https://www.androidfilehost.com/?fid=529152257862665225
using instructions from here
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Don't forget to ask your question in the q&a section next time (not in the general section) see sticky thread "read before posting"
alray said:
flash the 7.18.161.51 ruu.zip
https://www.androidfilehost.com/?fid=529152257862665225
using instructions from here
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Don't forget to ask your question in the q&a section next time (not in the general section) see sticky thread "read before posting"
Click to expand...
Click to collapse
Thanks for fast reply, problem is, when i try htc_fastboot oem rebootRUU , the phone just restarts.
When i boot into recovery, it takes much time, then it starts with some missing files and failed to mount /data error.
Krid86 said:
Thanks for fast reply, problem is, when i try htc_fastboot oem rebootRUU , the phone just restarts.
When i boot into recovery, it takes much time, then it starts with some missing files and failed to mount /data error.
Click to expand...
Click to collapse
When you tried to unlock the bootloader, you were able to get the token but once you've flashed the Unlock_code.bin, the phone just restarted to a still locked bootloader?
alray said:
When you tried to unlock the bootloader, you were able to get the token but once you've flashed the Unlock_code.bin, the phone just restarted to a still locked bootloader?
Click to expand...
Click to collapse
Right, i get the question, if i really want to unlock ,confirmed it, then the phone just restarts "normally" with locked bootloader.
I also tried to enable debug mode with a workaround, but when i restart , the settings are lost again.
Krid86 said:
Right, i get the question, if i really want to unlock ,confirmed it, then the phone just restarts "normally" with locked bootloader.
Click to expand...
Click to collapse
Phone just restarting when using "fastboot oem rebootRUU" and not getting the unlock after "fastboot flash unlocktoken Unlock_code.bin" are 2 typical symptoms of a defective eMMC. fastboot commands requiring to read the emmc will works fine e.g "fastboot getar all". commands requiring to write on the emmc will fail e.g "fastboot flash unlocktoken Unlock_code.bin" or "fastboot oem rebootRUU".
Wouldn't be surprised to see a lot of errors from your "fastboot oem dmesg" and "fastboot oem last_dmesg" output.
Welcome to the infamous blown emmc club
Mh, i thought The same first, but i read of many users with the same Problem and the same OS Version, this cant be a fluke...
Krid86 said:
Mh, i thought The same first, but i read of many users with the same Problem and the same OS Version, this cant be a fluke...
Click to expand...
Click to collapse
Nothing more can be done, without access to RUU mode and bootloader stuck in a locked state... nothing can be flashed.
Try with Ubuntu maybe can see the partitions and can unlock bootloader than flash TWRP
Sent from my XT1254 using Tapatalk
---------- Post added at 01:17 AM ---------- Previous post was at 01:15 AM ----------
Did m7 give you QHSUSB DLOAD some time on PC
Sent from my XT1254 using Tapatalk
Stock RUU
Krid86 said:
Hi,
I now read 10h Threads, searched with google, but i can't find a Solution. I have a HTC One M7 which is bircked after the last update of Vodafone. I can enter Bootloader and the phone starts in Storage Encryption Mode, but i can't unlock the bootloader, can't start Recovery with adb, RUU.exe does not work now i have no more idea how i can fix the problem.
(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.51
(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: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4058mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-7661b1d7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Maybe you have an idea?
Click to expand...
Click to collapse
alray said:
flash the 7.18.161.51 ruu.zip
https://www.androidfilehost.com/?fid=529152257862665225
using instructions from here
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
Don't forget to ask your question in the q&a section next time (not in the general section) see sticky thread "read before posting"
Click to expand...
Click to collapse
Hello, Thanks a lot !!!!! :good::good:
Related
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 I'm stuck in Fastboot and can't seem to find anything to help my situation out. I was returning my phone to stock to return to ATT from ARHD 52.0 with the Hboot 1.54 and OS 4.20.707.6 Was following a guide now I'm totally stuck. Can't seem to find the RUU. Thanks.
bucklee said:
Hi I'm stuck in Fastboot and can't seem to find anything to help my situation out. I was returning my phone to stock to return to ATT from ARHD 52.0 with the Hboot 1.54 and OS 4.20.707.6 Was following a guide now I'm totally stuck. Can't seem to find the RUU. Thanks.
Click to expand...
Click to collapse
could you post 'fastboot getvar all' please, remember to remove IMEI and Seriel No. before posting
CYNiCAL2KX said:
could you post 'fastboot getvar all' please, remember to remove IMEI and Seriel No. before posting
Click to expand...
Click to collapse
Sorry for the late reply, Here is the Info.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(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: 4125mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm just stuck in fastboot usb mode and can't do anything to this. I have to return this phone to ATT by the end of the week and not sure they will be happy to receive it in this condition.
I tried to flash recovery via fastboot but this is what I am getting.
"FAILED (remote:Signature verify fail)"
Not sure what I can do now.... :-/
NVM, Figured out it was the bootloader, duh. But now I need to reset this to factory reset
Stuck in Boot Loop
Now I'm stuck in a Boot Loop. I can get into Recovery TWRP 2.6.3.3 But not sure what I should do next. Getting late will try again tomorrow. But If anyone has any tip for me it would be great thanks.
I'm freaking out a little bit. I was in the middle of trying to restore to stock. I got s-on back and locked the bootloader. Now I'm stuck on the bootloader. No matter what I press, it goes back to the bootloader. Adb no longer lists any devices connected to the pc. I can't get any of the RUU's I have downloaded to even open. Any ideas? Should the RUU be the next step?
I'm on xp
Bradlees said:
I'm freaking out a little bit. I was in the middle of trying to restore to stock. I got s-on back and locked the bootloader. Now I'm stuck on the bootloader. No matter what I press, it goes back to the bootloader. Adb no longer lists any devices connected to the pc. I can't get any of the RUU's I have downloaded to even open. Any ideas? Should the RUU be the next step?
I'm on xp
Click to expand...
Click to collapse
1- why did you s-on? Always keep s-off unless you send your phone for repair under warranty.
2- adb can't work from bootloader only fasboot, so ''fastboot devices'' should list your phone.
3- post the output of ''fastboot getvar all'' except IMEI so we can determine if you can use a ruu.
4- which ruu are you trying to flash?
alray said:
1- why did you s-on? Always keep s-off unless you send your phone for repair under warranty.
2- adb can't work from bootloader only fasboot, so ''fastboot devices'' should list your phone.
3- post the output of ''fastboot getvar all'' except IMEI so we can determine if you can use a ruu.
4- which ruu are you trying to flash?
Click to expand...
Click to collapse
If trying to turn my phone in for an upgrade, hence the return to factory.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3755mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm trying to download the tmobile us RUU I got off the link in here.
Bradlees said:
If trying to turn my phone in for an upgrade, hence the return to factory.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3*******
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3755mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I'm trying to download the tmobile us RUU I got off the link in here.
Click to expand...
Click to collapse
Edit out your serial no above ..
I posted this RUU for someone yesterday ..here's the link to the rom.zip
https://www.dropbox.com/s/mql8sas0udb1427/rom.zip
copy the file to your fastboot folder and flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << yes two times
fastboot reboot
clsA said:
Edit out your serial no above ..
I posted this RUU for someone yesterday ..here's the link to the rom.zip
https://www.dropbox.com/s/mql8sas0udb1427/rom.zip
copy the file to your fastboot folder and flash it with fastboot
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip << yes two times
fastboot reboot
Click to expand...
Click to collapse
Success! You saved me.
If I could hit the thanks button more, I would.
Bradlees said:
Success! You saved me.
If I could hit the thanks button more, I would.
Click to expand...
Click to collapse
it's no problem .. like i said i just posted it for another guy yesterday so it was fresh on my mind
Hi guys, i flashed Guru' Reset with CWM and after the phone turned on it only shows black screen with statusbar and after 1-2 mins it restarts again. I have (S-ON, Bootloader UNLOCKED)
arber95 said:
Hi guys, i flashed Guru' Reset with CWM and after the phone turned on it only shows black screen with statusbar and after 1-2 mins it restarts again. I have (S-ON, Bootloader UNLOCKED)
Click to expand...
Click to collapse
You have not provided much information.
Which GURU reset you used ? Which firmware you were on before flashing it ?
Also attach you phone to pc in fastboot mode, open command prompt and type in fastboot getvar all
Copy, paste the result over here. Make sure you remove IMEI and Serial No from it.
Also it's generally advised to use TWRP with HTC One.
Judging from my Bootloader mode info my OS Version was 2.24.401 so i flashed Guru_Reset_M7_2.24.401.1 with TWRP (i don't know which firmware it was on because it was bricked when i got it, it kept restarting)
Here is the info from cmd
C:\fastboot>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: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(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.042s
I am a newbie to HTC, sorry ..
arber95 said:
Judging from my Bootloader mode info my OS Version was 2.24.401 so i flashed Guru_Reset_M7_2.24.401.1 with TWRP (i don't know which firmware it was on because it was bricked when i got it, it kept restarting)
Here is the info from cmd
C:\fastboot>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: 2.24.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4187mV
(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.042s
I am a newbie to HTC, sorry ..
Click to expand...
Click to collapse
can you go into settings ?
GOOD news is that you can achieve S-OFF on this HBOOT version for free and very easily.
Just do as it is said in this thread.
http://forum.xda-developers.com/showthread.php?t=2487888
S-OFF has many advantages. And if you follow the guidelines and always read before doing anything, you won't get into any trouble.
Once you achieve S-OFF. you can install any firmware on your phone.
abdulwakil said:
can you go into settings ?
GOOD news is that you can achieve S-OFF on this HBOOT version for free and very easily.
Just do as it is said in this thread.
http://forum.xda-developers.com/showthread.php?t=2487888
S-OFF has many advantages. And if you follow the guidelines and always read before doing anything, you won't get into any trouble.
Once you achieve S-OFF. you can install any firmware on your phone.
Click to expand...
Click to collapse
You cant get s-off without a working rom on the phone, so thats got to be fixed first.
@arber95 reflash the guru reset file using TWRP 2.6.3.3 recovery, it should work then.
Hold down power button + volume down, the 2 lights on the bottom will flash approx 15 times, just keep holding, when the lights stop flashing, release to power button only, this will take you back to the bootloader.
Flash TWRP 2.6.3.3 recovery using fastboot commands http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
enter recovery, hopefully the guru reset file is still there on your internal storage, if not you'll have to push it to your internal storage using adb, then uplug your phone and flash it.
Seanie280672 said:
You cant get s-off without a working rom on the phone, so thats got to be fixed first.
@arber95 reflash the guru reset file using TWRP 2.6.3.3 recovery, it should work then.
Click to expand...
Click to collapse
I helped him RUU to stock.
He didn't want S-OFF. Just a working phone. He used ruu after incrementally flashing signed firmwares to 4.19.401.9..
Strangely his phone dialer was Fcing even after stock RUU 4.09.401.9
Last thing I know he catched 4.09.401.11 OTA and updated to it.
Don't know if the problem got solved.
As @abdulwakil noted. I'm back to Stock 4.4.2 with no root and relocked bootloader. Now my problems are: Dialer FC, i cant swipe notification center at all, and the phone restarts every exactly 4 minutes (which is strange), and it's not reading the simcard or getting signal (which it used to before)
@Seanie280672, help needed.
arber95 said:
As @abdulwakil noted. I'm back to Stock 4.4.2 with no root and relocked bootloader. Now my problems are: Dialer FC, i cant swipe notification center at all, and the phone restarts every exactly 4 minutes (which is strange), and it's not reading the simcard or getting signal (which it used to before)
Click to expand...
Click to collapse
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Seanie280672 said:
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Click to expand...
Click to collapse
This is my present getvar
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(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!
Seanie280672 said:
Sounds to me like you have the IMEI / Baseband problem, the only fix if the RUU didnt fix it is to send it off for repair, dont send it to HTC, they will charge you as your bootloader is re-locked, unlocking your bootloader voids your waranty, try your carrier if your on contract, its a hartdware problem and no amount of flashing will fix it.
Only way to hide that you ever unlocked your bootloader is to get s-off and falsh a very early rom, then lock and s-on before updating, however, now your probably on HBOOT 1.56, s-off is only possible through sunshine and will cost $25.
Click to expand...
Click to collapse
his phone was working on cm12, how come ?
arber95 said:
This is my present getvar
(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.9
(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: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4214mV
(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!
Click to expand...
Click to collapse
please remove your imei and serial from your post.
You could try flashing this, this is a full wipe firmware, it will wipe everything and re-build your partitions is the same firmware you have now: https://www.androidfilehost.com/?fid=23329332407579671
I would recommend after that to straight away, flash TWRP recovery and then push a custom KK sense rom to your internal storage and flash it, see if you have the same problem., if the problem still persists, you have a hardware issue.
Seanie280672 said:
please remove your imei and serial from your post.
You could try flashing this, this is a full wipe firmware, it will wipe everything and re-build your partitions is the same firmware you have now: https://www.androidfilehost.com/?fid=23329332407579671
I would recommend after that to straight away, flash TWRP recovery and then push a custom KK sense rom to your internal storage and flash it, see if you have the same problem., if the problem still persists, you have a hardware issue.
Click to expand...
Click to collapse
He is on 4.09.401.11 firmware. and S-ON
abdulwakil said:
his phone was working on cm12, how come ?
Click to expand...
Click to collapse
Someone else had the same problem recently, I was just trying to find the thread, i'll call for some expert advice, cant quite remember, CM12 / 11 does something slightly different
@clsA @nkk71 @Danny201281
---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------
abdulwakil said:
He is on 4.09.401.11 firmware. and S-ON
Click to expand...
Click to collapse
not according to his fastboot getvar all he's not. (bootloader) version-main: 4.19.401.9
Seanie280672 said:
not according to his fastboot getvar all he's not. (bootloader) version-main: 4.19.401.9
Click to expand...
Click to collapse
lol, he hasn't posted the present getvar all output. let him do that.
abdulwakil said:
lol, he hasn't posted the present getvar all output. let him do that.
Click to expand...
Click to collapse
well here is 401.11 full wipe https://www.androidfilehost.com/?fid=23329332407579952
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
arber95 said:
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
And is it still playing up ?
This is all the wipe and non wipe firmware files, https://docs.google.com/spreadsheets/d/tvdrXmIGYk0OWi0jtqih_0g/htmlview?pli=1, obviously you can only go up as your s-on, im surprised though that you can update whilst having those problems and they're not being fixed by the updates, I would be tempted to update as far as 6.09.401.5 full wipe, then flash twrp 2.6.3.3 and flash trhis rom by clsA
https://www.androidfilehost.com/?fid=95916177934521009
arber95 said:
I'm sorry for being silly guys, but phone got a new update
This is the new getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3900mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Yeah definitely sounds like unknown imei and baseband although I would expect you to only see the HTC logo after unlocking the screen.
For some reason CM roms work even with this issue. I believe it's because there is no Sense overlay with CM But I'm not exactly sure why they work.
Can you go to Settings>About>Phone Identity. And check your IMEI number is it displayed as Unknown?
Also Settings>About>Software information>More. And check your baseband is it displayed as Unknown.?
Seanie280672 said:
And is it still playing up ?
This is all the wipe and non wipe firmware files, https://docs.google.com/spreadsheets/d/tvdrXmIGYk0OWi0jtqih_0g/htmlview?pli=1, obviously you can only go up as your s-on, im surprised though that you can update whilst having those problems and they're not being fixed by the updates, I would be tempted to update as far as 6.09.401.5 full wipe, then flash twrp 2.6.3.3 and flash trhis rom by clsA
https://www.androidfilehost.com/?fid=95916177934521009
Click to expand...
Click to collapse
Again Sim not recognised, dialer FC, notification center doesn't open, and now it restarts more often (every 2 mins or so)
Hello, i came here with a problem, i updated the android and after that when i reboot it i got this problem : A red exclamation point triangle appear and says:
Mount SDCARD failed 1 times
Mount SDCARD failed 2 times
Mount SDCARD failed 3 times
Mount SDCARD failed 4 times
Mount SDCARD failed 5 times
Can not mount SD Card. (no such device)
Write host_mode: 0 done
I tryed apply from sdcard,phone storage and cache nothing i got only a reboot and back to this thing, after i tryed wipe data/factory reset and wipe cache partition also only a reboot and nothing else.
Phone infos :
>Unlocked
>M7_UL PVT SHIP S-ON RH
>Radio 4T.28.3218.04
I think that came from an android update that i tryed to do and it stucked almost at finish and i restarted it i dont know what to do if you can help me i will need also a tutorial . Thanks for your time! I wait for an answer .
JohnnyPTM said:
Hello, i came here with a problem, i updated the android and after that when i reboot it i got this problem : A red exclamation point triangle appear and says:
Mount SDCARD failed 1 times
Mount SDCARD failed 2 times
Mount SDCARD failed 3 times
Mount SDCARD failed 4 times
Mount SDCARD failed 5 times
Can not mount SD Card. (no such device)
Write host_mode: 0 done
I tryed apply from sdcard,phone storage and cache nothing i got only a reboot and back to this thing, after i tryed wipe data/factory reset and wipe cache partition also only a reboot and nothing else.
Phone infos :
>Unlocked
>M7_UL PVT SHIP S-ON RH
>Radio 4T.28.3218.04
I think that came from an android update that i tryed to do and it stucked almost at finish and i restarted it i dont know what to do if you can help me i will need also a tutorial . Thanks for your time! I wait for an answer .
Click to expand...
Click to collapse
The "Mount SDCARD failed" errors are normal, there is no sd card on that phone. These error will always shows when booting in recovery mode. The problem was most likely caused by rebooting the phone before the update was finished, hence why its now only booting in recovery mode. You'll need to post the output of "fastboot getvar all" (hide your imei and serialno) before I, or someone else, can help you further.
alray said:
The "Mount SDCARD failed" errors are normal, there is no sd card on that phone. These error will always shows when booting in recovery mode. The problem was most likely caused by rebooting the phone before the update was finished, hence why its now only booting in recovery mode. You'll need to post the output of "fastboot getvar all" (hide your imei and serialno) before I, or someone else, can help you further.
Click to expand...
Click to collapse
Thanks for your time alray, there is it :
(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.12.161.9
(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: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4326mV
(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
And CID
cid: VODAP102
JohnnyPTM said:
Thanks for your time alray, there is it :
(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.12.161.9
(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: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4326mV
(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
And CID
cid: VODAP102
Click to expand...
Click to collapse
Hey sorry for late reply. Look in the general section, there is a ruu collection sticky thread. Download the 7.xx.161.xx ruu and flash it to your phone using instructions given there, it should fix your phone. If you have any problem or question flashing that file post back here.
alray said:
Hey sorry for late reply. Look in the general section, there is a ruu collection sticky thread. Download the 7.xx.161.xx ruu and flash it to your phone using instructions given there, it should fix your phone. If you have any problem or question flashing that file post back here.
Click to expand...
Click to collapse
Thanks, it worked thanks alot.
Now i come back with another error after i updated this android now i cant listen music, on youtube any video isn't working and also my microphone isnt working too before update all of them working and now .. what caused that ...
htc 610: mount SDCARD failure
alray said:
Hey sorry for late reply. Look in the general section, there is a ruu collection sticky thread. Download the 7.xx.161.xx ruu and flash it to your phone using instructions given there, it should fix your phone. If you have any problem or question flashing that file post back here.
Click to expand...
Click to collapse
Hi Alray,
I am having the same issue with my htc 610 and I am glad that i was able to see this thread by google. I am wondering if you could give me some advises here. Regarding RUU, which one should I download from htc? Because there are three RUUs for htc 610 on htc website, pre-paid, post-paid and unlock. I got the phone from walmart that was labeled as "unlock". Should I use the one under "unlocked"?
And when it comes to following instructions posted in the collection thread, should I go by HTC Desire 601 RUU Collection thread? Thanks a bunch!
tfcheng said:
Hi Alray,
I am having the same issue with my htc 610 and I am glad that i was able to see this thread by google. I am wondering if you could give me some advises here. Regarding RUU, which one should I download from htc? Because there are three RUUs for htc 610 on htc website, pre-paid, post-paid and unlock. I got the phone from walmart that was labeled as "unlock". Should I use the one under "unlocked"?
And when it comes to following instructions posted in the collection thread, should I go by HTC Desire 601 RUU Collection thread? Thanks a bunch!
Click to expand...
Click to collapse
Can you please provide your "fastboot getvar all" output
alray said:
Can you please provide your "fastboot getvar all" output
Click to expand...
Click to collapse
For some reason I was able to get it:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.1121
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.502.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ****************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a3_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9O11000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 475c140c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.000s
tfcheng said:
For some reason I was able to get it:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.101.1372.19.1121
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.502.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: *****************
(bootloader) imei: ****************
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: a3_ul
(bootloader) platform: hTCBmsm8226
(bootloader) modelid: 0P9O11000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 475c140c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.000s
Click to expand...
Click to collapse
your version-main is 1.54.502.16 so it's the pre-parid verison.
download from here: http://dl3.htc.com.s3.amazonaws.com...1.1248827416.1501377631-1468744157.1486469825
It's a .exe ruu, so connect your phone to your pc with the usb cable (make sure it's correctly detected) then launch the ruu program and follow instructions. I don't know anything about the Desire 610 but afaik, all htc phones, when S-ON, must have a locked or re-locked bootloader to flash a ruu. So if it's unlocked, re-lock it using "fastboot oem lock" before using the ruu.
alray said:
your version-main is 1.54.502.16 so it's the pre-parid verison.
download from here: http://dl3.htc.com.s3.amazonaws.com...1.1248827416.1501377631-1468744157.1486469825
It's a .exe ruu, so connect your phone to your pc with the usb cable (make sure it's correctly detected) then launch the ruu program and follow instructions. I don't know anything about the Desire 610 but afaik, all htc phones, when S-ON, must have a locked or re-locked bootloader to flash a ruu. So if it's unlocked, re-lock it using "fastboot oem lock" before using the ruu.
Click to expand...
Click to collapse
Thanks a bunch! it worked!
alray said:
your version-main is 1.54.502.16 so it's the pre-parid verison.
download from here: http://dl3.htc.com.s3.amazonaws.com...1.1248827416.1501377631-1468744157.1486469825
It's a .exe ruu, so connect your phone to your pc with the usb cable (make sure it's correctly detected) then launch the ruu program and follow instructions. I don't know anything about the Desire 610 but afaik, all htc phones, when S-ON, must have a locked or re-locked bootloader to flash a ruu. So if it's unlocked, re-lock it using "fastboot oem lock" before using the ruu.
Click to expand...
Click to collapse
I have the same sd card message when i’m trying to boot my htc one phone as its stuck on the htc one logo screen