yashsingh1/xdaforums huggingface dataset:
[One (M8) Android Development] Sneakyghost:
Panic attacks :D

First thing: cool down, chill. Don't do anything stupid now. What happened to your phone? Well, it can be nothing, just a simple corruption of the Partition. That is easily corrected. BUT it can also mean bad RAM or some other hardware damage and if i encountered a corrupted partition on my phone, i mean a corruption after only a reboot, i would NEVER trust my phone again. I'd try to talk to HTC to have it serviced and if they refuse, i'd sell it and get another one... that much on how i view that...

So, what [MENTION=2977387]donmarkoni[/MENTION] said is 100% correct.

1: download 2.22.401.5 FullWipe FUU (your current firmware does NOT matter)

2: boot to bootloader, write SuperCID to your phone (fastboot oem writecid 11111111) like explained in post one actually...

3: Launch FUU and run it. It'll reformat data if the Chip is still good

4: Flash TWRP again from within fastboot (fastboot flash recovery nameofrecovery.img) download it HERE if you are GSM (you're from Kent, england, so yes, you are most likely not CDMA)

5: push ROM to phone and flash using TWRP (adb push rom.zip /sdcard/rom.zip). ADB works in Recovery. No working Android required.
[One (M8) Android Development] smeejaytee:
thank you yes im gsm and i am already super cid the problem i have is adb no longer works for me but i have a rom on my externel sd card ill try it hopefully ill be ok thanks for your help

edit: ps will the full wipe fuu work with no adb or will i have to do it via another pc thank you so much again for your help like i said i just want to be safe
[One (M8) Android Development] Sneakyghost:
I just wrote that. ADB doesn't necessarily need a ROM. It works in TWRP as well.

I think you're confused about ADB and Fastboot - two things mate...

Fastboot is used in bootloader, uses a different driver set on PC too.

ADB is working only in android (hence it's used either in recovery because that's a "small" android or booted full android), but never in Bootloader. And ADB has its own set of drivers.

For both, you can verify if they're working with a simple command

- fastboot devices will return the serial of the device in order to show that it's communicating.

- adb devices will return the serial of the device in order to show that it's communicating.

If you boot your phone to Fastboot and the FUU fails, check with that command first if Fastboot works at all.

If it turns out that your pc has driver problems, you gotta fix them first. Easily done by downloading HTC sync manager, installing it, then removing it again (drivers will stay).

Why am I repeating what's already on page #1?

mobile post
[One (M8) Android Development] smeejaytee:
sorry fastboot is working fine i was unsure whether full wipe fuu needed adb i was just making sure i appreciate your help really
[One (M8) Android Development] Sneakyghost:
I'll ask a second guy who just came into our support system to come in here - he has the exact same issue and if its not you asking in two places, its weird that the same happened to another dude at around the same time. I'd like to compare the two cases please,

It could be recovery doing a bad job or just random.
[One (M8) Android Development] smeejaytee:
im actally just speaking to someone who has had exactly the same issue after flashing a viper theme it hung at boot so he hard reset and his data partition was corrupted so its not just me it would seem also someone had a similar issue after flashing viper a couple of days ago but he fixed it by flashing twrp as he was on philz when it happened and had to install the rom from an sd card but got it working
[One (M8) Android Development] Sneakyghost:
No sh!t?

Hard reset yea? Both of you?

What recovery exactly?

Lets see what the third guy says if he comes over here.

On the HTC Ville (One S) there was a problem with a factory reset from bootloader while TWRP was installed - it did what you experience now, it killed the partition table.

I have an odd feeling we have a similar scenario going on here. Need to work out the similarities in order to prevent this from happening again.

One thing for sure: its pretty much nothing to do with the ROM or theme. This is below the layer of that software.

[EDIT]

Were you two running the fixed unoffical TWRP by chance? the one that fixes the missing OS line in bootloader?
[One (M8) Android Development] smeejaytee:
ok i was using philz when it happend the guy ive been speaking to has suggested a different approach he said worked for him its a binary called mkfs.ext4 ill show you his instructions thanks again

First

* Download this mkfs.ext4 binary @ [cant post links yet, i PM it to you."

* Connect your device to the PC

* Boot your device in recovery mode

* Open a command prompt on the PC (cmd.exe), type and confirm each command with ENTER:

make sure you copy mkifs.ext4 into0 the directory where you have adb.exe located

* cd "place where you have your fastboot.exe and adb.exe"

* adb push mkfs.ext4 /tmp

* adb shell

* chmod 777 /tmp/mkfs.ext4

* /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext ra_isize -m 0 /dev/block/mmcblk0p47

You will now see some text scrolling along. Just let the tool finish and youre /data partition is perfect once again.

i can show you his opening post too if it helps

here

I have your solution ��

Why?

Because I had exact same problem as you have now.

I'm on venom rom. Flashed 2.0.0 rom had not updated firmware however.

After flashing theme Viper dark I got very, very, very long boot time.

After 15 mins or so I hard "button rebooted" device. Resulting in data block being totally corrupted.

As your virtual SD card is a partition on /Data, and data is totally corrupted you won't see or be able to mount your SD card too.

Reflashing recovery, rom or whatever won't help /data stays corrupt.

Now the best part....

I got the tools for you to make your data block fine again, so it again can be mounted and you can see and use the internal sdcard.

You will of course loose anything on the data and virtual sdcard so you must flash a rom after fixing data.

Tools are on my pc, and I'm on my phone right now so I will upload it later and give you link and instructions.

only trouble is now i dont know which to use and i got adb working so thats a plus
[One (M8) Android Development] Sneakyghost:
OK cool then its not TWRP.

Philz is not recommended for Team Venom stuff. It doesn't cope with some stuff. Namely, the automatic OTA won't work but i think also some aroma stuff doesn't work right there.

Maybe it is random after all. I suggest you use the official TWRP from now on if you get this fixed.

The FUU should also fix this i believe. It might be easier for now.

Try either method and let us know what worked for you. Please.
[One (M8) Android Development] smeejaytee:
i certainly will although the other guy has said full wipe wont work as you cant wipe something that isnt mounted so maybe i should try that first im confused a bit by all of this but if i get it running again i will use twrp and stay with it ill keep you posted thanks for your help once again
[One (M8) Android Development] Sneakyghost:
Dont get confused by the "wipe" tag in the FUU name.

It is actually redoing the partition. Don't worry. It'll be very similar to the tool you described. That tool is also inside the recovery and you are just using it manually with that solution. I would not be surprised if the FUU flash executes the exact same command...

[EDIT]

I need sleep, back tomorrow. Thanks for working with me here. Interesting stuff.

Please, Team Venom users, as of now it looks like some devices don't boot the 443 ROM while on old firmware and some very few get a corrupted data partition if then forcefully rebooted, so i strongly suggest anyone passing by here reading this, go update your firmware before flashing ViperOneM8_2.1.0 and same for the other recovery zips obviously.

[EDIT 2]

Turns out, third guy was also using Philz touch. Stay away from that as well for now.
[One (M8) Android Development] smeejaytee:
hi again i just tried installing full wipe fuu and got this problem whilst installing

Extracting files to C:\Android folder

Cannot create adb.exe

Cannot create AdbWinApi.dll

but adb is working why is this saying that it told me to close everything and reboot windows and try again i did that and rerun the installer and got the same issue any ides please

i just checked and ive already got those files but adb doesnt say exe. but it does say application i believe thats the same thing
[One (M8) Android Development] Sneakyghost:
Probably no write permissions to your own C drive? Are you on an admin account on your PC?

Or that ADB is running and the file locked so you can't overwrite it. Open your task manager and kill adb if you see it running, then try again. Make sure you're admin.

mobile post
[One (M8) Android Development] smeejaytee:
that might be why i didnt run cmd as admin

adb is running in processes ill close it but do you mean run the fuu aplication as admin or how can i do it thank you again and im soory to be a nuicence

my laptop says that i am logged on as administrator
[One (M8) Android Development] dgtiii:
Can't hurt to run the full FUU application as Admin
[One (M8) Android Development] Sneakyghost:
Run FUU explicitly as admin by right clicking and choosing run as admin.

You can also use the taskkill command in Windows to end a program forcefully. Here's some documentation: http://www.computerhope.com/taskkill.htm

Example:

Open cmd and run:

taskkill /f /im adb.exe

mobile post
[One (M8) Android Development] smeejaytee:
not to worry i ran it and im all booted up thanks so much for your help im using twrp now ill stay with that just need to download the latest viper rom thanks again
[One (M8) Android Development] Sneakyghost:
Perfect. Then I can close my eyes now and sleep, yeah? Thanks! :p

mobile post
[One (M8) Android Development] dgtiii:
Thought you were already asleep! Good work mate.
[One (M8) Android Development] smeejaytee:
yes thank you and goodnight pleasant dreams thanks so much for your help
[One (M8) Android Development] donmarkoni:
Oh... I was thinking too that he is already asleep. He know this sh!t so good, that he can type it while sleeping. ;)

Good to see you got it sorted. :)

BTW, guys, I'm using PhilZ recovery since forever and never had any problems, just for the record. :D
[One (M8) Android Development] Sneakyghost:
You're not gonna promote Philz now after it obviously was involved in three corrupted data partitions in a day?

If you're so happy about it you can help narrow the cause down by trying to repro the scenario.

It's easily fixable as you can see.

Please mate, do what they did and try to get your data partition broken.

Flash old firmware, flash Philz again, flash Viper 2.1.0, if it gets stuck at boot, send logs before killing it, then force reboot and see if the partition gets killed.

I'll probably do that myself as well later.

mobile post
[One (M8) Android Development] donmarkoni:
OK. :D I'm sorry to irritate you mate, never meant so. Downloading full Viper 2.1.0, slow speed at work... Stay tuned... ;)
[One (M8) Android Development] Sneakyghost:
I'm not irritated, I'm trying to get an idea what this is. I don't want lots of broken data partitions in our support. I guess it's the "old firmware/new ROM" problem but we need to rule out the recovery as well. Before that, it's not safe to assume any recovery, no matter if Philz or CWM or TWRP are good to use.

[EDIT]

having a bit of a busy day here so I'll only be looking at this again later.

mobile post
[One (M8) Android Development] smeejaytee:
I'm just glad to have my phone working again I really appreciate the help you gave me yesterday and I'm thankful your looking intoit in case it happens to others your a good man I don't know what I would have done without your help
[One (M8) Android Development] Sneakyghost:
TmoUS 2.22.531.5

K no worries probably just a select few phones reacting like *******.

Since [MENTION=4174733]Behold_this[/MENTION] closed his Firmware thread over in T-Mo, i'll do a quick FULL WIPE and NO WIPE FUU for those guys wanting it my way and wanting to run ViperOne with the new TmoUS firmware.

Here are the files.

Recent additions​

​

TESTED WORKING (by [MENTION=4884973]beats4x[/MENTION], thank you so much!!!)

Downloads as usual, page #1, Post #1​

[EDIT]

Now ready to break my phone big shout out to the donor who made this all possible ;) #Hacked :D

(Seriously, last nights bug is putting me off and i want to know why it happened. Thanks [MENTION=2977387]donmarkoni[/MENTION] for helping with trying to repro it!)
[One (M8) Android Development] wirral59:
Is there a 2.22.401.5 no wipe for international version with fixed TWRP version to always show OS version I know there is no difference to 2.22.401.4 would like 2.22.401.5 version to show in bootloader My OCD lol thanks
[One (M8) Android Development] Sneakyghost:
Nah. At the time i did those i couldn't make myself include a hacked TWRP because it kinda breaks with my principles. Did so for the TmoUS today tho cuz i am tired of the support cases where people can't obtain their MainVer and OS line in Bootloader and i am then trying to figure out their current firmware. Bloody annoying. So, now i broke with my principles and did it but for you, you'll need to flash it manually right after the FUU before booting. Then your OS line will stay.... sorry...
[One (M8) Android Development] wirral59:
Understood Sneaky thanks Is there a way I can make my version number be 2.22.401.5 in bootloader It's just my OCD lol I'm running Viper 2.1 so I'm on 2.22.401.5 right? Btw thanks very much for all your hard work and sacrificing your device for us It's very much appreciated
[One (M8) Android Development] Sneakyghost:
There sure is.

download the .4 NoWipe zip, extract the android-info.txt, edit it to say .5 where you find the line MainVer and then push it back to the zip.

Its exactly what i noted on messing with RUUmode zips in Post #5

you can also avoid flashing any partitions again by leaving only one image in the zip, something like splash (sp1.nbh) which is harmless and then flash that zip in RUUmode with the edited android-info.txt.

It will then make the OS line read the proper version. Very easy mate.

Check out post #5

_______________________________________

I skimmed your log now. Thanks. I learned something new again this time actually. This is it:

The M8 flashing process is different than on the M7 - i had seen a log before, which had a long section before the error 90 stage, but didn't pay attention. Now i see whats going on there.

Previously, the Pre-Update only updated the hboot and then asked you to "flush" image again immediately.

Now, its flashing half the package and then throws error 90 and then flashes the rest. Now, the critical parts are all flashed together and the less vital ones like the TP and Sensor-Hub and such are flashed later.

If i am not totally mistaken, this is a security measure following the "incompatibility bricks" from the last phone generation, where flashing some hboot into some firmware lead to a few bricks. I might be mistaken but this is how i understand it.
[One (M8) Android Development] schollianmj:
ok, this may be a stupid question, but shouldnt using the full wipe method wipe my custom ROM off? I was under the belief that my phone would be inop until I went into recovery and installed a ROM from the SD card....

I used the full wipe 2.22.401.5 and while it did wipe the internal, it also wiped out my recovery, but didnt wipe out my ROM. Luckily... I got it to reboot, but since it had no recovery I tried to install one, I preferr twrp, so I downloaded the app from play store, but it wouldnt run because it couldnt get Root. I tried to flash recovery from Fastboot, but it kept failing. finally tried a version of twrp that was included with Hasoons all in one tool... granted the tool wouldnt flash it, but when I moved it to my ADB directory I got it to work via fastboot.

Once I finally got my Recovery back working I used it to reflash SuperSU... then i wiped everything and reflashed my ROM clean. No clue what I did wrong or what happened...
[One (M8) Android Development] digitard:
There is no ROM image included in these so it wont wipe the ROM itself. Just the storage, but not /system from what I read on page 1 I think.

I normally fastboot and update the firmware

reboot

fastboot and install recovery

reboot

recovery install my same ROM (for SuperSU and any randoms that may have somehow gotten wiped to be safe) without wiping user data

reboot

profit

Worked fine w/ the newest firmware just put up. Did that both yesterday and today, and had installed the prior current 2.22 yesterday to alleviate my long boot times even though I had flashed a 2.22 version early on... since the new T-MO firmware came out today I updated to that one to be safe with the new radio, and making sure I don't have any WIFI calling issues once that's updated w/ Viper. No problems at all from my Macbook Pro (OSX 10.9)
[One (M8) Android Development] wirral59:
All done Sneaky thanks mate
[One (M8) Android Development] Sneakyghost:
[MENTION=2977387]donmarkoni[/MENTION] i just flashed Philz in fastboot, didn't erase anything but phone booted into Dalvik, was set to ART before.

You noticed that crap?

How can recovery cause that? Something definitely dodgy with that recovery.

Aroma looks terrible in Philz.

Flashed stuff with Philz, does NOT cause phone to be stuck at kernel stage.

All seems fine except the weird, random switch to Dalvik.

Cannot repro broken partition problem. Hmm. Guess i'm gonna let it be and wait for more clues to turn up. Out of ideas.

Yeah i haven't figured out how to make the FUU wipe system without including a full system image. So the /system partition doesn't get touched.

However, since /data goes away your ROM suffers a heavy blow that equals a factory reset and if your ROM depends on a modified kernel, it might not boot at all anymore afterwards, hence my statement "phone won't boot" because its better to state that than saying "Hey, after the FullWipe you can still boot but it will be factory reset" because for some people it would mean they expect to have a booting android and then they dont...
[One (M8) Android Development] donmarkoni:
Hmm... Strange... Will try that with ART/Dalvik swap as soon as I can.

It's a known Aroma bug, believe it or not. Well, it's caused by PhilZ cause it's developed, updated with new kernels and drivers, unlike Aroma, which is very old now, not updated since forever... Use PhilZ v.6.26.6 for the time being.

Should I even try more to break partition? I thought that dirty flashing had better chance of making a mess. I'll try when I get bored one of these days. ;)
[One (M8) Android Development] smeejaytee:
I also had trouble seeing anything in aroma on philz it was terrible

Btw this is how it happened to me I was on the latest viper I flashed the dark one theme from venom hub in recovery I went thought clicked next to everything and hit the reboot button at the end when it rebooted it hung one the HTC one screen for a while so I rebooted and went to recovery and cleared caches I will add I didn't notice if the problem had occurred yet so after clearing caches it still didn't boot so I hard rebooted again and I then spotted the could not mount data issue I hope this helps you
[One (M8) Android Development] old.splatterhand:
[MENTION=1102297]Sneakyghost[/MENTION]

Is there anywhere the stock TMUS 2.22.531.5 firmware.zip around? I mean the one

with

HTC signature?
[One (M8) Android Development] Sneakyghost:
Flashed back TWRP while on ART -even erased Recovery and Kernel cache (fastboot erase cache) and dalvik stuck. Now this is weird.

I used Philz Touch from here: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/m8/ the version philz_touch_6.48.4-m8.img which had the latest file date.

Just admit it: TWRP is better. Common mate... :laugh:

KK mate good to know. I think since it obviously worked all the way through recovery the thing happened upon reboot. I am inclined to believe that the older firmware and the newer ROM/Kernel don't like each other. Either way, i am giving up on this, there were no new cases today and its easily fixable, so lets hope that was a once-off thing and people are smart enough to update their firmware now.

There is. In the TmoUS forum where i got it from. Thread is pretty much at the top today. I'll be so kind to search for you. Oh, here it is, took me 20 seconds to find the thread again: http://xdaforums.com/showpost.php?p=54905572&postcount=122 ;)
[One (M8) Android Development] pro4ever:
hi sneaky my software number says 401.4 when reboot into bootloader its got 401.5 have i done something wrong?
[One (M8) Android Development] Sneakyghost:
Well mate, i don't know what you did. You didn't tell me. How can i say if its wrong or not?
[One (M8) Android Development] old.splatterhand:
Thanks. I searched myself too, but maybe my keywords were not good enough.
[One (M8) Android Development] schollianmj:
That makes sense. thanks for the knowledge.
[One (M8) Android Development] pro4ever:
its my fault m8 had 401.4 firmware adb ur 401.5 thats what i got
[One (M8) Android Development] Sneakyghost:
Sorry man i dont understand a word you say and its very late, been working on firmware stuff and support tickets all day i am not gonna guess around i'll just tell you this: if software in phone says a different number than the OS line in bootloader that just means ROM and Firmware have different versions, so what. Nothing wrong. Ok.

I think i am going to bed i am getting in a bad mood now.

Laters folks.
[One (M8) Android Development] pro4ever:
phone is soff software version ends in 401.4 on my phone seen ur guide wanted to update so i can use venom rom as its 401.5 latest so i download

15.08.2014	2.22.401.5

http://www.androidfilehost.com/?fid=23622183712457302

e3047c8bc8e6abcb62e3eea2cd3ddaee

m8_ul

and Step-By-Step:

1. If device is booted into Android, reboot into bootloader by running:

Code:

adb reboot bootloader

1.a Or else, if your device is in a different state or you just prefer the button method:

Press Power for 15 seconds and hold Vol UP at the same time, when the screen and charging LED go dark immediately slide your finger down to Vol Down until you see the bootloader screen. Notice: First VolUp, then VolDown as soon as the screen goes dark (and you hear the windows connection sound if your phone is hooked up).

2. Now place the Firmware_xx.zip into your adb/fastboot folder.

3. Now run:

Code:

fastboot oem rebootRUU

4. Followed by:

Code:

fastboot flash zip Firmware_xx.zip

ur guide all like u said in ur guide and thats what i have if it still ok for me to install venom all good just thought it was odd as bootloader says 401.5 and in settings about software says 401.4:good:
[One (M8) Android Development] Souldrinker:
As Sneakyghost told you the software version and the bootloader versions are two different things. The bootloader shows the firmware version and the about software show the rom version.

For me the bootloader show 401.4 (since I flashed that fuu a while ago) and the software 401.5 since I'm on Viper 2.1. Those versions doesn't need to match. As long as you're on firmware 2.x the latest Viper will run just fine...
[One (M8) Android Development] jureca:
You Might also include the System.img?, Thanks

Enviado desde mi HTC One_M8 mediante Tapatalk
[One (M8) Android Development] smeejaytee:
I have a feeling you may misunderstood me yesterday somewhere along the line I was on the 2.22 firmware but I want sure which one or is that what you mean by older firmware because I may have been on the 14 and not the 15 or if you were referring to someone else I'm sorry for trumping in