OK...I've read the Wiki and the Glossary, I've searched the forums, I've been obsessively reading this forum for a week, and I still have some very basic questions that I'm hoping someone can either point me to a link or just drop some info for me. I know many of you have been at this since the Dawn of Android, but sometimes I feel like I'm walking into my first day of med-school when everyone else has been here for 5 years. Assume for a moment that I am a tabula rasa where the rest of you are now writing in the margins of a dense technical manual. Because that's what it feels like for me.
First, some background info: I want to learn how to do all this stuff, but this phone was expensive! I don't want to break it. So I'm cautious. I'm not a programmer but I'm not technically inept. I am good at following directions. I don't panic when things go wrong. So I think I can root, flash, and all the fun stuff that comes with having an Android device. But I have some questions that are still unanswered. I'll try to be as concise as possible (too late, I know):
1) I have the SPH-D720 model. I see rooting guides for the I9020 but not the SPH-D720. Will those other guides work for my device? I've seen other people ask this same question get sent to BuglessPete's guide so I'm assuming so, but I want to be sure.
2) I know that GRJ90 and 2.3.5 just came out. My phone is updated to both. It looks like most of the root guides are still referring to 2.3.4 or 2.3.3. Should I wait until someone releases an updated 2.3.5 guide, or is the method still the same?
3) Backups...these are different than saved settings, yes? So when I root my phone (which apparently requires unlocking the bootloader now) I'm going to lose all of my apps/themes/settings, right?
4) Do any of the developers offer tech support?
I now throw myself to the mercy of the masses, prepared for flames, but hoping for help.
NoobyMcNoob said:
1) I have the SPH-D720 model. I see rooting guides for the I9020 but not the SPH-D720. Will those other guides work for my device? I've seen other people ask this same question get sent to BuglessPete's guide so I'm assuming so, but I want to be sure.
Click to expand...
Click to collapse
It's the same.
- fastboot oem unlock
- flash a custom recovery for your device (crespo4g) using fastboot
- boot into CWM, mount system and flash the su binary
NoobyMcNoob said:
2) I know that GRJ90 and 2.3.5 just came out. My phone is updated to both. It looks like most of the root guides are still referring to 2.3.4 or 2.3.3. Should I wait until someone releases an updated 2.3.5 guide, or is the method still the same?
Click to expand...
Click to collapse
No change unless you are trying to flash a modified boot.img for adb remount (this is not necessary if you merely want root access)
NoobyMcNoob said:
3) Backups...these are different than saved settings, yes? So when I root my phone (which apparently requires unlocking the bootloader now) I'm going to lose all of my apps/themes/settings, right?
Click to expand...
Click to collapse
Yes, fastboot oem unlock wipes everything, including the SD card.
Thanks. So a follow up question then:
Is it possible to back up all of my settings and whatnot, and then quickly put them back after rooting the phone? No biggie if not, and since all of my contact info is on Google that sync happens automatically.
Another question - when I'm installing the sdk, do I need all the other stuff that it automatically selects or can I dump all that and just download the USB driver package?
NoobyMcNoob said:
Another question - when I'm installing the sdk, do I need all the other stuff that it automatically selects or can I dump all that and just download the USB driver package?
Click to expand...
Click to collapse
You will need the usb driver and platform tools.
Sent from my Nexus S using XDA Premium App
NoobyMcNoob said:
Thanks. So a follow up question then:
Is it possible to back up all of my settings and whatnot, and then quickly put them back after rooting the phone? No biggie if not, and since all of my contact info is on Google that sync happens automatically.
Click to expand...
Click to collapse
You could use something like titanium backup, but watch what you restore as some things cause issues.
Sent from my Nexus S using XDA Premium App
Awesome. I'm taking the leap now! So far, nothing screwed up...
So...I can't get the correct driver installed. In all the guides it says I should have the Bootloader Interface listed as the driver. But that is not one of my options - Allgamer's guide says there should be 3 choices, but I only have 2:
Android ADB Interface
and
Android Composite ADB Interface
How do I choose the Bootloader Interface?
You need to be in the bootloader on the phone I believe. I am new to the nexus s so I am not 100 percent sure.
Didn't work from the bootloader either - still showing Android ADB Interface.
I guess I'll uninstall everything and start from scratch.
So I recently got a Xoom and would like to root it. I can easily search through forums and follow instructions, but I want to be sure on what I have to do. I've rooted and flashed several Android devices already, so I'm no newbie, but once I bricked an Atrix so since then I've always been super cautious.
So now.. how do I root and install CWM on the Xoom? It's on 4.0.4 OTA.
Do I have to unlock the bootloader first?
Specific references to threads and step by step instructions preferred. Thank you!
xFrozen said:
So I recently got a Xoom and would like to root it. I can easily search through forums and follow instructions, but I want to be sure on what I have to do. I've rooted and flashed several Android devices already, so I'm no newbie, but once I bricked an Atrix so since then I've always been super cautious.
So now.. how do I root and install CWM on the Xoom? It's on 4.0.4 OTA.
Do I have to unlock the bootloader first?
Specific references to threads and step by step instructions preferred. Thank you!
Click to expand...
Click to collapse
Yes, you will have to unlock first. There's a bit to set up first, but if you read the instructions and get everything you need set up in one place it's pretty easy. Also, it's actually hard to really brick a Xoom. A few have managed but it's not easy.
Try this guide...everything should still work fine, and it explains a lot
http://forum.xda-developers.com/showthread.php?t=1249798
Good luck!
Hello Everyone im new to the boards here
I'm Trying to root my Friends Xoom for him. He told me he already started the process and unlocked stuff but cant flash anything or succesfully root. I dont know what he actually did and to be honest neither does he..... * put a gun in my mouth haha*
So my question is can i just follow the guide posted and start from the very first step and redo everything and still be ok ?? He has it updated to OTA ICS 4.0.4 I found several guides for 4.0.3 but im not sure if those instructions would still work if anyone could clarify this for me i'd greatly appreciate it
okantomi said:
Yes, you will have to unlock first. There's a bit to set up first, but if you read the instructions and get everything you need set up in one place it's pretty easy. Also, it's actually hard to really brick a Xoom. A few have managed but it's not easy.
Try this guide...everything should still work fine, and it explains a lot
http://forum.xda-developers.com/showthread.php?t=1249798
Good luck!
Click to expand...
Click to collapse
Ah, thanks, it worked
Dooms87 said:
Hello Everyone im new to the boards here
I'm Trying to root my Friends Xoom for him. He told me he already started the process and unlocked stuff but cant flash anything or succesfully root. I dont know what he actually did and to be honest neither does he..... * put a gun in my mouth haha*
So my question is can i just follow the guide posted and start from the very first step and redo everything and still be ok ?? He has it updated to OTA ICS 4.0.4 I found several guides for 4.0.3 but im not sure if those instructions would still work if anyone could clarify this for me i'd greatly appreciate it
Click to expand...
Click to collapse
I also had a problem after unlocking. It unlocked fine, but then I couldn't flash CWM through fastboot. My problem was the Application Variable thing, I assume. What I did was go to the platform tools folder (which for me was C:\Program Files (x86)\Android\android-sdk\platform-tools ). I held shift and right clicked Platform Tools, then pressed "open command window here" and then I flashed CWM through fastboot in that window. Just make sure the CWM image is in the Platform Tools folder, along with fastboot.exe.
If you have any issues with that, PM me and I'll try to help.
omg Frozen thank you so most for that post i literally had the same problem CWM would not flash till i did exactly what you said in the last post thank you soo much greatly appreciated
There is one VERY important piece that is left out of most threads.
The newest Xooms that were release overwrite CWM files upon reboot unless you take specific steps to make sure it doesn't... e.g.
have the update.zip you want to use preloaded on the sdcard via pc
or
use a usb with a otg and a version of CWM that can apply update.zip from the USB drive.
Also beware of threads that dont mention what version of the OS they are for. For example its very easy to root your device, but it be on an on 3.x OS and then the OS will update it to 4.04 on the next boot cycle, and wont give you a chance to pick your ROM update. As a result your device is not rooted at this point, and CWM is not installed because you didnt have root in time to move these files:
adb shell mv /system/recovery-from-boot.p.old /system/recovery-from-boot.p
adb shell mv /system/etc/install-recovery.sh.old /system/etc/install-recovery.sh
while in root.
Really sucks.
So in a nutshell those with the latest Xoom tablets that were released, must make sure you find a update.zip that is compatible with ICS 4.04 and then get it to your SDCARD or USB Drive via any method possible - and then flash the right CWM that supports what you want to do, then catch that as it reboots the very first time but pushing the down button and then up button of the volume controls, and then you can install the root (update.zip).... then if all is well you will be able to boot normally, and then go back and get into CWM and install the ROM of your delight.
Experts feel free to chime in so I don't mislead anyone. I wouldn't follow the above advice until an expert puts their AOK on it.
http://forum.xda-developers.com/showthread.php?t=1242241
Any Xoom any update BTW I had my mz601( Telstra ) on offical ics rooted by this method.
Hi everyone, I have a Nexus S from Best Buy on ATT. Right now I'm stuck with 2.3.4 (build gtj61). I'm very new at this but am trying to research how to upgrade to ICS. From what I can figure I can either Flash the full rom to 2.3.6 and wait for the update to hit, or I can fastboot an image to 2.3.6 or 4.0.4.
What I need to know is which option would be easier for a noob and can you help me find a guide to complete the process. So far the best thing I have found is the guide on android addicted.
Even though it may seem pretty comprehensive to some of you, to a complete noob like myself it is very confusing. For example when it says to download the Android usb / adb driver it doesn't really say what to do with it. And the very next step it shows 2 files that it didn't tell me to dl and basically loses me.
Can anyone tell me what is the easiest way to go about this and what exactly I need to do.
Thanks
Dan
No need to keep repeating the four letter word (noob). We've all been there before. My suggestion to you is of course the safest route for any beginner: find the OTA update.zip for 2.3.6 and wait for the phone to prompt you for the ICS update. And while you're enjoying your stock ICS experience, start reading up on bootloader unlocking, rooting and using custom kernel and ROMs so you can make full use of your Google phone.
Hope this helps! Cheers!
Sent from my Nexus S
I got mine back from repair today, and of course, they replaced the perfectly working 4.0.4 with a 2.3.6. The phone automatically started downloading the update a mere minute after booting, so what I'm stumped on is why yours didn't automagically update itself right away.
Maybe you could force an update check by typing *#*#2432546#*#* into the dialer, then checking the System Updates point inside About Phone.
Unlocking and flashing custom ROMs can be fraught with problems, and are not exactly for the faint of heart, given that there is no one-click executable to flash new ROMs like there was for Windows Mobile (my old phone was/is an HTC Universal, running Windows Mobile 6.5. A real fossil...). There are many guides on the forum, most of them stickied, be sure to chew through them, make backups, and pray to your chosen deity when you start typing in ADB
drivers are a HUGE pain. If you do this while running a linux distro (I run ubuntu) you don't need drivers. they are native with linux.
Anyways Linux is great and you should stop using winblows.
welcome!
Sent from my LS670 using XDA
DC80X said:
Hi everyone, I have a Nexus S from Best Buy on ATT. Right now I'm stuck with 2.3.4 (build gtj61). I'm very new at this but am trying to research how to upgrade to ICS. From what I can figure I can either Flash the full rom to 2.3.6 and wait for the update to hit, or I can fastboot an image to 2.3.6 or 4.0.4.
What I need to know is which option would be easier for a noob and can you help me find a guide to complete the process. So far the best thing I have found is the guide on android addicted.
Even though it may seem pretty comprehensive to some of you, to a complete noob like myself it is very confusing. For example when it says to download the Android usb / adb driver it doesn't really say what to do with it. And the very next step it shows 2 files that it didn't tell me to dl and basically loses me.
Can anyone tell me what is the easiest way to go about this and what exactly I need to do.
Thanks
Dan
Click to expand...
Click to collapse
You could always follow the steps in this thread;
http://forum.xda-developers.com/showthread.php?t=1445621
I used the same Method for My GT-I9020T (T-Mobile)
I was on 2.3.6. A month after my wifes phone got the OTA to 4.0.4 I still was on 2.3.6.
I followed the steps in the thread above and did the Up-Grade Myself.
No rooting, No Boot loader un-locking, From stock recovery.
Worked perfectly for me.
Read through that thread above to see what other AT&T users said about this.
Also his XDA threads are no longer being updated so after reading through the posts, go to his new place here:
http://www.randomphantasmagoria.com/firmware/nexus-s/
to see the latest info and files.
good luck.
My T-Mobile phone is this one:
model number: SGH-T959V
firmware: 2.2.1
kernel version 2.6.32.9
build number: FROYO.VUVKD1
My T959V is already unlocked but not rooted. Can I use superoneclick to root it? Everything I have read on this forum refers to FROYO.UVKJ6 - not my version. I want to start slowly with modding, and learn to walk before I run. Assumptions can prove dangerous when modding these Androids. Thanks in advance!
sveris
Yes, you can root with super one click.
Or, you could flash a new kernel that would root for you & give you cwm.
Don't use rom manager on this model.
There was a kernel named bali that gave you overclocked.
http://forum.xda-developers.com/showthread.php?t=1080871
champ1919 said:
Yes, you can root with super one click.
Or, you could flash a new kernel that would root for you & give you cwm.
Don't use rom manager on this model.
There was a kernel named bali that gave you overclocked.
http://forum.xda-developers.com/showthread.php?t=1080871
Click to expand...
Click to collapse
Many thanks for the prompt reply, and the suggestion, too. I'm surprised at how fast someone answered my question, considering the T959V is an older phone. I think I will hold off on the custom kernel with overclocking for right now.
My plan was to first root the phone, get rid of some of the applications that I never use, and proceed from there. I do want to retain a few applications which came with the phone, e.g., basic ones like the browser, news & weather, maps, voice dialer, etc. - just because I am familiar with them. I know I can always replace these with others from the Android Market, but don't want to cripple myself too much immediately.
Can you also recommend a bloatware removal tool that allows me to remove apps one at a time?
Now that I think about it a bit more, will I lose these apps anyway when upgrading to a newer/higher OS? Is there any advantage to trying an older/lower one like Gingerbread first before going to ICS, or should I simply jump over the middle ones and go right to KitKat?
I will search the forum for a thread or guide which compares the features of each OS.
I use titanium backup. The free version would work (pro version is worth it).
Here's an old thread about safe to remove.
http://forum.xda-developers.com/showthread.php?t=1044011
Have fun with trying all the different roms.
Definitely have fun with things. It's a great like phone and nearly impossible to brick permanently. The various "reviews" will always be in reference to what else was out there at the time. Titanium Backup and keeping backups current is a great idea as you get different ROMs.
A lot of the older ROMs were hosted on servers now shut down, but if there is something you're looking for, ask, as someone may have a backup floating around.
---
Posted from whatever phone booted today
jeffsf said:
Definitely have fun with things. It's a great like phone and nearly impossible to brick permanently. The various "reviews" will always be in reference to what else was out there at the time. Titanium Backup and keeping backups current is a great idea as you get different ROMs.
A lot of the older ROMs were hosted on servers now shut down, but if there is something you're looking for, ask, as someone may have a backup floating around.
---
Posted from whatever phone booted today
Click to expand...
Click to collapse
Thanks for your input, Jeff. I did some limited modding with a Motorola phone years ago, but this stuff seems a bit more complex and perhaps more unforgiving re: mistakes.
I definitely see the wisdom to backing up one's phone before beginning, but that alone seems like a daunting task. At least as outlined in some of the guides on this forum. The other thing I've noticed is that while the instructions can be step-by-step and quite complete, the first few steps can create problems.
For example, having the correct Samsung USB drivers installed is emphasized. But, even though I've searched and searched the forums for instructions on how to verify that I have the correct drivers installed, I can't find a thing. My T959V has always worked flawlessly re: its USB connection to my Dell notebook, but I never gave much thought to whether or not the correct Samsung 32-bit drivers were installed. And, does that mean installed on my phone or my notebook - or both? Perhaps I' getting bogged down with the details, but I don't want to end up with a brick!
I'll keep reading all the great info on the forum pages and proceed from there. From my limited info gathering, it would seem that some of the Vibrant ROMs will also work on the T959V. Is that true? I know the two models are actually a bit different.
Backup, for me, means recovery backups and Titanium Backup backups, both copied to another device (in case I wipe my microSD). Not so bad.
USB drives are a PITA under Windows. There isn't a sure-fire way to get the right one installed for Odin / heimdall, which is different than the one for adb on this build, which is different than the one for that build,... I try them out until I get one that works when I have to, but do everything I can on Linux or Mac.
Vibrant ROMs are basically not compatible with the T959V. The hardware is different enough in key places.
---
Posted from whatever phone booted today
champ1919 said:
I use titanium backup. The free version would work (pro version is worth it).
Here's an old thread about safe to remove.
http://forum.xda-developers.com/showthread.php?t=1044011
Have fun with trying all the different roms.
Click to expand...
Click to collapse
I think I'm almost ready to root and upgrade FROYO.VUVKD1 to stock GB 2.3.6, using Superoneclick, but I'm wondering about two things.
One guide method suggests using:
1) Kies mini to first upgrade to stock GB 2.3.6, then,
2) Supermanager to make a backup copy of the EFS folder, and finally,
3) Superoneclick to root the phone.
Another method begins by rooting the phone, then upgrading to stock GB 2.3.6 and offers more than one method to do the upgrade.
Seems I recall reading about disadvantages to using the Samsung Kies mini software, but I don't recall the specifics. So, should I avoid using Kies mini and should I upgrade first or root first? Thanks in advance for any input.
jeffsf said:
Backup, for me, means recovery backups and Titanium Backup backups, both copied to another device (in case I wipe my microSD). Not so bad.
USB drives are a PITA under Windows. There isn't a sure-fire way to get the right one installed for Odin / heimdall, which is different than the one for adb on this build, which is different than the one for that build,... I try them out until I get one that works when I have to, but do everything I can on Linux or Mac.
Vibrant ROMs are basically not compatible with the T959V. The hardware is different enough in key places.
---
Posted from whatever phone booted today
Click to expand...
Click to collapse
I appreciate the caution re: using Vibrant ROMs. I was a bit surprised to see posts in the T959V specific forum about it sometimes being okay to use them. I guess it's like Caveat Emptor, eh? Sometimes they work, but not necessarily on every T959V - even when starting from scratch with a stock ROM backup.
sveris said:
I think I'm almost ready to root and upgrade FROYO.VUVKD1 to stock GB 2.3.6, using Superoneclick, but I'm wondering about two things.
One guide method suggests using:
1) Kies mini to first upgrade to stock GB 2.3.6, then,
2) Supermanager to make a backup copy of the EFS folder, and finally,
3) Superoneclick to root the phone.
Another method begins by rooting the phone, then upgrading to stock GB 2.3.6 and offers more than one method to do the upgrade.
Seems I recall reading about disadvantages to using the Samsung Kies mini software, but I don't recall the specifics. So, should I avoid using Kies mini and should I upgrade first or root first? Thanks in advance for any input.
Click to expand...
Click to collapse
If you're going to upgrade to Gingerbread 2.3.6, you should give lumin's guide a shot since that's the best method to use in case you soft-brick your phone.
http://forum.xda-developers.com/showthread.php?t=1470716
That will get you a completely stock 2.3.6 rom. I don't recall if you can successfully root 2.3.6 with superone click though, but there are a lot more rooted gingerbread kernels out there that will be useful to you.
I recommend the blastoff kernel by @bhundven since he knows his stuff. I'm not biased 'cause we were both in Team Acid
http://forum.xda-developers.com/showthread.php?t=1828171
FBis251 said:
If you're going to upgrade to Gingerbread 2.3.6, you should give lumin's guide a shot since that's the best method to use in case you soft-brick your phone.
http://forum.xda-developers.com/showthread.php?t=1470716
That will get you a completely stock 2.3.6 rom. I don't recall if you can successfully root 2.3.6 with superone click though, but there are a lot more rooted gingerbread kernels out there that will be useful to you.
I recommend the blastoff kernel by @bhundven since he knows his stuff. I'm not biased 'cause we were both in Team Acid
http://forum.xda-developers.com/showthread.php?t=1828171
Click to expand...
Click to collapse
Actually, lumin's guide is the one I was referencing when I posted those instructions. But, he didn't mention any issue about using Kies mini or that its use might limit future modding. I guess I'll keep searching the forums for more advice or a definitive answer. And I'll take a look at the description of the blastoff kernel you recommended.
Thanks again for taking the time.
Heimdall (the one clicks) and odin (kies) drivers will clash. You'll need to decide which method you will want to use (or use different usb ports for each method). Being new, I would suggest the one clicks for you.
Unless you wish to have the official, official release, there isn't really a need to go kies route imo. The one clicks are the same.
champ1919 said:
Heimdall (the one clicks) and odin (kies) drivers will clash. You'll need to decide which method you will want to use (or use different usb ports for each method). Being new, I would suggest the one clicks for you.
Unless you wish to have the official, official release, there isn't really a need to go kies route imo. The one clicks are the same.
Click to expand...
Click to collapse
Thanks for reminding me about the clash potential. But now I'm getting confused again. Lumin's guide suggested the following:
1) Kies mini to first upgrade to stock GB 2.3.6, then,
2) Supermanager to make a backup copy of the EFS folder, and finally,
3) Superoneclick to root the phone.
Would this be mixing and matching like you said, or am I missing something?
sveris said:
Thanks for reminding me about the clash potential. But now I'm getting confused again. Lumin's guide suggested the following:
1) Kies mini to first upgrade to stock GB 2.3.6, then,
2) Supermanager to make a backup copy of the EFS folder, and finally,
3) Superoneclick to root the phone.
Would this be mixing and matching like you said, or am I missing something?
Click to expand...
Click to collapse
The "problem" is that you want Froyo. You'll be stuck with basically three-year old tools. Froyo was incredibly painful to use, even compared with Gingerbread. There wasn't much of a demand to "go back to Froyo" once the stock Gingerbread upgrades hit people's phones. Edit -- Looks like there is a heimdall one-click for Froyo, thanks to @FBis251 http://forum.xda-developers.com/showpost.php?p=50931923&postcount=10
In my opinion, just go straight to stock Gingerbread. It shipped that way or OTA upgraded to it for most of the phone's life (until Apple sued Samsung and got it pulled from retail).
This is the thread you should be following for Gingerbread or later: http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
jeffsf said:
The "problem" is that you want Froyo. You'll be stuck with basically three-year old tools. Froyo was incredibly painful to use, even compared with Gingerbread. There wasn't much of a demand to "go back to Froyo" once the stock Gingerbread upgrades hit people's phones. Edit -- Looks like there is a heimdall one-click for Froyo, thanks to @FBis251 http://forum.xda-developers.com/showpost.php?p=50931923&postcount=10
In my opinion, just go straight to stock Gingerbread. It shipped that way or OTA upgraded to it for most of the phone's life (until Apple sued Samsung and got it pulled from retail).
This is the thread you should be following for Gingerbread or later: http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Click to expand...
Click to collapse
Well, you may have convinced me to upgrade directly to GB 2.6.3. Just a couple more questions and I'll be ready to take the plunge.
Will the upgrade lock my unlocked phone - back to T-Mobile? I'm on another carrier now. Other than that, I think I'm prepared.
I installed Supermanager and made a backup copy of the efs folder on my T959V, then copied it to the SD card and also to my PC. But, just when I decided to upgrade using Kies mini, I believe I found another contradiction.
In lumin’s guide, he says to do the following:
• - Download Kies mini if you do not already have it. When you follow this link you will see two tabs - 'Manuals' and 'Software ' - click [Software] and download.
• - Make sure your phone is charged.
• - Double check that USB Debugging is not enabled. Go to [Settings] > [Applications] > [Development] and UN-Check [USB debugging].
• - Start Kies mini on the computer.
• - Make sure phone is not connected to computer yet.
• - In USB Settings on my phone I select [Kies (Firmware update)] if it is not set to ask every time.
• - Plugged in phone, let device drivers install on computer. You will see a notification on your computer when complete.
• - Then Kies mini will recognize the phone.
• - Hit [upgrade] and wait.
• - Phone will eventually reboot. Check your IMEI.
I interpret that to mean – according to lumin’s guide - that USB debugging should NOT be enabled.
However, from the T-Mobile Support website, this link, http://support.t-mobile.com/docs/DOC-1810 it says:
Prepare the Samsung Galaxy S 4G
1. From the Android home screen, press the Menu key and tap Settings.
2. Tap Applications.
3. Tap USB settings.
4. Tap Ask on connection.
5. Tap the Escape key once to go back to the Applications menu.
6. Tap Development.
7. Tap USB Debugging.
8. Tap the Home key to exit the settings menu.
9. Insert the USB data cable into the phone and then into an available port on the computer.
10. Select Samsung Kies at the phone prompt. The PC should recognize several devices and begin installation. This is normal and may take a few minutes. Unplug the data cable when completed.
I interpret that to mean – at least according to T-Mobile Support for the T959V - that USB debugging SHOULD be enabled.
So, which is correc: enable or disable USB debugging modet? Do I need a remedial reading course? Or, is lumin saying the same thing as T-Mobile, but in a different order? After reviewing both sets of instructions several times, this is what I think is the situation. Lumin first turns off USB debugging and instead of selecting Ask on connect for basic USB settings, he then selects the Kies firmware update option. However, T-Mobile Support instructs the user to select the Ask on connection option, first, followed by ENABLING the USB debugging function.
Does that mean either method works, just getting from point A to point B by taking different paths?
OK, heimdall will basically reset your phone to stock if you mess up.
Once a phone is carrier unlocked, it is carried unlocked (unless you restore a pre-unlock efs, which isn't something that is likely to happen inadvertently).
That said, you either should try something or decide that you are too risk-adverse for flashing and especially rooting a phone.
Again, heimdall one-click is probably the most robust way to get there
---
Posted from whatever phone booted today
Decided to follow the instructions in lumin's guide to do the GB upgrade - rather than the ones from T-Mobile Support. It worked like a charm. All is well for now. Will check everything for a few days before rooting and removing bloatware. Thanks again to all for advice, recommendations, links, and guidance.
Glad you're able to enjoy an upgraded phone!
---
Posted from whatever phone booted today
sveris said:
Decided to follow the instructions in lumin's guide to do the GB upgrade - rather than the ones from T-Mobile Support. It worked like a charm. All is well for now. Will check everything for a few days before rooting and removing bloatware. Thanks again to all for advice, recommendations, links, and guidance.
Click to expand...
Click to collapse
If you'd like to debloat your phone, I made a site that lets you download a zip file that will do the debloating for you. All you need to do is pick which apps you'd like removed, then flash the zip.
http://teamacid.sourceforge.net/debloater/
Enjoy!
PS: You'll need a custom kernel and recovery to flash the zip.
I'll keep that in mind. Still want to check out everything for a few days, since I've noticed a few minor differences after the upgrade.
I just made another backup copy of the efs folder, and noticed something I did not expect. The copy I made when the phone was on Froyo looks empty, while the one for GB 2.6.3 is definitely not empty.
Froyo efs - 0 files - folders
GB 2.6.3 efs - updated file system plus 3 folders - root, .android, and imei
Did I do something wrong the first time I backed up the efs folder while running Froyo? Does it matter, now that the phone is running GB 2.6.3?
I have a VZW GS3 - the I535 model - which I rooted well over a year ago and flashed with a fairly stock-like 4.1.1-based ROM. I would like to wipe the device and put on a fresh ROM (also preferably somewhat stock-ish, as I use the Google apps a lot), for a few reasons:
1. Every 5 days, I get a prompt to install a Verizon security update. Obviously, this is pretty annoying after over 1 1/2 years.
2. The phone has generally slowed down quite a bit, eats up more battery than ever, etc.
I have tried to navigate the sticky threads and figure out my best option. Obviously not opposed to going to a 4.2.x, 4.3.x, or 4.4.x-based ROM as long as it's possible without bricking the phone. So... where do I start? Where do I finish? I'm not an idiot, but I rooted the first time using the very easy-to-follow instructions in this thread and never really learned the nuts and bolts of it: http://forum.xda-developers.com/showthread.php?t=2046439
Thanks!
ncscotts said:
I have a VZW GS3 - the I535 model - which I rooted well over a year ago and flashed with a fairly stock-like 4.1.1-based ROM. I would like to wipe the device and put on a fresh ROM (also preferably somewhat stock-ish, as I use the Google apps a lot), for a few reasons:
1. Every 5 days, I get a prompt to install a Verizon security update. Obviously, this is pretty annoying after over 1 1/2 years.
2. The phone has generally slowed down quite a bit, eats up more battery than ever, etc.
I have tried to navigate the sticky threads and figure out my best option. Obviously not opposed to going to a 4.2.x, 4.3.x, or 4.4.x-based ROM as long as it's possible without bricking the phone. So... where do I start? Where do I finish? I'm not an idiot, but I rooted the first time using the very easy-to-follow instructions in this thread and never really learned the nuts and bolts of it: http://forum.xda-developers.com/showthread.php?t=2046439
Thanks!
Click to expand...
Click to collapse
Your already rooted? You can first of all disable that stupid notification for the update crap. It's a matter of going into the system files and removing or renaming two different files.
As far as roms as long as you follow the instructions you won't brick your phone, however ignoring one step will cause major issues, feel free to ask away
From my CM11 S3
Thank you. It was indeed easier than I thought. Ultimately, all I had to do was copy the zip file(s) to my SD card and flash them via TWRP (already installed on my phone, as it was already rooted). Now, I figured this out after multiple hours trying to will the "adb" command into submission and unnecessarily installing Google Android development tools on my PC... then wondering why the gapps zip kept failing.
So, anyway, my phone is running smooth as silk on CyanogenMod 10.2 now with the CORRECT associated version of gapps. I only wasted one evening in figuring it out.
ncscotts said:
Thank you. It was indeed easier than I thought. Ultimately, all I had to do was copy the zip file(s) to my SD card and flash them via TWRP (already installed on my phone, as it was already rooted). Now, I figured this out after multiple hours trying to will the "adb" command into submission and unnecessarily installing Google Android development tools on my PC... then wondering why the gapps zip kept failing.
So, anyway, my phone is running smooth as silk on CyanogenMod 10.2 now with the CORRECT associated version of gapps. I only wasted one evening in figuring it out.
Click to expand...
Click to collapse
if you havent already i would back up your IMEI. guide on how to do it here: http://forum.xda-developers.com/showthread.php?t=1852255