yashsingh1/xdaforums huggingface dataset:
[Verizon HTC One (M7)] one4thewings:
People much smarter than me are saying SuperCID doesn't make any sense on a Verizon phone since it's not a common mobile network type. Furthermore SuperCID could cause a situation in the event of an unwelcome OTA. So it's highly recommended you change back to the VZW__001 CID.
[Verizon HTC One (M7)] andybones:
try updating your HTC drivers.

if you instal htc sync it should install them for you.
[Verizon HTC One (M7)] crazyg0od33:
I did. you tried helping me in the other thread haha. :)

No dice
[Verizon HTC One (M7)] mjs31:
May not be exactly the same, but I just moved over from AT&T where I had a rooted HTC One. Every so often,, after trying different ROMS, kernals etc my "Other" storage would get pretty high. Sometimes as high as 20GB. I thought it might be some recovery backups, but those were not big enough. The only way I could every clear it was within CW recovery. There are a couple of options to clear external and internal card. I know you may not have a recovery setup, but I believe it is some type of partition that is taking up that space and used as a cache/backup/??. I ended up dragging and dropping needed items from my card and then wiping the external card (basically where all of my photos, music, etc. were stored) and it cleared this back to about 6 or 7 Gig. Now, just wiping my card on my own did not clear the "Other", I had to do it within recover which leads me to believe it is a hidden partition.

Again, not sure if this is what you have, but I was wiping, factory resetting, deleting everything in sight but it was always still high until I wiped the external via recovery.
[Verizon HTC One (M7)] andybones:
Ah Yea, sorry about that.
[Verizon HTC One (M7)] crazyg0od33:
no problem :D

I'm sure I'll work something out eventually
[Verizon HTC One (M7)] andybones:
When I finally got mine to work I was trying a bunch of different drivers, I know it's bean beat to death lol but if you haven't already tried this too worth a shot.

until then, best of luck man, hope you get it soon!
[Verizon HTC One (M7)] crazyg0od33:
yeah I've tried all of the latest drivers but all I get in device manager is 'My HTC' with the yellow exclamation next to it
[Verizon HTC One (M7)] andybones:
Sounds weird but have you tried another USB cord?
[Verizon HTC One (M7)] scotty1223:
been trying to catch up on these posts,and all my forums on xda,so forgive me if ive missed something :eek:

to yall having space/storage issues... are you,or were you,on a 4.3 rom?

4.3 brought the internal storage to a new location(data/media/ instead of data/media/0) so if youve gone from one to the other,youve prolly got things stored in both locations,and it wouldnt surprise me for the other location to show up as "other".

i had this issue myself when going from 4.2 to leaked europen 4.3

i was tempted to try and delete the new data/media and rename data/media/0 appropriately using root explorer,but im not sure if this would have any wierd side affects.

couple things should fix the issue:

-delete the other storage location with a file manager(do this at your own risk)

-install the stock recovery and select factory reset from hboot. this will wipe it ALL and clear out places your custom recovery cannot.

-run an ruu,wich should also affectively do a factory reset

on the fastboot prollem,try different ports and cables,no usb hubs,no usb 3.0,uninstall htc sync,and keep an eye on anything else capable of talking to the phone(pda net,easy tether,even itunes). also try windows 7,windows 8 is tricky
[Verizon HTC One (M7)] one4thewings:
In my case, no. I had a 7 GB "Other" allotment and I was on the stock VZW build.
[Verizon HTC One (M7)] lordv8r:
It could be the usb port. I had issues with mine and I did a search and found out that you need a USB 2.0 slot. As soon as I switched to the 2.0 slot on my laptop I had no problems. It's worth a shot.
[Verizon HTC One (M7)] m4rk0358:
I've got 10.3 gb in "other" which should include my one TWRP backup. I'm on a stock, rooted 4.2.2 ROM.
[Verizon HTC One (M7)] crazyg0od33:
yeah my MB only has USB3 so I think thats my issue. I'm running 4th gen haswell on an Ssus Maximus VI Impact and the board only used USB3 due to the m-ITX form factor...waiting for my roommate to return to try his usb2 port

EDIT - well it actually DOES have USB2 ports, but they dont work either. So I think it's the MB drivers or something. But it's weird that my nexus works no issues at all :/
[Verizon HTC One (M7)] Zwitterion:
This may not be the problem, but for my One to be recognized with my USB 3 ports I had to swap the Windows 8 drivers with updated Intel ones. I'll look to see if I kept the link on how to do it (which entailed booting with the option of allowing unsigned drivers, and then installing the new drivers)
[Verizon HTC One (M7)] crazyg0od33:
Yeah I've seen and tried that method. At some point in that process my USB keyboard and mouse aren't recognized by windows and I need to do a system restore
[Verizon HTC One (M7)] craigschroeder:
Prevent OTA's

I'm sure this has been answered before so if it has please point me in the right direction. Is there a mod that will completely ignore any OTA. I think I remember modifying a file on my Galaxy Nexus so that when an OTA is pushed out, my phone will ignore it because it's flagged that the ROM is current....something like that.
[Verizon HTC One (M7)] crazyg0od33:
if I do this and development doesn't pick up I don't want to be stuck on 4.2.2 for the life of my phone. Even if it breaks s-off, will my phone brick if I update via OTA to an official 4.3? That's literally the ONLY thing keeping me from buying right away.
[Verizon HTC One (M7)] isdnmatt:
If you change your CID back to VZW, no, it won't brick. You won't have to take the regular OTA though. You'll be able to upgrade 4.3 easily and maybe before official push even.
[Verizon HTC One (M7)] crazyg0od33:
but that would only be possible if dev takes off. Although I assume even if it doesnt, someone will still put up an image of the 4.3 so us rooted users can upgrade to it even stock
[Verizon HTC One (M7)] treetopflyer:
Make sure you aren't using a windows 8.1 machine. I had the same problem and after much searching, found out adb was broken on Win8.1 builds. Did the procedure on another Win 8.0 machine and worked flawlessly.
[Verizon HTC One (M7)] scotty1223:
no,you wont be stuck on 4.2.2. s off by itself doesnt prevent OTAs,as long as you are 100% stock otherwise,you can take otas if you wish.

you guys are lucky in that you allready have an ruu that you can use to restore all partitions to stock. if you run it,and change your cid to stock,ota should be possible.

i can gaurantee you someone will make a flashable zip of the OTA that you can install via a custom recovery,and provide you with the new firmware so you can install the update manually. im sure once a good number of folks have s offed,and/or an exploit is found for unlock youll see more and more custom roms.

as i said above,in a worse you could OTA,but there are no real beneifts. in order for the OTA to be successful several criteria need met,not the least of wich include:

-stock cid(very important)

-stock recovery

-stock kernel

-stock system files and bload INTACT

-correct firmwar

-correct release build(leaks typically will NOT ota)

-prolly others im forgetting ;)

while most of those things will just casue the OTA to fail,having the wrong cid could well brick yuor device. there were bricks of evita(one xl) and ville(one s) when folks tried to ota with supercid installed.

while id advise not OTAing if at all possible,dont let the notion of being stuck on 4.2.2 keep you from s off. you will have updated roms to flash,and in a worse case you can OTA,so send that sucker in :)
[Verizon HTC One (M7)] crazyg0od33:
You sold me. I'm going to send mine in. I've been putting off setting it up like I want for fear of losing everything in a bootloader unlock. I only have like 15 apps installed, so I'm not too worried. I did a helium backup just in case though :D

Can't wait :laugh:
[Verizon HTC One (M7)] dottat:
Scotty-

Got mine back today. I figured since I was htc-dev unlocked i would try changing my CID back to VZW__001 first and using my original unlock. Didn't work. So with my CID still VZW__001 I went to htc-dev with a new token and was able to get a new unlock bin. I therefore never unlocked with supercid... are we sure the syntax of that vzw CID is correct? I know it's character count specific.. but it it's the VZW CID so i can't see how it would allow unlock on htc dev?....

Unless....
[Verizon HTC One (M7)] one4thewings:
Very interesting. I'm looking forward to hearing the reply.
[Verizon HTC One (M7)] isdnmatt:
Is anyone else having issue with the CWM recovery. The runs the backup, but no actual files are created on the internal storage when it finishes.

EDIT: Nevermind, I found it.
[Verizon HTC One (M7)] one4thewings:
I don't know if it helps or not, but it would definitely be a CWM issue if that's what you're seeing. I installed the latest TWRP and the backups are being created and running as they should.
[Verizon HTC One (M7)] lluke04:
How do you change the CID?

I'm getting mine back tomorrow and was wondering if I should try going to htcdev and unlock with superCID or just changing CID to VZW__001.
[Verizon HTC One (M7)] elgordo123:
Cant install TWRP

I have S-Off, Bootloader unlocked. CID set to VZW_001. Boot into fastboot, able to see devices and was able to write unlock_code.bin (shows unlocked at top).

However I cannot get TWRP installed. I've tried both openrecovery-twrp-2.6.1.0-m7.img and openrecovery-twrp-2.6.3.0-m7.img. Reanmed them to twrp261.img and twrp263.img I even tried fastboot erase cache, I have tried to fastboot flash recovery twrp263.img many times. When I disconnect the phone and go back and select "recovery" I just get the standard white "entering recovery" then it reboots into the OS.

I have no idea what to do. I tried adb shell then su but it says su not found.

What am I doing wrong?

SOLVED:

I dont know why it didn't like twrp. I grabbed recovery-clockwork-touch-6.0.3.6-m7vzw.img and installed it via fastboot and I got cwm. I really wanted twrp but at this point I dont care.
[Verizon HTC One (M7)] andybones:
sounds like something isn't right, if you can install CWM recovery, you can install TWRP.. did you check the MD5 of the .img?, it's much easier to just rename the file to something easy like. recovery.img

fastboot flash recovery recovery.img

here, I uploaded the latest TWRP recovery.img named to recovery.img try adding this and giving it a shot.

make sure it reads in red "fastboot USB"

fastboot flash recovery recovery.img

also check to make sure the MD5 matches. Dev-host is great for files like these.

http://d-h.st/hMU
[Verizon HTC One (M7)] scotty1223:
not sure why the original token did not work,unless the diag file changed the mid(:eek:) or some other parameter. sounds like something is definately different if you were able to get the token and it worked with a vzw cid. we are sure of the syntax- VZW__001

it would be interesting to see a new fastboot getvar all and see if anything else has changed(x out your esn,imei)

quite some time ago i got a token with my t mobile one,with a vzw cid. but it had the t mobile mid,so thats not so odd.

the bottom line is something is different,or your original token should have worked,and you should have not been able get a working unlock code with vzw creditials ;)
[Verizon HTC One (M7)] dottat:
(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 1.12.42.0731

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.10.605.8

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno: FA37XXXXXXXX

(bootloader) imei: 99XXXXXXXXXXXX

(bootloader) meid: 99XXXXXXXXXXXX

(bootloader) product: m7_wlv

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN073****

(bootloader) cidnum: VZW__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4215mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-97af273845

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!
[Verizon HTC One (M7)] scotty1223:
whats the rest of your mid? thats not a personal bit of info,it will be same for all vzw phones,its just the model id.
[Verizon HTC One (M7)] andybones:
C:\apktool> fastboot getvar all

< waiting for device >

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.54.0000

(bootloader) version-baseband: 1.12.42.0731

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 1.10.605.8

(bootloader) version-misc: PVT SHIP S-OFF

(bootloader) serialno:

(bootloader) imei:

(bootloader) meid:

(bootloader) product: m7_wlv

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN073****

(bootloader) cidnum: VZW__001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4142mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-97af273845

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.090s

the modleid gets blocked like that.. PN073****

I assume this isnt good..?
[Verizon HTC One (M7)] scotty1223:
ooooooooooh gotcha! thats why its working with the vzw cid.

be careful with your phone like this... along with supercid,you could easily run a gsm ruu and really goof things up!

i dont think you can do this with your stock bootloader,but you can try changing your mid back to vzw with

fastboot oem writemid PN0731000
[Verizon HTC One (M7)] andybones:
is their risk of bricking doing this?

also with locked or unlocked boot loader?

and thank you

edit:

C:\apktool>fastboot oem writemid PN0731000

< waiting for device >

...

(bootloader) [ERR] Command error !!!

OKAY [ 0.010s]

finished. total time: 0.010s

C:\apktool>
[Verizon HTC One (M7)] dottat:
Did it actually change it ?
[Verizon HTC One (M7)] scotty1223:
Thanks for trying it... I didn't think it would work,but it was worth a shot. I thot maybe since the phone is in a "supermid" state,of sorts,maybe the regular hboot could change it. But,writemid is not part of the normal ship oem commands.

Looks like you will need an ENG hboot to change it.

There's no real danger,as long as your cautious what you flash. And don't take any OTAs... The same thing that bricks devices with supercid may be triggered by this as well :eek:
[Verizon HTC One (M7)] andybones:
Is their any chance of us getting a ENG Hboot, who can make one?

So basically, don't OTA, and don't flash anything stupid, just be cautious but there isn't really any harm done?

will the phone still be recognized as Verizon in like the Play store an everything?
[Verizon HTC One (M7)] crazyg0od33:
ugh now this has me worried about S-off all over again haha
[Verizon HTC One (M7)] andybones:
no reason to be..

it isn't hurting the phone, and with an ENG hboot which will hopefully come we can change it back.

Not the biggest deal in the world but still kinda sucks..

would really like to be able to get it back to stock.

but S-OFF was worth it...

---------- Post added at 11:17 PM ---------- Previous post was at 11:09 PM ----------

what type of bricks are we talking here like ppl messing up commands because having super CID and too much power over phone, or bricking the phone you can't stop from happening?

also what's the real dangers to watch out for having the mid# like this bedsides not taking OTA.

I know you mentioned basically same as Super CID but mind mentioned a few common ones. thank you in advance.
[Verizon HTC One (M7)] scotty1223:
sorry guys,i didnt mean to scare you. no real danger as long as your smart enuff to NOT run a gsm ruu,and not take any OTAs.

the OTA thing may be no big deal. we just need someone to accidentally(:p) or purposely try it and find out. it would be the same scenario as taking an OTA with supercid: the phone freaking out,and the processor putting itself into a "do not boot" mode,wich,while s off prolly will not trigger qusb_dload. the result would be a phone only recoverable via disassembly and jtag. or an insurance claim ;)

again,i dont mean to scare anyone,its just we dont know what will happen to OTA with supercid or supermid,so i just want to throw out the possibility,since there were real live bricks with evita and ville.

other than the OTA,there are no real dangers. as i said,just dont flash a gsm ruu. an eng hboot has to come from htc. the patched hboots from moonshine,are only extending the capabilities of the stock,unlocked hboot. they have basically been modded to ignore the lack status flag,and act as "unlocked" all the time,and they are removing the block that lets you only flash boot,recovery,and system(so you can fastboot flash hboot hboot.img or any other partition in similar manner). unfortunately,they are not adding any engineering commands :( the list of oem commands is the same as the ship hboots.

if youre curious about fastboot oem commands,you can list whats availble with: fastboot oem ? (make sure you get the "?")

there does exist an eng hboot. since the sprint crowd has flashed the eng hboot,and yall have allready flashed the gsm 1.44 hboot,i assume it will work for m7_wlv as well. i hate the link the process,as folks that have confidence in what theyre doing have alot of potential to brick the device with the additional eng commands,and the folks that dont have alot of confidence it can be a freaky experience,as the eng hboot will prolly not boot the phone(you change it,then change it immediately back),and can be a grey screen rather than an actual bootloader screen. further fastboot reboot-bootloader may cause the phone to turn off and be unresponsive :eek: i thot i had bricked my phone,and havent messed with it since. further,i wouldnt want the folks who only look after they leap,to think they can create a vzw play edition by changing their mid and running the gpe ruu.

the gsm crowd is using the eng hboot to change their mid to the google play/developer/european mid so a full conversion that recieves OTAs is possible.

i can search for the mid-change threads,but my recomendation would be just do not take any OTAs until its known for sure if the supermid affects them or not. i honestly wwouldnt mess with that freaky eng hboot ifn i didnt have to.
[Verizon HTC One (M7)] scotty1223:
for what its worth,me one x is in the same state:

c:\miniadb_endeavor>fastboot getvar all
INFOversion: 0.5a
INFOversion-bootloader: 1.39.0000
INFOversion-baseband: 2.1204.135.20
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 2.17.401.2
INFOserialno: HTxxxxxxxxxx
INFOimei: xxxxxxxxxxxxxxx
INFOproduct: endeavoru
INFOplatform: HBOOT-T30S
INFOmodelid: PJ461****
INFOcidnum: HTC__001
INFObattery-status: good
INFObattery-voltage: 4117mV
INFOdevpower: 100
INFOpartition-layout: None
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: None
INFOhbootpreupdate: 2
INFOgencheckpt: 0
all: Done!
finished. total time: 0.870s

i bricked my previous factory s-off one x messing with an old eng hboot,so i wont be attempting to change mine! :p
[Verizon HTC One (M7)] lluke04:
LoL. So, I'm coming here to get my answer... :D

You seem to know a lot... I am getting my One back tomorrow. So, what is the best way to go about unlocking? Should I change my CID back to VZW__001 and goto htcdev to unlock? Can I use the same unlock.bin I already have?

Any help is greatly appreciated!!!
[Verizon HTC One (M7)] dottat:
I would think that the best we can do right now is revert the CID.... then unlocking using htc-dev. It will allow this because of the mid we all have.
[Verizon HTC One (M7)] andybones:
so this is a bit re-assuring I think right?

at least this isn't the only phone.

BTW what method did you use for S-OFF that did superMID?
[Verizon HTC One (M7)] one4thewings:
Okay, this may be a question for Scotty but I'm sure I'm not the only one with the question...

IF we got our bootloader unlocked from HTC Dev already with SuperCID. Is it worth getting our bootloader unlocked with VZW__001? It seems to me that the unlock.bin is about as stock as the SuperCID unlock.bin since we are still in a SuperMID situation. Right?

Or no? Is it worth doing this process again with the VZW CID? And if so, is that wiping my device again? Am I having to install Recovery again?
[Verizon HTC One (M7)] andybones:
once your boot loader is unlocked, it's unlocked (which token only matters upon it working, not supercid, or any of that change the way the boot loader gets unlocked), and since you are Super MID you can go get an unlock token at ANY time, or if we get ENG hboot to fix that, you can superCID at any time to get unlock token, I personally have 3 unlock tokens for my phone..

1 is stock (I got in the 1st day)

2 is S-OFF Super CID

3 is S-OFF VZW_001,

maybe be a bit over doing it, but I like to be prepared lol

and have a copy of just about everything.
[Verizon HTC One (M7)] one4thewings:
That makes sense. I already have been keeping copies of everything I've used and keep it organized. It certainly doesn't hurt to request another unlock file with the VZW__001 CID.. I guess I'll do that now.
[Verizon HTC One (M7)] Derick60:
I didn't even know I needed to save it. Guess I need to get on that...
[Verizon HTC One (M7)] elgordo123:
Used your TWRP image and it worked great. Also installed Bonestock 1c! Schwing!!!! (Wayne's World joke - you might be too young)
[Verizon HTC One (M7)] andybones:
No way man, LOVE Mike Myers and all his films!
[Verizon HTC One (M7)] scotty1223:
i personally would go back to stock CID. your original unlock_code does not work anymore,since you have a new MID.

this is what i would answer as well:

yes,it appears the diag files are not just doing this to the one,so that is a bit reasuring. ive used plenty of diag files with an xtc clip,but ive never noticed the wonky MID before. but,those were older devices. maybe this is a new thing,or maybe i just never noticed :o

lol,the X is s off via sonics java card :p

i dont think its really worth worrking about,getting multiple tokens. as andy said,once youre unlocked,youre unlocked... no real need to ever relock. plus,there are other ways to change the lock status besides htcdev :eek:

since the MID is letting you unlock with ANY cid, im in agreement that reverting to vzw cid and then unlocking is a good way to go. that way,if you need to re-unlock,you dont need to get a new token or chagne cid to do it.

to more directly answer, dont think you need to relock just to re-unlock with a new token. if you ever need to re-unlock,you can just get a new token/code then. :)
[Verizon HTC One (M7)] scotty1223:
well,well!the below is inc 2(vivo_w) s-offed via diag file and xtc clip. notice the mid :D

c:\miniadb_endeavor>fastboot getvar all
INFOversion: 0.5
INFOversion-bootloader: 0.98.0000
INFOversion-baseband: 1.09.01.0722
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.34.605.4
INFOserialno: xxxxxxxxxxxx
INFOimei: xxxxxxxxxxxxxxx
INFOproduct: vivo_w
INFOplatform: HBOOT-7630
INFOmodelid: PG3210*** [COLOR="Red"]<-looky here!![/COLOR]
INFOcidnum: 11111111
INFObattery-status: good
INFObattery-voltage: 3836mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-82f6ac2f
INFOhbootpreupdate: 12
INFOgencheckpt: 0
all: Done!
finished. total time: 0.041s

c:\miniadb_endeavor>
[Verizon HTC One (M7)] dottat:
You make me want to pull out my old rez and see what that says. Is this unique to Java card or did other methods do this also I wonder.
[Verizon HTC One (M7)] andybones:
Haha .. Well. That would explain it!
[Verizon HTC One (M7)] scotty1223:
unique tot he diag file. the xct clip emulated an engineering sim card,so the diag file would work,much the same as the java card lets the diag work here. it just plugged into the sim card slot via a special flex cable,rather than an sd connected via an OTG usb cable.