yashsingh1/xdaforums huggingface dataset:
[One (M8) Q&A, Help & Troubleshooting] KinTharEl:
Update. I was able to get TWRP installed and flash SuperSU. Still have S off and I have no idea how to get that done. I tried using the toolkit by Squabbi and unfortunately wasn't able to get the S off. Any ideas?
[One (M8) Q&A, Help & Troubleshooting] BerndM14:
You mean S-ON? You could try firewater but that's a shoot and miss in which case it'll have to be Sunshine S-OFF(Only alternative) and that costs $25.

Back to troubleshooting:

Boot into recovery mode and sideload a ROM from the PC. You can also do an adb push ROM.zip /storage/ext_sd/ or if you have a SD Card reader on PC, remove the SD card, put it in PC and manually copy/move a ROM to the SD Card.

You don't need S-OFF to flash custom Recoveries. You'll need it in order to do a full conversion to Google Play Edition though, as a result of partition sizes changing. ROMs on the other hand is fine with S-ON.

Of course if you're going to flash custom ROMs make sure it's for the correct firmware that you're currently using. You're device still uses 2.xx.xxx.x firmware so don't download a 3.xx.xxx.x custom ROM for it. This is the case with Sense based ROMs, not sure about AOSP(Apparently it's not an issue with it). Outdated firmware will have the radio not work properly, which means, possibly, no bluetooth, gps, wifi, data.
[One (M8) Q&A, Help & Troubleshooting] KinTharEl:
Sorry. S-ON, that's what I meant. Yep, as you said, I was able to flash a custom recovery just fine with the S-ON. Was also able to flash SuperSU for it. After this, I was able to access the internal memory of the phone. It showed only one folder on my PC, the TWRP folder. But in the recovery, I'm able to see the root directories, which I can't on the PC. Tried flashing the stock ROM from the HTC dev site by pasting it into the phone, which sadly failed. I'll check again for the 2.xx ROMs. Maybe that's the miss I did.
[One (M8) Q&A, Help & Troubleshooting] BerndM14:
Don't bother with HTCDev site, those are kernel source codes and not backups.

COLLECTION of Stock backup's <<There's the nandroid backups for plenty of devices just look for the right one in post 1. Also in post 2 the author showed how to do the restore, make sure it's unpacked and placed in the correct path directory.
[One (M8) Q&A, Help & Troubleshooting] KinTharEl:
Update so far.

S-On

TWRP flashed.

Tried all the methods that you guys have mentioned.

Nandroid backup is failing.

When I use an OTG Flash drive to flash SuperSU, it succeeds, but when I hit the option to reboot, TWRP says that SuperSU isn't installed on the device and gives me an option to install it, which fails.

Tried a ROM from CM, which also failed.

Tried a sideload with adb, which also failed.

Haven't been able to use firewater to turn S-Off, where the push command just hangs.

Therefore, I am stumped at the moment. I've been thinking of using RUU to restore the phone to stock, but I haven't been able to find anything worthwhile. Is this a valid idea that I can use? Anyone has any links to this that I can use? Help would be appreciated. Thanks.
[One (M8) Q&A, Help & Troubleshooting] sigshane:
In looking for a solution to your problem, everything I have found so far requires S-OFF. I myself used the weaksauce/firewater method to do mine, did that not work for you? And if not, I have to ask if you followed the directions verbatim?

There is also the sunshine method - have you tried that method to S-OFF the phone?

This is gonna require someone to pay 25 bucks, but 1) it is well worth it, at least at this point in your efforts, 2) you don't have to pay until the S-OFF is successful, and 3) your friend should be footing that bill anyway.

Once you've gotten S-OFF achieved, you are one step - prolly the biggest step - closer to getting this thing done.

Look at it this way - after all of your troubles and frustration, wouldn't $25 be small beans to pay for a working phone?
[One (M8) Q&A, Help & Troubleshooting] RossMacgill:
S off can only be done with a working phone, eg stock sense rom, S-off is not your problem, installing a rom is, get something like ADHD rom, or the correct stock rom for your CID and then flash that. Job done working phone, then s-off if you wish but its not a requirement, but nice to have and well worth $25
[One (M8) Q&A, Help & Troubleshooting] KinTharEl:
Yeah. I've been searching and came to the same result, that I need the S-off. But all the methods that I have seen require that the phone needs to have a working ROM to turn S off. I'd have been able to use weaksauce/firewater for it. I saw a video of a bricked M8, and he seemed to restore it back to total stock using RUU. I'm currently downloading the RUU for the Google Play Edition, seeing as I can't find the RUU for the Sense UI WWE. In the same video, he has S-ON, from what I saw in the bootloader. Wondering if this method could possibly work. Any ideas? Here's the link for that video. The phone is a Sprint M8, but the same logic should apply for the WWE, if I'm not mistaken. Link to Video

The problem with asking the friend (he's a kid friend of my brother), is that he can't foot the bill.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Not going to work. In the video, he is flashing the RUU which corresponds to his phone's CID.

You need to have the GPE CID to use the GPE RUU. Otherwise it will fail CID check and fail to install. And you can't change CID with s-on.

And unfortunately, there are no WWE RUUs.

I would try fastboot erase cache and install TWRP again. Then flash a ROM corresponding to your firmware (Sense 2.x). ROMs simply failing to flash is often just a matter of erasing cache and re-installing recovery.
[One (M8) Q&A, Help & Troubleshooting] KinTharEl:
I see. Thanks for the clarification. I didn't try flashing it yet seeing as I wanted to know what I was getting into before I actually did anything. Just for the sake of giving information, the RUU I downloaded is 2.12.1700. Version of Android is 4.4.4. Guessing it probably won't work, but I'll reflash the recovery as you had suggested. I'll try Android Revolution 22.1 for this, hopefully it works. I'll keep you guys posted.
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
I don't see any info of your device except the hboot version.

With that hboot version 3.18.0.0000 all the latest custom ROM won't properly work on your device.

Why don't you give more detail - run command fastboot getvar all and post here the result (delete the serialno. and imei no.)

From there we can see whether any stock backup for you. Most important now is to have a fully working phone .. then you can start any other thing like S-Off and flashing custom ROM
[One (M8) Q&A, Help & Troubleshooting] KinTharEl:
(bootloader) version: 0.5

(bootloader) version-bootloader: 3.18.0.0000

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

(bootloader) version-cpld: None

(bootloader) version-microp: None

(bootloader) version-main:

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

(bootloader) serialno: HTXXXXXXXXXX

(bootloader) imei: 3XXXXXXXXXXXX

(bootloader) imei2: Not Support

(bootloader) meid: 00000000000000

(bootloader) product: m8_ul

(bootloader) platform: hTCBmsm8974

(bootloader) modelid: 0P6B65000

(bootloader) cidnum: HTC__038

(bootloader) battery-status: good

(bootloader) battery-voltage: 0mV

(bootloader) partition-layout: Generic

(bootloader) security: on

(bootloader) build-mode: SHIP

(bootloader) boot-mode: FASTBOOT

(bootloader) commitno-bootloader: 42372cde

(bootloader) hbootpreupdate: 11

(bootloader) gencheckpt: 0

Update: I've checked through the logs that TWRP shows, and I've found that when trying to sideload, or flash SuperSU(Even when it says successful), cache won't mount. I tried manually mounting it through the option in TWRP, but it won't select the cache at all. I also can't copy anything onto the phone memory. My option to try anything just with the phone so far has been to use an OTG USB Drive and mount that.
[One (M8) Q&A, Help & Troubleshooting] ckpv5:
1. Empty version-main : The TWRP that you have is a very old version.

Use TWRP 2.8.1.0 link in my signature.

2. HTC__038 and hboot 3.18.0.0000 - your correct software/ROM version no. is 2.10.720.1

There's a nandroid backup for this version here : http://xdaforums.com/showthread.php?t=2701376

So try TWRP 2.8.1.0. Try also to enable MTP and see whether the sdcard/internal storage mountable to your PC.

Download the 2.10.720.1 nandroid backup then use the OTG to restore. You can make a backup of boot and select USB as the storage for the backup, you'll see the folder structure in your OTG drive. There is where you need to transfer the nandroid backup (after you extract it on PC)

Note :

1.If this is successful then you can try to S-Off with Sunshine but it is a hit or miss for your device version ... most likely won't work

2. You can follow the right procedure to do OTA update to 3.35.720.1 then you can flash any of the latest custom Sense based ROM and the lollipop ROM too.

3. Just be on stock then wait for OTA for the official lollipop like most of us here.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
If its a GPE RUU, and you don't have the GPE CID (or SuperCID), it won't work. I already said that, so I don't know why you are still "guessing" anything.

---------- Post added at 10:14 AM ---------- Previous post was at 10:11 AM ----------

No version number means obsolete TWRP (as ckpv5 mentioned). Flashing a more current TWRP will fix this, and will probably also fix the flashing issues you had with various ROMs, and might fix the mount cache issue.
[One (M8) Q&A, Help & Troubleshooting] KinTharEl:
Got it. I'll try it out as soon as I'm done with work. I was out of town the past few days, so I wasn't really able to reply. Thanks for the advice though. I'll definitely look into it.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] petrafan007:
I can't find anything anywhere that would allow me to connect this tablet to an hdmi tv. Is there simply no way?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Skizzlle:
The only way you can do it is by buying a Chromecast(35$)

And then screen mirror with the application (Chromecast) play store
[Nexus 5 Q&A, Help & Troubleshooting] rahul9five:
Also it was earloer rooted with towelroot. But i did unroot it with superSu a couple of weeks before ..
[Nexus 5 Q&A, Help & Troubleshooting] _MetalHead_:
What error is it giving you?
[Nexus 5 Q&A, Help & Troubleshooting] rahul9five:
It just says error. But after a little digging i came to find that this is probably because i tweaked a few system files when i was rooted. Like the mixer_path... Now i cant seem to remember the changes i made neither can i find the oroginal file for nexus 5 stock on the net.. Could you or anyone please help.. Any advise
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
Google nexus factory images. Just to be sure flash the recovery, system, and boot images in fastboot from 4.4.4
[Nexus 5 Q&A, Help & Troubleshooting] rahul9five:
Will i have to unlock my bootloader for all this? As i rooted my phone with towelroot i didnt have to unlock it earlier
[Nexus 5 Q&A, Help & Troubleshooting] jd1639:
You do need an unlocked bootloader. Get bootunlocker from the play store it'll unlock without wiping the device.
[Android Q&A, Help & Troubleshooting] techguy804:
Someone pl;ease help me a need the orginal mixer_paths.xml file from an LG Realm running Kit Kat. Someone please if you have this send it to me via p,m or somthing, i need it badly.

Thanks So much
[Android Q&A, Help & Troubleshooting] sheatim:
I sent you the URL to my copy. Let me know if you need anything else.
[Android Q&A, Help & Troubleshooting] MagicPlants:
Can I also have the link please? i need the stock rom for LG Realm
[Android Q&A, Help & Troubleshooting] kadariustaylor44:
lg mixer_paths

can i please have the copy of the mixer_patjs file too. It gotaccidentally deletedc
[T-Mobile, Samsung Galaxy SIII] rcurtis805:
There's a post in the at&t Samsung Galaxy 3 original android development for cm12 running lollipop 5.0. I flashed it on my t999 and it works great. Just follow the flashing instructions and flash all the files they say to flash. Your welcome.
[T-Mobile, Samsung Galaxy SIII] Bitcloud30:
So what kernel are you using?
[T-Mobile, Samsung Galaxy SIII] malick186:
I am dowloading it right now! Does the sim working properly since there is difference in modem! :confused:
[T-Mobile, Samsung Galaxy SIII] malick186:
Finally installed it. All cm features are missing :(
[T-Mobile, Samsung Galaxy SIII] cyanogen_patrick:
Err....

Well, I can't say anything. I'm working on porting cm11 from the Note 2 LTE to the S3. If that works, I'm porting cm12 to the s3, hopefully.
[T-Mobile, Samsung Galaxy SIII] rcurtis805:
Yeah it's an alpha build so the bells and whistles of cm features aren't available. It's basically just a working version of 5.0. As time goes on they will add the bells and whistles.
[T-Mobile, Samsung Galaxy SIII] thirdzcee:
Its actually an almost perfect build for me... Only issue is camera and contacts fc when a synced contact's name is more than one word.... Even had faster GPS lock than 4.4 roms...

Don't seem to miss cm features as I don't use much... Just probably on screen buttons and skip tracks with volume button is what I'm missing
[T-Mobile, Samsung Galaxy SIII] bobthesalesclerk:
Running this on my phone. It was kind of wonky at first but after 2-3 wipes/flashes this is the best ROM I have ever run on this phone.

If you get tons of force closes, no root, and can't seem to download anything wipe and re flash.

As of now everything is working for me(including the camera using nexus camera).
[T-Mobile, Samsung Galaxy SIII] allendj81:
Test builds V4 is running great, ive been running it for 2 days and ive had 0 FC's! just camera doesnt work, but you can download an alternate camera from the play store (nexus camera or camera zoom FX works for me). All you have to do before flashing is modifying the "updater script", open and edit the updater script and just replace all "d2att" with "d2tmo", save changes. Do a clean flash. I use the usual apps (fb, tw, whatsapp, a couple basic games) and everything works well. I dont use any apps that use the camera (vine, instagram, etc) so I cant report on those. No need to flash a kernel or different radio.
[T-Mobile, Samsung Galaxy SIII] bobthesalesclerk:
V5 is working fine for me. Everything works except video recording(pictures work with Nexus Camera) and cast screen on Chromecast. I tried the fix for the Nexus 7 but it disconnects immediately.
[T-Mobile, Samsung Galaxy SIII] outlawnunn:
I used es file manager changed all d2att to d2tmo and reziped the file and still won't flash. What am i doing wrong?
[T-Mobile, Samsung Galaxy SIII] malick186:
just remove the first line and then try ?
[T-Mobile, Samsung Galaxy SIII] allendj81:
I tried editing the update script using root explorer, and it did the editing. however, when I moved/copy and paste the edited update script back to the Rom zip, it would move the original/unedited update script. So this is what I did: I extracted the update script and edited with root explorer, then I emailed the edited update script to myself, then I open the rom with 7-zip on my computer and replaced the original update script with the one I edited, saved the zip to my desktop. I then proceed to flash and it worked perfectly.
[T-Mobile, Samsung Galaxy SIII] patrickae:
I dont suppose you could share the file? For the rest of us.
[T-Mobile, Samsung Galaxy SIII] allendj81:
I rather not, for some reason the guy who put together the zip took down the thread and his account is suspended, who knows what happened. Its very easy to modify tho, give it a try.
[T-Mobile, Samsung Galaxy SIII] sipher26:
i took a day or so by finally got my son s3 working
[T-Mobile, Samsung Galaxy SIII] rcurtis805:
The current build is build 5 dated 11/25. It works better than build 4. You can use a few different cameras but stock camera still not working right. If you use Philz touch recovery you don't need to modify the script, it will flash just fine. It will say your phone is an i747 but that is just cosmetic it changes nothing with functionality like data or calls, etc. Because this is just a software rom and doesn't change anything hardware specific. Enjoy.
[T-Mobile, Samsung Galaxy SIII] TheOneM8:
Thank you...

Where is the download link? I have been looking all over the place for CM12 on T999
[T-Mobile, Samsung Galaxy SIII] ShernDog:
I tried changing all the d2att to d2tmo and it is all changed but when I try to flash it, it gets a couple fail messages about mounting something and then I try to reboot it gets stuck in bootloop.

When I try to flash without changing the d2att it won't even flash.
[T-Mobile, Samsung Galaxy SIII] Mervingio:
Anyone got V5?
[T-Mobile, Samsung Galaxy SIII] ShernDog:
https://drive.google.com/file/d/0B1l...ew?usp=sharing

It's here.
[T-Mobile, Samsung Galaxy SIII] Mervingio:
Say file not exist [emoji15]
[T-Mobile, Samsung Galaxy SIII] getochkn:
Thing to remember when editing the update-script file

First, use something like notepad++ and not any windows programs like wordpad or anything. They can insert extra characters that linux can't use.

Second, use 7-zip to put the file back into the zip. Don't unzip it and try to rezip it. Just open the rom zip file, navigate to the proper folder and drag the new update script into it. Other zip programs don't zip right.
[T-Mobile, Samsung Galaxy SIII] nirogu325:
There's a new thread.
[T-Mobile, Samsung Galaxy SIII] bobthesalesclerk:
Running Liquid smooth.
[T-Mobile, Samsung Galaxy SIII] HeyPrivate:
Working

Working for me on my T999 after changing the updater script :good:
[T-Mobile, Samsung Galaxy SIII] jesusprice:
Liquid Smooth Lollipop is smooth enough that I've been using it as a daily driver

No random Reboots or anything
[T-Mobile, Samsung Galaxy SIII] pekcle:
How is the battery life?
[T-Mobile, Samsung Galaxy SIII] allendj81:
if you want the most recent cyanogen 12, go to the at&t SIII section and look for. Just the same thing and update the updater scrypt by replacing all de d2att to d2tmo. The usual bugs are still there (camera and keyboard swype), just download the nexus camera and the google keyboard from google play. Its running smoothly and battery life is normal. Themes are working too.
[T-Mobile, Samsung Galaxy SIII] jchroneo:
Private Number Caller ID Issue

Hey Guys,

So Im relatively new to the flashing ROM on my S3, but, I got it all up and loaded properly. My BIGGEST issue is: that I cannot see whos calling me, who has called me, and who I am calling. Under my "Recents" section, all numbers shown as 'Unknown'. When I receive ANY call, the Caller ID displays as 'Private Number'. I have been searching through forums, and have not located a solution just yet. Can anyone help me resolve this? I have an S3 T999 with T-Mobile. All assistance is greatly appreciated! :confused:
[T-Mobile, Samsung Galaxy SIII] ganiman:
I've been running CM12 for the last 24 hours. So far so good with one exception. It seems that bluetooth devices cannot pair to my phone, but my phone can pair to them. The phone is discoverable, but when the other device, like say my car, tries to initiate the connection it will fail. It works in the reverse, which is a little annoying as I rely on my car's handsfree functionality for calls and music and it does not auto-connect when I start my car and I have to manually connect from the phone each time.

Besides this bluetooth issue, it seems pretty solid. It was nice to see the S3 still getting some love. I am having a hard time justifying a new phone after this upgrade. Besides some slight upgrades like faster CPU, bigger display and maybe a finger print scanner (who cares?), what does a new phone really have to offer? The S3 is still a solid device (would like some LTE, but I am around Wi-Fi 99% of the time anyway).
[T-Mobile, Samsung Galaxy SIII] crazyemon3y:
So I've been trying to find an official CM 12 nightly build for the S3 from the Cyanogenmod wiki page, and for the past few months, I couldn't find it. However, as of the 30th of April, there are CM 12.1 nightlies available, but they are no longer using the unified d2lte page. For whatever reason, they have gone back to using the carrier build pages, so for us, this means the d2tmo page. However, the d2tmo page does not show up on the device section of the wiki, so you have to go to the d2lte, then click on d2tmo in order to access the official nightlies.
[T-Mobile, Samsung Galaxy SIII] ganiman:
Nightlies are here for reference:

http://download.cyanogenmod.org/?device=d2tmo
[T-Mobile, Samsung Galaxy SIII] tjg_marantz:
Confusion. Got an S3 from Videotron a while back. Unlocked it, now with Koodo. I'm running Slim Kat 4.4.4. Downloaded CM downloader app and it's rightfully telling me that Sept 3 nightly of 12.1 d2tmo is available. Download it. Reboot into CWM recovery, install zip and it says this zip is for tmo, lte and one other but this phone is d2att. I thought Videotron phones were d2tmo. If I download the d2att nightly, should that work without issue? Sny ideas as to why cmw recovery thinks one thing while cm downloader thinks another?
[T-Mobile, Samsung Galaxy SIII] audit13:
If you have a custom recovery, you should be able to flash the d2tmo from recovery. That is what I did with my videotron t999v.
[T-Mobile, Samsung Galaxy SIII] ImpassionedRule:
Likely you flashed the d2att recovery, so it thinks it's a d2att rather than a d2tmo. Try the d2tmo or d2can recovery.
[T-Mobile, Samsung Galaxy SIII] tjg_marantz:
That's probably it. I know my last install (from stock to slimkat) went poorly so I was trying so many different things to make it work that I probably did exactly that.

I now find myself in a strange spot hehe. The d2att nightly from Sept 2 is running on my phone without too much issue (bluetooth not connecting, minor since I rarely use it) so I am leery to fix what is seemingly not broke.

Anyways, thanks for the reminder about the recovery, that is very likely exactly what I did previously. I'm in limbo land now. :fingers-crossed:
[T-Mobile, Samsung Galaxy SIII] audit13:
The t999 needs the d2tmo version of twrp. Don't flash the d2can version as the d2can is made for the i747m.
[Xperia Z3 Compact Accessories] jokingo:
Hello.

I wonder if my recently mounted tempered glass protector hold on well when I insert the mobile in water, I bought the ultimate shield protector. ¿Does anyone know if it could take off over time after inserting it in water oftenly?

thank you! Great community :)
[Xperia Z3 Compact Accessories] Dsteppa:
After you applied the screen protector in water, just remove the excessive water that's between the phone and the protector. Do it with a squeegee or use a hairdryer.
[Xperia Z3 Compact Accessories] smanet:
I tried a quick wash of phone, with the shield on. It stayed without problems!

Inviato dal mio D5803 utilizzando Tapatalk
[Xperia Z3 Compact Accessories] jokingo:
Thank you guys, I will try not to wet the screen very ofte.
[Xperia Z3 Compact Accessories] Spongeworthy:
I found that once I used water to apply the screen protector large amounts of moisture were still trapped inside the screen even after a week. They weren't like water bubbles either, the protector was completely flush. Anyways, this moisture started become really obvious and discoloring my screen until I took it off. Anyone else have problems with doing this?
[Xperia Z3 Compact Accessories] jokingo:
Hello, I don´t know your issue exactly. But what is recommended to do is to clean the mobile screen with alcohol or the washcloth supplied with the protector. You shouldn´t use water I think...
[Xperia Z3 Compact Accessories] Spongeworthy:
You should definitely not use alcohol unless its heavily diluted or you can wear out the oleophobic coating on the screen. A wet application with water i think is fine, everyone does it, cant seem to figure out why i have this problem.