yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
There are a few things to look out for. Just re-read the first several posts in both my Q&A and Development threads and at least skim over the last few pages of the Q&A one.
[T-Mobile, Samsung Galaxy SIII] 1milenia:
i think i read it about 3 times,just to no members success in the instal,and how they went about it
[T-Mobile, Samsung Galaxy SIII] DJ_SpaRky:
I you actually research it, I'm sure that you will find that info. I have posted a how to at some point in the past, so look for that.
[JAM, MDA Compact, S100 Software Upgrading] stuhyde:
Evening people, hope uve got a bit of info for me :D

Im getting my MDA Compact tomorrow on TMobile network. Ive already got an O2 contract which I am going to keep on using and the TMobile sim will not be used.

a) Whats the best/cheapest way to get the phone unlocked so I can use my O2 simcard?

b) How do I flash my phone with the latest IMate Jam ROM, Ive read some posts, but it seems a bitawkward to do and I dont want to end up with a broken phone after only a few hours :o

Or do I just stick with the ROM that is on there, but when I boot the phone, I reset it straight after touching the screen to continue on setup?

Any info very very much appreciated!!!

:wink:
[JAM, MDA Compact, S100 Software Upgrading] bobster:
Before you do anything, make sure you make a backup of your MDA as it is. Follow the instructions elsewhere using the d2s procedure to make a backup of your ROM to an SD card, 256MB cards are best and once you have made the backup, use the ntrw tool to copy it to your PC.

You will beed this should you ever return your MDA under warranty !
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Miami_Son:
OK, had the S4A for about a week. Lots to like coming from my S2, but a few niggling things that irk me.The main one is the e-mail app notifications. I had the combined Inbox on my S2, but all it ever showed me on the widget was when there were new e-mails. For some reason, the S4A also combines the new text messages count into the e-mail widget icon making it look as if there are new e-mails. Even if I read the text messages they still pop up in the widget count until I also delete them through the e-mail app. This is annoying as hell, obviously. Is there any way to turn this behavior off? I only want to see a message count on the e-mail widget for actual e-mails. What's the point of having messages show up in the e-mail app? I can't do anything but read and delete them (doesn't delete the actual message, just its appearance in the e-mail app). I still have to go to the messaging app to reply, forward, etc.

The other problem is the e-mail app itself. I have Push turned off and one of my accounts set to manual retrieval. Still, it downloads e-mail without me doing anything. I have to turn off sync completely to stop it, which is a pain as I have to remember to turn it on to retrieve e-mails and then it gets everything going back 24 hours (minimum setting) whether it is new or not. This using an Outlook account. If e-mail retrieval is set to manual why would the phone retrieve e-mails as if set to push? It should do nothing regardless of whether sync is on or not. That's how it worked on my S2.

TIA
[AT&T Samsung Galaxy S 4 Q&A, Help & Troubleshootin] Miami_Son:
Nothing? Could someone just verify that this is the way their S4A works, as well? It just makes no sense to me why it does this.:confused:
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
Hey all, my sister just got a brand new GSII from T-mobile and wants me to put cyanogenmod on there. I saw that the 4.3 was still a bit buggy so I'm going with 10.1 / android 4.2

All of the stickys for rooting are a bit old so I'm not totally confident choosing one without posting first. She's on 4.1.2, what would you guys say is the best route for rooting? the toolkit? the odin way? or the last method. Speaking of which, is this phone T989 or the D?

Looking forward to answers, thanks guys!

PS - Do these rooting methods also unlock the phone?
[T-Mobile Samsung Galaxy S II SGH-T989] Decimus Meridius:
Tmob is the t989, the kodo version is the t989D. I used Odin when I rooted mine a few months ago. I'm also on tomb.
[T-Mobile Samsung Galaxy S II SGH-T989] soupysoup:
The best and only way to go is to Odin the latest twrp tar file onto the device the flash superuser zip of ur choice, once u Odin the recovery to the device though u can just flash the cm zip and gain root that way if u want a custom rom, rooting this phone is very easy its all in the recovery
[T-Mobile Samsung Galaxy S II SGH-T989] Cesar124:
I used Odin and flashed a 4.2 rom, If your looking for a stable rom then just stick to 4.2/4.1.2 roms as 4.3 roms aren't stable enough as a DD and probably won't be for a few weeks/months.
[T-Mobile Samsung Galaxy S II SGH-T989] gabriel1946:
Like others said Odin is the easiest way.. Before this phone I rooted my HTC vivid that dam phone was retarded unlocking it had to connect the ground wire to the positive battery on mother board than sync with the file it was stupid hard compared to this phone
[T-Mobile Samsung Galaxy S II SGH-T989] Sanadrate:
Yeah my amaze was a pima but odin is like key lime pie. Can't go wrong
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
Wow thanks all! Does any of this require of change when you do NOT have an SD card?
[T-Mobile Samsung Galaxy S II SGH-T989] Sanadrate:
I didn't use a sd
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
Ok so I rooted with ODIN and flashed CWM. Made a backup, put CM and Gapps on SD card, factory wipe, dalvik/cache wipe, installed zips, and its stuck in boot loop. What went wrong? How can I stop loop? Remove battery?
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
I also adb pushed the libskia.so file based on some searching and still nothing...

then just tried restoring the backup and that wouldnt work either! going to restore back to stock until hopefully I get some answers :(
[T-Mobile Samsung Galaxy S II SGH-T989] holeindalip:
Did you wipe the system partition too or just a factory reset?
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
just factory I believe, what all the how to's have been saying. Not sure I saw a system reset??
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
wipe data/factory

wipe cache partition

then in advanced we have

wipe dalvik cache

wipe battery stats

thats it for wipes..
[T-Mobile Samsung Galaxy S II SGH-T989] gamzerz:
Don't mean to hijack the thread, but i have the T989D. I was wondering if i can flash the same twrp versions as the t989. And what version of superuser should i get? Also, is twrp2.4 fine for flashing the latest roms (this is the one i have downloaded right now)?

Thanks in advance!
[T-Mobile Samsung Galaxy S II SGH-T989] soupysoup:
If ur using any newer rom besides 4.3 try using twrp older cwm has a problem flashing the newer roms, it doesnt like to load the preload partition so u will end up with boitloops, if u want 4.3 u need the 4.3 recovery, u can find it in the op, just flash in recovery and then reboot to recovery and flash 4.3
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
I have no idea what I'm doing wrong...

Root via Odin, root successful

Flash CWM

wipe every option

install zips from sd (cm10.1 for GS2 Tmob/ and the 10.1 gapps)

reboot, still loops,

push .so, still looping

what else is there?
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
How can I flash a twrp? Do I have to start from the beginning or where?
[T-Mobile Samsung Galaxy S II SGH-T989] soupysoup:
U can go one of two ways, for twrp u can DL the flashable zip and flash it in cwm, or u can use Odin and DL the tar file for the latest twrp and flash it over cwm with Odin, and the 4.3 recovery zip is flashable right through recovery
[T-Mobile Samsung Galaxy S II SGH-T989] holeindalip:
Which cwm are you using?

You have to go to mounts and storage
[T-Mobile Samsung Galaxy S II SGH-T989] father87:
FINALLY!!!!!!!! so much old info on here, should really be redone. It was due to the old recovery, thank you! I woulda never figured that out.

HOW TO ROOT AND FLASH CYANOGENMOD 10.1 TO YOUR TMOB GS2 IN 2013!

Download latest 10.1 ROM and put on your SD card or internal storage

CM10.1 nightly

Download latest Google Apps/Gapps under the 10.1 column and put on your SD card or internal storage

Gapps

Download Odin3-v3.307

Odin3-v3.307.zip

If you're already on Android version 4.1.2 then you're fine, continue below, if not;

Download 4.1.2 stock rom

Tmobile GS2 Stock 4.1.2 ROM

1) “Extract” or “unzip” the downloaded stock ROM to get the .tar.md5 file

2) Run Odin3_v3.07.exe on PC desktop

3) In Odin - only check ‘Auto Reboot’ and ‘F-Reset’

4) Click on the PDA button then browse to the folder where you extracted the stock ROM “tar file”

‘T989UVMC6_T989TMB_T989UVMC6_HOME.tar.md5′

5) Connect USB cord to phone and PC and boot into download mode. In Odin, the ID:COM box will change its color and its an indication that the device is connected properly to PC. If you still do not get any results, try another USB port on your computer.

6) Click the Start button to begin flashing.

7) Wait until it finishes or watch out for the word “PASS”.

Once the phone completely reboots, perform wipe/factory reset to get a fresher firmware installation.

1. Hold Power and Volume Up together, this will switch the device into recovery mode.

2. Release Power after holding it for a second but continue to hold the Volume Up button until recovery menu appears.

Select wipe cache

Select wipe data/factory reset.

Select reboot

That’s all! your Samsung Galaxy S II SGH-T989 now fully installed or restored to the original Android 4.1.2 Jelly bean

Ok, now that you're on 4.1.2, let's continue. The above step is also how to restore the phone back to stock.

Follow this STEP BY STEP noob friendly way to root, using the ODIN v3 provided above

Root Tmob GS2

Flash custom recovery

Download the TWRP recovery mode

TWRP 2.2 for Tmob GS2 aka Hercules recovery.tar.md5

plug phone back into PC and put in download mode

select the pda and select the recovery.tar file, hit start and let it finish

boot into recovery

wipe system, dalvik, cache, etc.

select install

find your cm10.1zip and install

then find your gapps.zip and install

reboot, could take about 2-5 mins.

DONE!
[T-Mobile Samsung Galaxy S II SGH-T989] monkeybuttons:
Nice. Perhaps you should create a new thread in general with this info?

Also, in CWM recovery, the way to wipe system is under "mounts", then you "format /system". There is no "wipe" option for system. It's quite confusing really. TWRP is much easier to use, and as mentioned, CWM must be version 6+ to flash a newer Rom.
[T-Mobile Samsung Galaxy S II SGH-T989] 'Murica:
There is no need for another thread on how to root, this one works 100% on rooting your device. http://xdaforums.com/showthread.php?t=2195283

~~~~~~~~~~~~~~~~~~~~~~~~~

I am here to help and provide knowledge to help others with there problems/issues. If you do have a question don't be afraid to shoot me a PM and I will help you and put you in the right direction to the best of my ability and will Hey your problem and/or issue solved.

~~~~~~~~~~~~~~~~~~~~~~~~~
[T-Mobile Samsung Galaxy S II SGH-T989] holeindalip:
I just want to ask one question, why do you need root to install custom firmware?
[T-Mobile Samsung Galaxy S II SGH-T989] meekrawb:
You do not need to. Not with this phone, anyways.
[T-Mobile Samsung Galaxy S II SGH-T989] holeindalip:
I know, I was just wondering why murica was talking about root??
[Captivate Q&A, Help & Troubleshooting] androidfine16:
hey guys

anyone know a kernel that support new slimbean 4.3 rom that isnt the stock one?
[Captivate Q&A, Help & Troubleshooting] ryankgrant:
Use the search feature.

Doubt there is currently one for the cappy, but if you have brass balls you could always try one out and report your findings. Goodluck.
[Captivate Q&A, Help & Troubleshooting] nespid:
I've tried several official and unofficial semaphore kernels with no luck. Freezes after Att logo.
[Captivate Q&A, Help & Troubleshooting] cannondaleV2000:
Not yet wait a while and il bring maclay kernel to the cappy
[Nexus 7 (2013) Q&A] Marck527:
Hey guys just received my n7 yesterday and am very pleased with this, however I have some questions.

Does rooting (only) removes your OTA updates access? I also own a Galaxy S4 (rooted) and I can't get OTA, it says it's modified, but I did flash a custom update on it and kernel. So if I just root my n7, and not flash anything, I will still get OTA's correct? I just want to use some apps which requires root access and not planning to flash a custom rooms or anything. Thanks for any help.
[Nexus 7 (2013) Q&A] rmm200:
Mine is always rooted, and I get all OTAs.
[Nexus 7 (2013) Q&A] Username invalid:
You just need to have the stock recovery to receive OTAs.
[Nexus 7 (2013) Q&A] timrock:
So if I have twrp installed, i won't receive them?
[Nexus 7 (2013) Q&A] Username invalid:
Takes 10 seconds to reflash the stock recovery.
[Nexus 7 (2013) Q&A] sfhub:
UPDATE: SuperSU-v1.55 added the fix for the OTA update issue, so this post is

no longer necessary

unless you are using an older version of SuperSU

This post also applies to JSS15Q update.

I actually went through and tested JWR66N rooted with SuperSU and the JSS15J OTA update. I expected it to work but it exited with an error.

Ironically the JSS15J OTA actually did patch every single file successfully but near the end while setting permissions, it came up with an error, so after reboot you'll actually be running with all JSS15J rom files, except your build will still say JWR66N, you'll still be running the JWR66N recovery, and you'll still be running the 3.05 bootloader.

I tracked down the issue and put together a fix for it. If you want, it is attached to this post. You just run it after installing SuperSU, so basically:

adb reboot bootloader

fastboot boot twrp.img

within TWRP

install UPDATE-SuperSU-v1.51.zip (SuperSU v1.55 or greater incorporates the OTA fix)

install UPDATE-SuperSU-v1.55.zip

install UPDATE-SuperSU-ota.zip (can be chain installed, just make sure you choose to install it 2nd)

reboot

You'll need to redo these steps (both the installs) after you receive the OTA to preserve root and ability to receive future OTAs.

Also as others have mentioned it is best to be running stock recovery (which the above commands will allow you to do because twrp is never flashed on the tablet) I've attached the stock recovery for JSS15J in case someone needs it.

If you make ANY modifications or delete files from the stock ROM with your new root privileges, then you will greatly increase the chances of the OTA failing. Adding new files is normally fine.
[Nexus 7 (2013) Q&A] rmm200:
Well shoot - now you have me worried. I did install TWRP, but never considered that would block OTAs. Do they attempt to install and fail?
[Nexus 7 (2013) Q&A] sfhub:
On some platforms, especially when flashing bootloaders and/or radios, the stock recovery pulls some funky maneuvers to get that done. Often custom recoveries are not privy to those maneuvers. Also sometimes custom recoveries will experiment with custom kernels which don't always have the bootloader and/or radio devices mapped the same as the stock kernel. This can lead to problems to.

Thus it is safest to use stock recovery to flash OTAs.

I have flashed the complete JSS15J OTA except for the bootloader part using TWRP and it works ok. All the ROM files are patched.

I just didn't feel like risking my tablet with the bootloader flash portion of JSS15J OTA using twrp. It might work fine. I just know from the past the potential for issues are higher in that section of the OTA flash.
[Nexus 7 (2013) Q&A] TheAltruistic:
Is it common for nice folk on here to upload a stock zip of say for example, 4.3.1 when it releases so that we can flash it through a custom recovery (e.g., TWRP, CWM etc.), without having to change our custom recoveries? :confused:
[Nexus 7 (2013) Q&A] sfhub:
It was common on other platforms I've used, but I don't know about here.
[Nexus 7 (2013) Q&A] phazerorg:
Root will not prevent an OTA update from coming in and installing, and a custom recovery won't "block" (it just won't be able to complete the install of it automatically). I have been installing OTA updates on rooted Nexus devices with custom recoveries since the Nexus One, and assuming the new Nexus 7 works the same way, the following applies:

If you are running stock ROM, your deivce will receive the notification and download the update, even if rooted

If you are running stock recovery, the update will install automatically as normal

If you are running a custom recovery like CWM or TWRP, it will fail to install automatically but it will still have downloaded to the device and you can use the custom recovery to install it yourself (I've never had this fail)

If you have modified files in /system, the OTA update is pretty much guaranteed to fail regardless of which recovery you use

If you successfully install the OTA update, you will no longer have root, so flash SuperSU using a custom recovery after the OTA update installs

Also:

You can always look for the OTA zip URLs on XDA and just download the update yourself to flash if you don't want to wait for it to come to your device (this is what I always do)

You can flash factory images instead of the update, without losing data (see other threads for how)

If you want to keep stock recovery installed, you can always use fastboot to boot a custom recovery without flashing it, in case you ever need it

The above is accurate and correct as far as I'm aware from my own experience over the years with Nexus devices. I'm sure someone will be happy to correct me if anything is wrong :) Hope this helps.
[Nexus 7 (2013) Q&A] sfhub:
I thought the same about root not blocking the OTA update install from being successful, but that was with years of using superuser.

With SuperSU (I am not sure which version introduced it) they set the immutable flag on a file in almost every OTA. I believe this is to support some OTA survival mode. This causes the OTA to fail in the section where it sets permissions. All the files are patched at that point, but the build.prop hasn't been modified to reflect the new version # and the bootloader and recovery haven't been flash.

You'll essentially be running JSS15J but your software will report it is on JWR66N, your bootloader wouldn't have been patched, and you would be running JWR66N recovery.
[Nexus 7 (2013) Q&A] nolook:
yes the ota update zip always gets posted so you can manually flash with a custom recovery...

just keep in mind you need to keep your files stock otherwise it might not work

Sent from my Nexus 7 2
[Nexus 7 (2013) Q&A] Mightym83:
When you say keep your files stock what does that mean exactly? I have titanium backup app installed would that be one of them? Thanks.
[Nexus 7 (2013) Q&A] chrismast:
Titanium backup is an app, I assume with files he is targeting e. G. Config files.

Sent from my Nexus 7 (2013)
[Nexus 7 (2013) Q&A] sfhub:
It means don't modify or delete any files in /system

Don't remove a system app that shipped with the tablet. You can install a new version as that just hides the one in /system, but if you remove or modify the original, then the OTA will very likely fail (depending on how complex the OTA is)

Adding files is ok.
[Nexus 7 (2013) Q&A] ScOULaris:
Alright, so here's my scenario. Hopefully someone can tell me what should happen:

I am running the stock ROM on my Nexus 7 (2013), but I have ClockWorkMod Recovery installed and I'm using Koush's Superuser app for root permissions. The only system file that I think I have changed is my hosts file because of Adaway. That is easily reverted, though.

So can I just download the OTA, install it manually from the custom recovery (flashing the update.zip file), and then re-flash Koush's superuser app back onto the device?

Will that go smoothly, and will the newer build number be accurately reflected in my About Phone afterward?

(that last part is just my OCD talking)
[Nexus 7 (2013) Q&A] timrock:
This was very helpful, and this is the category i fall in. However, i have installed a kernel. does that change anything?

So basically what you are saying is this, with my current set up:

1 - i will get the update, it will download, but wont install. I should boot into TWRP and install the file that way. Correct? Where is the downloaded file stores?

2 - I can just wait for the download to be posted on here, and just install via twrp.

3 - either way, after installing it, i will lose root. I should then boot into twrp and flash supersu.

Correct?
[Nexus 7 (2013) Q&A] sfhub:
Theoretically it could work. I believe the flash has worked with twrp.

Personally I always put stock recovery back to flash ota's though especially if there is a bootloader (or radio if you have a mobile version) because on some platforms they involve special procedures that may not be in the custom recovery.

On nexus it looks like it will work with custom recovery but it takes so little effort to put stock recovery back I just do it automatically.

Having said that, I've seen one person post it worked on twrp but haven't read an experience on cwm. Not saying it will or won't work.
[Nexus 7 (2013) Q&A] acdcking12345:
If we are running the stock ROM, but have it rooted with the custom recovery, why cant we just use Wegfresh's nexus toolkit to Unroot and image using the updated IMG file?

Then go through and use it to recreate the root\custom recovery again?
[Nexus 7 (2013) Q&A] sfhub:
I don't use toolkits, but if it has worked for you in the past it will probably work.

I am not sure what you mean by "updated image" though as the latest google releases are usually delivered as ota update.zip
[Nexus 7 (2013) Q&A] Geese1:
I'm in a similar situation. We bought my wife one of the new Nexus 7 models and I rooted it right out of the box before giving it to her so that she wouldn't have to re-setup the whole thing when the device got wiped. However I forgot that there were two initial updates and so I rooted it after only doing the first one. Now it's prompting her to install a new update, but after downloading it reboots into TWRP and I'm not sure what to do from there. I see a number of posts saying to go back to the stock recovery to do the OTA updates, but being a noob when it comes to rooting (our two Nexus 7s are the first devices I've rooted) I'm not sure how exactly to do this, or if it's even necessary.

I figure once I learn how to do this on hers, I'll be all set to update both of ours again once this new update that's just rolling out now gets posted.

Any help would be most appreciated!
[Nexus 7 (2013) Q&A] timrock:
for the time being, until the update is rolled out, i went back to stock recovery. You can do this via Wugs Toolkit, which can be found in the Development section. After installing it, click on Launch, under Advanced Utilities and when the next window pops up, just choose Restore Stock Recovery. If this is your first time do it this way, the app will need to download some files before performing the tasks. Just follow the prompts on the screen.
[Nexus 7 (2013) Q&A] ScOULaris:
I am planning on doing this as well. I should be fine just flashing the stock recovery image file with fastboot, right?
[Nexus 7 (2013) Q&A] timrock:
yes, someone mentioned that ADB is fine.
[Nexus 7 (2013) Q&A] Geese1:
Thanks timrock. Just out of curiosity, is there a guide to the manual way to flash the stock recovery? I rooted the devices manually so as a learning tool I'm wondering if it might be more beneficial to learn how to do this manually as well.

[Edit] - forgot to ask, will going back to the stock recovery partition wipe the device? I really hope not as I'd like to keep all my data intact if possible.
[Nexus 7 (2013) Q&A] timrock:
I rooted mine using the toolkit. But there is a way. I believe it's posted in this thread somewhere. I recently saw it.

No. Going back to stock recovery will not wipe the device.

Here it is. First post has the directions.

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