[Q] Rooting FROYO.VUVKD1 with Superoneclick - Samsung Galaxy S (4G Model)

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?

Related

[Q] POLL: BEST way to root, ROMS, Q about factory reset

Hi everyone,
Noob here, looking for some phone specific info. After extensive research I have not found exactly what I'm looking for thus the reason for this post. Thanks in advance.
I'm looking for help finding the safest, simplest, most reliable way to root my 959v. I want to root so that I can a) delete preloaded browser bookmarks b) delete preloaded bloatware c) file share with my PC over WIFI (with Samba?) and d) block pop up ads (adfree). I need to be able to undo this in case of a warranty issue and I don't want to lose any of the function of the phone (i.e. front face camera, contacts sync, wifi).
Couple questions: Will factory reset take care of the bloatware and bookmarks?
Also, has anyone found a way to put a 4g toggle switch icon, like the power bar that comes with the phone, or do I need a new ROM to do this, and what does everyone recommend as for an O.S. / ROM. Thanks!
Firmware: 2.2.1
Kernel: 2.6.32.9
Build: FROYO.VUVKD1
i would suggest you flash ravers odin kj6 rom. then flash drhonks kj1 kernel with odin too in order to root it. both go in pda section. then flash through cwm soma's simplysimple rom wich is debloated or just use titanium backup to remove bloat from your rooted stock kj6.
I consider myself pretty technical but I don't completely understand Roms and kernels. By flashing a ROM, are you changing the OS and/or GUI? Does it overwrite the old OS or just make an amendment to it? Will any old Roms be left taking up useless space in memory? What about kernels? Thanks,,
Joe
Flashing a new rom is like re-installing windows on a PC. you need to backup your data before you flash.
The best way to root, is to either use ODIN to flash a new kernel that already had root (doesn't replace the whole rom), or use the latest superoneclick to root. Rooting does not erase your data. Then you can use a program like titanium backup to remove bloatware.
check out the dev form, and look for the bible thread, there are links to roms and guides on how to safely flash your phone. You are going to have to read up a bit to become familiar with how this phone works.
good luck.
Normally, I follow FB's ext4 guide.
But since my phone has been UnBrickable Modded, I've made a kj6 Back-To-Stock One-Click. This oneclick will basically get your phone to where it would be if you got your phone new with kj6 preloaded. RaverX3X tested for me, so I know it works well. After you run the one-click, odin kj1 from drhonk or extract the zImage and Heimdall it to KERNEL and RECOVERY partitions.
If you run the One-Click a second time, you will also get the right bootloaders for GB.
What if I have the KD1? What is all this KJ6/KJ1 about? Do I have to find and manually reinstall drivers for my device? Does a ROM need to be compatible with a Kernel or vice versa? How do I know what ROMS/Kernels will work with my device?
Farlander said:
What if I have the KD1? What is all this KJ6/KJ1 about? Do I have to find and manually reinstall drivers for my device? Does a ROM need to be compatible with a Kernel or vice versa? How do I know what ROMS/Kernels will work with my device?
Click to expand...
Click to collapse
Well, KJ6 was just released (leaks and source).
KJ1 (kernel) was the last voodoo kernel that drhonk made.
There isn't a KJ6 voodoo kernel, yet.
KD1 is Froyo.
Drivers... If the drivers you have now work, then don't change them
The roms and kernels we are all talking about will work with your device, because they are modified leaks for your device.
Just don't go off flashing stuff from other device forums. That is stupid.
You're basically safe if you mix froyo kernels with froyo roms, and gingerbread kernels with gingerbread roms.
Ok thanks a lot that I can understand. I'll need to brush up on differences between gingerbraed vs. froyo, and whether or not ice cream sandwich is going to be worth the headache. I'm actually happy with the stock rom, it's just that I hate bloatware, and any spy programs, and I want total control over my file access, wifi file sharing, bookmarks/etc. So really all I need to do is root the phone, I was thinking of superoneclick, but I'm not sure the device is supported.
Okay. You NEED to READ. Really dont know if SuperOneClick works with our phone? Come on. Do some research first.
There's a lot of techno jargon babble out there I'm trying to sort through, I'm not 100% literate on everything smartphone yet. When you flash a new kernel, say, KJ6, what happens to your applications? In a windows system they would stop working, but their data files would still exist. Are programs unchanged, do they leave useless data files, or can they somehow be reactivated, like the installer package and the data are in the same folder, just need a little help filling in the blanks Thanks
I know how you feel, but there is not "do it just like this and you will get this result," because development has been fast and furious, even a little ad hoc. The Bible is useful to a point, but in the end you are just going to have to read and cautiously test. If you stick with stock KJ6, your phone should work as intended. If you move to a custom ROM, some things may be buggy and other things may work even better than stock. For instance, battery life is improved via a couple roms I have tried, but wifi (dynamic dhcp) suffers. You just have to proceeed CAUTIOUSLY. Tha's the best advice I can offer.
Farlander said:
There's a lot of techno jargon babble out there I'm trying to sort through, I'm not 100% literate on everything smartphone yet. When you flash a new kernel, say, KJ6, what happens to your applications? In a windows system they would stop working, but their data files would still exist. Are programs unchanged, do they leave useless data files, or can they somehow be reactivated, like the installer package and the data are in the same folder, just need a little help filling in the blanks Thanks
Click to expand...
Click to collapse
If you are looking to JUST ROOT your SGS4G then I would recommend SuperOneClick. Version 2.2 worked for me running stock 2.3.6.
I'm rooting my phone as we speak using superoneclick 1.6.5 shortfuse. I enabled usb debugging, download samsung drivers to pc, installed drivers to pc, then started superoneclick and plugged in the phone. Clicked rageagainstthecage, "ROOT", then after about 10 minutes my girlfriend called me, which I had to answer, only to find out that she was breaking up with me, then it got to the part where it says "running rageagainstthecage" and now it's basically frozen after 30 minutes, superoneclick icon saying "(Not Responding)" Great...
Update: No combination of rebooting and rageagainstthecage was compatible with my device/os/version of superoneclick. I used SuperOneClick 1.6.5, my OS is stock 2.2 froyo, and the with usb debugging enabled, it froze every time. Using psneuter, it worked ok, the superuser icon is there... so, for a test. I went to the browser, still cannot delete those annoying bookmarks. Ok, so now to try and delete some bloatware.... still cannot delete any factory installed programs. So, that seems a bit pointless, I'm going to play with wifi filesharing, file explorer, and see what I can access, will report back.
My ultimate goal is to have a fast as **** phone, complete functionality, no bloatware, all custom apps, I want to be able to shortucut ANYTHING to the desktop, especially a 4g toggle switch. How close am I? So far the phone runs a lot slower than before I rooted.
<< Another wierd glitch, when I went to the market without rebooting the phone first, the screen went black, it vibrated in sets of 3 pulses, and I had to hard power down to reset. Went back to market and problem did not reoccur>>
Ok so I installed Titanium Backup, umm yay now for some fun, started deleting everything that didn't look familiar including those pesky sec.android.acore.blahblahblah and now my phone does that 3 vibe thing and I have to reboot. Ok so next chore is reflashing the rom I guess....
Glad you got it working... ummm, sort of?
From what I understand about where you are, I would
1. Use odin 1.8.5 to flash KJ6 stock.
2. Let it reboot and do its thing for a bit (say, 5 minutes?)
3. Check to see if everything is working, stock--4g, wifi, browser, market etc.
4. Use SuperOneClick 2.2 (after setting usb debug in settings-->applications) to root. May take a few tense minutes, but it works. Least it did for me.
5. Load your titanium and uninstall stock apps as you desire.
6. Get a full charge and calibrate your battery.
7. Lust after the roms (especially the great looking 2.3.5 based one by Raverx3x) that require CWM, but cry over your fear of a no-stock recovery.
Should get you where you want to go.
Farlander said:
Ok so I installed Titanium Backup, umm yay now for some fun, started deleting everything that didn't look familiar including those pesky sec.android.acore.blahblahblah and now my phone does that 3 vibe thing and I have to reboot. Ok so next chore is reflashing the rom I guess....
Click to expand...
Click to collapse
Well, I'm officially the master of this sheeet box. DAAAAANG SKIIPPPY FOLKS I had a soft brick condition, didn't know what the f to do, started getting lost on google and good old you tube led me home, can you believe I was bout to cut my usb wire to make a jig no no no not necessary, just hold both volume button and plug in usb, it goes to download mode. Next I couldn't get odin to recognize the phone but eventually went straight to pc (not through my usb hub) and it popped up, I flased the zip of the closest thing I could find to my stock 2.2 froyo, now I have KB5, kernel 2.6.32.9 wtf wow it almost the same but noticeably different, the settings menu is different, it came pre-rooted, but video skype works perfectly and on front facing camera booyah
been fun fellas talk again soon
I am glad you are where you want to be, but DUDE! I assumed you knew how to get into download mode up vol+down vol+plug in usb. Jeeez! That's frickin' basic! Anyway, glad you're sailing. You should be able to Odin 2.3.6 and root it with SuperOneClick 2.2 now, if you want. I am still trying to get upo the nerve to load CWM and try Raverx3x's Octane. It's a downgrade from 2.3.6, but the screenshots look tasty!
Farlander said:
Well, I'm officially the master of this sheeet box. DAAAAANG SKIIPPPY FOLKS I had a soft brick condition, didn't know what the f to do, started getting lost on google and good old you tube led me home, can you believe I was bout to cut my usb wire to make a jig no no no not necessary, just hold both volume button and plug in usb, it goes to download mode. Next I couldn't get odin to recognize the phone but eventually went straight to pc (not through my usb hub) and it popped up, I flased the zip of the closest thing I could find to my stock 2.2 froyo, now I have KB5, kernel 2.6.32.9 wtf wow it almost the same but noticeably different, the settings menu is different, it came pre-rooted, but video skype works perfectly and on front facing camera booyah
been fun fellas talk again soon
Click to expand...
Click to collapse
Really wtf. Download phone drivers, Odin program, Ravers Odin Kj6 ROM and drhonk KJ1 kernel. You need nothing else.
SOC 2.x
How many times and in how many (slightly) different ways can one say the same damn thing? If he has flashed KJ6 already and wants to keep that kernel, then I still say SuperOneClick 2.2 will root his device. Am I wrong? Why do people keep using SOC 1.x then complain about not getting it to root their gb 2.3.6 successfully?
SOC 2.x...use it!
http://shortfuse.org/
chris31jct said:
Really wtf. Download phone drivers, Odin program, Ravers Odin Kj6 ROM and drhonk KJ1 kernel. You need nothing else.
Click to expand...
Click to collapse

[GUIDE] Getting Started With Your G2x

Yes, this guide is outdated a bit. I lost my job and in between school, 3 kids, and writing resumes, I do not have the time to do the proper research and update this. I apologize for my desertion, however, if anyone would like to take it over, feel free to copy/paste the contents of this post and repost, update, and request a sticky from the mods.
Disclaimer
If you have an LG P999 (Not the P990!) you should not brick while using this guide. If you do happen to brick your device, I will not accept responsibility for it. Nor will I support you. There is more than enough information in our section to fully troubleshoot almost any known problem. If I link to a thread, please read AT LEAST the original post (OP) in its entirety before taking the steps it contains. If a method I linked does not work, please let me know. I don’t have the time to read every post on every thread on every section.
This guide is for Windows users only. If you are on a Mac or Linux box, there may be ways of doing this, but I don’t have any way of testing it. You’re on your own.
Purpose
So you just got the LG P999 (T-Mobile G2x or Wind O2x) or you’ve had it for a while and finally decided to root it. This is an updated step-by-step guide on what you need to do in order to unleash your device.
Credit
Thank you to all of the developers and scripters out there. I didn’t do any of the work and I claim no rights to anything linked in this guide.
Thanks to:
KiNG OMaR
jboxer
Volk
kairi_zeroblade
Mr Rusty
phburks
All the other people who contributed to all of these methods.
Anyone who spends their free time coding, modding, troubleshooting, helping, and a special thanks to anyone who does his or her research.
General Information
This guide assumes you’ve had your phone long enough to have gotten T-Mobile’s 2.3.3 Gingerbread update by now. If you’re on 2.2.2 Froyo, search on how to update to 2.3.3 Gingerbread as it will upgrade (maybe?) your radio as well.
If you are an advanced user and coming from a different phone and are used to different practices, let me break it down for you. The bootloader and radio are already unlocked (or S-OFF, if you will). There are only 2 radios which may actually be exactly the same, but they are not flashable zips. All ROMs are compatible with either radio.
All links are tested and up-to-date as of 11 April 2012.
Step 1: CWM
Install ClockworkMod Recovery (CWM) via NVFlash. This should always be your first step no matter what you intend to do with your device. Installing CWM will allow you to flash roms, kernels, etc., as well as recover from minor bricks or bad flashes. DO NOT install CWM via Rom Manager. The following thread will help you install NVidia's APX drivers and flash CWM via NVFlash:
[RECOVERY]CWM-Based Recovery 5.0.2.8 For P999(Internal & External SD)
After completing this step, you will be able to access CWM at any time from a power off state by holding the Power and Volume Down buttons until the white “LG” logo goes away and the blue “LG” logo appears. Release the buttons when you see the blue "LG" logo and wait for the CWM menu to pop up. I recommend at this point that you test it out to make sure it works and that you perform a backup with CWM. Once backed up, copy it to your computer, burn it to a CD, archive it on your tape drive, whatever. It’s just good practice to keep these things in case someone’s link goes down and you really needed that file to return to stock.
Step 2: Decision
Here, you will make a decision:
Are there any apps that you need to save your progress in (for example, Angry Birds scores, etc.) and can’t simply be reinstalled?
If no, skip to Step 4: Flash
If yes, proceed with Step 3: Root
Step 3: Root & Backup
I know, I know. There are apps that can backup your angry birds scores and all that, but this makes reinstalling all of your apps easier. First, you need to download an app to backup your apps. Titanium Backup is my favorite. The price tag seems a little high at first glance, but it’s worth it, especially if you plan on doing this to other phones in the future. Download Titanium Backup from the market, and purchase the PRO key. If you want to go the cheap route, there are alternatives. Next, we need root access. Achieve this by following this post:
[ROOT] G2X Gingerbread 2.3.3. stock ROM with flashable zip in Clockworkmod Recovery
You have a rooted phone and Titanium Backup now. Open Titanium Backup and allow it root access. Press menu, then “batch” and backup user apps only. Never backup system data. You will only get yelled at when people find out that you backup system data.
Step 4: Wipe & Flash
Select a ROM. There are many to choose from (stock Gingerbread, AOSP-based Gingerbread, AOSP-based Ice Cream Sandwich, MIUI). If you’re not sure what you’re looking at, flash one from each category and play with it for 30 minutes to make a final decision. Please read the OP for the ROM you are flashing and follow their directions. If it is not based on the stock ROM, you will need to flash a zip that contains Google’s Apps (gapps). Read your ROM’s OP for the details on this.
When you flash a new ROM, at a minimum, perform the “Wipe Data/Factory Reset” in CWM just prior to flashing the ROM. This will clear old data and cache. I recommend using:
[TOOL] G2x Nullifier [UPDATED!] 26 March Cache only Nullifier!
The dual wipe nullifier is in my opinion, not needed. Single wipe will be fine. Keep in mind, once you nullify, you need to flash a ROM immediately after you nullify! If you reboot after nullifying, you have a soft-brick that should be recoverable, but that’s extra grief you don’t need. So, again, make sure you have a ROM ready to flash on your SD card BEFORE you use the Nullifier.
Step 5: Restore & Enjoy
If you backed up your apps in Step 3: Root & Backup, open up the Market and redownload Titanium Backup and the PRO key (or whatever cheap alternative you decide on) and start it up, granting root access. Press menu, “batch” and restore missing apps with data.
All done! If you want to underclock or overclock or flash kernels, you need to read up on it. They will not be included in this guide.
I am open to *constructive* feedback. If your feedback is “this guide sucks,” move on. I don’t need you here. If you have a legitimate problem with the contents and maybe a suggestion on how to fix it, by all means, let me know. I know there are a couple guides out there, but some are outdated. Just putting a fresh one up for those just joining the game.
I don’t ask for donations. Save them for the people who do the real work. If I helped you out, just hit the thanks button.
Very simple and easy guide, nicley done
Sent from my LG-P999 using xda premium
Awesome Guide. I was thinking of doing something like that for noobs like me. You can include OC/UV guide from Klatmon
http://forum.xda-developers.com/showthread.php?t=1558080
Its a great guide. Plus you will have a complete G2x guide for dummies after this as Step 6 (optional) .
Great guide, only issue is in step 3 you say to gain root. The way we gain root is to flash a rom that already has it. I would recommend backing up data before that point us possible (i don't remember if backup apps can be run without root)
And, you might want to link to http://forum.xda-developers.com/showthread.php?p=24087341 thread for the cwm flashing, it's one file to download and one thing to run, helluva lot simpler for a first timer
Also, pm a mod and ask if you can get this stickied. We need something like this up top
Sent from my LG-P999 using Tapatalk 2
cricketAC said:
Awesome Guide. I was thinking of doing something like that for noobs like me. You can include OC/UV guide from Klatmon
http://forum.xda-developers.com/showthread.php?t=1558080
Its a great guide. Plus you will have a complete G2x guide for dummies after this as Step 6 (optional) .
Click to expand...
Click to collapse
Yeah, my original thought was that the oc/uv guide was a little advanced for the level of the guide. I think I will add it though, thanks for the tip!
Klathmon said:
Great guide, only issue is in step 3 you say to gain root. The way we gain root is to flash a rom that already has it. I would recommend backing up data before that point us possible (i don't remember if backup apps can be run without root)
And, you might want to link to http://forum.xda-developers.com/showthread.php?p=24087341 thread for the cwm flashing, it's one file to download and one thing to run, helluva lot simpler for a first timer
Also, pm a mod and ask if you can get this stickied. We need something like this up top
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
The root method I linked to is merely a flashable zip with superuser. It keeps the current rom but adds root access so that people can back up their stuff prior to flashing.
I will add the easy flash for cwm for sure though. Thanks for the feedback!
r4d14n7 said:
Yeah, my original thought was that the oc/uv guide was a little advanced for the level of the guide. I think I will add it though, thanks for the tip!
The root method I linked to is merely a flashable zip with superuser. It keeps the current rom but adds root access so that people can back up their stuff prior to flashing.
I will add the easy flash for cwm for sure though. Thanks for the feedback!
Click to expand...
Click to collapse
Lol my bad i didnt even read the link
Sent from my LG-P999 using Tapatalk 2
Don't we also have the option to create an update.zip from TBuPRO to reinstall all previous apps from within recovery??? I have read about it but never done it. And thanks for this great tut.
harrytorta said:
Don't we also have the option to create an update.zip from TBuPRO to reinstall all previous apps from within recovery??? I have read about it but never done it. And thanks for this great tut.
Click to expand...
Click to collapse
i would highly advise against this...
doing that across roms of the same version is risky, doing it across roms of different versions is down-right mad. it just plops them back into the rom pre-installed with data and everything, bad bad bad idea.
I tried searching about it on google but found nothing so thanks for the reply. Kinda sucks that it would muck with things though :\
I've never done it either. It's tempting to "flash" your old apps back over, especially with the amount of time it takes for Titanium Backup to run, but as Klathmon stated, it's probably a bad idea. Patience is a virtue, I suppose.
Very easy guide for noobs like me, I have a problem my phone shows p999 in about phone and its have a logo of videotron. but the sticker at the back cover shows p990 :S should i go with p999 method ??
Hasooboy said:
Very easy guide for noobs like me, I have a problem my phone shows p999 in about phone and its have a logo of videotron. but the sticker at the back cover shows p990 :S should i go with p999 method ??
Click to expand...
Click to collapse
That's an interesting situation. I would install the LGMobile Support Tool and see what model it says you have. If I had to *guess* it's a P999 but you should definitely contact one of the other Videotron users and ask them. That is beyond my scope of knowledge, so proceed with caution!
r4d14n7 said:
That's an interesting situation. I would install the LGMobile Support Tool and see what model it says you have. If I had to *guess* it's a P999 but you should definitely contact one of the other Videotron users and ask them. That is beyond my scope of knowledge, so proceed with caution!
Click to expand...
Click to collapse
I have connect my phone with Lg software update its detect as p999dw and proceed towards the update process after Update process my phones become T mobile G2X which was videotorn earlier I am thinking of making new thread with all the information i have along with snap shoot
Hasooboy said:
I have connect my phone with Lg software update its detect as p999dw and proceed towards the update process after Update process my phones become T mobile G2X which was videotorn earlier I am thinking of making new thread with all the information i have along with snap shoot
Click to expand...
Click to collapse
Yeah, enjoy your new G2x. haha...
Always nice to give back to the community! Give it a shot! I haven't seen much Videotron stuff here yet, just T-Mobile and Wind.
r4d14n7 said:
Yeah, enjoy your new G2x. haha...
Always nice to give back to the community! Give it a shot! I haven't seen much Videotron stuff here yet, just T-Mobile and Wind.
Click to expand...
Click to collapse
One more thing i just want to know what happen if i install CWM of p999 which its is most probably then what happened if its p990 :S
Thanks!
Easy to follow, thanks alot!
Good guide, one additional section would be a general overview of ICS-based vs GB-based ROMs, advantages of ICS are latest Android OS, but downside is non-working binary drivers for video camera & playback & uses more memory for OS. GB is more functional & stable, but older-style.
Great Guide!!!!!:
thanks for this amazing guide. Works perfectly without any problems.
Hasooboy said:
I have connect my phone with Lg software update its detect as p999dw and proceed towards the update process after Update process my phones become T mobile G2X which was videotorn earlier I am thinking of making new thread with all the information i have along with snap shoot
Click to expand...
Click to collapse
lol i wish i had you're problem. If my phone was doing that i'd have no issue what so ever getting the march 2012 baseband

[Q] Rooting Woes

Greetings and salutations. I have lurked here for quite some time, gathering all information possible before attempting to root my phone. The first phone I rooted was my HTC Inspire (I think that's what it is called) after spending almost 2 months of researching. I loved CM7 and the time it took me to boot was incredibly and extremely noticeably improved; I'm talking 4 minutes down to 35 seconds. Then one unfortunate day, I ran it over on accident and busted the screen. Luckily, my upgrade was right around the corner, so I upgraded to the ATRIX 2 (foolishly without doing proper rooting research, I was desperate for a phone).
I am finally fed up with 2.3.6, and want to taste this ICS goodness I see everywhere, but being on AT&T I have realized that may not happen for a few more months. I have been doing the research, but am unable to 'grasp' the root process for my phone. I am going based on rough memory of the process for my HTC, and things just don't add up, and I would hate to brick my phone.
These are the pages I have been reading, but I may have missed something in the flurry of reading I have been doing over the past week.
http://forum.xda-developers.com/showthread.php?t=1327741
http://forum.xda-developers.com/showthread.php?t=1396650
The ROM I decided upon is NottachAtrix something, located here:
http://forum.xda-developers.com/showthread.php?t=1567241
Relevant Info:
PC - Win7 (Custom Built)
Linux Box - Mint 8 (Currently won't boot, GFX issue, too lazy to fix atm)
ATRIX 2 - AT&T Network
Sys Version - 55.13.25.MB865.ATT.en.US
Droid Version - 2.3.6
Kernel Version - 2.6.35.7-g98a0a06
Build # - 5.5.1-175_EDMR1.25
I am unsure of what 'drivers' need to be installed, I have enabled USB Debugging, and set my phone to charge only; yet the .bat file included in the 2.3.6 root does not see my phone. I have searched, and not found any definitive answer on the topic either. Have I overlooked something? Are there any other files I need to have (Radio, GSM, whatevers)?
Thank you in advance for any assistance available.
noodlesdefyyou said:
Greetings and salutations. I have lurked here for quite some time, gathering all information possible before attempting to root my phone. The first phone I rooted was my HTC Inspire (I think that's what it is called) after spending almost 2 months of researching. I loved CM7 and the time it took me to boot was incredibly and extremely noticeably improved; I'm talking 4 minutes down to 35 seconds. Then one unfortunate day, I ran it over on accident and busted the screen. Luckily, my upgrade was right around the corner, so I upgraded to the ATRIX 2 (foolishly without doing proper rooting research, I was desperate for a phone).
I am finally fed up with 2.3.6, and want to taste this ICS goodness I see everywhere, but being on AT&T I have realized that may not happen for a few more months. I have been doing the research, but am unable to 'grasp' the root process for my phone. I am going based on rough memory of the process for my HTC, and things just don't add up, and I would hate to brick my phone.
These are the pages I have been reading, but I may have missed something in the flurry of reading I have been doing over the past week.
http://forum.xda-developers.com/showthread.php?t=1327741
http://forum.xda-developers.com/showthread.php?t=1396650
The ROM I decided upon is NottachAtrix something, located here:
http://forum.xda-developers.com/showthread.php?t=1567241
Relevant Info:
PC - Win7 (Custom Built)
Linux Box - Mint 8 (Currently won't boot, GFX issue, too lazy to fix atm)
ATRIX 2 - AT&T Network
Sys Version - 55.13.25.MB865.ATT.en.US
Droid Version - 2.3.6
Kernel Version - 2.6.35.7-g98a0a06
Build # - 5.5.1-175_EDMR1.25
I am unsure of what 'drivers' need to be installed, I have enabled USB Debugging, and set my phone to charge only; yet the .bat file included in the 2.3.6 root does not see my phone. I have searched, and not found any definitive answer on the topic either. Have I overlooked something? Are there any other files I need to have (Radio, GSM, whatevers)?
Thank you in advance for any assistance available.
Click to expand...
Click to collapse
You can root by following:
http://forum.xda-developers.com/showthread.php?t=1742879
About ROM there are many available for our Atrix 2 in "Atrix 2 Android Development" section with a proper method of installing it.
prasannapmv said:
You can root by following:
http://forum.xda-developers.com/showthread.php?t=1742879
About ROM there are many available for our Atrix 2 in "Atrix 2 Android Development" section with a proper method of installing it.
Click to expand...
Click to collapse
The link you provided contains a 404'd attachment. I am looking for the exact steps to gain SU on my Atrix 2, as the provided steps seem to be failing. Threads explain to have proper drivers installed, but what drivers and where? My PC see's my phone just fine, if I change to USB Mass Storage I can drag/drop files to my phone, Moto Central activates my moto sync thingie, and charge only, well, charges. I have USB Debugging enabled, yet the 'one click' batch file does not see my phone
If you are on 2.3.6:
Install the OTA and upgrade your phone to 2.3.6
Download the 2.3.6 root zip from HERE
Make sure you have the right drivers installed then connect your phone to your PC.
Unzip the file and then double-click "Click-To-Root.bat".
Refer to the trouble shooting step bleow the 2.3.5 method if you are unable to attain root!
Click to expand...
Click to collapse
What drivers? Install what OTA? If I am on 2.3.6, why do I need to upgrade to 2.3.6? There is no 'troubleshooting' listed under under the 2.3.5 method, just the manual commands the batch file performs. Do I have to use this Motofail thingie to root? It has not been mentioned in other threads...
noodlesdefyyou said:
The link you provided contains a 404'd attachment. I am looking for the exact steps to gain SU on my Atrix 2, as the provided steps seem to be failing. Threads explain to have proper drivers installed, but what drivers and where? My PC see's my phone just fine, if I change to USB Mass Storage I can drag/drop files to my phone, Moto Central activates my moto sync thingie, and charge only, well, charges. I have USB Debugging enabled, yet the 'one click' batch file does not see my phone
What drivers? Install what OTA? If I am on 2.3.6, why do I need to upgrade to 2.3.6? There is no 'troubleshooting' listed under under the 2.3.5 method, just the manual commands the batch file performs. Do I have to use this Motofail thingie to root? It has not been mentioned in other threads...
Click to expand...
Click to collapse
Follow the instruction as given:
Install motorola 5.2 phone drivers
download the attachment from the link I gave you and extract it.
Enable usb debugging from setting/application/developement
connect your phone to motorola phone portal mode
Open the attachment folder
then click on "click-to-toot.bat"
rooting process will start
your phone will reboot 2-3 times
Use these drivers, they should work. Reboot your computer and then follow this guide. You should be rooted in no time. Just make sure that you are using a high quality (preferably OEM) cable to connect your A2 to your computer.
Good luck! Also be reminded that the Atrix 2 is not the Atrix 4G. So since NottachTrix is for the A4G it won't work on the A2 :\.
cogeary said:
Use these drivers, they should work. Reboot your computer and then follow this guide. You should be rooted in no time. Just make sure that you are using a high quality (preferably OEM) cable to connect your A2 to your computer.
Good luck! Also be reminded that the Atrix 2 is not the Atrix 4G. So since NottachTrix is for the A4G it won't work on the A2 :\.
Click to expand...
Click to collapse
Thanks for the help. As technology savvy as I am, it never dawned on me that I may have to reboot. I am so used to keeping my PC on for weeks at a time, shutting down usually once a month to clean the cpu fan, case fans, and mild dusting to keep it 'clean'.
I'll have to do some more searching for another custom ROM then; hell, if I had the spare time I'd help with CM.
Will be rebooting in a bit and giving it a shot.
After a few days of relaxing, I cracked back at getting SU on my A2. Success! SU achieved. I then searched around for a decent ROM to use on my A2 (MB865) and decided upon this one here:
http://forum.xda-developers.com/showthread.php?t=1686157
After reading up on it, I did some research on CWM, since it does not 'recognize' the A2, to figure out how to boot in to recovery, and stumbled upon this:
http://forum.xda-developers.com/showthread.php?t=1346977
After performing the steps, and flashing the REMUS rom, I now have a softbricked phone. I am currently unbricking it as I type this. What exactly did I do wrong? Did I miss something? Is the REMUS Rom not actually compatible with the A2 (MB865) like it claims?
First off we need more info. Did you factory reset and wipe both caches first? Did the install say that it finished successfully?
What for you mean by its "soft bricked"? Will it not boot into Android? Sounds like you wiped data and had a mis-flash. As long as you haven't borked the boot image, you night still be able to try a re-flash. Make sure you wipe cache partition, Dalvik, and delete user data/factory reset in CWM, then flash again.
Sent from my MB865 using xda premium

Stock GB Rogers to JB questions

I've been sitting on my stock Rogers Infuse 4G since I got it, hoping that they would at the very least release an update to ICS. I've pretty much given up all hope, especially now since the Infuse was listed as one of the "violators" in the recent lawsuit. So, in giving up there, I've started to try and get up to speed with what's available in terms of custom ROMs for the Infuse, etc...
I previously had a Captivate (seems like I pick the wrong phones) and have kept that one stock as well (now my wife's phone) aside from the official 2.3.3 update Samsung came out with for it. I checked in here once in a while to try and keep track of some of the updates as I thought about going for a custom rom, but I never had the balls to try anything (I've only ever flashed one phone in my life, and it was bought 2nd hand for $20 ) since I actually *must have* a working phone due to having a kid (daycare calls are kind of important!). However checking today, it seems like I am totally out of the loop and I just don't have the time to try and wade through thousands of pages on various threads to find out what the current "ways" are and such... but I know what I want to achieve so I'm hoping you folks are nice enough to at the very least give me a "search you noob" and point me to some threads :silly:
Since I'm totally stock, from what I'm gathering I think I need (and really I more of need a complete checklist of things to do rather than a "do it for me" kind of thing) to do is:
1) jot down my modem and apn settings and such (already done)
2) back up everything i need, pop out sd card (know how to do this)
3) wipe/clear to factory default (... and this)
4) back up the current rom - everything in case I want to return back to exactly the way the phone is stock
5) figure out what i need to do to flash CWM or something so I have the necessary recovery mode options?
6) flash to ICS (since from what I gather, I need to do that if I want to go to JB)?
7) follow instructions I found on the unnoficial CM10 JB thread to flash to JB
?) flash a new kernel? (is this done already during a rom flash; are there any new kernels?)
As commented, I can figure out 1-3 since I'm not stupid, but I have no idea what is even needed to do 4, nor do I know exactly all the tiny, necessary, steps to do the rest after that... especially since reading some things it seems like most of this is for AT&T users and since I'm on Rogers with a I997R (I assume the R means Rogers), I don't want to mess up my modem or other things to prevent the phone working for me... and these are the steps I'm hoping people can help me with.
So far, in prep, I've noted my phone info (basically everything in Phone settings) and I can back up all my apps and such that I care about, and I've downloaded the unofficial CM10 JB download and the Google apps apk as well, and on the same thread was a link to a 1-click ICS flash or something... so I got that too. Since I want to end up with JB, I'm not too concerned (or should I be?) with it being AT&T stuff to get to ICS, since it's the JB flash that I'd really want to ensure works for me.
Is anyone willing to help me out? I really wish I didn't have to be the "next loser" to make a thread like this but I just haven't had the time to be able to keep up with all the info going around (voodoo mods and whatever else?!) to be able to make sense of all this myself!
Thank you!
This looks like a good place for you to start
http://forum.xda-developers.com/showthread.php?t=1197248&highlight=how+to+root+rogers
First thing to do of course is read, read, read. Understanding what you are doing and why you are doing it is the most valuable resource you can have.
The gist of it is though: to install the custom updated roms, you need root. For Rogers infuse users that is very easy to do; all you have to do is install a rooted kernel in odin. After you do that you make a nandroid (and/or EFS) backup, and install whatever rom you want. CM9 and CM10 have their own kernel, so don't worry about that.
adfurgerson posted the step-by-step guide above me, although the links in the OP may be down. I have the mirrors here: http://minus.com/moAvVibed/
the 3 files in there are:
Odin_Infused_Gingerbread_Kernel_v1.zip - This is the rooted kernel you are flashing
Odin_Stock_Rogers_UXKG3_Kernel.zip - This is the stock rogers unrooted kernel if you want to unroot and go COMPLETELY stock for whatever reason (I doubt you will ever need to use this tbh)
Odin_UXKG3_rooted_no_bootloaders_v2.zip - The stock Rogers FIRMWARE. If you ever mess up you use this to "start from scratch". You will still be rooted though if you don't use the stock kernel above.
So yeah, just flash the kernel in odin as described in the above thread and you will have root + cwm.
From there you reboot into cwm (turn off, turn on holding vol+ and vol- buttons) and make a nandroid backup of your stock rogers rom (or an EFS backup with the infuse toolkit: click here), flash CM9 as per the instructions in the OP, and finally CM10 as per the instructions in the OP.
Also remember:
1. The infuse is almost impossible to hard brick. The only real way to do so is to improperly flash bootloaders, which a rogers infuse user will never have to do. Only AT&T users coming from Froyo have to do it. So keep that in mind.
2. On the chance that you get soft-bricked (screen won't go past samsung logo for example) you can always go back to flashing the stock rom/rooted kernel again in odin and start all over again.
The only thing that I can add to Threi's excellent reply is to mention the one click to ICS. It is in the first post of Scott's CM10 thread,it should give you the ICS recovery that is needed to flash JB without flashing a full ICS ROM.
I suppose I should have mentioned that I also have rooted my phone already (used SuperOneClick, worked fine). Is there any reason why I would use that "rooted kernel" versus just having root on my phone (ie, having su installed... dunno what else it did, I don't think it did anything to my kernel)?
I guess my biggest unknown is all the backup processes that can be done and how to do them? Is "nandroid" a one stop shop for doing backups of everything? Although there's the complete stock Rogers rom linked above (which I'll nab anyways!), I was thinking I would try to make a complete copy of my own phone (just in case)... I guess next step is to search for "nanroid"
Are there any other backup tools I could use/check out (not apk backup tools... those are easily located in the app store, or performed with adb myself).
j.smith said:
I suppose I should have mentioned that I also have rooted my phone already (used SuperOneClick, worked fine). Is there any reason why I would use that "rooted kernel" versus just having root on my phone (ie, having su installed... dunno what else it did, I don't think it did anything to my kernel)?
I guess my biggest unknown is all the backup processes that can be done and how to do them? Is "nandroid" a one stop shop for doing backups of everything? Although there's the complete stock Rogers rom linked above (which I'll nab anyways!), I was thinking I would try to make a complete copy of my own phone (just in case)... I guess next step is to search for "nanroid"
Are there any other backup tools I could use/check out (not apk backup tools... those are easily located in the app store, or performed with adb myself).
Click to expand...
Click to collapse
Flashing a kernel is how you obtain cwm which allows you to flash custom ROMs(cwm is clockwork mod recovery). A nandroid is a backup you create in cwm that is copy of your phone that will return your phone to the exact state it was at the time backup was made.
adfurgerson said:
Flashing a kernel is how you obtain cwm which allows you to flash custom ROMs(cwm is clockwork mod recovery). A nandroid is a backup you create in cwm that is copy of your phone that will return your phone to the exact state it was at the time backup was made.
Click to expand...
Click to collapse
Aha, perfect description. I didn't realize I had to get a new kernel to have CWM... and I'm guessing because of signing and such, that a custom kernel (with CWM) is required in order to flash a non-signed rom, which is why you couldn't just do it on stock, right?
Ok, so now armed with that info that clears up a lot, I guess I have just one question left (which I can probably find the answer to with some searching). I have read what that voodoo lagfix is and is this something that is standard now on all kernels (because if it can cause issues, I'd rather just have a kernel without it)? Are there any "rooted" kernels without the lagfix built in so I don't have to remember about disabling the lagfix? ...or is there a way to install CWM on to my current kernel?
*edit* Ok, I realize I might be a bit too picky about the voodoo lagfix thing. I found two good threads on dealing with Rogers specifically, so I'll read over those (and suck it up about voodoo) and see how it goes. Since my vacation got unfortunately cancelled due to a sick kid, I have some time to experiment this weekend... hopefully ending up with JB on my phone!
Glad to see your on you're on the way to JB. After you install a custom kernel be sure to make a nandroid in the backup and restore option of CWM before you flash a ROM. That is like your safety net, if you wiped everything and had a bad download that wouldn't install, you will have a nandroid to restore.
adfurgerson said:
Glad to see your on you're on the way to JB. After you install a custom kernel be sure to make a nandroid in the backup and restore option of CWM before you flash a ROM. That is like your safety net, if you wiped everything and had a bad download that wouldn't install, you will have a nandroid to restore.
Click to expand...
Click to collapse
Yep, just flashed the rooted cwm kernel and performed a backup. I read somewhere that you can/should back up your efs in case you lose your imei... so I'm just going to quickly look in to that, then i wipe and do some flashes to jb... shouldn't take long hopefully!
Ok, I seem to be stuck at trying to get the one-click ICS install to work. I've got the EZUpdater package to ensure I have the right drivers, yet everything I try with the one-click seems to tell me that the drivers aren't installed and then launches an installer which also doesn't seem to detect the phone... yet EZUpdater will run fine, etc...
I'm just about to reboot and launch device driver in a mode to list all hidden/previously installed devices and nuke them from history to hopefully purge my system of all traces of any drivers and install EZUpdater one more time to get the drivers installed.
Any reason why my phone wouldn't show up in this one-click (it uses heimdall or whatever) program, but seems to work in most everything else (adb even runs fine)?
*edit*
Got it all working! I couldn't get the one-click ICS to work for the life of me... it just didn't see the drivers even though they were there and working. I guessed maybe it had to do with me running Windows 7 x64 and having x64 drivers, but the one-click maybe being 32bit. I even tried installing the x64 Java JRE but didn't seem to make any difference.
I ended up having to flash CM9 which worked fine, then going to CM10. Had no issues doing that... wish I had just tried that before since that one-click wasted hours of my day and got me somewhat frustrated!

[Q] Want To Root my Samsung Infuse I997 - NOOB Here.

Want to get my Infuse rooted and upgraded to either ICS or Jelly Bean.
I got the official GB update because phone was lagging. Some improvements but still lagging.
So I'm doing my research to find out, that it seems, I can't root GB and then upgrade to ICS/JB. That I would have to downgrade to froyo first.
So I've downloaded the Odin zip file and everything is ready, I'm just a few clicks away from doing the process I got from this page
http://forum.xda-developers.com/showthread.php?t=1092021
Then I do some more research and notice this Hemdaill version.
Anyway bottom line, I want to avoid bricking my phone or any other catastrophe.
So my questions are(sorry for the wait):-
- Should I just go ahead with the instructions in the above link to go back to froyo before thinking about flashing a ROM for ICS/JB?
- If I go ahead with the above, can I go straight from froyo to ICS/JB or do I have to get GB first?
- Is there are a superoneclick root for GB on Infuse, and if so would I be able to upgrade to ICS/JB?
- I'll take any tips or recommendations. That's basically all I have to ask.
Yeah this is exactly what I used about 4 months ago. It was the first time I've ever tried something like this. It was SUPER easy, just follow the directions and then flash whatever you want.
Sent from my SGH-I997 using xda app-developers app
Back to stock BUT with a few problems
Since I'm new I can't comment on the original's page where I got the process from.
Problems:
- I used the rooted version that was listed in the download. I have the SuperUser app icon. It opens. But I cannot delete apps that came with the phone. Will do a bit more research.
- Wifi is not working. Won't even try to connect. Maybe the SuperUser needs an internet connection, I don't know, research will ensue.
- At the risk of sounding even more like a noob, I will go do some more research but please responses are welcome.
If the above Odin worked. It should have installed a stock Gingerbread experience... WiFi/data/gps etc... Should work just fine.
Superuser only allows apps to gain special permissions to access new features... One app for example that is useful is Rom Manager that can install CWM recovery thus allowing you to flash ICS, then JB... Another useful app is Titanium Backup which will allow you to uninstall /backup/restore any app...
The easiest way from here is to read the OP for cm10. It has a link for a Odin recovery process (which has instructions for getting CWM using SGS kernel flasher), then a link for ICS. Then you can get Jelly Bean...
Remember that three finger method to get into CWM (hold vol +/- and power)
Edit: theoretically all you need is ICS CWM recovery to flash JB... Once you have that. You're good to go. Read EVERYTHING before doing something silly.
Skebodan said:
Since I'm new I can't comment on the original's page where I got the process from.
Problems:
- I used the rooted version that was listed in the download. I have the SuperUser app icon. It opens. But I cannot delete apps that came with the phone. Will do a bit more research.
- Wifi is not working. Won't even try to connect. Maybe the SuperUser needs an internet connection, I don't know, research will ensue.
- At the risk of sounding even more like a noob, I will go do some more research but please responses are welcome.
Click to expand...
Click to collapse
If you still having problems just run Odin again. This is what I used ......http://forum.xda-developers.com/showthread.php?t=1613523
omansteveo said:
If you still having problems just run Odin again. This is what I used ......http://forum.xda-developers.com/showthread.php?t=1613523
Click to expand...
Click to collapse
Thanks for the tips.
I flashed again but **** before it did not auto reboot like it says it would and it was also checked in Odin to do that.
Anyway what I did was through the recovery mode I basicalky factoryvreset the phone, all the data all the cache and reinstalled the packages that was an option as well. Hell I chose everything. But it's working now, and it's a bit late.
Don't know if I want to try flashing to ICS while ai'm a bit groggy.
But thanks everybody for the tips and to the OP developer.
Xda always a big help.

Categories

Resources