[One (M7) General] funkytut:
LOTS of questions

Phone info:

root@m7:/ # cat /proc/emmc

cat /proc/emmc

dev: size erasesize name

mmcblk0p19: 000ffa00 00000200 "misc"

mmcblk0p34: 00fffe00 00000200 "recovery"

mmcblk0p33: 01000000 00000200 "boot"

mmcblk0p35: 73fffc00 00000200 "system"

mmcblk0p26: 00140200 00000200 "local"

mmcblk0p36: 27fffe00 00000200 "cache"

mmcblk0p37: dc8000000 00000200 "userdata"

mmcblk0p22: 01400000 00000200 "devlog"

mmcblk0p24: 00040000 00000200 "pdata"

mmcblk0p27: 00010000 00000200 "extra"

mmcblk0p31: 04b00200 00000200 "radio"

mmcblk0p16: 03c00400 00000200 "adsp"

mmcblk0p15: 00100000 00000200 "dsps"

mmcblk0p17: 007ffa00 00000200 "radio_config"

mmcblk0p20: 00400000 00000200 "modem_st1"

mmcblk0p21: 00400000 00000200 "modem_st2"

mmcblk0p28: 00100000 00000200 "cdma_record"

mmcblk0p18: 02000000 00000200 "reserve_1"

mmcblk0p30: 034ffa00 00000200 "reserve_2"

mmcblk0p32: 05fffc00 00000200 "reserve_3"

mmcblk0p29: 06069e00 00000200 "reserve"

mmcblk0p25: 00004000 00000200 "control"

C:\Users\cbrown>fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 1.56.0000

(bootloader) version-baseband: 4A.22.3263.14

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 4.06.1540.2

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

(bootloader) serialno: HTxxxxxxxxxx

(bootloader) imei: 3xxxxxxxxxxxxxx

(bootloader) meid: 00000000000000

(bootloader) product: m7_ul

(bootloader) platform: HBOOT-8064

(bootloader) modelid: PN0712000

(bootloader) cidnum: BS_US001

(bootloader) battery-status: good

(bootloader) battery-voltage: 4282mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: dirty-bee46337

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.045s

list of radio basebands from Godfirst related to T-Mobile.

(T-Mobile US) Radio_4A.14.3250.15_10.34.1150.02L ---> http://d-h.st/CWV

(T-Mobile) Radio_4A.17.3250.20_10.440.1150.04L ------> http://d-h.st/2P0

(T-MOBILE USA 4.3/3.24.531.3) Radio_4A.21.3263.03_10.38m.1157.04L ---> http://d-h.st/Ekv

(4.4 Developer Edition OTA) Radio_4A.22.3263.14_10.38n.1157.04L ---> http://d-h.st/imB

Are the T-Mobile radios different from the T-Mobile US radios?

My story:

Newbie.

T-Mobile customer

No previous Android experience. Minimal firmware experience.

Switched from GalaxyS (I) to HTC One developer edition.

Previously had 3G in Mankato, MN and in Minneapolis area.

New phone gave me H/LTE/4G/3G/2G, depending on location, in Minneapolis area, but only "2G" in Mankato.

Wifes new iPhone gives her "4G" in Mankato on the same carrier.

Online research suggested that updating the radio firmware might take care of the problem.

I downloaded the 4.4 Dev Edition OTA before I rooted my phone and put su and twrp on it.

It already had unlocked bootloader.

I left s-on.

I think that all I essentially did was to replace the stock recovery and root.

After that, the first thing I tried was to load the T-mobile radio from here: http://xdaforums.com/showthread.php?t=2248586

The result did not break my phone, but did cause my battery usage rate to double and it did not address the problem I was trying to fix.

I then tried the Radio_4A21.3263.03_10.38m.1157.04L from your list above.

I had absolutely no radio after that and the phone began rebooting itself repeatedly (after launching twrp).

I had to build a command line in a text editor and paste it in to get it executed before the next boot.

I went back to the original image, which I had luckily backed up and things have returned to normal.

After digging around in another zip file to find out what baseband it was, I discovered that the zip files are to be "installed" instead of using the dd command, so now I figure I must have tried to move the binary zip file into the space defined for the radio.

Is it possible I overran another section with this file? Things appear to be working correctly. Is this the kind of thing that s-on prevents?

I tried to "install" it and things went better, but still no 3G or 4G.

It's my understanding that the only difference between a T-Mobile issue phone and this one is the firmware.

Is there a resource to tell me what radio technologies are in use for a given carrier in a given area?

I saw some discussion of "refarmed" (reframed?) on the T-mobile site.

Is there a radio expert who knows what happens with different radios?

Is is possible that someone with a T-mobile HTC One can transplant his/her radio image to me and others?

follow on questions to FAQ from Godfirst

Q: Do I need S-OFF for firmware flashing?

A: YES!

Does this apply to radios too? It looks like I can leave s-on under certain circumstances.

Could you tell me, in general, when that's true?

Q: Can I install a U edition firmware on a UL edition phone?

A: YES, but you might loose the ability to connect to LTE or have some other incompatibilities.

How do I determine if the firmware is U or UL? (I have a UL device.)

Q: Can I flash this firmware.zip on any HTC One?

A: Not if your device is S-ON. To be able to flash it on S-ON device, your modelid (example: PN0710000) and cidnum (example: HTC__001) must match the firmware.zip version you are about to flash.

Are modelid and cid linked somehow? Are they indelible parts of the phone? If not, how dangerous is it to change them?

Q: If my modelid or cidnum doesn't match, can I brick my device if I try to flash firmware.zip anyway?

A: As long as your device is S-ON flashing firmware.zip with non matching modelid or cidnum will result in error and nothing will be flashed, so there is no risk of brick.

This is the reason I have not elected to go s-off. I'm too inexperienced to take the training wheels off yet.

Is there a set of rules I can follow that will allow me to take the training wheels off?

Q: Do I need to have locked, unlocked or relocked bootloader to be able to flash firmware.zip?

A: Bootloader will not need to be relocked if flashing any custom firmware from this thread.

I purchased the Developer edition. Is there any circumstance where I could or should relock the bootloader?

Q: If I can't flash newest firmware.zip because of wrong modeid (MID) or cidnum (CID) does it mean I can't use custom ROM based on the latest HTC update?

A: In most cases you should be able to run any custom ROM as long as hboot update is not mandatory.

Is this the bootloader? If I update this, is that the only time I care about MID/CID?

Additional questions:

When I look at my layout, I get:

dev: size erasesize name

mmcblk0p19: 000ffa00 00000200 "misc"

mmcblk0p34: 00fffe00 00000200 "recovery"

mmcblk0p33: 01000000 00000200 "boot"

mmcblk0p35: 73fffc00 00000200 "system"

mmcblk0p26: 00140200 00000200 "local"

mmcblk0p36: 27fffe00 00000200 "cache"

mmcblk0p37: dc8000000 00000200 "userdata"

mmcblk0p22: 01400000 00000200 "devlog"

mmcblk0p24: 00040000 00000200 "pdata"

mmcblk0p27: 00010000 00000200 "extra"

mmcblk0p31: 04b00200 00000200 "radio"

mmcblk0p16: 03c00400 00000200 "adsp"

mmcblk0p15: 00100000 00000200 "dsps"

mmcblk0p17: 007ffa00 00000200 "radio_config"

mmcblk0p20: 00400000 00000200 "modem_st1"

mmcblk0p21: 00400000 00000200 "modem_st2"

mmcblk0p28: 00100000 00000200 "cdma_record"

mmcblk0p18: 02000000 00000200 "reserve_1"

mmcblk0p30: 034ffa00 00000200 "reserve_2"

mmcblk0p32: 05fffc00 00000200 "reserve_3"

mmcblk0p29: 06069e00 00000200 "reserve"

mmcblk0p25: 00004000 00000200 "control"

Can I get a source of information to describe each of the components?

Are the names standardized?

Does erasesize mean that one only has to erase 200 (hex bytes?) to erase the section?

What significance does the naming of the dev column have? Does it correlate to real memory base addresses?

mmc = memory manager c????

blk = block?

0p20 = 0.20?

are there any 1pxx's?