yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] fkofilee:
Folks

Can i refer you to my Desire C Process to retrieve the unlock code from the Partitions?

I believe HTC may have slipped the unlock code in here somewhere again.

While im not any good at writing scripts, can someone please write me a .sh file that will search for an 8 digit number across ALL Parititions and dump it into a .TXT file as i cant remember how to export the results to aTXT file
[One (M8) Android Development] Sneakyghost:
?

ViperOne M8 FTW
[One (M8) Android Development] Antagonist42:
Try this thread http://xdaforums.com/showthread.php?t=1959445

[DEV][REF] El Grande Partition Table Reference

This'll help with tools and info ;)

Bashing away at my HTC Desire C
[One (M8) Android Development] Sneakyghost:
[MENTION=5089229]russellvone[/MENTION] i updated my post one page back with what you need. Hope it helps.
[One (M8) Android Development] Sneakyghost:
I like that Button-Thingy in your signature, the one about a-holes... was that for me?
[One (M8) Android Development] russellvone:
much appreciated
[One (M8) Android Development] Sneakyghost:
Mate. You are more than welcome. But i do expect that you drop your findings here so others can profit, if you pursue the matter any further. That's the only real way this works. Let me know if 12 is correct and if the script works or not.

There is nothing more annoying than work being done twice.
[One (M8) Android Development] russellvone:
I always share my findings. it's a habit I picked up from a good friend of mine

[MENTION=5537766]Modding.MyMind[/MENTION]

EDIT/UPDATE

sp1 is the splash screen.

I didn't use your script so I can't confirm working on Verizon M8

I just used dd to pull it, from it's location, then dd to flash a custom splash1.img....then used dd to flash stock splash1.img back

thanks
[One (M8) Android Development] Sneakyghost:
1.12 international system dump required

I've been a complete idiot.

I forgot to dump my system when i got my M8.

I can't S-OFF.

Anyone here who's gotten a 1.12 international system dump or could make me one? i really only need system and data to get HTC OTA function to work, Recoveries seem to be available already. I can do with a RAW dump or a common recovery backup, whatever there is. Any help appreciated.

Thanks

[EDIT]

User [MENTION=4782292]mick_soul[/MENTION] was kind enough to provide a TWRP backup of 1.12. Thank you so much!

[EDIT 2]

I just now realized there is a thread full of Backups made by [MENTION=4252827]Mr Hofs[/MENTION] right here: http://xdaforums.com/showthread.php?t=2701376

Just in case anyone needs a backup ;)
[One (M8) Android Development] donmarkoni:
@Sneakyghost, hello... :D

I just know how delighted you will be with this post full of useful info. ;)

Well, anyway, I'm here, so I'll try to make small contributions as I did for M7.
[One (M8) Android Development] Sneakyghost:
-.-

This thread was already DOA.

I got no S-OFF, there are no RUU's I can haz access, so well, your post is just about as useful as the whole thread.

signatures are for girls
[One (M8) Android Development] donmarkoni:
I read about you not having S-OFF, but thought you had it by now. Sorry to hear the opposite. Which hboot, 3.16?

I had luck and did S-OFF - unlocked via htcdev, installed PhilZ recovery, installed ViperOneM8 and firewater did it's magic.
[One (M8) Android Development] Sneakyghost:
The short version: device affected by the infamous hardware difference, now i found two dead pixels and begged my carrier to swap it out but they seem to be low on stock so they only offered repair. Pick-Up was supposed to happen tuesday, truck never came, instead got email asking me for a phone call. Appointed to tomorrow/Saturday. Will try to negotiate an exchange. If fail == wait for [MENTION=711482]beaups[/MENTION] to work his magix somehow sometime.

Can do nothing firmware without being able to test what i upload. Soz. Also, not much available right now anyhow. Guess Firmware only begins to kick off with the arrival of 4.4.3 bases. Hope we see some RUU's leak out of HTC by then.
[One (M8) Android Development] dgtiii:
I hope it works out and you get an exchange mate! Best of luck....
[One (M8) Android Development] russellvone:
[MENTION=1102297]Sneakyghost[/MENTION]

I've updated my findings

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

[INFO]Partition List HTC ONE M8 / RAW DUMP SCRIPT

[quote name="Sneakyghost" post=51853239]Mate. You are more than welcome. But i do expect that you drop your findings here so others can profit, if you pursue the matter any further. That's the only re......
[One (M8) Android Development] Sneakyghost:
[/QUOTE]

Thanks a ton for confirming that the splash is in a different location than on the M7.

In fact, on the M7, the splash is in partition 13, which on the M8 is called "Wi-Fi". So if I should have a guess, flashing an M7 splash screen zip would probably break Wi-Fi.

On the other hand, modifying the M7 splash zip's is a breeze - unpack and replace mmcblk0p13 with mmcblk0p12 in the updater-script. The splash will most likely still be of the same size due to the same display resolution, so no worries.

People should by all means avoid to flash M8 splash zip's on the M7 though - partition 12 is the hboot on the M7. Doing that will replace the bootloader with the splash. The phone will be a brick.

Anyone creating a splash screen thread should place this as a warning in the OP or write an updater script with a device check so that it doesn't flash on the M7!

signatures are for girls
[One (M8) Android Development] mswlogo:
I have two Sprint HTC M8's.

One that 3G stopped working and the other one fine.

A few folks feel it was after the first Sprint OTA (that many of us applied manually) lost 3G.

I've "backed" up all the partitions from the working phone.

Sprint is scheduled to replace the first phone (with probably a refurb and on back order) nice guys. Hence why I currently have 2 phones.

So I have nothing to lose.

Would it be insane to just blindly restore all these partitions from the working phone to the broken phone?

Will that surely brick it? Are there a few partitions I should definitely skip that contains some phone identity or keys info?

Thanks for providing this script it will serve as a "backup" for the new phone anyway.
[One (M8) Android Development] Sneakyghost:
Yeah. I can work it out tomorrow. Not tonight, I need to shut down my machine soon. If you hang in I could probably tell you which lines in my script too delete so it's not backing those up, then restore the ones you get to the other phone. I'd just beg you to write the restore script yourself cuz I don't have the time. It's basically just reverting the dump command. Dd works in both directions. It's really easy once you get the hang of it.

signatures are for girls
[One (M8) Android Development] mswlogo:
Yeah, reversing script is easy and I know DD goes both ways. Thanks.

Do you know by chance which partition contains the "PRI" (Primary Roaming Index) information (not the PRL). I suspect that this is the culprit and they are not easy to roll back.

Since digging down this path Captain has posted the original firmware and the firmware has reverted but PRI did not. So I don't think PRI was included in his firmware (or it knows to ignore going in reverse).

Thanks again.
[One (M8) Android Development] guyd:
I did exactly that and flashed my favorite splash screen from the M7 onto my M8 by editing the updater-script and pointing it to the correct partition. Worked perfectly!
[One (M8) Android Development] Sneakyghost:
Did you look at my partition list for clues on that "PRI"?

Did you open candidate partitions with a hex/text editor to see if you can find clues?

What about the radio_config (rcdata)? It contains some configuration but nothing reading explicitly "pri".

About the restore job: actually you should not restore any partition which contains individual device data (serial, imei). In order to avoid that, you'll have to load each partition dump except data (I know it's not there and that partition is too big) into a hex tool and search for IMEI, then repeat the search for serial.

You can exclude all partitions which come as image files in a RUU, because those do not contain unique device data.

[EDIT]

Aren't the Sprint guys the lucky one's who already got a RUU.zip?

Did you run that over your damaged phone? Wouldn't that help?

signatures are for girls
[One (M8) Android Development] alasdair.grant:
I used your spreadsheet to dump partitions from my phone to make an ruu so that I could convert back after I went to GPE. Worked perfectly. Thanks for the info.
[One (M8) Android Development] housry23:
So you have a working sense ruu? Have you tested it? For which M8 version?
[One (M8) Android Development] alasdair.grant:
Yes I do. Tested multiple times. Went to gpe and back to sense 3 times. It's for HTC__039. Unbranded Aussie. Only thing missing is /data/preload.
[One (M8) Android Development] housry23:
Did you have to split the system image? This is good news here. I'm going to look into making a RUU for the Dev edition. I've never tried before. Any tips on how? I'm at work and will do some research on it tomorrow, but I'd love to have a full RUU for the Dev edition.
[One (M8) Android Development] alasdair.grant:
No splitting. I just dumped the block and renamed it system.img. I basically dumped all the partitions and that matched the gpe ruu ..

---------- Post added at 02:43 AM ---------- Previous post was at 02:42 AM ----------

Later I Will send the commands I used and the list of partitions I dumped. At work now.
[One (M8) Android Development] housry23:
Hmm... Others have tried and the system always fails to flash on sense RUU.
[One (M8) Android Development] alasdair.grant:
Well they did it wrong then.
[One (M8) Android Development] mswlogo:
The RUU is for the "Harman" Firmware/ROM. I like the Harman Firmware/ROM but as soon as I flashed the first OTA firmware. Problems started. Others have felt that way as well. I believe the Harman Firmware maybe similar to what was in the OTA. I wanted to try to back it to completely stock.

I have a Stock M8 and it works fine. I'm gun shy about updating firmware.

So I was curious if I could "restore" it (i.e. RUU it) from a Stock Firmware Phone.
[One (M8) Android Development] Sneakyghost:
Yeah I totally get your point. It's possible with S-OFF. What you need to know is: stay away from GSM firmware for your Sprint phones, restore only partitions with no individual/unique device data.

I realized I have no Sprint dump to look through so I can't make 100% sure I tell you the right partitions to avoid. I believe the fastest way to determine what is safe to restore is to make a full dump with my script (first determine if your phone got the same partition layout, else adjust the script), then delete all images which are also in the RUU, then open each remaining image with a hex tool and run a search for the device IMEI, then repeat and search for device serial.

That way you'll only have to look at a very few images.

Once you've got a list of partitions to avoid, you can put up a request here for someone to dump an old Sprint firmware for you.

signatures are for girls
[One (M8) Android Development] mswlogo:
I have a dump of clean phone (I bought a 2nd one).

I restored the broken one to as close to factory as I could then dumped it.

Then I diffed it with a clean phone dump.

I eliminated everything that was the same.

This is what's left that is different and some of the differences I see.

I added notes at the end of what I saw.

I tagged some with common pattern diff (this might be IMEI) because it was like 4 Bytes difference I saw repeated in multiple diffs.

dev: size erasesize name

mmcblk0p2: 076f7c00 00000200 "pg1fs" SIMLOCK + 32 Bit Number Diff

mmcblk0p3: 00004000 00000200 "board_info" HAS MEID

mmcblk0p5: 00040000 00000200 "mfg" HAS MAC ADDR

mmcblk0p6: 017afc00 00000200 "pg2fs" Has Keys

mmcblk0p12: 00500000 00000200 "sp1" Regular Patterns of Differences

mmcblk0p14: 00008000 00000200 "ddr" RDD- Difference

mmcblk0p18: 00800000 00000200 "radio_config" Has MSL HAS nnnn@hcm.sprintpcs.com where nnnn is different

mmcblk0p22: 03200000 00000200 "custdata" Common Pattern Diff + Random Diffs

mmcblk0p25: 00180000 00000200 "modem_st1" Random Diffs

mmcblk0p26: 00180000 00000200 "modem_st2" Random Diffs

mmcblk0p27: 01400000 00000200 "fataldevlog" Random Diffs

mmcblk0p31: 00140400 00000200 "local" All Diff Small Rest 00

mmcblk0p33: 00100000 00000200 "cdma_record" Ramdom Diffs

mmcblk0p37: 01900000 00000200 "carrier" Common Pattern Diff + Ramdom Diffs

mmcblk0p38: 00040000 00000200 "sensor_hub" Lots of diffs in Header

mmcblk0p39: 01e00000 00000200 "devlog" Common Pattern Diff with other files

mmcblk0p41: 02de6000 00000200 "reserve" Few Chars diff in Header
[One (M8) Android Development] Sneakyghost:
Hmm that's good. What I didn't get though: your second clean and working phone is on the same software level or older? Because if your theory shall be proven correct, we need a dump of an old Sprint version before the OTA, which according to your theory, broke yours and a few other phones.

Differentiating partitions and hoping to find hex patterns that could resemble an IMEI or serial is a good idea but by far not safe enough to rely on it, hence I would just go without doing that. It will be enough to search the plain text strings with a normal search function for IMEI and serial of the donor phone.

Past HTC phones had no encrypted unique identifiers I believe.

signatures are for girls
[One (M8) Android Development] alasdair.grant:
Here are the ones I dumped for my ruu.

dd if=/dev/block/mmcblk0p16 of=/sdcard/adsp.img

dd if=/dev/block/mmcblk0p42 of=/sdcard/boot.img

dd if=/dev/block/mmcblk0p11 of=/sdcard/hboot_signedbyaa.img

dd if=/dev/block/mmcblk0p6 of=/sdcard/pg2fs.img

dd if=/dev/block/mmcblk0p20 of=/sdcard/radio.img

dd if=/dev/block/mmcblk0p43 of=/sdcard/recovery.img

dd if=/dev/block/mmcblk0p8 of=/sdcard/rpm.img

dd if=/dev/block/mmcblk0p12 of=/sdcard/sp1.img

dd if=/dev/block/mmcblk0p45 of=/sdcard/system.img

dd if=/dev/block/mmcblk0p9 of=/sdcard/tz.img

dd if=/dev/block/mmcblk0p17 of=/sdcard/wcnss.img

---------- Post added at 09:50 AM ---------- Previous post was at 09:31 AM ----------

Also you can't just push system back by itself using dd or in ruu mode if you are going back from ge converted to sense. You must flash all the backed up partitions in ruu mode so that repartitioning will take place. This is where others made a mistake.
[One (M8) Android Development] housry23:
Awesome man thank you! I know someone with a completely stock Dev edition so I'll get him to dump and try it myself. ?
[One (M8) Android Development] Sneakyghost:
If you care to look at my M7 thread (technically it is now [MENTION=5324408]herwegan[/MENTION]'s thread now though) for the thing i called "FUU" and get the idea how to layout the structure, you'll easily be able to recreate HTC's thing.

The idea is: unpack an original RUU (doubleclick the exe) then hold it there, then check where it extracted to (/TMP/somecrypticnumberkey) with e.g. Process Explorer or similar tool and then copy that extracted RUU folder to some other place (the RUU will delete itself after completion, but if you copy it to some other place it won't).

Then take out all leftover installshield files (you can find out by diffing your RUU folder against my FUU - everything in my FUU needs to stay, the rest can go away). Then you have reduced its size already considerably. Then you can drop any RUUMode zip into this structure (where ARUWizard.exe resides) and then use WinRAR to create a self-extracting archive, put some nice graphix in and Voilá! you got your self-made RUU.

Regarding the dumped images: i would make sure to rename e.g the hboot dump to "hboot" and not "hboot_signedbyaa" because as a matter of fact, its a raw image, its not the stripped-down image of the RUU and its NOT signed. Keeping the names separate from the original names will ensure that people recognize this as custom stuff. This is important also for the final RUU filename plus a clear and explicit warning that that is custom stuff and carries a considerably higher risk than a factory made RUU. It is by no means similar. Its very different. RAW images from DD are not stripped of blanks (unless you are so familiar with DD that you were able to properly use the strip white space parameter).

If you ever intend to release anything like that to the public, you need to be very responsible. It is not acceptable to push out stuff to XDA where nowadays the majority of users are consumers and not devs. This thread here is in the DEV section and what you do is totally interesting, its exactly what i love to do, but when we do this, the dev section does not mean everyone reading here is actually an advanced user. Most are not. Everyone publicizing stuff has a certain amount of responsibility.
[One (M8) Android Development] housry23:
Thanks for the info. I'll definitely look at the thread. I'm only doing this for personal use. If successful, I could share, but I'd rather not and wait for an official RUU. I completely understand what you mean about having some responsibility if releasing an unsigned, unofficial, home brewed RUU.
[One (M8) Android Development] donmarkoni:
I'll just leave this here... ;)

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Marko\Desktop\M8\fastboot>fastboot devices
SH********** fastboot

C:\Documents and Settings\Marko\Desktop\M8\fastboot>fastboot erase cache
erasing 'cache'...
OKAY [ 0.078s]
finished. total time: 0.094s

C:\Documents and Settings\Marko\Desktop\M8\fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.016s]
finished. total time: 0.016s

C:\Documents and Settings\Marko\Desktop\M8\fastboot>fastboot flash zip hboot_firewater_m8_1.54.401.5.zip
sending 'zip' (458 KB)...
OKAY [ 0.188s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) total_image_number=1

(bootloader) start image[hboot] unzipping & flushing...
(bootloader) [RUU]UZ,hboot,0
(bootloader) [RUU]UZ,hboot,56
(bootloader) [RUU]UZ,hboot,100
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
(bootloader) current_image_number=0

OKAY [ 1.781s]
finished. total time: 1.969s

C:\Documents and Settings\Marko\Desktop\M8\fastboot>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s

C:\Documents and Settings\Marko\Desktop\M8\fastboot>fastboot devices
SH********** fastboot

C:\Documents and Settings\Marko\Desktop\M8\fastboot>

That was new hboot on their firewater site, although not (yet) enghboot. Looks like the guys are working... :cool:
[One (M8) Android Development] Sneakyghost:
YeahKThnxBye... :(

My device went into service now after i tried to negotiate an exchange and failed. They even made me swallow a two-week period without device.

Dunno how i could accept that, Its pretty damn unacceptable. I bought a 660 Euro device from my carrier, extended my contract early, paid off the M7. Its a pretty big Win for them. Then they refuse an exchange simply because i called 1 bloody day after the 14 days buyers remorse period...

SUCKS. Had to buy an old Sensation for 50 bucks to get me over those two weeks. Which sucks even more. Slow, small, run down. How am i supposed to do my work if i cant make or receive calls?

I sometimes wonder what the story is with support in germany. I am pretty sure that wouldn't be possible in e.g. the US.
[One (M8) Android Development] donmarkoni:
Sorry to hear that mate. Didn't mean to "step on your sore toes". :(

But, at least you can do something. I would be pretty much f***ed up here, by my country's laws, and how are they put to practice.

I hope they can't fix it, or put it back together without noticeable damage, so they must give you another one... One... M8... m8... mate... (notice the words game?) Hope to cheer you up a little.

Stay optimistic, you realistic german guy! :)
[One (M8) Android Development] Sneakyghost:
That's exactly what I'm hoping for. Please break it! Make me have a new one please.

Knowing the repair quality Arvato delivers, it's very likely they actually do break it. 2012 I had 3 OneS sent in for repair with them and they broke them all...

Gesendet von meinem HTCSensation mit Tapatalk
[One (M8) Android Development] dgtiii:
Sneaky, I apologize in advance for the off-topic, but I need your expertise and insight mate. [MENTION=2977387]donmarkoni[/MENTION], please feel free to chime in sir.

I have the Dev edition M8, s-off, running Viper and the stock kernel it comes with since the day I got it (currently Viper 1.60). This is going to be more interesting in a moment, but after I got s-off I successfully supercid'd, and updated to wwe firmware 1.54.401.5 (same base as Viper) using the rebootRUU method I learned from [MENTION=1102297]Sneakyghost[/MENTION] in his M7 firmware thread - worked flawlessly. Using fastboot flash in RUU mode, I have also flashed a red text removed modified hboot and a splash screen, all no problem, all working just like on the M7. So far so good, right?

Well today, I looked at the M8 updates thread in the General section, and on page 23 it mentioned an OTA update to the Dev edition (1.54.1540.9), with a link to the update thread: http://xdaforums.com/showthread.php?t=2739571

I thought ok, why not? I downloaded the OTA, extracted the firmware, the firmware files looked normal, I deleted the included hboot, boot, and recovery images, like I've done every time I've flashed firmware on the M7 & M8. I then did the normal RUU flash steps, the flash was successful, did it a second time to be sure, even though it didn't look like this was necessary (did not get the pre flush message, everything flashed the first time), got the success message again, then did fastboot reboot-bootloader, just like normal. INSTANT BRICK! My M8 did not reboot, lost the red charging light (since it was plugged in to my PC), and my PC detected the dreaded QLOAD_BULK device. Wtf? I've tried every trick I know to get the device on, it's dead.

So I went back to the Dev OTA update thread I linked and read more (which I fully admit, I should have done before), and another person on there, [MENTION=3647976]guyd[/MENTION] did the exact same steps as me, and had the exact same result, and I mean exact same, hard brick.

So my question is, what is different about flashing firmware on the M8? How could it work (just like on the M7 with s-off) when I flashed the .401.5 firmware (and modified hboot, splash, etc,), yet hard brick on another firmware following the exact same process as what has always worked? [MENTION=3647976]guyd[/MENTION] had the exact same issue, and I think [MENTION=1335963]c5satellite[/MENTION] had issues flashing the .401.5 firmware. Any ideas/insights mates?

Thanks for your patience and I apologize for the long OT.

Edit : the only file in the firmware I flashed which I didn't recognize/is different from the M7 was the wcnss.img, but that is in the partition list here for the M8, so I thought it would be ok.
[One (M8) Android Development] guyd:
I still have my hard bricked M8 sitting in the box waiting for someone or someplace that can jtag/riff/etc bring it back to life for me.

[MENTION=372570]GSLEON3[/MENTION] found my post about what happened to me and offered to help, but I've not heard anything back from him.

I also removed the recovery.img and boot.img from the firmware.zip file using WinRAR before flashing it. (I kept the hboot.img)

Like you, I thought extracting the firmware.zip from an OTA.zip file would would work in fastboot oem rebootRUU mode.

Like me, you now have an expensive brick :eek:

If you have any success in finding a solution your (our) dilemma, please PM me.