Hey guys! So, I got a pop up on my phone last week for the 4.4.2 update However, I seem to be unable to install it. I get booted into twrp, so I try to install it from there, but it says flash failed. I am completely hopeless with things like this (wasn't me who rooted my phone etc). Any help would be very appreciated and apologies for my stupid question.
fsmn said:
Hey guys! So, I got a pop up on my phone last week for the 4.4.2 update However, I seem to be unable to install it. I get booted into twrp, so I try to install it from there, but it says flash failed. I am completely hopeless with things like this (wasn't me who rooted my phone etc). Any help would be very appreciated and apologies for my stupid question.
Click to expand...
Click to collapse
you need stock recovery to install ota. Find the stock recovery you need and flash it like any recovery
Code:
fastboot flash recovery <name_of_file>.img
fastboot reboot
and try to install the ota again.
alray said:
you need stock recovery to install ota. Find the stock recovery you need and flash it like any recovery
Code:
fastboot flash recovery <name_of_file>.img
fastboot reboot
and try to install the ota again.
Click to expand...
Click to collapse
How do I figure out which stock reovery I need?
fsmn said:
How do I figure out which stock reovery I need?
Click to expand...
Click to collapse
post the output of fastboot getvar all minus IMEI/sn
Hi there.
I like fiddling and wanted to build some BLE apps and hence required Android 4.3 or higher. We were seriously slow with the updates here in South Africa and I decided to root and load stock HTC 4.3 and later 4.4. My phone does however want to do OTA updates on 4.4 (even though other M7 users here don't have it yet, only received 4.3 about a month ago, which was when I flashed 4.4). I understand 4.4.2 for the M7 is out and would like to keep with the HTC stock updates. I do however experience your exact same issue and have read previously that I need a stock Recovery.
My question is exactly the same as yours. How do I know which Recovery to download and where do I download it from. Finding ROMs is easy and so is custom Recoveries (like TWRP), but not sure about finding the stock Recovery.
Thanks guys!
---------- Post added at 03:42 PM ---------- Previous post was at 03:29 PM ----------
Wow, that reply was so quick, it was even before my addition to the question
Here is the printout:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(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__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 3955mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s
Thank you for the assistance!
The Stock recovery needs to match your current "version-main", so in your case a 3.63.x.x , if you can match all 4 numbers that's best but for sure the first two.
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.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.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__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Recovery for stock_3.62.401.1
https://www.dropbox.com/s/i9v6ungs3dw1low/stock_3.62.401.1.img
bored_stupid said:
Recovery for stock_3.62.401.1
*link*
Click to expand...
Click to collapse
Thank you!
Let me know how you get on
bored_stupid said:
Let me know how you get on
Click to expand...
Click to collapse
I FINALLY got it to work (yes, totally hopeless)! Yay! Thank you both for the help!
Thats great news. could edit main thread title to include [SOLVED], thanks
Related
I'm looking to return my phone to 100% stock purely because I'm not benifiting from being Rooted as some apps i.e Barclays doesn't work. I no longer have the original back up of my phone when I first rooted.
I've tried downloading the EU ROM for my phone and install via the exe file however keep getting a 101 error. My phone is T-Mobile UK and I've tried everything I can think of.
If someone could give me a clear walkthrough of how to restore my phone to stock I'd be very happy.
Thanks.
adzie91 said:
I'm looking to return my phone to 100% stock purely because I'm not benifiting from being Rooted as some apps i.e Barclays doesn't work. I no longer have the original back up of my phone when I first rooted.
I've tried downloading the EU ROM for my phone and install via the exe file however keep getting a 101 error. My phone is T-Mobile UK and I've tried everything I can think of.
If someone could give me a clear walkthrough of how to restore my phone to stock I'd be very happy.
Thanks.
Click to expand...
Click to collapse
can you post a "fastboot getvar all" (remove IMEI and s/n)
(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.161.1
(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: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4278mV
(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.049s
adzie91 said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 2.24.161.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP001
Click to expand...
Click to collapse
How long or short do you want the process?
Long version: achieve S-Off, remove tampered, restore nandroid, restore stock recovery, set locked, etc. etc. etc.
Short version: flash your Guru Reset http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
__during installer: select WIPE, unselect ROOT, select "stock recovery", select "stock radio", you will be able to receive official OTAs
Hit the thanks button if I've helped
I've been able to flash a rom it seems which doesn't seem to be rooted. I shall repost the getvar shortly
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.161.1
(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: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(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.049s
adzie91 said:
I've been able to flash a rom it seems which doesn't seem to be rooted. I shall repost the getvar shortly
Click to expand...
Click to collapse
I would just flash the Guru Reset I posted above, because it's made for your phone/version, and you'll be able to receive any OTA updates just fine
nkk71 said:
How long or short do you want the process?
Long version: achieve S-Off, remove tampered, restore nandroid, restore stock recovery, set locked, etc. etc. etc.
Short version: flash your Guru Reset http://www.htc1guru.com/dld/guru_reset_m7_2-24-161-1-zip/
__during installer: select WIPE, unselect ROOT, select "stock recovery", select "stock radio", you will be able to receive official OTAs
Hit the thanks button if I've helped
Click to expand...
Click to collapse
f
That's what I've done. However, when I try to enter rocovery now I get a warning triangle. I imagine that is normal. I've no idea how to use S-Off lol
nkk71 said:
I would just flash the Guru Reset I posted above, because it's made for your phone/version, and you'll be able to receive any OTA updates just fine
Click to expand...
Click to collapse
It says that that one is for Vodafone? Is that normal?
adzie91 said:
It says that that one is for Vodafone? Is that normal?
Click to expand...
Click to collapse
So is your phone: (bootloader) cidnum: VODAP001
(from your getvar all)
Oh how unusual Well thanks. I have already flashed a incorrect one, so I've just re-rooted my phone and then I'll flash the zip you've provided. I've been searching ALL day for this solution and you've solved it like that.
Thank you very much!
adzie91 said:
Oh how unusual Well thanks. I have already flashed a incorrect one, so I've just re-rooted my phone and then I'll flash the zip you've provided. I've been searching ALL day for this solution and you've solved it like that.
Thank you very much!
Click to expand...
Click to collapse
No problem glad it worked.
BTW, I just noticed your signature which say T-Mobile, so you thought it was a T-Mo phone, but turns out to be a Vodafone.
---------- Post added at 05:04 PM ---------- Previous post was at 05:03 PM ----------
adzie91 said:
f
That's what I've done. However, when I try to enter rocovery now I get a warning triangle. I imagine that is normal. I've no idea how to use S-Off lol
Click to expand...
Click to collapse
that's "stock recovery", so you will now be able to receive OTAs correctly
Hello Everyone,
I flashed my HTC One with the new Cyanogen Mod 4.4 Kitkat. I decided to to revert back to the stock rom, unfortunately I never backed up the rom and now I am stuck on the boot loader screen. Before anyone starts to lecture me on meddling with things I have no knowledge of, I am aware of that, so I would appreciate constructive comments
I have tried ADB sideload, which didnt work. (the zip file was sent to my phone but when I install it flashes some text and reports as finished).
I havent a bulls notion on what to do next. I am a total Noob and looking for a solution in the forums is like looking for a needle in a haystack lol.
I have attached a photo of the bootloader screen and the rest of the data below.
I would be very grateful for any help as I have tried my very best to fix it myself - thanks again :good:
Phone Serial : FA33CW901648
C:\Users\IBM_ADMIN\Desktop\htc tool kit>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33CW901648
(bootloader) imei: 354436050233087
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
irishguy2014 said:
Hello Everyone,
I flashed my HTC One with the new Cyanogen Mod 4.4 Kitkat. I decided to to revert back to the stock rom, unfortunately I never backed up the rom and now I am stuck on the boot loader screen. Before anyone starts to lecture me on meddling with things I have no knowledge of, I am aware of that, so I would appreciate constructive comments
I have tried ADB sideload, which didnt work. (the zip file was sent to my phone but when I install it flashes some text and reports as finished).
I havent a bulls notion on what to do next. I am a total Noob and looking for a solution in the forums is like looking for a needle in a haystack lol.
I have attached a photo of the bootloader screen and the rest of the data below.
I would be very grateful for any help as I have tried my very best to fix it myself - thanks again :good:
Phone Serial : FA33CW901648
C:\Users\IBM_ADMIN\Desktop\htc tool kit>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA33CW901648
(bootloader) imei: 354436050233087
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.050s
Click to expand...
Click to collapse
flash twrp 2.6.3.3 then do a full wipe and then sideload your rom to install it
HTC One Softbricked
xnknown said:
flash twrp 2.6.3.3 then do a full wipe and then sideload your rom to install it
Click to expand...
Click to collapse
Hi there, just wondering how can I flash TWRP when im stuck on the bootload screen?
Sorry this is all new to me, thanks
u can flash it via fastboot
---------- Post added at 09:45 AM ---------- Previous post was at 09:43 AM ----------
irishguy2014 said:
Hi there, just wondering how can I flash TWRP when im stuck on the bootload screen?
Sorry this is all new to me, thanks
Click to expand...
Click to collapse
put the twrp file in your adb folder and right on the screen shown in your screenshot type fastboot flash recovery nameoffile.img
xnknown said:
u can flash it via fastboot
---------- Post added at 09:45 AM ---------- Previous post was at 09:43 AM ----------
put the twrp file in your adb folder and right on the screen shown in your screenshot type fastboot flash recovery nameoffile.img
Click to expand...
Click to collapse
Thank you very much for your help !!! all sorted :good:
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 fellas,
While i was trying to install new "Custom Rom" on my htc, obviously i was with s-on, so for som reason i deleted the original firmware, and now the phone wont boot..
So my question is can someone help me, please?
todorov.drago1 said:
Hello fellas,
While i was trying to install new "Custom Rom" on my htc, obviously i was with s-on, so for som reason i deleted the original firmware, and now the phone wont boot..
So my question is can someone help me, please?
Click to expand...
Click to collapse
Post your "fastboot getvar all" output, but delete your IMEI and serial no. And post your exact recovery version
donkeykong1 said:
Post your "fastboot getvar all" output, but delete your IMEI and serial no. And post your exact recovery version
Click to expand...
Click to collapse
C:\Android\sdk>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.19.401.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: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3859mV
(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!
finished. total time: 0.084s
My recovery is CMW 6.0.4.6-m7ul
todorov.drago1 said:
C:\Android\sdk>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.19.401.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: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 3859mV
(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!
finished. total time: 0.084s
My recovery is CMW 6.0.4.6-m7ul
Click to expand...
Click to collapse
What rom are you trying to flash? I would recommend you to get rid of CWM and use TWRP to reflash your rom, that will probably fix your problem.
alray said:
What rom are you trying to flash? I would recommend you to get rid of CWM and use TWRP to reflash your rom, that will probably fix your problem.
Click to expand...
Click to collapse
Well I'm trying to go stock again if its possible.
Will TWRP fix this, ill try it ?
By the way I'm s-on so no custom rom for me, now atleast I know that.
todorov.drago1 said:
Well I'm trying to go stock again if its possible.
Will TWRP fix this, ill try it ?
By the way I'm s-on so no custom rom for me, now atleast I know that.
Click to expand...
Click to collapse
You don't need s-off to flash custom roms.... only an unlocked bootloader and the correct custom recovery version.
If you want to back to stock then you'll have to flash the 7.19.401.51 RUU
alray said:
You don't need s-off to flash custom roms.... only an unlocked bootloader and the correct custom recovery version.
If you want to back to stock then you'll have to flash the 7.19.401.51 RUU
Click to expand...
Click to collapse
Ok I tried to flash this RUU, it is the correct I guess.. http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944/page3
But it says :
invalid sparse file format at header magi.. what does that mean? I think that the RUU.zip is too big I guess ? or I don't know
Ok I was able to get past that, but now I've got another problem when I enter TWRP/CMW I get this messege :
Unable to mount partition path /sd card..
and I think that this kinda screws up my RUU installation now. So what is the fix for that if there is any ?
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