yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Not a problem, but thanks.

Yes, all but external storage and USB_OTG.

I think enewman17 actually has recovery flashable TW stock roms and a recovery flashable stock recovery; here for NJ1 and NJ2 and stock recovery. The ROMs are pre-rooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
actually already knew about the roms, but i was actually looking about XDA and found this:

http://xdaforums.com/galaxy-s3-att/development/s3-r3born-rom-based-likewise-s5-t3106075

this should be flashable via TWRP yes? the reason i'm asking is that i would like to do touchwiz, but at the same time the s3's is a bit out of date by now, this seems to be a combination of touchwiz from the s5, and s6 all ported to the s3, however in the requirements it says CWM recovery, so i'd like to be sure it will work via TWRP before trying it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
It should work fine with TWRP, in fact it has been so long since CWM was updated that it won't install all ROMs. I have been watching that thread for a bit also and am waiting until he finishes the update he is working on. If you like the R3ARMED rom because of the S5/S6 bits, you may also like the Likewise ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
ok, so now the only thing i'm wondering is how do i tell if i'm on the 4.4 modem/bootloader?

the last stock rom from OTA i had installed was from august, and android version 4.4.2, according to download mode my boot loader is 3

whatever that means i have no idea
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
There is an app in the Playstore, Phone Info *Samsung* by vndnguyen.

If you have Terminal Emulator on your phone you can tell with two commands:

getprop ro. bootloader
getprop | grep version.baseband

The 4.4.x versions for the i747 are NE4, NJ1, and NJ2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
ok, so everything go's good until it reboots after installing rearmed, i see the TWRP style samsung galaxy s3 logo, then my blue notification light comes on and pulses as if it was booting, then it reboots again but this time into recovery mode, i factory reset and wiped data as the instructions said to, and i did get some armoa installation thing (one part of which also asked me to choose a kernel, i chose the one that said "stock ob3 kernel" as i don't know what the other ones would do)

the installer even said that battle frontier 4.1 rom was installed successfully, but like i said earlier in the post, nothing but the blue notification light

any idea's? (atm i'm trying to restore from my backup again after doing a full wipe, so that i have something to use until i get the rearmed thing working)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
huh, i've noticed something, cm12 is the ONLY rom that seems to want to work, tried likewise, it stayed at the samsung boot logo for ages, i did eventually get rearmed to correctly install, but it has the same problem as likewise, touchwiz doesn't seem to like working at all anymore, while cm12 installs perfectly every time

what the heck is wrong with my phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
My first guess is that CM12 is not the only rom that will work. Try another 5.1.1 based AOSP or CM ROM to verify this.

Going back from a 5.1.1 ROM to a KitKat TouchWiz ROM will probably require formating the internal sdcard. Selecting wipe in recovery is not the same as formating. Did you actually format the internal sdcard? If formating alone doesn't do it then installing a stock recovery and factory reset from within the recovery should fix things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
there doesn't seem to be a format button in twrp other then the format data button
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I think you can only format data and only wipe system in twrp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
then how the heck am i supposed to install likewise or rearmed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
Whenever I install a ROM, I used the advanced wipe feature and wipe everything and install from an external SD card.

Look at the twrp log as it wipes. I think I recall seeing twrp format the system partition from the wipe option. I don't have the phone at the moment so I can't confirm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
that's what i already do, yet i still get stuck at the samsung boot logo (the new one with the colored dots around it, not the old one with the blue circle and the expanding samsung logo, as the rom i'm trying to use is based off the versions of touchwiz from the S5, S6, and note 4)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I just tried to install Rearmed 4.1 to a d2tmo and I also get stuck in that it installs but won't boot. I tried it with different kernels too. I finally gave up and tried the latest nightly cm12.1 which installs and runs properly. I then use Odin to flash back to stock, factory wipe, and the phone is fine. I know the d2tmo is not the same as the d2lte.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
actually mine is the d2att, not the d2lte

and is it just rearmed that also doesn't work for you, or does likewise rom also not work for you?

because i also tried likewise and it had the same problem as rearmed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I haven't tried likewise but I will.

Your phone is now referred to as d2lte. Before the s3 builds were unified, the att s3 was referred to as d2att and the Canadian s3 was referred to as d2can.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
so audit13, what would be the exact instructions for flashing stock touchwiz 4.4 back onto my phone? since you said that you did so on your own phone i'd assume you'd be able to help me do so
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
I see you are running an i747. Make sure you are running the nj2 bootloader and modem.

The nj2 modem, bootloader, and ROM are located here: http://xdaforums.com/galaxy-s3-att/general/rooted-ucufnj1-stock-rom-t2985006

All of these can be flashed via the latest version of TWRP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
KOT94H.I747UCUFNJ2 is nj2, yes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] audit13:
The Samsung Info App will confirm that the bootloader and modem are fnj2. If they are, you can flash the ROM from the latest version of TWRP.

Edit: forgot to mention that a full wipe (Dalvik, data, and system) is recommended before flashing the nj2 ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
ok, i for the life of me can not get it to actually boot into the os, i get as far as the AT&T logo, then after the familiar AT&T boot sound, it locks up right there, only thing still doing anything is the notification light pulsing

i did an advanced wipe, with everything except micro-sd and usb-otg selected
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] logoster:
nevermind, got my backup to work correctly

now twrp says it can root my device for me, but it doesn't seem to succeed, so i'm wondering what's the best way to root stock touchwiz 4.4.2? (this is on the AT&T i747, with the fnj2 bootloader and modem) as i'd like to reset the knox counter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
The most reliable way seems to be flashing the supersu.zip from within TWRP. Links to it can be found in the OP of several of enewman17 s stock rom threads. The zip can also be found in the supersu thread by chainfire.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrrocketdog:
http://xdaforums.com/showthread.php?t=1538053

"all i can really do is stay out of my own way and let the will of heaven be done"
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dawgdoc:
Thanks for getting the link for him. I was on a public wifi and running low on battery and therefore didn't take the time to search.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] Kimi Kei:
thanks to all
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ashyx:
POWER + HOME together iirc.
[Galaxy Tab 4 Q&A, Help & Troubleshooting] mab71:
Palm swipe over the screen.. Like on any galaxy phone
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ashyx:
Doesnt work. As said POWER + HOME
[Galaxy Tab 4 Q&A, Help & Troubleshooting] mab71:
Mine does
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ashyx:
Stock rom or custom?
[Galaxy Tab 4 Q&A, Help & Troubleshooting] mab71:
Stock
[Galaxy Tab 4 Q&A, Help & Troubleshooting] ashyx:
Got it now, was disabled.
[T-Mobile LG G4] raw2000j:
Does anyone know how to fix writing to the sd card like xtreme rom has?
[T-Mobile LG G4] dgjenkins:
Easiest way I've found is to download "Foldermount" from the Play store. Let it run once. It will tell you it needs to fix and reboot your device. Let it reboot and you're good to go!
[T-Mobile LG G4] maximus20895:
I justed posted another app as well:

https://play.google.com/store/apps/details?id=nextapp.sdfix&hl=en
[T-Mobile LG G4] NinjaBuzz:
Xposed module XInternalSD

Xposed module XInternalSD works also.
[T-Mobile LG G4] Biker1:
[/COLOR]

Been using that one for awhile now. Works great.
[T-Mobile LG G4] Synchronicities:
I used that SDFix app, too. Worked perfectly, short and fast.
[General Topics] racerx_:
i'm trying to implement a new template on my website, but i'm running in to a bit of trouble trying to edit the css to get the font colors i want... anyone out there that could lend me a hand?
[Moto 360] medmansri:
Since updating to Wear 1.3, I've had more error messages than ever before. It's been disconnecting from my phone for no reason.

The new thing I've noticed today is "Google services missing from phone"

Everything is already up to date (Play services, Wear and Android OS)

I've liked the interactive watch faces with the new v1.3 but these errors are really annoying.
[Moto 360] jdtruong:
I updated my watch yesterday and today I'm receiving the same message.
[Moto 360] baciany:
i Have the same ssue, can anyone help?
[G4 Q&A, Help & Troubleshooting] raw2000j:
Does anyone know how to be able to write to sd card anything i could edit in buildprop or any app i could download that will work in lollipop?
[G4 Q&A, Help & Troubleshooting] mr73:
FIX

Hi, I had the same problem here on my LG-H815 (Root). Go to App-Store, search for SDFIX: KitKat Writable MicroSD (NextApp, Inc), download and install, It solves the Issues with the SD-Card.

Or read here > http://xdaforums.com/showthread.php?t=2684188 .

Marcel.

PS: Sry for my bad english, im from Germany.
[Sony Cross-Device Development Themes and Apps] Ambor:
Hi Sony Users, I present a wonderful

Collection of my polygon style wallpapers

Creadits:

RXS MoonBreakers Team
​

Wallpapers Download:

Link​

​
[Sony Cross-Device Development Themes and Apps] ogunja:
Supreme creativity friend! ?????
[Sony Cross-Device Development Themes and Apps] fchaster:
download link not working ?i really like the black -red . .
[Sony Cross-Device Development Themes and Apps] Ambor:
:)

https://plus.google.com/+MichałAmbroziakAmbor/posts/LLhsEqJPmVH
[Sony Cross-Device Development Themes and Apps] charliebigpot:
Wonderful!

I took took the liberty of making the grey even darker to make the red really stick out!

(hope you don't mind!)
[Sony Cross-Device Development Themes and Apps] Ambor:
Ok
[General Questions and Answers] mr_qu:
Where can i find a good patched facetune apk? I found a 1.0.10 version that didn't work properly (it installed but non of the functions worked as they should).

I am new to android so i don't know where to look.
[XDA Assist] XDA Visitor:
AFter rooting my z1 in lollipop i tried to install some boot animations and when i got bored of it i wanted to get back to original but i cant access it.In the procees i thought that if i would delete all boot animations i would be able to get mine.but i couldnt please help me get that boot animation again.I need my lollipop animation again please help
[XDA Assist] TEKHD:
Hello there! Welcome to XDA!

First register an XDA account (so you can ask in the proper forum)

then, you may ask for help here: (see below)

Sony Xperia Z1 Q&A, Help & Troubleshooting

Your device experts are located there....(You will have a much better chance of getting help there)

Also, here is the Main Sony Xperia Z Area just in case:

http://xdaforums.com/xperia-z1

Always Remember to use the Search...

Thank you! Hope this help!
[General Questions and Answers] mihirsjain.mj@gmail.com:
PLEASE CAN U TEACH ME HOW TO INSTALLING A ROM OR RESTORING A CWM BACKUP USING FASTBOOT

Sd card not mounting phone in bootloop

I was flashing a zip on my htc evo 4g and after flashing it my phone got into a boot loop i have taken a backup but i can't restore it because it gives me error unable to write to ums lunfile(no such file or directory) i cant open my recovery because if i open it goes again in boot loop

WHEN I OPEN recovery open after that i can't restore or mount or do anything.

Please help me urgent i'm scared my father will shout me a lot if anything happens. I'm sorry if i have posted in the wrong place but please ASAP i'm SCARED PLS HELP ASAP . Thanks in advance. If you want me to upload the file which i flashed i can do it for sure. just tell me.
[Sony Cross-Device Development Themes and Apps] ogunja:
Friends!

There was a change to google play services, Android Lollipop ? 5.1.1. Before we used 438 and now becomes 238.

Notes / What's New

It seems that -4XX is now for Marshmallow+, and -2XX is for Lollipop+. I.e., if you're on Lollipop, and you had -438 before, now you'll need -238, etc.

*WARNING*: We've seen reports of constant crashes with these. Proceed at your own risk.

To figure out the right version of Google Play services for your Android device, go to*Settings -> Apps -> Google Play services, and look at the last 3 numbers in the parentheses.*

Download link - http://goo.gl/QWiDyU
[Sony Cross-Device Development Themes and Apps] abhinav.tella:
Yep it crashes lol, I installed it as soon as I saw it on APK Mirror (Run by Android Police and files are safe)
[Sony Cross-Device Development Themes and Apps] whalesplaho:
thanks for tha update brov.... exhausted my thanks!!!

even tha latest play services is for LP (5.0.2+)

---------- Post added at 05:42 AM ---------- Previous post was at 05:36 AM ----------

please brov can i get tha softkeys but tha Z3 shud be Z2.... thanks:good::highfive:
[Sony Cross-Device Development Themes and Apps] rajibdpi:
thanks
[Sony Cross-Device Development Themes and Apps] ogunja:
??

Search po JimmzTheme or JimmzTheme Dream Style. He makes great themes. ??

?
[Sony Cross-Device Development Themes and Apps] anakdayak:
Tnx bro install on my z1 stock odex 5.0.2 without any issue.
[AT&T LG Optimus G] nidlaX:
For those of you who activated 2G-only mode in your Mobile Network Settings and can't use that menu anymore due to crashes, there is a relatively easy way to reverse this condition and bring back the menu functionality while untoggling 2G-only mode.

1. Make sure your ROM is rooted (should be the default state of Paulicat's ROM).

2. Use ESFileExplorer (or a similar root capable file manager) to backup the contents of the following directory:

/data/data/com.android.providers.settings/databases/...

(Note that the critical file to backup is 'settings.db', the journal and other files are not critical but should be copied just in case)

3. Make a copy of 'settings.db' in a temporary location

(You will edit this copy of the database)

4. Use an SQLite editor (I used SQLite Debug) to open the 'settings.db' file you copied previously

5. Open the 'global' table and find (by the 'name' column) the row with 'name' that is 'preferred_network_mode'

6. Update the 'value' of this row from '1' to '0'

7. Execute your transaction and commit the changes to the table

8. Close the db and re-open it to verify that your changes have persisted

9. Return to '/data/data/com.android.providers.settings/databases/...' and delete the entire content of that directory

10. Immediately copy and paste the edited 'settings.db' file into the '.../databases/...' directory

11. Immediately turn off and restart your phone

At this point, you should have changed your phone's network preference setting from 2G only back to 2G/3G. This will also allow you to access the Mobile networks settings menu again.

I didn't find this solution for months because I didn't realize that the Android global settings database was stored in the above directory. I hope posting this here might help someone.

Reference: http://xdaforums.com/showthread.php?t=2230207 (You may follow the suggestion to make this change via adb)
[Fire HD 6 and 7 General] DoLooper:
Install ADB Driver for Sideload Mode

Windows can’t recognize the Fire in sideload mode until you install the driver for it.

Note: These steps are pretty much identical to Post #1. Refer there for illustrations.

1. Connect the tablet to the computer and put it into sideload mode, like this: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.

To reboot to recovery:

- From CMD window, run: adb reboot recovery

or

- Manual: (a) Power off the Fire. (b) Hold the power and volume-up buttons until Amazon logo appears, then let go.
​

2. Open Device Manager, find KFARWI under Other Devices, right-click it and select Update Driver Software.

If you don't see KFARWI under "Other Devices," see hidden text.

When KFARWI isn't under Other Devices, first be sure you "clicked" Apply Update from ADB on tablet to get into sideload mode.

If you did, see if "Android Device" is listed at top of Device Manager with a driver under it.

If Android Device is not listed, unplug/replug the tablet and see if KFARWI shows up under Other Devices. If it does, go to step 3. If it doesn't, post the problem.

If Android Device is listed, open CMD window in folder containing adb.exe and run adb devices command

- If adb devices returns an ID, this driver is working and you don’t need to install a different one.

- If adb devices does not return an ID, in Device Manager, right-click the driver, select Update Driver Software and go to Step 4.

​

3. Press Browse my computer for driver software and then Let me pick from a list of device drivers on my computer.

[See “Select your device’s type”]

4. Click Android Device.

[See "Select the device driver you want . . .”]

5. Select the same driver you use for “normal” OS mode (post #1, step 10) and press Next.

6. Click Yes at warning screen.

Driver is updated!

7. In CMD window, run adb devices command and confirm you see your device ID and "sideload," like this:

​

8. DONE! Issue the sideload command or reboot to exit sideload mode.

Note (shouldn't happen, but . . . ) If you don't get a device ID and you had a driver installed at step 2 and updated it, you'll have to uninstall the driver.

In Device Manager, right-click and uninstall the driver under Android Device.

Restart computer and reboot tablet (to get out of sideload).

Go into sideload mode, right-click KFARWI under Other Devices and see if it has Update Software option.

- If YES, update the driver.

- If NO, reboot once more and go into sideload and you'll have Update option. Update the driver.
[Fire HD 6 and 7 General] DoLooper:
Info and Tips for Using the Command (CMD) Window - for "Newbies" :)

Here's some basic info for using the CMD window and entering commands found in the guides.

Open CMD window

Hold down the shift key, right-click an empty space in an open folder (including desktop), and choose "open command window here"

Give commands on-the-fly

If you used 15-Second Installer (post #1) you can open the CMD window from any convenient location, so you can easily give adb commands "on the fly."

Example: Open CMD from desktop and run adb devices to confirm adb recognizes your Fire.

Install an app (or sideload a bin file)

Open CMD window in the folder containing the file and enter the command: adb install filename.apk

If you open CMD from a different folder, include the full path: adb install "full_path_to\filename.apk"

Format: If there are spaces in the path or filename, put quote marks ( " ) around "full_path_to\filename.apk"

Drag & drop files and copy/paste commands

To enter a long or complicated command or file name into the CMD window, use drag & drop or copy/paste.

Drag and Drop

Type: adb install <--type a space after "install"

. . . then drag and drop your file into the window. The "full_path_to\filename.apk” will be inserted at cursor.

Copy and Paste

Select the command or long file name and use CTRL-C to copy it. In CMD window, type adb install(space) as above, right-click the top bar of the window and choose Edit then Paste.
[Fire HD 6 and 7 General] rking38:
Installing drivers for sideload

Is there a discussion or a fix for installing the ADB drivers for sideload using windows 10? I'm not sure if Windows 10 is the issue, but instead of getting KFARWI in device manager, I get MT65xx android device. I've followed the instructions after step 9 several times with no luck. I've tried updated the drivers with the ones mentioned in step 3 but ADB device doesn't list a device. Any suggestions?
[Fire HD 6 and 7 General] DoLooper:
Sounds like you're opening Device Manager while in recovery, not sideload mode. Look at step 1 again: Reboot to recovery, use the volume buttons to highlight “apply update from ADB,” and press power button.

Once in sideload mode, you should see KFARWI.

(I edited OP to make step for getting into sideload more obvious)
[Fire HD 6 and 7 General] rking38:
Wow...follow the instructions from step one! thanks for your patience :)
[Fire HD 6 and 7 General] DoLooper:
15 Second ADB problem

Someone else encountered this with 15 Second installer. Are you running Win10? What flavor (pro, home, etc)? At what point exactly is "Access Denied" displayed with version 1.4.2?

Also, do you have folder, C:\adb or C:\users\username\adb? If yes, what files are in it?

Please let me know these things so I can try to find a fix. EDIT: [MENTION=6953333]MRDirtyPixels[/MENTION] I'll post how to update the driver when you reply. Thanks!
[Fire HD 6 and 7 General] jiznon:
Fire HD 6 on 4.5.3

Win7 Ultimate x64

I'm having an issue at "Apply update from ADB". I do not have this option in recovery - only "Reboot your Fire", and "Reset to Factory Defaults".

I've had ADB drivers installed from past projects. Tried it, got this issue. Went back and installed the ADB drivers from the 15 second installer to see if that helped, still have this issue.

Also, at no point is my Fire listed under "Other Devices" - I don't even have that listed as a category. The Fire is always listed under "Android Device" > "Android Composite ADB Interface", so I figured my drivers were all set.

Any ideas would be greatly appreciated.

**EDIT: Should I somehow remove/uninstall all ADB related drivers and software and try again?
[Fire HD 6 and 7 General] DoLooper:
You use sideload mode to downgrade to 4.5.3 from OS 5. (It's only an OS 5 recovery option.) Since you're on 4.5.3, presumably with OTA blocked, you don't need sideload. Sounds like your drivers set up right for OS mode. Go root!

EDIT: [MENTION=6005499]jiznon[/MENTION] Be sure OTA is blocked. Else you'll OTA update as soon as you turn on wifi to root!
[Fire HD 6 and 7 General] jiznon:
Oh, great! I may have overlapped a guide or two. Thanks so much!

I managed to turn airplane mode earlier as the OTA began to download. Should be good, ya?
[Fire HD 6 and 7 General] DoLooper:
NO! you'll have to turn it off and use wifi to root. Run these commands:

adb shell pm block com.amazon.dcp

adb shell pm block com.amazon.otaverifier
[Fire HD 6 and 7 General] jiznon:
I see. That step isn't for sometime in the guide I'm following (it also states to install sideload drivers). Maybe it should be edited.

http://xdaforums.com/fire-hd/general/root-developer-preview-lollipop-os-5-t3172408/
[Fire HD 6 and 7 General] DoLooper:
Well, it's the step you do before turning on wifi to root. Notice that first step says that if you're on 4.5.3, get kingroot and go to step 6. So you're right there, at step 6.