yashsingh1/xdaforums huggingface dataset:
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] ShrekOpher:
The phone will be like new. It will completely reset the software. It will still be carrier locked to Tmobile.

If you want to root go here:

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

EASY STEPS >>> N910T -> COD6/COG2 -> ODIN -> CF-ROOT -> TWRP RECOVERY -> FIX -> Done!

You can carrier unlock it using cellunlocker.com if you want to use it on a different service.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] masri1987:
No problem man, this is what we are here for to help one another.

What's the result
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Mikeort:
all working like a charm

thanks
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] sublimaze:
Glad you got it worked out. Welcome to the world of root & modding :highfive:
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] ahq1216:
1st mistake, using craigslist.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Jammol:
I purchase devices in craigslist without issues. I always very imei numbers before final purchase and never ever EVER buy phones that are not with the carrier I'm on.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] Webergti:
The mistake the people do is the now with reactivation lock from Samsung even if is not on in settings/security/reactivation lock check if you factory reset the phone in recovery it will activated it self and the next time you go to initial wizard it will ask for the last Samsung account and password to that last Samsung account in the phone is kind of anti theft because before even if you had a password all you had to do to get it working was to do a factory reset in recovery mode so the mistake people may be doing is doing a factory reset on recovery instead of doing it under settings/backup and reset/ factory reset it will ask for password will clear the reactivation lock account so if you sell a device do other people a favor and don't reset the phone from recovery but from setting

Now if the phone is stolen or under installment payment and is not pay off and payment are not made the carrier can block the IMEI (International Mobile Equipment Identity) and that can happen even if you buy the phone and is been working for day week or month you may turn the phone off or reset and the next time you try to make a call it will say not registered network that means the if you have a full working sim install from the carrier phone in this case t-mobile the phone is block from the carrier but there are ways to fix it you have to look for some one to fix the IMEI that means with special hardware box and software they can change the IMEI # and get it fully working but why pay someone else more money and go the extra hassle when you can check the IMEI most carrier in the us have a web service to check the IMEI or you can just call the costumer service line and ask if the phone is clean not stolen and fully payoff

Google T-mobile IMEI check and the first link will take you to IMEI checker

Google At&t IMEI check and the first link will take you to IMEI checker

Google Verizon , Sprint and Us Cellular IMEI ESN (Electronic Serial Number) check and the first and second link will take you to ESN IEME checker
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] qunnin:
So does this means reflashing the phone via odin will clear the Samsung Activation lock?

Thanks for your advice
[One (M8) Q&A, Help & Troubleshooting] v1n0dhn:
I used to have an iPod touch before finally getting the One M8. I played around with jailbreaking the iPod and what not because I never really used the iPod. Now that I got the One (M8), I've been having a mental battle on whether I should root my phone or not. This is the only phone I have and I don't have any money to get a replacement in case something goes wrong. I have RUINED i mean RUINED devices because of something stupid I've done and I don't want that to happen to my phone. I use my phone for everything, texting, media consumption, social media, communication etc. so losing the phone isn't an option. Also how can I make a complete backup of my phone so I can restore data if I root.

QUESTION TIME: Should I root or not? What are the advantages? What are the pitfalls? I really want to root but at the same time I don't want to root because I'm afraid I'll ruin it.

PHONE: HTC One (M8) on AT&T running 5.0.1 Lollipop with the latest stagefright update.

EDIT: I also want to put Cyanogen Mod on it? How do I go about doing that?
[One (M8) Q&A, Help & Troubleshooting] jkolner:
I have rooted all my HTC phones and have never had any problems. I Unlock and Root cos i want 100% control.

I used this guide when i rooted my M8.
[One (M8) Q&A, Help & Troubleshooting] redpoint73:
Same here; I've modded 2 Samsung tablets, 4 HTC Android devices (3 phones, 1 tablet) , and 2 HTC (old school) Windows Phones before that. Never had a major problem (such as a brick) on any of them.

That being said, anybody willing to mod these devices should at least be aware of the risks (as you well seem to be) and willing to live with the consequences, however unlikely.

But honestly, spend the proper amount of time (a couple hours, at least) to read the guides, forum threads, and understand the processes,

before

you try to do anything. Do the proper research/learning and follow instructions precisely, and the risk is very low.

Also, be sure to backup your personal data as much as possible, every step along the way; to prevent the disappointment of data loss, or facilitate reverting the mods (is needed).

Don't proceed without a good understanding of what you are doing. And do

not

try things recklessly or "experiment" if you get stuck and panic (a common mistake). If you get stuck, look on here for the answer; or just post your issue and somebody will help.

Remember that everyone here at one time had to start from scratch, just like you. But as long as you are patient, and good at following instructions, you should be fine. Especially if the goal is to just put custom recovery on the phone, root, and flash a custom ROM; the risk of permanent damage is very low. At the worst, you may get stuck in a bootloop or otherwise not able to boot the phone due to a mistake on your part, so simply some random occurrence. But this is most often an easily recoverable condition.
[One (M8) Q&A, Help & Troubleshooting] jshamlet:
Only you can know if the advantages to rooting outweigh the disadvantages. I personally wouldn't own a device that I didn't have at least root control over, but that's just me. On the other hand, I've put off installing the stagefright update because even unrooting isn't enough to make taking OTAs safe - that's a huge con.

You really have to consider that you will be the system administrator of a small computer, and a computer which the manufacturer didn't trust you to administrate. However, pretty much everything you would be doing are known, documented tasks at this point. If you are willing to put in the effort to read everything you can, and plan before you act, you can turn your device into the perfect (for you) machine. Or, you can step back from the challenge and just use it as it came. The HTC One M8 is actually a perfectly fine device right out of the gate, so there is no shame in leaving it as it is.

There are worthwhile reasons to root. I personally can't live without being able to configure the firewall (iptables), AdAway, Titanium Backup, AppOps, GSAM battery monitor, wakelock detectors, etc. However, my wife, who isn't techie at all, is happy as a clam with her 100% bone stock Samsung Galaxy Mega. She just uses the thing and doesn't worry about all of that stuff.
[One (M8) Q&A, Help & Troubleshooting] tony_5309:
Good answer Sir. Wish most of the folks on here did this already. I remember when I first started out when the HTC Hero and Evo first came out, there was never this many people screwing up their phones like you see now.

[MENTION=6944193]v1n0dhn[/MENTION], just read and teach yourself how to do things before jumping in with 2 feet. Then determine for yourself if this is for you.
[One (M8) Q&A, Help & Troubleshooting] v1n0dhn:
I've started the process.

So, I've convinced myself to root my phone. I'm right now waiting for my adb backup to finish. I read up on rooting a little more and have gained a little more confidence. I backed up my sms to gmail using an app and copied my important photos and app data to my pc. I'll make another reply when this is done and I when I unlock the bootloader.
[One (M8) Q&A, Help & Troubleshooting] 3484jacks:
There's pretty much all the detail you need above but I must stress the importance of backups. Back up (like you are doing) SMS, Photos, Bookmarks all that stuff, but also once rooted make a nandroid backup, and pretty much every time you do anything (install a ROM, recovery etc.), nandroid that sh**. It will save you at some point. Just read all the posts asking for help because they wiped everything while installing a ROM but didn't have a back up when it went wrong.
[One (M8) Q&A, Help & Troubleshooting] v1n0dhn:
I've started the root process and i agree that backups are important. All i have to do now is flash a recovery and them cm and gapps.
[T-Mobile Galaxy Note 4 Q&A, Help & Troubleshooting] ispot:
Is there anyway to disable the auto play upon bluetooth connection without disabling the "Media Play" on connected device property?

I used Titanium Backup to un-install the built-in music app.

Is there any other way to disable that annoying autoplay?
[Galaxy S6 Accessories] Muezick:
Trying to find different ways to broadcast my phones screen or emulate a desktop environment with my galaxy s6 where the output is to an external monitor.

I know MHL is a bust for the s6, it doesn't support it. Beyond that, all I can find are wireless solutions. Chromecast, Miracast and Samsung's proprietary garbage. But are there any others?

My question is, are there any obscure apps, or hardware gadgets that might work with Android that I could do this with. I've got an OTG and a USB hub, I've seen USB to HDMI outs, why don't these work with Android? No Software? Pure hardware incompatibility?

I hunted around these forums a little before posting this, but didn't find anything related, so I apologize in advance if there's some central thread discussing this for the S6.

Thanks for reading
[Galaxy S6 Accessories] dubt17:
Chromecast and cast your screen :)
[XDA Assist] XDA Visitor:
Hi

please someone help me in this . my iball andi avonte 5 is been stuck on the boot and customer or official rom is also not available on internet

please help me to fix . or suggest me any rom which can work in this device

thanks
[XDA Assist] OfficerJimLahey:
Hello, and welcome to XDA! :cowboy:

Unfortunately there is no trace of this device on this site (only one thread for the 4.5h cousin). You may have some luck in the general help thread.

Please create an account, so you can post in other forums. From there, add a post to the following thread:

> Android Development and Hacking > Android Q&A, Help & Troubleshooting > [Ask Any Question][Newbie Friendly]

Please note any modifications to the device, as they may be relevant to how the stuck boot got there, and what the solution can become.

Hope this helps, and good luck! :)
[Verizon Samsung Galaxy S III] cory733:
what i did so far. used odin to flash h1 baseband rom so i can root. rooted with cydia. downloaded e-z recovery. installed cwm. that didnt read my storage and nothing in it would work. installed twrp with e-z recovery. same problem.(edit: when I got to twrp it said "no o.s. found" so I then had to reboot into download mode and flashed the stock rom) Then downloaded android terminal emulator. downloaded cwm and installed by typing in the commands. got into cwm and made a backup. wiped data, cache, dalvik. tried to install "cm-11-20150831-SNAPSHOT-XNG3CAO3FN-d2lte". it installed but went into a boot loop and would end up back at cwm every time. wiped data, factory reset, restored backup. tried again, same thing, restored again. tried installing "cm-12.1-20150915-NIGHTLY-d2vzw" this time. it got stuck saying "patching system image unconditionally.....". wiped data, restored stock, tried again this time with "cm-10.0.0-d2vzw". it didnt even install. now im restoring again to stock.

the reason im trying vzw roms also is because i have a verizon note 2 on straight talk and was gonna try to use that sim card in my s3.

http://xdaforums.com/galaxy-s3-verizon/help/straight-talk-sch-s986c-t3036314/page3

^^this thread has some info about it but im new here and havent found anything else about it. before i try getting it to work with my verizon cdma sim card i at least would like to just get cyanogenmod working on my s3.

am i using the wrong roms? is this in the right forum?

thanks
[Verizon Samsung Galaxy S III] cory733:
now supersu is gone from my phone. i just installed es file explorer and checked allow root permissions and supersu didnt even come up. i uninstalled and reinstalled in the play store also and nothing happened
[Verizon Samsung Galaxy S III] Droidriven:
You need the d2vzw ROMs, if you are using lollipop then you need to go to developer options and turn on root access, set it to apps and adb.

There is a TWRP made specifically for d2tfnvzw, it has our source code in it, the other d2vzw TWRPs don't mount our devices correctly.

I worked with a dev at OctOS to get our device fully supported, all their d2vzw stiff has our code in it now. I can link you to the TWRP if you have trouble finding it.

I know pretty much whatever you need on this phone, just hit me up with anything you need help with and I'll get you straight.

Have you backed up your IMEI in terminal emulator yet, I recommend doing so because this phone has a habit of losing IMEI when flashing back and forth between ROMs, flashing stock tar won't fix this.
[Verizon Samsung Galaxy S III] cory733:
hey droid thanks for getting back to me. i cant find the twrp for the d2tfnvzw, just the d2vzw. were you saying that i could use the d2vzw because it has the straight talk code in it or i need the exact straight talk version? yes if you have the link i would appreciate it because i didnt see anything except the d2vzw. how would i install it with cwm already on there? would it just overwrite it?

i had no idea about backing up imei until today. but this is already after installing the h1 rom and getting it rooted. then trying cm 4 different times. if my info was lost, would it just be blank? or would it have different numbers that are just useless to me. because its still there but i didnt write down the numbers before i did all this. but anyway today i think thats what i did, ive done so much with this phone that i cant even remember exactly, but i opened up terminal emulator, typed in something involving rebootnv/ something and it rebooted then i copied the efs folder from my phone and put a copy on my computer.

i just did another restore of the first backup i made. supersu is still gone. i downloaded my android tools and it says that supersu was still an enabled app. i never hid it or disabled it in any way that im aware of. i tried uninstall and reinstall from play store and the terminal emulator command and the #*#* numbers on the phone dialer. nothing. es file manager also got root access without supersu coming up.

also it seems like its not getting 3g at all. usually it goes from 3g to just 2 bars or one bar where i live. but now its just steady at two bars. even with wifi off. does 3g stop showing up if the phone is not in service? i dont remember.

btw this phone has android 4.1.2
[Verizon Samsung Galaxy S III] Droidriven:
If you want a working TWRP then you'll need the d2tfnvzw version, any d2vzw or d2lte ROM should work fine for you.

If you lose IMEI it won't show in settings. The reboot nvbackup that you did in terminal emulator was the IMEI backup I mentioned, it sounds like you did it correctly, if it gets wiped out for whatever reason then you can restore it by typing "reboot nvrestore", it is saved in a safe place on internal that won't get wiped out between flashes and wipes unless you format internal memory, it will be erased if you do that. As long as the only format options you use are to format system and data partitions then you won't have to worry about losing the NV backup, don't format anything other than system and data, do not format internal SD and you'll be fine. If you ever have to restore the NV backup then you'll have to create a new one like the first time because restoring it erases it from where the backup was kept, to stay backed up after restoring you need to make another.

SuperSU won't show as an app, its built in to system settings.

Did you enable root access in system settings>developer options? It has to be set to " apps and adb" or the device will act like it isn't rooted. When you flashed in CWM and rebooted it should have prompted you to "fix root", select yes if it does.

Yes, the 3G disappears when you don't have service and need to renew time on the device.

Here is the TWRP for d2tfnvzw

https://plus.google.com/+DonaldHoskins/posts/FLdc2CkSHRu

Flash it in CWM then go to the advanced options in CWM and select "reboot to recovery" this will boot you straight from CWM into TWRP, then make your backup and youll keep TWRP and wont need CWM, it would be a good idea to restore your stock nandroid in CWM and boot into it then boot back to CWM then flash the TWRP then reboot into it then make a nandroid of your stock in TWRP because TWRP will not restore CWM nandroids, doing what I just instructed allows you to keep TWRP and a stock nandroid that you can actually restore. After getting TWRP and a stock nandroid in TWRP you can delete the CWM backup from your internal SD if you aren't going back to CWM at any time, you won't need it if you do as I instructed.
[Verizon Samsung Galaxy S III] cory733:
thanks for the link and info, ill work on that next. this phone actually never had an IMEI. not even behind the battery. it just has a 2 line section called MEID that shows a Dec and a Hex number. i give one or both of these numbers to straight talk when they activate the phone. (had this phone activated,deactivated and reactivated a couple times)

i had supersu as an app because i installed it from the play store. it was showing before and i use it on my note 2. but now the pop up for granting superuser permission isnt even coming up.

since i cant just switch the sim cards between my two phones, is it even worth putting a verizon rom on my s3? i would still have to call straight talk and have it switched anyway. or is that because the d2lte roms dont work for mms.. is that the only reason to use the verizon roms instead? you said before in pm that if i put my note 2s sim in my s3(after installing verizon rom) that i would have to press *228 to reset the prl. and that might mess it up for the note 2 that im using. would i just have to repeat dialing *228 in my note 2 if i switched the sim back to that one? also i believe you said in a different thread that theres no way to get 4g on these phones? that was also one of my reasons for wanting to put a verizon rom on the s3. basically this phone is a backup that has just become a learning experiment now
[Verizon Samsung Galaxy S III] Droidriven:
I don't know what you've got going on with superSU, does root checker verify you are rooted? If you have root access as normal and everything works then I wouldn't worry about it as long as it works.

Your IMEI should show in system settings>about phone. IMEI has several names: ESN, IMEI and a few more, they are all the same thing, it's what the network uses to identify your device as that particular device and not another. That number is what registers on the network, without it the device is useless, it won't even work on WiFi if its NV bricked.

Dialing *228 on a Verizon SIM ruins it for Verizon, from what I know, it won't work for Verizon after that no matter what you dial. Using the SIM on the ST S3 is only to get signal and data, it doesn't have to be activated by any process, just inserted and OTA programmed in the device. Actually any CDMA SIM works but the Verizon 4G specifically gets the stock MMS working, it even corrects MMS issues on non rooted stock ST S3. The 4G SIM is needed to get the ROMs working because the ROMs are actually built for the Verizon S3 which is a 4G device that requires 4G SIM, that is how Verizon regulates their 4G data, this makes our device require the SIM when running Verizon ROMs, even the d2lte ROMs require SIM because they are built for LTE(4G) devices, hence d2 "lte". The ROMs have to follow their programming, their programming says they must have SIM so a SIM must be used regardless of what the device is.

The 4G was hardware disabled in the device, it can't be re-enabled. This device actually has the Verizon S3's motherboard in it even though it says it is an SCH-S968C, if you open it up and look inside you'll see SCH-I535 stamped in more than one place on the hardware pieces. Its a rebranded Verizon S3 basically with 4G disabled.

Is any of this making any sense yet?

I have a thread that I ran across where a guy used his active Verizon SIM in a ST S3 by going to his verizon user account online and entering the phone info, this is not really a legit way to do it, the network is fooled into thinking one device is the other without the second device actually being legitimately activated on the Verizon network, this is a shady practice and isn't recommended because if the network catches on they'll kill you ESN(IMEI) and the device will be useless and un-repairable. It can be done but isn't worth the risk, I will tell you how to do this, its against the rules on XDA, if you do so then do not come posting here about it no matter what issues you are having, the practice is frowned on around here and most won't help you with it if they are serious about XDA.
[Verizon Samsung Galaxy S III] cory733:
yeah i dont use verizon its just a verizon phone on straight talk.

my copy of the stock rom is this one that im sure youve seen before

COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5

since i couldnt make a copy of my actual stock on my non rooted h2 stock rom.

so youre saying to revert to this before i install twrp? i would install it as a zip and not as a restore correct?
[Verizon Samsung Galaxy S III] Droidriven:
Restore your stock nandroid in CWM, then reboot into system normally, then boot back to CWM and flash the TWRP .zip, then go to advanced options in CWM and select "reboot recovery" it will boot straight to TWRP then you make a nandroid of your stock in TWRP then you don't need CWM or the stock nandroid that was created in CWM.

I'm just trying to explain how to get TWRP and have a stock nandroid in TWRP because the nandroid made in CWM won't work in TWRP, if you're gonna run and keep TWRP then you'll need a stock nandroid to use in TWRP if you ever need it. Otherwise you would have to go back to CWM to restore the stock nandroid that you made in CWM. Doing what I'm saying eliminates the hassle of going back and forth between CWM and TWRP.

If you're already on stock then you don't need to restore the nandroid in CWM, you just need to flash TWRP .zip then reboot to it from within CWM and make a TWRP nandroid and do away with CWM and the nandroid you created in it, your CWM nandroid van be found on your extsd in Clockworkmod/backups folder, just delete the entire Clockworkmod folder.
[Verizon Samsung Galaxy S III] cory733:
kinda forgot about this project for a while but decided to finish it. i installed the version of TWRP you showed me and it and cyanogenmod installed just fine this time. i actually just installed this twrp from twrp itself. tried putting the sim from my note 2 in my s3 just to try. it didnt work. i didnt dial *288 or anything. but i ordered another sim. will see if everything works when i get the sim.

thanks for your help
[Verizon Samsung Galaxy S III] cory733:
maybe spoke too soon. now its not letting me boot into twrp for some reason. even though i already did before and made a backup. i get the blue letters up top saying its booting to recovery but then it just skips it

edit: works when enabling advanced reboot options and rebooting to recovery from phone