yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
I've been trying to flash an AT&T HTC One M8 with the GPe ROM found here: http://xdaforums.com/showthread.php?t=2706441

I've used this guide and everything went fine: http://htc-one.wonderhowto.com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444/

I was in the TWRP Recovery and wanted to format the internal sd card for a fresh start, so I formatted. Afterwards I was unable to get back into the recovery, for some reason I can't erase or format recovery using fastboot, erasing the cache and flashing the recovery image again only brings me to a flickering TeamWin screen, then tries to normally boot but nothing is there for it to boot into so it just sits in a boot loop.

I've tried Philz recovery as well. That works for a little bit but after 10-15 seconds the phone tries to boot normally again and I get stuck in the boot loop.

I tried running `fastboot oem rebootRUU`, that brought me to a black HTC screen and gave me the ability to use fastboot. In RUU mode, I erased the cache again and reflashed the recovery, then erased the cache again and rebooted to fastboot. Tried to boot into Recovery and was greeted with the flickering TeamWin logo and a boot loop.

Can anyone give me a hand here?
[One (M8) Q&A, Help & Troubleshooting] androidbuff123:
if you are able to go to RUU mode.. I would suggest you install the Google Play Edition RUU found here..

http://xdaforums.com/showthread.php?t=2708589

This should set you to the GPE that you were on.

If you want to go back to sense.. flash the AT&T 1.58 RUU that was posted in the ATT forum. (make sure you remove the tampered and relocked flag before you do that).
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
I'm trying that now, will post back with results :)
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
I tried that and I'm still in a boot loop. This was the output:

$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip

target reported max download size of 1830711296 bytes

sending 'zip' (522633 KB)...

OKAY [ 18.266s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) zip info parsing...

FAILED (remote: 99 unknown fail)

finished. total time: 18.618s

$ fastboot flash zip RUU-HTC_One_M8_GE-1.16.1700.16_rooted.zip

target reported max download size of 1830711296 bytes

sending 'zip' (522633 KB)...

OKAY [ 18.234s]

writing 'zip'...

(bootloader) zip header checking...

(bootloader) zip info parsing...

FAILED (remote: 99 unknown fail)

finished. total time: 18.404s
[One (M8) Q&A, Help & Troubleshooting] androidbuff123:
Doesn't the ruu post say that the flash will fail the first time and if you try it again it should go thru.
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
Yes, and I did try twice but got the same error both times (the error I got was different than in the example). I just realized I don't have S-Off, but am stuck in bootloader without any access to `adb` :(
[One (M8) Q&A, Help & Troubleshooting] androidbuff123:
You need to be soff

---------- Post added at 06:22 PM ---------- Previous post was at 06:19 PM ----------

You can also boot a recovery without actually flashing it. Once in boot loader try

flashboot boot recovery.img

Use the actual name of the recovery image instead of recovery.img.

Make sure the twrp or whatever recovery you are using is in the same folder.
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
How can I make my phone S-Off without any access to ADB though? I'm pretty much stuck in Bootloader/Fastboot
[One (M8) Q&A, Help & Troubleshooting] androidbuff123:
if you are able to do fastboot commands.. try using the firewater s-off http://firewater-soff.com/instructions/

you may not be to do this either since you said you don't have adb. Can't help you beyond here.. If you are able to get to RUU mode.. I would suggest trying flashing RUUs since they are most comprehensive.

Did you try flashing the sense RUU?
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
I used `flashboot boot` with TWRP and Philz and both are acting as if they were flashed and booted into; I'm still having the same flickering issues with TWRP and Philz works for a brief period, but for both of them, after 10-15 seconds they both try to boot normally and get stuck in a loop. If i can use adb long enough before it reboots maybe that'd help...

But why is the recovery rebooting after 10-15 seconds? is it because I'm S-On?
[One (M8) Q&A, Help & Troubleshooting] androidbuff123:
could be.. but you technically do not need to be s-off to flash a custom recovery. You only need to unlock your bootloader.

Have you tried fastboot flash boot.img?

of course. you need to get hold of a boot.img file first. I read somewhere once that If you are bootloader unlocked instead of S-Off, you also need to fastboot flash a boot.img after each time you flash a ROM from recovery.
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
Using Philz, I see that it can't mount or open anything in `/cache/`... I'm guessing that that's because I wiped the internal storage with TWRP initially. Is there anyway I can mount my phone and add the directories manually?

It really sounds like I need access to ADB but I can't run anything because nothing can mount the internal storage.
[One (M8) Q&A, Help & Troubleshooting] umjammerlammy:
In the bootloader, what is next to OS-?

You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
I've tried that now. It looks as if it's trying to boot but then I just end up back in the bootloader. I'll try with a different image.

In the mean time: I had managed to get Philz CWM formatting the storage properly (with /system, /data, etc), and without any errors that it couldn't mount /cache/recovery (because I had managed to format /cache manually before it rebooted). It's still rebooting 10-15 seconds after booting into recovery, even in the middle of formatting...

I have done more exploring in between reboots and it doesn't look like there's an `/sdcard` directory that it can mount either
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
Nothing, since it was wiped earlier.
[One (M8) Q&A, Help & Troubleshooting] androidbuff123:
Try flashing the recovery using the htc one all-in-one toolkit. see if that helps. I'm pretty much out of ideas beyond this point.
[One (M8) Q&A, Help & Troubleshooting] Android The Greek:
Restore a stock backup in twrp then flash the att ruu

If you are in the US message me your number and I can walk you through it
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
UPDATE

As mentioned in my initial post, I wiped/formatted my internal memory so I have no internal file structure.

My attempts at booting into or flashing a recovery are failing after 10-15 seconds since they can't mount to anything in the internal memory.

I'm stuck in Bootloader and it seems like the only tool I can utilize is `fastboot`.

I'm currently looking for a way to restore a file structure to my internal memory.
[One (M8) Q&A, Help & Troubleshooting] umjammerlammy:
You tried 'fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img'?
[One (M8) Q&A, Help & Troubleshooting] ashyx:
What about flashing the stock recovery and then trying a factory wipe?
[One (M8) Q&A, Help & Troubleshooting] BenPope:
If fastboot erase cache doesn't allow you to get into recovery, I can only suggest you're flashing the wrong or a corrupted recovery. Re-download the correct one and flash it.
[One (M8) Q&A, Help & Troubleshooting] JustLikeThat:
I've redownloaded it about 4 times now
[One (M8) Q&A, Help & Troubleshooting] Android The Greek:
You need to push a backup sense Rom or gpe to your phone the restore the backup.
[iPAQ rw6828, XDA Atom General] sal1pdp:
Which software support Quicktime MOV' files on 02 XDA Atom

Thanks in advance .....
[iPAQ rw6828, XDA Atom General] choycm:
Use DivX

Convert the *.mov file into DivX formats using the Pocket DivX Encoder. Then use TCPMP Player to playback the file in your PocketPC.

Pocket DivX Encoder:

http://divx.ppccool.com/

TCPMP Player:

http://tcpmp.corecodec.org/download

Have fun! It's pretty fast. Good quality conversion & playback too.
[Ouya Q&A, Help & Troubleshooting] IceTorture:
I'm looking for a version of Mod_Collection4Ouya that has come and gone, and to me has been a rare find. If anyone has it stored anywhere, may a link be provide? My reason for this would be is this being the last version that provided a feature called "In Gameloft games, report Bluetooth HID Device as Moga HID". Perhaps I'm wrong on some details, but I am looking for Mod_Collection4Ouya.4.4.apk., if anyone could provide a link, that'd be extremely helpful! Thanks community!
[Ouya Q&A, Help & Troubleshooting] ajb999:
I believe it is version 4.1 you are looking for according to this posts changelogs.

http://xdaforums.com/showthread.php?t=2359390

Does version 5.1 not work for what you are trying to do?

Here's a link to 4.4

https://docs.google.com/file/d/0B9mcZwWJuSpBZC1Xb3EtWEJyekk/edit?usp=docslist_api
[One (M7) Q&A, Help & Troubleshooting] samuelrhaynes:
I attempted to install CyanogenMod 10 for HTC One a few days ago but failed to get it working properly. No matter, I restored a nandroid backup of ARHD 71.1 and everything is working as normal again, however I notice some thing odd when accessing the internal storage by pc.

It appears to split the allocation of folders, some appearing in "Computer\HTC One\Internal storage" and others in "Computer\HTC One\Internal storage\storage\emulated\0" and I have no idea why! They all show up in the same location when viewing in the phone, so must be some error with the symlinks or something

I'd rather not lose all the apps and data, so if I need to wipe/format, would I be able to titanium back up everything?

I attached screenshots to help explanation

Thanks in advanced
[One (M7) Q&A, Help & Troubleshooting] clsA:
it's because CM 10 is too old it uses the old folder structure from android 4.1.2

just delete the storage folder and it should be fine .. I'm pretty sure CM 10 created it
[HTC Droid DNA] santod040:
PL83IMG_DLX_WL_K44_SENSE55_VZW_MR_VERIZON_WWE_4.09.605.1_Radio_1.02.01.0207_NV_VZW_4.46_002_release_357426_signed_Hboot_2_4

PL83IMG_DLX_WL_K44_SENSE55_VZW_MR_VERIZON_WWE_4.09.605.1_Radio_1.02.01.0207_NV_VZW_4.46_002_release_357426_signed_2_4

These are the two signed encrypted Official RUU packages for Kitkat, for the Droid DNA.

They are complete and untouched and should be able to be used to update and/or return any DNA to stock kitkat.

I have seen users who are stuck in s-on states, with no OS, and other troublesome scenarios.

I thought posting this up, might help those folks and possibly others as well.

The smaller package, would be the pre-update and the larger one, being the final Kitkat RUU.

I have not used these, as I have no need.

So you are attempting to use these at your own risk.

They are directly from HTC Corporate though, and should be just fine.

First Package: Links removed for now, users seem to be having bad results

Second Package: Links removed for now, users seem to be having bad results

Disclaimer:

This will wipe your entire device!

XDA:DevDB Information

4.09.605.1 RUU, ROM for the HTC Droid DNA

Contributors

santod040

ROM OS Version: 4.4.x KitKat

ROM Kernel: Linux 3.4.x

ROM Firmware Required: Latest hboot, radios and firmware

Based On: Sense 5.5

Version Information

Status: Stable

Stable Release Date: 2014-05-26

Created 2014-05-27

Last Updated 2014-07-05
[HTC Droid DNA] santod040:
Reserved

--Boot into Bootloader/Fastboot USB Mode

Step 1.)

fastboot oem rebootRUU

-- Wait for the device to reboot to a black screen with a silver HTC logo

Step 2.)

fastboot flash zip filename.zip

Repeat

Step 3.)

fastboot flash zip filename.zip

-- When it says it is done in the terminal/cmdprompt execute the following

[The green bar only fills up about 75% of the way]

Step 4.)

fastboot reboot
[HTC Droid DNA] santod040:
Reserved
[HTC Droid DNA] jamiethemorris:
This is something that should go without saying, but maybe some people don't know, perhaps you should just put a note in the op saying it will wipe the entire sdcard.
[HTC Droid DNA] ryryrocco:
If I run these how will it effect my s off/unlocked status. Do I need to relock to run if I am s off unlocked/rooted.
[HTC Droid DNA] billa:
The smaller pre-update goes through fine, but then the larger one fails with a signature error.

This is what I've done so far...

fastboot oem lock

fastboot oem rebootRUU

fastboot erase cache

fastboot flash zip small.zip

fastboot flash zip small.zip

*** went though fine ***

fastboot reboot-bootloader

fastboot oem rebootRUU

fastboot erase cache

fastboot flash zip large.zip

*** uploaded fine, then checking signatures and finally failed with this message ***

C:\Cell\Android\ADB>fastboot flash zip large.zip

target reported max download size of 1514139648 bytes

sending 'zip' (1111519 KB)...

OKAY [ 41.739s]

writing 'zip'...

(bootloader) signature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: 186.424s

Bootloader is v 1.57.0000 locked, S-ON

Now obviously I can't S-Off it since it's getting stuck on the HTC bootlogo.

Any suggestions? thanks
[HTC Droid DNA] Epiel:
Same here!!

---------- Post added at 05:05 PM ---------- Previous post was at 04:28 PM ----------

he smaller pre-update goes through fine, but then the larger one fails with a signature error.

This is what I've done so far...

fastboot oem lock

fastboot oem rebootRUU

fastboot erase cache

fastboot flash zip small.zip

fastboot flash zip small.zip

*** went though fine ***

fastboot reboot-bootloader

fastboot oem rebootRUU

fastboot erase cache

fastboot flash zip large.zip

*** uploaded fine, then checking signatures and finally failed with this message ***

C:\Cell\Android\ADB>fastboot flash zip large.zip

target reported max download size of 1514139648 bytes

sending 'zip' (1111519 KB)...

OKAY [ 41.739s]

writing 'zip'...

(bootloader) signature checking...

FAILED (remote: 12 signature verify fail)

finished. total time: 186.424s

Help me bro!
[HTC Droid DNA] santod040:
As I said in the OP.

I have not used these, as I have no need.

Do so at your own risk.

I posted them hoping they would help people in already soft bricked situations, etc,..

But they seem to be doing more harm then good, so I have removed the links.

Sorry for any trouble they caused.

Only suggestion I have is, check your MD5's and I will double check my source files against what's uploaded again, later today.
[HTC Droid DNA] billa:
It didn't do any damage at all, the small pre-update went though fine just the larger OS failed.

No harm done, though I noticed that the contents of the larger file is missing some files in the archive. I've read on some other forum that the correct update file is around 600k instead of 1gig (your file seems to be padded with something).

I have downloaded it twice from two different mirrors, maybe check your local hard drive file size against the upload and see if there's any discrepancy.
[HTC Droid DNA] santod040:
It's a factory RUU, not the OTA files.

I already posted the OTApkg.zips.

This is intended to be a full signed stock rom.

Meaning you should be able to apply it, no matter what was on the device prior.

It does not patch an existing install, it supposed to install the full OS/rom.

RUU's and OTA zips are two different things.
[HTC Droid DNA] billa:
Completely understand, but there must be something wrong with the larger file as it's failing on an identical version unit with the bootloader and s-on locked (and same is happening with other users).

By definition an RUU (and its rom.zip component) should restore an equal or lower version unit without failing.
[HTC Droid DNA] santod040:
I am aware it seems to have an issue, and aware of what it should be able to do, that's why I pulled the links for now.

I actually just got done downloading the file again and am about to check it against what I already had.

Will update with more info, when/if I have anything new to add.

MD5 is still exactly the same... :/
[HTC Droid DNA] billa:
Looking inside large archive, the total sum of the file sizes adds up to less than 10 megs, far from about 1gig, unless there are some hidden files...

android-info.txt 104 .... 2014-03-13 7:18:32 pm

boot_signed.img 6,727,936 .... 2014-03-13 8:10:10 pm

dzdata_16g.hdr 13,872 .... 2014-03-13 7:57:06 pm

dzdata_16g.img 679,472 .... 2014-03-13 7:57:06 pm

dzdata_32g.hdr 20,272 .... 2014-03-13 7:57:24 pm

dzdata_32g.img 939,824 .... 2014-03-13 7:57:24 pm

dzdata_64g.hdr 24,064 .... 2014-03-13 7:58:00 pm

dzdata_64g.img 1,171,456 .... 2014-03-13 7:58:00 pm

If you had the full ruu.exe it would be easy to extract it all.
[HTC Droid DNA] Epiel:
I just have to wait!
[HTC Droid DNA] goodman_east:
just because the encryption key has changed compared to RUU3.06.605

so u cannot flash RUU4.09.605 directly.

but u can flash the fimeware.zip from the OTA4.09.605, then flash the RUU4.09.605

---------- Post added at 10:31 AM ---------- Previous post was at 10:17 AM ----------

firstly, the ruu encryption keys changed several times.RUU1.15.605.* has the first key. RUU2.0*.605, including 2.04.605, 2.06.605, 2.08.605, has the second key. and RUU3.06.605.* has the third key. above all can be decrypted easily. but RUU4.09.605 has the second generation way of encryption and the key changed again.

secondly, ur ruu has been decryption, and some .imgs havelost.
[HTC Droid DNA] billa:
Yes in the first step the smaller pre-load firrmware.zip file goes through fine, but then in the second step with or without rebooting and trying to flash the larger OS file it fails with a key error. Isn't the function of the pre-load to update the keys and prepare the device for the OS file?

Usually the larger OS file also contains a copy of the smaller pre-load files, but looks like it's missing in this one.
[HTC Droid DNA] Epiel:
I have around one month with my phone without OS, I hope you can fix it!!
[HTC Droid DNA] goodman_east:
i'm trying to get the RUU4.09.605.* and can share it.

---------- Post added at 12:24 PM ---------- Previous post was at 12:21 PM ----------

Isn't the function of the pre-load to update the keys and prepare the device for the OS file?

yes, the key is in hboot.img.

and the pre-update step is to update the hboot.img
[HTC Droid DNA] tat2me2:
I hope someone comes up with a solution for this problem, I need to restore my wifes DNA but i'm only able to flash the smaller zip as well - tried everything from factory reset to recovery in the hboot menu, nothing is working, just keep getting bootloop.
[Xperia Z2 Q&A, Help & Troubleshooting] AndroidInsanity:
Hey guys, purchasing my Z2 later this week hopefully but I have a few questions that are buggin me.

With the Z1 if you unlocked the bootloader it removed a camera software that made lower light performance worse, is that the case with the Z2? Or is camera quality the same?

is there actually ANYONE on here that has a non defective/ no issues with their device? All I see are complaints!

And last but not least, Has the latest update actually made the Z2 a lot faster?

Thanks :)
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
unlocking your bootloader on D65XX removes/breaks nothing at all

me and a freind have purchased two Z2s between us and it seems that the older model is poor quality and has bad issues but the one we bought a week ago has no issues

ill be buying a Z2 for my self and ill give any issues i have if any

sony have said that Z2s after mid may wont have "any issues"

the last update is an improvement but unfortionatly alot of bugs with the Z2 are still there

alot are actualy Caused by android 4.4.2, all of which are fixed in 4.4.3 the Z2 should recieve after certifacation from google

my opinion of the device:

i love the Z2 it is amazing, although the old model having some majour heating issues or random blackscreen flashes etc ive found to love the newer mid may bach device, it is extremly fast with minor things i dont like

things i dont like-

finger print magnet

too much bloatware

its made of glass (im rough with my phones - i managed to break a nokia 3310)

many others,

things i like-

fast as can be

looks simple, elegant

UI is awesome/fairly useful

sony Features i love

many others too

just ask if you want to know something
[Xperia Z2 Q&A, Help & Troubleshooting] se1000:
Unlocking the bootloader has no effect on the camera. Everything works except for video unlimited and music unlimited (i think).

I haven't had any problems with mine at all. Couldn't be happier.

402 is a good firmware, even the stock one seemed very polished to me. The phone is very snappy and smooth. Excellent device.
[Xperia Z2 Q&A, Help & Troubleshooting] AndroidInsanity:
awesome thanks guys, does anyone know an explanation why it affected camera quality on Z1 and not Z2 then?
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
its sony being wither lazy or weird

they can optionaly make things how they want, if they wanted the Z1 could have had the camera not depend on DRM keys but sony being them odd selfs i think they did to promote or push people into buying a different xperia
[Xperia Z2 Q&A, Help & Troubleshooting] AndroidInsanity:
I heard it was something to do with removing BIONZ software, if the bootloader unlocked then it could be copied by other OEMs, that's why they removed it. but not sure.
[Xperia Z2 Q&A, Help & Troubleshooting] Envious_Data:
well i dont havnt realy read up about this at all for several reasons

i know if they do steal boinz they can get in trouble

1. its stealing

2. copyright conflictions

3. i dont think they do, xperia cameras are crappy, says samsung, HTC, and some others
[Xperia Z2 Q&A, Help & Troubleshooting] se1000:
Very plausible, the Z2 doesn't have BIONZ, at least not in software form. It does have X-Reality but that works after you unlock the bootloader. In any case, feel free to unlock, there are virtually no drawbacks. Do what I did and make sure you cash in on your free music, movies and apps first though, I believe once you're unlocked you can't use those codes. Not sure.

The only thing is, as of right now there's no way to backup the TA partition on the Z2 but honestly, I haven't found one reason not to unlock the bootloader yet.

** Edit: Z2 has BIONZ image processing, sounds like they implemented it via hardware this time.
[Xperia Z2 Q&A, Help & Troubleshooting] nreuge:
X-Reality does not work on unlocked Z2 with the latest stock rom (.402).

Fortunately, there is a patch that bring it back :)
[Xperia Z2 Q&A, Help & Troubleshooting] AndroidInsanity:
Oh, that's pretty weird!
[General Questions and Answers] toebee76:
So I looked around but couldn't find an answer to my question. I'm sure it must have been asked somewhere but I couldn't find it. I would like to know if two different clock speeds with the same voltage use the same amount of energy. My g2 kernel goes as low as 300mhz but in my voltage testing the lowest voltage it can handle is 675mv. However I found that I can use that same voltage at 422mhz and still be stable. Would they both consume the same amount of energy? I've noticed cpu usage is slightly higher at 300 vs 422. I'm guessing that is because it takes longer to process. Does the cpu usage play into the energy used? Or does it still use the same amount of energy and it just takes longer to complete the process. Is there a formula to figure out which is best? Thanks for reading!
[General Questions and Answers] appviz:
Good question. I believe it also depends on the architecture that whether consume same amount of energy or different. The concept of clocks is physics. Clock speed determines number of spikes in a cycle of voltage. In other words they are introduced to bring the processing faster. Everyone wants speed but better battery life. So what they will do is increase clock speed to handle more information in the same cycle and there by using same energy. This is theoretical. But practically more the clock speed more efficient the CPU/Architecture need to be , to handle things effectively at the same energy consumption. Otherwise it may consume more. This is what I think. Let me also have a search. If I find out anything else, will let you know :cowboy: