Database Develop

Active cmdline overflow! Can't enter custom recovery, S-ON

I'm new to the HTC One and I almost didn't know what I was doing, so I messed up really bad.
What did I do:
My friend wanted to try cm11 in his phone, so I unlocked the bootloader, installed cmw 6.0.2.8 and then the cm11 rom. It all went fine, but he realized that a lot of data he had wasn't recovered by Google's backups. so I thought that installing a rom with htc sense we could recover the majority of contacts and other things that he had. So I downloaded and installed this rom:
HTML:
http://forum.xda-developers.com/showthread.php?t=2626050
and installed it (wrong rom). When the installation finished, the phone rebooted into bootloader with the 'Active cmdline overflow' error.
I tried different solutions but nothing worked for me.
So, here goes the phone's info: (I got it in RUU mode, I hope it doesn't matter)
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA**********
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I flashed recovery a few times, always erasing cache, but I still can't enter recovery.
I hope someone can help me.

Frinalal said:
I'm new to the HTC One and I almost didn't know what I was doing, so I messed up really bad.
What did I do:
My friend wanted to try cm11 in his phone, so I unlocked the bootloader, installed cmw 6.0.2.8 and then the cm11 rom. It all went fine, but he realized that a lot of data he had wasn't recovered by Google's backups. so I thought that installing a rom with htc sense we could recover the majority of contacts and other things that he had. So I downloaded and installed this rom:
HTML:
http://forum.xda-developers.com/showthread.php?t=2626050
and installed it (wrong rom). When the installation finished, the phone rebooted into bootloader with the 'Active cmdline overflow' error.
I tried different solutions but nothing worked for me.
So, here goes the phone's info: (I got it in RUU mode, I hope it doesn't matter)
(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA**********
(bootloader) imei: 35*************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG309
(bootloader) battery-status: good
(bootloader) battery-voltage: 3866mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I flashed recovery a few times, always erasing cache, but I still can't enter recovery.
I hope someone can help me.
Click to expand...
Click to collapse
this fix is touch and go with your current hboot, give it a try, if it works then :fingers-crossed: if not then its :crying: as your s-on
http://forum.xda-developers.com/showthread.php?t=2739126

Seanie280672 said:
this fix is touch and go with your current hboot, give it a try, if it works then :fingers-crossed: if not then its :crying: as your s-on
Click to expand...
Click to collapse
Yes, I alredy tried it, but after installing the noBCB recovery, I still cant access it.
I also searched for nand backups for my CID, but there aren't any. (I don't know if that would even help at all)

Frinalal said:
Yes, I alredy tried it, but after installing the noBCB recovery, I still cant access it.
I also searched for nand backups for my CID, but there aren't any. (I don't know if that would even help at all)
Click to expand...
Click to collapse
nope, nothing will work until you fix that error.
if you carry on reading through that thread you will see that people experiencing that problem have had to downgrade their HBOOT in order to get it to work, unfortunately you need to be s-off to do that, I think one user had success using a certain version of cwm recovery, here you go, try this:
http://forum.xda-developers.com/showpost.php?p=53634257&postcount=90

Seanie280672 said:
nope, nothing will work until you fix that error.
if you carry on reading through that thread you will see that people experiencing that problem have had to downgrade their HBOOT in order to get it to work, unfortunately you need to be s-off to do that, I think one user had success using a certain version of cwm recovery, here you go, try this:
Click to expand...
Click to collapse
Thanks for helping. I tried it and it still doesn't work. I'll keep searching around the forums to see if I can do anything.

HTC One stuck somewhere after installation of cyanogenmod

Hello Everyone,
I am new to the whole custom rom thing, so I tried something simple on my HTC One (M7). The Install program that is new from Cyanogenmod. It was all looking fine and it installed (I think) in the end, after a few restarts, I was left with the blue cyanogenmod icon, a blue arrow going around it and white text beneath saying cryanogenmod. This went on for 4 hours. I thought this cant be normal and tried to restart the phone. It all worked, but when it was booting normally again, nothing changed, still the icon with the arrow circling it. So that wasn't all how I wanted it to be. I went in the recovery mode and I got there fine, but I noticed some things that were strange, for example, it told me, that it could not mount /data.
All I really want now is either the Stock Android that came with the HTC or the Cyanogenmod Version working, either way I have no idea on how to continue, I hope you can help me.
Thank you
Jonah

jonahmoeller said:
Hello Everyone,
I am new to the whole custom rom thing, so I tried something simple on my HTC One (M7). The Install program that is new from Cyanogenmod. It was all looking fine and it installed (I think) in the end, after a few restarts, I was left with the blue cyanogenmod icon, a blue arrow going around it and white text beneath saying cryanogenmod. This went on for 4 hours. I thought this cant be normal and tried to restart the phone. It all worked, but when it was booting normally again, nothing changed, still the icon with the arrow circling it. So that wasn't all how I wanted it to be. I went in the recovery mode and I got there fine, but I noticed some things that were strange, for example, it told me, that it could not mount /data.
All I really want now is either the Stock Android that came with the HTC or the Cyanogenmod Version working, either way I have no idea on how to continue, I hope you can help me.
Thank you
Jonah
Click to expand...
Click to collapse
What custom recovery and version were you using?
Which Cyanogenmod were you flashing and where did you get it?
Did you check the MD5 of the files downloaded?
Can you post a fastboot getvar all except remove the imei and serialno?

What custom recovery and version were you using?
ClockworkMod Recover v6.0.4.8
Which Cyanogenmod were you flashing and where did you get it?
It didn't specify anywhere on their homepage, all it said it was using the last stable version, since I did this two days ago it should be I face the latest they have for the Htc One
Did you check the MD5 of the files downloaded?
I did in face and it all checked out fine
Can you post a fastboot getvar all except remove the imei and serialno?
(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.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4270mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.119s
Thanks for the quick replay @majmoz

jonahmoeller said:
What custom recovery and version were you using?
ClockworkMod Recover v6.0.4.8
Which Cyanogenmod were you flashing and where did you get it?
It didn't specify anywhere on their homepage, all it said it was using the last stable version, since I did this two days ago it should be I face the latest they have for the Htc One
Did you check the MD5 of the files downloaded?
I did in face and it all checked out fine
Can you post a fastboot getvar all except remove the imei and serialno?
(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.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4270mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.119s
Thanks for the quick replay @majmoz
Click to expand...
Click to collapse
have you tried to flash the rom using a custom recovery instead of using the installer?
http://wiki.cyanogenmod.org/w/Install_CM_for_m7
use the recovery version specified in the above link.

[Q] Problems installing Roms and Recoveries

I bought my HTC One from Trademe (NZ's ebay) supposedly brand new, but it turns out it was already S-OFF and had CID 1111111. After unlocking the bootloader, I tried to install a custom recovery. All of the ones I tried seemed to install properly, but on booting, would get stuck at the 'entering recovery...' screen, however adb still worked here. Eventually I found two recoveries that do work (philz touch 6.25.0 and TWRP 2.6.3.3 thanks to this post) upon trying to install a custom rom, however the only ones that successfully install and boot are stock roms from this site. When booting custom roms the white boot screen flashes black once disappears except for a small white line at the top of the screen which disappears after a second or two. When booting cm-11 adb devices tells me an unauthorised device is attached. Attached are the recovery logs from various roms. Sorry if this is a bit long, but it's really frustrating me.

I dont' know if it helps, but this is the output from fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA367W919828
(bootloader) imei: 357864052420443
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

robtherobot101 said:
I dont' know if it helps, but this is the output from fastboot getvar all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3836mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
You have s-off, just use a RUU to restore your phone and you're done.

Do I need to change my CID to do that and does it matter which RUU I use?

robtherobot101 said:
Do I need to change my CID to do that and does it matter which RUU I use?
Click to expand...
Click to collapse
Oftentimes you do not have to with SuperCID but if it balks then change it to match the RUU. You will want to stick to RUU for your variant, i.e., GSM, CDMA, Dual-Sim, etc. You need to be careful since you are S-OFF the system will not save you if you run the wrong RUU and brick your phone!

majmoz said:
Oftentimes you do not have to with SuperCID but if it balks then change it to match the RUU. You will want to stick to RUU for your variant, i.e., GSM, CDMA, Dual-Sim, etc. You need to be careful since you are S-OFF the system will not save you if you run the wrong RUU and brick your phone!
Click to expand...
Click to collapse
How do I know the CID from these files?

robtherobot101 said:
How do I know the CID from these files?
Click to expand...
Click to collapse
The better question is do you want the International (.401); DevEd (.1540) or a specific carrier variant? The Int'l and DevEd will get upgrades faster than carrier variant. Check out this Collection of RUU he list the CID for most of the RUU.

Just in case anyone ever stumbles upon this thread in the distant future, let it be known that I managed to install this rom successfully and it's got all the useful features you'd expect from Cyanogenmod (and a few more).

robtherobot101 said:
Just in case anyone ever stumbles upon this thread in the distant future, let it be known that I managed to install this rom successfully and it's got all the useful features you'd expect from Cyanogenmod (and a few more).
Click to expand...
Click to collapse
What recovery did you use?
nevermind i just used philz and this rom is amazing i actually like it more than viperOne

HTC One 801n Black Screen

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)

Looking for correct RUU.exe

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