yashsingh1/xdaforums huggingface dataset:
[Motorola Photon Q 4G LTE] dslinfreak:
well, color me purple now. Not a great thing for me and now I look like an absolute retard. I think I'm gonna go back to hs now and retake linux OS.
[Motorola Photon Q 4G LTE] Loader009:
For me everything looks ok.

The partition is mounted and the recovery can access the partition.

It should work but it doesn't.

I am kind of clueless.

If I remember correctly, there was in TWRP an option to wipe data/internal storage (or something like that).

Could you try this one? (And post the last_log again.)

I think that it wipes in a blink of an eye because there is nothing to delete.

With the wipe data/internal storage I think it formats the partition instead of doing a "rm -R" (wipe data) on several folders. (I think it is rm -R, I don't actually know it.)

I have problems if I backup data from (external) sdcard. I have to move my backup to the internal storage (not in a recovery!) to successfully restore my backup.

It is annoying, but I haven't found a solution to be 100% sure that the recovery reads the backup correctly from the (external) sdcard.
[Motorola Photon Q 4G LTE] arrrghhh:
What about a recovery.log after the failed attempt?
[Motorola Photon Q 4G LTE] Loader009:
He already has:
[Motorola Photon Q 4G LTE] AndyYan:
I tried the "format data" option like you said, and it seems to go nicely - the log says it recreated filesystem properly - until it "hot reboots" again. Bang it. Log attached: http://d-h.st/chh

I have always been backing up to/restoring from external SD card without any flaws. Now I can't restore my backup, but only because restoring backup involves wiping /data...
[Motorola Photon Q 4G LTE] arrrghhh:
I kept looking for recovery.log... haha.

Nothing brilliant is coming to me at the moment, I will ask some people (much) smarter than I...
[Motorola Droid Bionic] raylgo:
My phone got borked but would still Fastboot so I'm going to FXZ it again and try the GSM hack all over again but it always made me sad that it is stuck on Jellybean. I was wondering if Kitkat can survive the build prop hacks that makes GSM work...
[Motorola Droid Bionic] raylgo:
For those who might still be wondering, it does work.

Used SlimKat + base kernel and Radiocomm hack and the GSM hack zip file. Works like a charm.
[Motorola Droid Bionic] cheesy poof:
Thanks for the update. I'm in the process of reading up on how to do this and switching off VZ. Good to here it still works.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] madboy1977:
Plz I just got a Tmobile MDA... With turkish Language

I would like 2 change it 2 English.. Anyhelp will be appreciated...

Here's Some Info on it...

Model Nr: WIZA200

Plattform: PocketPC

plasee.....
[8125, K-JAM, P4300, MDA Vario Software Upgrading] dcoelho:
Easy. Install an english rom (t-Mobile or other). Search for the tool awizard and read carefully the instructions.
[8125, K-JAM, P4300, MDA Vario Software Upgrading] madboy1977:
thank you brother very much :D
[8125, K-JAM, P4300, MDA Vario Software Upgrading] dharvey4651:
an easier answer... Flash this rom: T-Mobile Official WM5 English :cool:
[8125, K-JAM, P4300, MDA Vario Software Upgrading] mestrini:
Do you realize the most awesome thing? madboy1977 replied more than an year after the help post :eek:

This must be some kind of record, no?:D:D
[8125, K-JAM, P4300, MDA Vario Software Upgrading] dharvey4651:
Haha. I can't believe you noticed that... Thats histerical though...
[Moto G Q&A, Help & Troubleshooting] NMAndroid:
This has been a problem (do not now if it is) since day 1 where I have 2 sims in the phone and some calls come as a Unknown although the number of the person is already in the contact list.

Morever problem becomes more worse where if the call is missed and the you try to call back, it does dials as there no number.

I have a friend who is also using Moto G and he is not facing the issue.

Would you please help in this ? Is is some setting that needs to be done ?

Thanks & Regards,

Harish
[Moto G Q&A, Help & Troubleshooting] tharas:
Hi Harish,

Check the numbers stored in your contacts... Sometimes while saving a new contact number the "+" in the "+91 xxxxx xxxxx" does not get saved... Instead it is saved as "91 xxxxx xxxxx"... it might be the cause of your problem...
[Moto G Q&A, Help & Troubleshooting] NMAndroid:
Hi,

Have checked and that does not seems to be a problem.

Thanks
[AT&T HTC One (M8)] supitsronnie:
I wanted to return my HTC One to stock, and it took me hours to do so. I had to search for multiple threads, and it was a big hassle and pretty confusing. I am back to stock now, although I am still S-Off. I figured I would compile a thread helping others in similar situations return to stock. This guide will help you return to sense, lock your bootloader, unroot, hide your tampered banner, as well as prevent your device from showing up as relocked. You're device will still remain S-Off after following these steps.

Here are the steps. I am assuming the recovery is device specific, and I wouldn't recommend flashing the recovery.img on any device other than the AT&T M8.

1. Make sure your device is S-Off. If not, download firewater and S-Off your device.

2. Restore a nandroid of the stock Sense ROM, or find a stock ROM to flash. You'll have to dig around; I used a nandroid.

3. Flash SuperSU.zip in recovery on top of the stock Sense ROM. You can find the SuperSU.zip here: http://download.chainfire.eu/396/SuperSU

4. Use adb to flash the stock recovery.img to your device. You can get the recovery files here. http://xdaforums.com/showthread.php?t=2711814 *ONLY FOR THE AT&T MODEL*

5. Boot back up into sense, and follow this guide to remove the tampered banner in recovery. http://xdaforums.com/showthread.php?t=2708565

6. Follow this guide to lock your boot loader and make it say **LOCKED** instead of **RELOCKED**. http://xdaforums.com/showthread.php?t=2708571

7. Boot your device back up, and open SuperSU. Go into settings and find the "full unroot" option and run that. Reboot your device like it suggests.

8. I would factory reset your device in settings or recovery to make sure everything's clean, although this step isn't necessary.

Enjoy Sense! Hope I was able to help some of you guys! ?
[AT&T HTC One (M8)] chrispyutec:
Do you think these steps could pass with returning it to an AT&T store for exchange?
[AT&T HTC One (M8)] supitsronnie:
I am not sure. I haven't tried returning to AT&T. The only thing they can get you for is S-Off, but some devices shipped S-Off so I don't know how likely that is to happen. AT&T shouldn't look into it too much. They don't have access to HTCDev so they can't see you've requested an unlock token.
[AT&T HTC One (M8)] garyd9:
I don't know about your AT&T store reps, but I can't think of a single one from a store local to me that would have any clue whatsoever on how to determine if the device was rooted, unlocked, etc.

Also keep in mind that, unless you've personally irritated one of them, THEY (usually) DON'T CARE. They might be required to check certain things by AT&T corporate, but do you really think that a typical sales rep is going actually exert any extra effort whatsoever to check the device?

Take the steps you mentioned. Leave the device S-OFF, but clear the "tampered" flag (as you mentioned) and any type of red warning that happens on the boot animation. Basically, just fix up the extremely obvious stuff that a sales rep couldn't possible ignore. When you go to bring it back, act like you've never heard of "XDA", and if someone asks if the phone was modified, tell them that you changed the default ringtone or something silly like that. (In other words, play dumb.)
[AT&T HTC One (M8)] supitsronnie:
Delete
[AT&T HTC One (M8)] jdk2:
I was in a store the other day with a friend who needed something done to his account. Beside us was a rep trying to activate an M8 for a customer. She kept running to the back to get different SIM cards and couldn't figure out why they wouldn't fit. She was trying to put them in the SD card slot :eek:

And you're worried about them checking bootloader locks and S-Off? :laugh:
[AT&T HTC One (M8)] garyd9:
To give an example of how "closely" an AT&T store rep examines a phone for exchange/return:

I noticed a couple days ago that the volume button on my own M8 is quite a bit more.. wiggly.... than the AT&T demo M8's in my local store. It doesn't really bother me, but I figured I was still in my "14 days" so I could get a simple exchange for a more perfect volume button.

So, I spent about an hour backing up my device, changing the CID back to CWS__001, switching the firmware back to AT&T stock, switching the recovery back to stock, patching the bootloader to NOT show "unlocked" or "tampered", etc. Basically, when I was done, it was nearly impossible for even a knowledgeable person to know I had "converted" the phone to a dev edition and so on.

I brought the phone to the store and here's what they did to examine it: NOTHING.

They saw that the screen turned on, and that was it. Nothing else. I was extremely disappointed. (Perhaps it relates that I had just factory reset it, so it was sitting at that stupid AT&T welcome screen... perhaps they didn't want to waste time tapping through all the prompts?)

Oh, and I ended up NOT doing the exchange. They brought a new one up, and it had the same wiggly volume button. So, we opened a couple more boxes and all were wiggly. Being that I didn't see any other defect in my existing phone, I decided to keep my known wiggle instead of risking a different different that wiggled just as much, but might also have some other issue.

Take care

Wiggles Gary
[AT&T HTC One (M8)] drivel2787:
where do we find the stock nandroid to use? Does this work to get back to stock to get the latest OTA update?
[AT&T HTC One (M8)] lostangelintx:
LOL you laugh. My AT&T girl did the same thing. She had the nano sim sideways in the sd card slot and couldn't figure why it wouldn't go in.
[AT&T HTC One (M8)] supitsronnie:
You can find stock nandroid backups here: http://xdaforums.com/showthread.php?t=2701376. Make sure your CID matches! Instructions are in that thread.

Yes, if you follow this method you will receive OTA updates again.
[AT&T HTC One (M8)] JoSway:
I have to use HTC's free screen replacement program, im rooted, unlocked, and s-off... soooo, i have to do this before sending them my phone right?
[AT&T HTC One (M8)] TheEmpyre:
There was a poster who claimed they told him he was ineligible for the replacement because they had him on record on HTCdev as unlocking his boot loader. Said he needed the dev edition to be able to do that without voiding his warranty. That was just one person though
[AT&T HTC One (M8)] mewikime:
I got my device 2 days ago and rooted immediately. Then I noticed I was on the old firmware version, so I used your guide to get unroot and back to stock. It worked well. Now I'm updated and rooted again :D
[AT&T HTC One (M8)] 4cdndctn:
deleted
[AT&T HTC One (M8)] Lil Jones:
Believe it or not all you have to do is put the stock rom back on the device. You still have a hardware warranty. If say, your speaker is broken that would have occurred regardless of you flashing the ROM. Flashing the rom is not a punishment for you to live with bad hardware... However try to put back to stock if you can.
[AT&T HTC One (M8)] dinaratai:
thank u for helping
[AT&T HTC One (M8)] redpoint73:
AT&T terms clearly state that they have the "right" to void warranty if the software is modified.

In reality, AT&T will not check or care. Its more important to keep you as a monthly account holder, versus the relatively modest price if a refurb phone. I've seen many reports of successful warranty exchanges with unlocked bootloader, root, even having an obviously custom ROM (like CM) installed.

Return to close as stock as possible/feasible to play it safe. But its likely not going to be a deal breaker.
[AT&T HTC One (M8)] rahtrip:
can i be S-Off and do ATT OTA's?
[AT&T HTC One (M8)] redpoint73:
Sure. But if you've bothered to s-off, why would you want to?
[AT&T HTC One (M8)] rahtrip:
Just wondering for future reference to see if I can ever fully return to "STOCK"/out of the box. I mainly S-Off-ed for Harmon/Kardon and ADSP enabling.
[AT&T HTC One (M8)] redpoint73:
If you ever wanted to return to stock, OTA is not the method I would recommend. RUU is easier.
[AT&T HTC One (M8)] Texas_Dave:
But there aren't any RUU for ATT M8 yet are there?
[AT&T HTC One (M8)] Wonders_Never_Cease:
http://xdaforums.com/showthread.php?t=2757462
[AT&T HTC One (M8)] BR7fan:
OK... Here is my problem.

I rooted and did all the stuff required,except for S-off.

I did a TWRP back up while rooted of my whole system. I was going to use that back up to restore.

My problem is that when TWRP wiped,my root went with it. Now TWRP will not install my back up.

I have checked for Nandroids for my ATT M8 in this thread,but they all say access denied.

I have access to my TWRP recovery.I just need to know how get my phone running again. Please and thank you.
[AT&T HTC One (M8)] mindmajick:
You should be able to use adb sideload from advanced in twrp. As long as you have adb access on your PC, that is.
[AT&T HTC One (M8)] redpoint73:
What happens if you just try to move a stock rooted or custom ROM to the phone and flash it (or sideload as recommened in the previous response)?
[AT&T HTC One (M8)] scott500:
Return HTC One M8 to stock

http://xdaforums.com/att-htc-one-m8/general/att-1-58-501-1-bootable-ruu-hboot-t2818556

It seems like this is about the easiest way to return your device back to stock. It's a bootable file you just copy to your phone.

From what I read... it does a factory restore, puts back stock recovery and hboot. I think thats pretty much a unrooted factory fresh device leaving s-off.

Someone please correct me if I'm wrong.

Hope it helps...
[AT&T HTC One (M8)] irmq8i:
I used this guide to restore my HTC One M8 from GPE back to Sense

Mine wasn't AT&T though but you can follow same steps and download the nandroid and recovery from the nandroid collection thread!

THANKS!
[AT&T HTC One (M8)] redpoint73:
Agreed. Although you would still need to change the UNLOCKED flag to LOCKED as noted in the top post of this thread.
[AT&T HTC One (M8)] dressanderc:
Alright, gentlemen, I need an opinion. My duo camera on my AT&T M8 has completely died, and I want to file a warranty claim with HTC. My phone was S-Off, Rooted, and SuperCID was set. I've done the following:

1. Stock firmware/ROM from Nandroid has been flashed - http://xdaforums.com/showthread.php?t=2701376

2. CID has been set to CWS_001 (I believe this is the OEM CID, as I didn't take note of it before setting SuperCID)

3. Tampered & Unlocked banners have been removed. Now I just have a Locked banner

4. Stock recovery has been flashed.

5. Used SuperSU to "Unroot" the device.

Anyone think I'd have any issues getting this thing swapped out?

EDIT: Chatted with AT&T's live support, and they are sending a replacement device. Under their Terms and Agreements, there was nothing listed about being responsible for s-off devices or possibly rooted (even though I've taken every measure to undo that). Should be here 4-6 days. I'll keep you updated on what they do as far as possibly charging me.
[AT&T HTC One (M8)] redpoint73:
There used to be a statement about warranty not covering any device with "modified software" or some such language. But I actually can't find it now, and they only make mention of devices with physical or water damage being "ineligible" so it seems like they have changed the terms.

In any case, in actual practice, AT&T doesn't give a poo whether the device is bootloader unlocked, S-off, rooted, etc. for the purposes of warranty service for a hardware issue. There have been many reports on XDA of folks returning various devices with root, unlocked bootloaders, S-off, even custom ROMs installed. I haven't seen any reports of anyone getting warranty service denied by AT&T due to mods. Of course it makes sense to return the phone to as close to stock as much as possible before returning "just in case". But the fact of the matter, if you are an AT&T account holder, those nice monthly service bills are worth more to them than the modest cost of a refurbed phone. This seems to be in direct contradiction to AT&T's present stance on locking bootloaders and apparently discouraging modding and rooting. But maybe it just makes more financial and logistical sense for them to enforce prevention on the front end, rather than on the warranty side.

Returning to HTC is a vastly different matter, as they can and often have denied warranty on modded phones. So anyone who has the AT&T version and is an active AT&T customer should go through AT&T for warranty service when needed.
[AT&T HTC One (M8)] dressanderc:
Well, I'm in a pickle. I got my replacement device and everything was perfect, or so I thought. Seems as if the microphone on the back of this thing is messed up real nice. Every time I attempt to record anything, be it a video or voice recorder, I hear absolutely nothing but static. Bad thing is, I've already rooted/unlocked this device and Firewater is not working on it, so I'm stuck S-on. Obviously now I can't remove the "tampered" banner and it states "relocked".

I'm going to my local corporate AT&T store in an hour or so. (Fun fact: when AT&T shipped my first replacement, they didn't include anything in the box). So I plan on spilling out how I bought the phone in April, camera died and I was shipped an empty box, had to wait for another, and now it has the mic issue. I'm also not planning on acknowledging anything regarding the banners, as I'm sure they'll check.

So this sucks. More than likely I'm going to end up with a device that takes nice pictures, but no video. Hopes aren't really high at this point
[AT&T HTC One (M8)] redpoint73:
You just quoted my post where I said AT&T doesn't care if the phone is modded. So why do you think they won't exchange the phone?

Refurbs with defects are unfortunately not at all uncommon, so you likely won't have any issue explaining to them that its a warranty replacement that has an issue.

Also, I think its normal for warranty replacement refurbs to be shipped with no accessories. So no worries there, either.

But one thing, AT&T stores won't exchange the phone past 14 days of the original purchase. I believe refurbs can't be exchanged at stores, and you will need to call and exchange by mail, or go to a Device Support Center, if there is one in your area.
[AT&T HTC One (M8)] dressanderc:
So, in short, AT&T cares nothing about the Tampered or Relocked banners? A quick google search, and I find all kinds of instances where they basically check the bootloader, see those banners, and that's it. Warranty is void, nothing we can do.
[AT&T HTC One (M8)] redpoint73:
I've probably seen a few dozen reports on XDA that this is the case, yes. Succesful warranty exchanges with unlocked bootloaders, s-off, etc. Even reports of folks returning their phone with a

custom ROM

still installed.

As previously mentioned, as far as I can tell, its no longer even in AT&T's terms that they can void the warranty based on software modifications (although it used to). They don't even have any grounds to do this anymore. If they do so, I would ask they show you in the warranty or service terms where it says they can do it.

That said, I would still try to return to stock as possible, just in case.

Are those cases through AT&T, or HTC? HTC will in fact void your warranty for an unlocked bootloader and mods.

If your experience is somehow different that what I've described, I'd love to hear about it. Good luck!
[AT&T HTC One (M8)] dressanderc:
I want to say they were AT&T, however, I could very well be incorrect in saying that. Just for my personal experience today, though, the rep basically told me the exact same thing you did. Didn't even bother looking at the phone, just informed me to contact the warranty claims department. So now, in my mind, I have a potential charge of close to $1,000 if (for whatever reason) they deem these warranties as void. That's a pretty big bet to make.
[AT&T HTC One (M8)] redpoint73:
But its a bet where the law and AT&T's own terms are on your side. Their terms only mention the warranty is void for physical or water damage, and makes no mention of software modifications.

http://www.att.com/shop/en/legalterms.html?toskey=exhibitR
[AT&T HTC One (M8)] dressanderc:
According to my AT&T rep that I worked with. "non-certified firmware may cause issues".

However, I was able to S-Off the device using Sunshine. I've flashed the 1.58.502.1 RUU and stock bootloader, removed the tampered banner, and re-locked the bootloader. (and of course un-rooted the device). Better safe than sorry; It now looks like this, so I'm pretty sure I cannot get any more stock:
[AT&T HTC One (M8)] redpoint73:
That's remarkably vague, and doesn't to me say anything. Note that he didn't say it would be "out of warranty" as he did with water or physical damage. My guess is they want to (understandably) discourage folks from returning phones bricked due to botched mods; but don't want to come out and say that.

And it doesn't say anything if their warranty terms. If its not in the written terms, they can't enforce anything. If they want to exclude software mods from the warranty, they have to have it in writing, they can't just make it up as they go along. For once, AT&T's terms are in your favor, so I'd keep that in mind if they try to argue otherwise.
[AT&T HTC One (M8)] dressanderc:
Yeah, for sure. If it comes to that I will use the loose terminology to my advantage. I think I'm good to go, though, they both looked exactly identical to my bone stock 3rd unit. Which, before I root, am giving it a week long test run to make sure it's good to go, haha.
[AT&T HTC One (M8)] rubirman:
Stuck with Header Errors

Hi Everyone,

I have been trying to return to a Stock HTC One M8 AT&T image since yesterday and have been running into all sorts of errors. I initially converted the HTC One M8 to GPE with S-Off and OTA support (after chaining CID to GOOG001) from CWS__001. In order for me to recover, I have tried using the HTC Stock RUU (both Windows and via fastboot). Each time, I get an error in reference to "Invalid Image" or "32 Header Error" via fastboot. I have tried changing the CID back to CWS__001 as a work around to no success. After changing the CID, I noticed that even though I typed CWS__001, in the boot loader, I see CWS_ _001 as if there is a space in there. I also tried relocating the bootloader but that did not help either.

The only thing I am able to do is to flash a GPE based RUU using fastboot that allows me to get up and running but that is not what I want. I even tried re-rooting the phone with TWRP recovery and applying the Skyfall and ViperRom and both fail as well. ViperRom failed with an error 7. It seemed that each time I tried applying a ROM, the Writing System and Writing Data went awfully fast which concerns me and might be the issue.

Here is my getvar output:

(bootloader) version: 0.5

(bootloader) version-bootloader: 3.18.0.0000

(bootloader) version-baseband: 1.14.21331931.LA02_2G

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main: 2.10.1700.4

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

(bootloader) serialno: xxxxxx

(bootloader) imei: xxxxxx

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul_ca

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B12000

(bootloader) cidnum: CWS__001

(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: 01eccc75

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

all: Done!

finished. total time: 0.015s

Any input you can provide will be greatly appreciated!