yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] blurp76:
Thanks! In any case i did this just in case something goes wrong with my phone.

I'd like to share a firmware.zip with just the files in a RUU, so i downloaded another firmware.zip, and i cross checked with the partition layout in the google spreadsheet. I cannot find corrispondence for several files:

Where are they coming from?

9.548.800 adsp.img ---> mmcblk0p16
438 android-info.txt ---> ???
1.306.624 dt.img	---> ???
348.224 emmc_appsboot.mbn ---> ???
2.096.384 hboot_signedbyaa.img ---> mmcblk0p11
4.341.932 persist.img	---> ???
4.188.160 pg2fs_spcustom.img ---> mmcblk0p6
46.334.976 radio.img	---> mmcblk0p20
1.057.448 ramdisk.img	---> ???
801 rcdata.img	---> mmcblk0p18
195.340 rpm.img	---> mmcblk0p8
309.234 sbl1-1.img	---> ???
309.234 sbl1-2.img	---> ???
309.234 sbl1-3.img	---> ???
11.802 sdi.img	---> mmcblk0p10
217.466 sensor_hub.img ---> mmcblk0p38
95.772 tp_SYN3508.img	---> ???
95.767 tp_SYN3528.img ---> ???
327.186 tz.img	---> mmcblk0p9
4.174.848 wcnss.img	---> mmcblk0p17
[One (M8) Android Development] Sneakyghost:
To establish which partition goes where, you can open a RUU image file with a HEX Editor like UtraEdit or UltraCompare, then open a RAW dump file of approximately the same size in the same program, compare them and if they match except for the white space (RAW pulls the whole partition including white space, the images do not contain the white space) you know where it goes. You might have to repeat this several times before you find the correct RAW dump.

I used to do this extensively on the OneS and the M7 but didn't have the time yet to analyze the M8 partitions. Sorry. That's why my spreadsheet so far only contains the obvious file associations.

You will have to do this searching yourself.
[One (M8) Android Development] blurp76:
Thanks for the detailed answer, very informative. So, i assume who built the various firmware.zip available for download extracted them from RUU or OTAs instead of a raw dd dump of the phone.
[One (M8) Android Development] Sneakyghost:
Of course. DD dumps are different. Its best to go by RUU images. Not by DD. In fact you hardly ever find anyone providing DD dumps. That's something you can work with if there is absolutely zero RUU/OTA material available for a device.

Or, like i originally intended it, to dump your FULL device right after you bought it so you can revert it to a cloned original state.

Actually, i have never needed to restore it that way though. Pretty redundant technology. Especially because DD isn't exactly the safest writing method, so, pulling with DD yes, but pushing back to device, i'd prefer the RUUMode way. DD only if not possible otherwise.
[One (M8) Android Development] los1010:
got a question having a hard-time getting firmware to flash i get an error code 130 Model Id if flash the rom without the firmware

will i have a bricked phone?
[One (M8) Android Development] Sneakyghost:
130 wrong model ID? Used to be 41.... interesting... can you name the exact text string after the number? What's it say exactly? Gonna add it to my list in Post 1 then.

You can just write SuperCID like detailed in Post 1. Then you can flash any firmware, i hope you are not Verizon or Sprint though because then you should not flash any firmware you find here.

If you flash a 4.4.3 ROM on a phone with old firmware, nothing really bad is going to happen, might just be you experiencing weird bugs like long boot times, maybe issues with the radio and such...
[One (M8) Android Development] los1010:
I have at&t sorry im new this firmware stuff and im soff and rooted i tried to superCID and it failed i really want to flash the new 4.4.3 roms but im afraid to brick
[One (M8) Android Development] Sneakyghost:
Jesus. Calm down. Nothing bricks from flashing a ROM. Firmware bricks devices. Go to post 1 and learn.

If fastboot oem writecid 11111111 fails, there's only two possible causes: either you are NOT s-off or you made a mistake.

How to do it is outlined in post 1.

There even is a link to a batch script which does it per typing in one number, then reboots your device and sets it to SuperCID without you needing to manually type the command.

Also, if you are new: please, please learn that "it failed" is nothing you will ever get much love for. What am i supposed to do with that? Magically know what you did? Guess around? Waste 10 posts until i found out what happened because you keep giving me 1 info at a time and the rest gets replaced by "it failed"? Learn to submit issues by describing what you did exactly, what lead up to the error, like order of commands put in, which commands, what version of software on your phone, what state, what carrier etc. Anything thats relevant to your particular situation.

In this case, relevant info is: S-OFF/ON, Device Type GSM/Sprint/VZW, what commands run and when? Which order.

Also, since this thread is in the development section and i want to keep it here, i wish to minimize the amount of support. Support is for Q&A, General and Help sections. This one should serve for finding out things, sharing things, providing info to other developers and users.

I suggest you open up a Help me please it failed thread in Q&A or add to an existing one.

I also want to know where you saw the 130 turn up? In the FUU interface or in Command Prompt while manually flashing the zip?
[One (M8) Android Development] los1010:
lol Thanks man i appreciate it i seen it in the FUU interface btw
[One (M8) Android Development] sgndroid1:
I did the T-Mobile US.
[One (M8) Android Development] amirsardari:
can we sign firmware.zip after edit by ourselves to not face with this error ?

For Error 12 “signature fail" do:

- might indicate that a signed firmware package is required. This would only happen with S-ON phones though.
[One (M8) Android Development] Sneakyghost:
Yea you can email HTC and politely ask them if they hand over their private key. Then you can sign it. Doubt that's ever gonna happen though, probably their best guarded secret.
[One (M8) Android Development] poondog:
Did you sign in pencil? I believe it must be done in pen.
[One (M8) Android Development] Sneakyghost:
Be nice Poony, u kno i no tolerate trolling on my thread except my own. :D
[One (M8) Android Development] poondog:
me2 ay :P
[One (M8) Android Development] amirsardari:
:laugh::laugh::laugh::laugh: give me email i will try

is there any way to obtain signature from their zip file :-b
[One (M8) Android Development] Sneakyghost:
You're obviously not getting it. Would you please refer to post one and five to learn how to work around the issue?

There is no signing of firmware.zip's in this world.

[EDIT]

I'll make it easier: no flashing of my packages on an S-ON phone. You will need to go to http:/theroot.ninja and get S-OFF in order to use the packages here.
[One (M8) Android Development] RockStar2005:
Found it! It was just in the regular HTC thread, not Sprint HTC one. Worked flawlessly!

http://xdaforums.com/showthread.php?p=54054835

Ok I guess the OS (firmware) and ROM/Build #s are slightly different.

Thanks anyway,

RockStar2005
[One (M8) Android Development] Luigiesin:
Hey guys.. So I'm a bit confused here... I'm running stock ROM (4.4.2).. S-off, supercid... I want to update to 4.4.3.

I want to flash FW using the manual sd card method (OP6BIMG.ZIP)... But I don't want to have to unlock bootloader again, nor have to flash stock recovery... Is there a method I can just flash the FW without having to unlock bootloader again afterwards? Just the necessary files to run 4.4.3.

I have a nandroid TWRP 4.4.3 I want to restore... But need the FW update.

Should I use M8_22.531.5_TMUS_TWRP2710_NoWipe_rename_to_ROM. ZIP and rename it to OP6BIMG.ZIP?

Thanks!
[One (M8) Android Development] Sneakyghost:
Yeah that is correct. As long as you are S-OFF you will not need to unlock or lock your bootloader, the state it is in now will suffice.
[One (M8) Android Development] Luigiesin:
Awesome! So I'll just rename the FW ZIP and use my SD to flash it. Thank you!

I enjoyed reading your OP last night.. Lots of info there... I don't think you left anything important out.. Hahaha.
[One (M8) Android Development] andybfmv96:
Is the FUU zip outdated? it looks like my radio downgraded.. (T-Mobile)
[One (M8) Android Development] Luigiesin:
Probable not... But one thing I've noticed is that the new radio is much slower on LTE in certain places comparing to the very 1st radio. But for sure is great on idle battery. I just flashed the original radio and my download speed is so much faster, but definitely has a bit more wakelocks.
[One (M8) Android Development] andybfmv96:
Isn't the newest tmobile radio like 2.something?

The fuu puts it on 1.19
[One (M8) Android Development] Luigiesin:
Maybe.. Don't recall.. I just flashed the original radio... But you could flash the modded firmware which contains the new radio.
[One (M8) Android Development] andybfmv96:
Flash failed for me. O.o whatevs I'll just stick to the radio. WiFi calling works so I'm content.
[One (M8) Android Development] Luigiesin:
My wifi Calling fails a lot with the new radio.. That's another reason why I went back to the original radio.
[One (M8) Android Development] Sneakyghost:
The radio is not having a 2 in it's version. You're probably confusing T-Mobile firmware version with the radio version. It's 2.22.531.5 for the firmware and 1.19-something for the radio, which is, except a few digits, identical to the WWE radio version.

I suggest you read post 1 to 5 and associated documents to learn about firmware, versioning and such if you want to know.

mobile post
[One (M8) Android Development] Sneakyghost:
The wakelocks stem from the radio not being 100% compatible with your current firmware and ROM, hence the wakelocks. Those wakelocks relating to radio uptime are almost always happening when the controlling bits in the ROM can't communicate correctly with the radio, and also when for instance the power manager firmware is of a different software generation compared to the radio. Other example is the bridge between SoC and radio, that likes to keep the SoC awake. One of the most annoying wakelocks, also usually caused by firmware parts not fitting well together.

I don't know the exact details, most is hypothetical stuff drawn from observations over the years, but one thing I can say for sure: messing with different radios without changing the complete setup yields NO comparable results.

If you want to compare an old radio against a new one, you need to run the entire phone software on the old level versus the entire phone software on the new level.

Everything else will produce totally random stuff, that has been wasting thread space on xda since years.

And I'll conclude this by saying: I'll not have radio discussions after this because it's 100% pointless.

mobile post
[One (M8) Android Development] Luigiesin:
Damn... You couldn't explain it better! I changed it because at work I'm getting less than 1mbit download when j was getting about 30mbit before...

I'm going to revert back flashing the firmware again and give it another try and see if it's a radio issue.

Thanks for the detailed information!
[One (M8) Android Development] Luigiesin:
Ok.. So I just flashed the firmware again.. So I'm running the latest radio... Now, I'm I missing any additional radio files on the ROM level? I checked my battery stats and I had Android OS awake for about 30 mins.. And before I changed radio to the old one, fresh after updating to 4.4.3, I didn't get that awake time on the OS.
[One (M8) Android Development] Sneakyghost:
Another unproven hypothesis of mine, often heavily objected by others, is that ROM's don't like firmware being swapped out under their bums.

When I change firmware, I always flash a fresh copy of a ROM on top.

Call me paranoid.

mobile post
[One (M8) Android Development] Luigiesin:
Yeah I get your point... I've read there are some files on the ROM level that are important for the radio... Anyways, the wakelock usually happens after charging to 100% and unplugging without using the phone for sometime... It happened this morning when I still had the radio I flashed yesterday... Going to give it another day now that I re-flashed the FW again and report back. Thanks Ghost.. I learned something very valuable today!
[One (M8) Android Development] gmac1990:
What is the latest firmware for AT&T and where can I get it?
[One (M8) Android Development] Sneakyghost:
http://dl3.htc.com/application/RUU_...20.51A.4198.01L_F_release_387305_signed_2.exe

Use RUU. Safest thing so far. I'll make a FUU once I get time off work again.

mobile post
[One (M8) Android Development] gmac1990:
Correct me if im wrong...S-OFF NOT needed for just using an RUU?
[One (M8) Android Development] Sneakyghost:
Correct. Conditions apply.

- software installed needs to be lower or equal as the RUU

- phone needs to be locked if it's S-ON.

- CID & MID need to match the RUU' list

mobile post
[One (M8) Android Development] gmac1990:
So ill do getvar and make sure CID matches to the file in the link you just gave me? Sorry for the noob questions.
[One (M8) Android Development] Sneakyghost:
If you choose to run the RUU while S-ON, you don't need to explicitly check, the RUU will just fail on you if they don't match with error 130 or 41 (also see post one for more error codes).

But you can of course run Fastboot getvar all to determine all the phones variables.

mobile post
[One (M8) Android Development] nrd\:
In the download comment its written 2.22.401.4 and 2.22.401.5 (no wipe versions) are the same / no changes?

im currently on firmware 2.22.401.4 with the Latest Venom rom 2.22.401.5 base, do I need / you recommend flashing the firmware 2.22.401.5?
[One (M8) Android Development] Sneakyghost:
No. Only kernel and recovery changed in 2.22.401.5. Since you replaced them with custom versions, you'll effectively not updating anything on your phone.

mobile post
[One (M8) Android Development] gadibob:
Preparing upgrade from stock 4.4.2 to (4.4.3 base rom, viperRom 2.3.0)

Hi,

in your post download page there several of files to download,

as my current Software is: 1.54.410.10 do i need to download the same one (same number) from the download (wipe / no wipe, is this important?), and run it to Preparing upgrade from stock 4.4.2 to (4.4.3 base rom, viperRom 2.3.0)

thank you

gadi
[One (M8) Android Development] Sneakyghost:
With that software you can just run the full wipe or no wipe version 2.22.401.5/4 then you don't need to additionally do the stock update.

If you need to do it the stock way, you should download the full wipe version to get the stock recovery.

mobile post
[One (M8) Android Development] gadibob:
thanks for the replay,

by now i download and "flash" 1.54.410.10 (no wipe) it have change my recovery from CWM To TWRP, then i flash the rom (is working fine).. now my ver is : 2.22.401.5,

do i need to update this software to the one in your download page version 2.22.401.5/4 again?

Sorry for the repeated questions..

Thank you,
[One (M8) Android Development] Sneakyghost:
Your ROM shows 2.22.401.5 in settings/about/software? Well that only shows the ROM version, not your firmware. Your firmware can be checked in Bootloader ("os" line, if it's not broken, see TWRP bug) or you can check it in Fastboot by running Fastboot getvar all.

mobile post
[One (M8) Android Development] gadibob:
hi,

It seems that i have the BUG of TWRP 2.7.1.0, (i have not found information yet how to fix)

I ran the command in ADB, here's the output: I have not seen information on the OS .. Have I done right?

C:\Users\user\Desktop\One_M8_All-In-One_Kit_v\fastboot>Fastboot getvar all

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.16.0.0000

(bootloader) version-baseband: 1.16.2133156.UA15G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

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

(bootloader) serialno: FA46HWM05384

(bootloader) imei: XXXXXXXXX

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B10000

(bootloader) cidnum: HTC__K18

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 098a72e5

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.022s

Thank you
[One (M8) Android Development] Sneakyghost:
Yeah you got that TWRP issue but it's not too bad I can see from your hboot and radio that you're on old firmware still. Go flash my no wipe version of 2.22.401.5/4 to update. Then you're good to go.

xxxx out your IMEI or it might be abused for stolen devices. You shouldn't leave your IMEI accessible to Google, ever.

mobile post
[One (M8) Android Development] gadibob:
Thank you for all the generous help And caring.

A lot of changes compared to "First getvar all command".. now OS show. (also in HBOOT).

Fastboot getvar all:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.18.0.0000

(bootloader) version-baseband: 1.19.21331147A1.09G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.22.401.4

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

(bootloader) serialno: FA46HWM0XXX

(bootloader) imei: 3XXXXXXXXXXXX

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B10000

(bootloader) cidnum: HTC__K18

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: off

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 5e4b24e4

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.025s

Thank you.
[One (M8) Android Development] n1234d:
It'll go away after you flash TWRP again, unless you flash the fixed version
[One (M8) Android Development] Sneakyghost:
I've had reports that the backups created with the "fixed" TWRP will be corrupted and impossible to restore.

If that is true (i had two corrupted nandroids myself lately but cannot remember with which TWRP i did them, so thats no proof) i would keep away from that version for now and wait until Team Win issues their next version. It will almost definitely be fixed in there.
[One (M8) Android Development] c5satellite2:
Can this be used as a boot loader flashable .img?
[One (M8) Android Development] guyd:
I've been using [MENTION=333497]migascalp[/MENTION] 's fixed version since he released it a while back.

I've done many backup's and several restores with it without issue!

I do however leave backup compression disabled.
[One (M8) Android Development] Sneakyghost:
Oh that's good to know because so far i've had only one report of it not creating functional backups and i was wondering if there were more.

So it might have been user error then.
[One (M8) Android Development] Sneakyghost:
That's a RUU mate. You didn't see the "exe" ending?

What you can do is what i do all the time: launch the RUU, then hold it where it is, open task manager, determine the /tmp/ path it extracted itself to (some cryptic number folder) and then copy out the subfolder of that folder (again named some cryptic number). Once you have that in some secure place, rename it to ATT RUU Whatever Version blahblah and then you have the RUU structure ready at your will. Inside is also a ROM.zip which is flashable in fastboot RUUmode. That is the image you are looking for probably. It will be encrypted and signed so you could even flash that S-ON. You cannot however unpack it and make your own firmware from it. You would need someone to decrypt it for you (extract hboot, which should be possible, and submit it to KMDM's git for ruuveal and he might or might not add that key to ruuveal, then you could decrypt it under Linux yourself - right now, kmdm seems to be away and doesn't seem to add new decryption keys, so i have a real hard time getting my zips decrypted. Don't bother asking me because getting my own stuff decrypted is about enough).

[EDIT]

I am adding HTC_621 Taiwan Mobile (x.xx.709.x) packages now. They need testing. I can't test them myself. Anyone from Taiwan willing to test them please do so. All files are up and available via Post #1 Downloads section

Recent additions​

​

[EDIT]

I have just come to know [MENTION=1162986]Captain_Throwback[/MENTION] and must say i am impressed with his skill and attitude. I am glad i can say i will be incorporating his TWRP into my FUU from now on because there seem to be no error reports for it and it's also universal (good for ROM's that are multi-device and offer a recovery with them... hint hint :D ) plus it incorporates latest additions from the TWRP main tree, so its kind of ahead of the official TWRP and there seem to be no flaws noteworthy with it. I appreciate the sharing and recommend everyone reading here to switch to it.

It can be obtained here: http://themikmik.com/showthread.php...-VARIANTS-TWRP-Recovery-(UNOFFICIAL)-v2-7-1-1
[One (M8) Android Development] Sneakyghost:
HowTo fix a broken internal sdcard, repair filesystem, restore filetable

Here's some info post with a definite and very easy solution i wanted to create as a late reaction to an issue described here around Page 20.

The Issue was about 3 people coming here out of a sudden with a "broken internal sdcard" - symptoms included a non-booting phone, failing rom flashes, no access to /data in TWRP or other recoveries and also the /data partition being unmountable.

There is a manual solution detailed on page #20 by [MENTION=5463312]smeejaytee[/MENTION], involving mkfs.ext4 (attached to this post) who never mentioned who actually told him the method (so i can't credit that person). This method can be tried if the below method does not work. It is technically the same though probably.​

The much simpler solution however has been made available by the TWRP developers through their latest update, 2.7.1.0. Here's how to fix:

In the meanwhile try this to fix:

1.) Boot into TWRP

2.) Tap: Wipe

3.) Tap: Advanced Wipe

4.) Tap: select Data, then tap: Repair or change File System.

5.) Tap: Change File System, select EXT4 even though it is already EXT4! (thanks [MENTION=2704897]elencross[/MENTION] for figuring this step out!)

Repeat 4 and 5 for internal storage maybe. Not sure.

Now you might want to reboot back into recovery, try again to mount data. Should work now.​

Note: this is a new function in TWRP and will require the latest download from teamw.in (GSM international only!)

Note 2: [MENTION=1162986]Captain_Throwback[/MENTION] has an even further developed, no-known-errors version for ALL variants (Sprint/Verizon/GSM) which you might like to try out.
[One (M8) Android Development] smeejaytee:
Glad you fixed it I can post the mkfs script if it's needed though let me know

---------- Post added at 06:56 PM ---------- Previous post was at 06:46 PM ----------

Hi again this this the latest version you're talking about as it seems a bit dated but it's the latest one I see on that page I actually think this may be the one I'm using but I haven't seen the repair option but that may just be because I haven't looked for it lol
[One (M8) Android Development] Sneakyghost:
Yea sure link me to the source would be cool so i can credit the guy who described the method. And access for the other users is good to have lol. I I noticed you also never linked the method in your original post either. Still making people use google ;)