Okay, first and foremost, by posting this tutorial I am not taking any responsibility if you brick your phone. This worked for me, and it should work for all US based Vibrant (3G) T959 models with the latest 2.2 update (KB5).
NOTE: Rooting and/or installing another recovery WILL void the warranty.
What you will need...
1. SuperOneClick v2.1.1
2. Cmenards's OverStock Kernel with ClockworkMod Recovery
3. Heimdall Suite (Go To CyanogenMod Wiki for Vibrant to download as it is over 8MB in size and won't upload here)
Please get all of these first.
Now, first step in the actual process... Thanks to Cyanogen for the tutorial on this part.
Windows ONLY:
1. Power off the Samsung Vibrant and connect the microUSB to the computer but not the Samsung Vibrant.
2. Boot the Samsung Vibrant into download mode by holding down Volume Up & Volume Down while connecting the USB to it.
3. Run the included zadig.exe in the drivers folder of the Heimdall Suite.
4. From the menu, choose Options » List All Devices.
5. From the drop down, select Samsung USB Composite Device or Gadget Serial.
6. Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
7. Heimdall can now be used safely on the Windows computer.
8. Create the following folder on the root of the internal SD card, Voodoo/disable-lagfix (case-sensitive).
9. Unzip Cmenard's Overstock Kernel.
10. Launch the Heimdall Frontend.
11. Select the extracted zImage in the Kernel (zImage) section.
12. Power off the Samsung Vibrant and connect the microUSB to the computer but not the Samsung Vibrant.
13. Boot the Samsung Vibrant into download mode by holding down Volume Up & Volume Down while connecting the microUSB to it.
14. Click Start on the Heimdall Frontend. A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.
The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section.
Part two of the procedure...
1. Extract the SuperOneClick file.
2. Open the SuperOneClick executable in that extracted folder.
3. Put your phone in Debug mode. (Settings --> Applications)
4. Connect your USB to the computer and the device.
5. Click Root and Wait (The phone will not restart).
6. Turn the phone off.
7. Boot into the recovery (hold the volume up+down while pressing the power button. let go of the power button when you see the samsung vibrant boot screen)
8. Scroll the list with the volume up or down buttons. The power button selects the item.
9. Select "advanced".
10. Select "fix permissions"
11. When it says finished, select "+++++Go Back+++++"
12. Select "reboot system now".
13. Open Android Market -> Search for Superuser -> Update
14. Search for "File Explorer" -> choose eStrongs (free and has root) -> Install
15. Open ES File Explorer -> Menu -> Settings -> Scroll to the bottom and check Root Explorer -> Check Mount File System
16. Press back button -> click the SD Card icon in the top left of the app
17. That will put you in the root. Go to system-->app and remove ONLY the bloatware you don't want (ie.. Slacker Radio, Avatar player, GoGo)
18. Exit the File Explorer and open the Market
19. Get the BusyBox installer from Stephen and install
20. Open the BusyBox installer you downloaded and follow the instructions.
After all is done, the annoying system apps you didn't want will be gone. The phone will be rooted. It will have the clockwork recovery and still be the official ROM.
NOTE: The only reason to remove the bloatware is because you must have at least 1600KB of free space in the /system folder of the device. If running the official KB5 rom, there is only about 560KB free. This frees up the space needed for the BusyBox installer to install BusyBox.
I am all for new guides/information and helping... curious though...
do you feel this is easier than just using odin to get back to jfd
moving the update.zip and rom to the internal sd
getting in stock recovery, pressing reinstall
flashing a rom
EDIT, emphasis, I am honestly not trying to sound like a ****... REALLY happy to see others taking the time to write out such good detail.
stock kb5 recovery will not open the update.zip. it gives an error every time i have tried.
^ needs the modified 3E. Another reason I like to ODIN to JFD.
s15274n said:
I am all for new guides/information and helping... curious though...
do you feel this is easier than just using odin to get back to jfd
moving the update.zip and rom to the internal sd
getting in stock recovery, pressing reinstall
flashing a rom
EDIT, emphasis, I am honestly not trying to sound like a ****... REALLY happy to see others taking the time to write out such good detail.
Click to expand...
Click to collapse
The main reason for the tutorial is because it is very difficult to find working links to the original 2.1 vibrant which allowed SuperOneClick to work out of box. I did find that it was easier than hunting down many different applications/files and most of this can be done from the PC.
This was also for those that wanted to keep the actual official 2.2 (KB5) rom on the vibrant, but have root access. I have tried using the update.zip method with the modified 3e only to find that a lot of the permissions get messed up. The only way that I was able to get the update.zip to work in establishing root was to actually use Odin to downgrade to the 2.1 rom. As soon as I used Keis to update to the new 2.2 rom (KB5) it would loose root and the ClockworkMod recovery.
After much trial and error, I found out this solution is a lot more stable (for me) to achieve root on the KB5 official rom.
If there is a better way, then I was not able to find an actual tutorial from here that stated how to perform root on the KB5 rom without it having permissions problem.
Don't worry about sounding like a ****. I didn't take it that way.
s15274n said:
^ needs the modified 3E. Another reason I like to ODIN to JFD.
Click to expand...
Click to collapse
I understand your affinity for Odin and JFD, but this tutorial is about having a rooted KB5. Sorry to sound like an ass here... regardless of your affinity for Odin/JFD, this is not the topic to shout that affinity.
This is for rooting the KB5 rom. If others wish to downgrade to the JFD, awesome. That is not what this thread is about. It is about a rooted KB5.
Not sure if I made that clear or not in the main tutorial, but this will give you a rooted KB5.
^ wow. Just letting that person know what their issue was while pointing out that if they went to JFD and had the 2E recovery it would not be an issue... pointing out how to fix something and giving an alternative.
I don't consider JFD a downgrade, because nobody stays on it... it's to root and flash a custom ROM... most of which are now going to gingerbread, CM7 and MIUI builds... an upgrade from KB5.
Someone could just as easily root 2.1 and flash a deodexed stock kb5 with root. There are MANY ways to do things.. I applauded you and have only offered other suggestions. I'll regress if you just don't want people to post here.
s15274n said:
^ wow. Just letting that person know what their issue was while pointing out that if they went to JFD and had the 2E recovery it would not be an issue... pointing out how to fix something and giving an alternative.
I don't consider JFD a downgrade, because nobody stays on it... it's to root and flash a custom ROM... most of which are now going to gingerbread, CM7 and MIUI builds... an upgrade from KB5.
Someone could just as easily root 2.1 and flash a deodexed stock kb5 with root. There are MANY ways to do things.. I applauded you and have only offered other suggestions. I'll regress if you just don't want people to post here.
Click to expand...
Click to collapse
I apologize if I did come off as an ass. Bad couple of days here, but that is no excuse. Again, I apologize.
The reason I consider it to be a downgrade is because the 2.2 based rom is the first to offer the ability to do certain things in regards to media. Netflix, HBO Go and the like wasn't working on the 2.1 based rom. The official reason why was because it didn't support the protection they needed to utilize.
I offer this for those that wanted to stick with the rom they got from Kies, but get rid of certain things and add root for installation of other tools.
Now that Samsung has changed their statement regarding a 2.3 release from "we are not sure when" to "we are not sure if", then I am a strong supporter of running custom roms.
I just know that I was looking for a way to do this at one point. Because of my OCD, when I get an idea in my mind... I can't stop until I either find a way to get it done or know for a fact it can't.
Again, I do apologize for coming off as a total ass. Thank you for trying to offer alternatives and posting here. I love being challenged on my ideas, but I shouldn't have gotten nasty in response.
5. From the drop down, select Samsung USB Composite Device or Gadget Serial.
I'm currently stuck on this step, since my system doesn't indicate what kind of usb device is on the current usb port. Nor do I see "Samsung USB Composite Device or Gadget Serial. I believe it's not picking up the device after I did step 1-4. Any insights on what is happening or what I'm doing incorrectly?
Tamborine said:
5. From the drop down, select Samsung USB Composite Device or Gadget Serial.
I'm currently stuck on this step, since my system doesn't indicate what kind of usb device is on the current usb port. Nor do I see "Samsung USB Composite Device or Gadget Serial. I believe it's not picking up the device after I did step 1-4. Any insights on what is happening or what I'm doing incorrectly?
Click to expand...
Click to collapse
I had this same issue, but it was because I was running the app in an Avast sandbox. When I re-ran it in normal mode, it worked as the OP described.
Many thanks for this tutorial, by the way. Very helpful.
plase update procedure.
GayBooSC said:
Okay, first and foremost, by posting this tutorial I am not taking any responsibility if you brick your phone. This worked for me, and it should work for all US based Vibrant (3G) T959 models with the latest 2.2 update (KB5).
NOTE: Rooting and/or installing another recovery WILL void the warranty.
What you will need...
1. SuperOneClick v2.1.1
2. Cmenards's OverStock Kernel with ClockworkMod Recovery
3. Heimdall Suite (Go To CyanogenMod Wiki for Vibrant to download as it is over 8MB in size and won't upload here)
Please get all of these first.
Now, first step in the actual process... Thanks to Cyanogen for the tutorial on this part.
Windows ONLY:
1. Power off the Samsung Vibrant and connect the microUSB to the computer but not the Samsung Vibrant.
2. Boot the Samsung Vibrant into download mode by holding down Volume Up & Volume Down while connecting the USB to it.
3. Run the included zadig.exe in the drivers folder of the Heimdall Suite.
4. From the menu, choose Options » List All Devices.
5. From the drop down, select Samsung USB Composite Device or Gadget Serial.
6. Click Install Driver.
NOTE: A prompt may appear warning that the installer is unable to verify the publisher of the driver. Ignore it and select "Install this driver anyway."
7. Heimdall can now be used safely on the Windows computer.
8. Create the following folder on the root of the internal SD card, Voodoo/disable-lagfix (case-sensitive).
9. Unzip Cmenard's Overstock Kernel.
10. Launch the Heimdall Frontend.
11. Select the extracted zImage in the Kernel (zImage) section.
12. Power off the Samsung Vibrant and connect the microUSB to the computer but not the Samsung Vibrant.
13. Boot the Samsung Vibrant into download mode by holding down Volume Up & Volume Down while connecting the microUSB to it.
14. Click Start on the Heimdall Frontend. A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically.
The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section.
Part two of the procedure...
1. Extract the SuperOneClick file.
2. Open the SuperOneClick executable in that extracted folder.
3. Put your phone in Debug mode. (Settings --> Applications)
4. Connect your USB to the computer and the device.
5. Click Root and Wait (The phone will not restart).
6. Turn the phone off.
7. Boot into the recovery (hold the volume up+down while pressing the power button. let go of the power button when you see the samsung vibrant boot screen)
8. Scroll the list with the volume up or down buttons. The power button selects the item.
9. Select "advanced".
10. Select "fix permissions"
11. When it says finished, select "+++++Go Back+++++"
12. Select "reboot system now".
13. Open Android Market -> Search for Superuser -> Update
14. Search for "File Explorer" -> choose eStrongs (free and has root) -> Install
15. Open ES File Explorer -> Menu -> Settings -> Scroll to the bottom and check Root Explorer -> Check Mount File System
16. Press back button -> click the SD Card icon in the top left of the app
17. That will put you in the root. Go to system-->app and remove ONLY the bloatware you don't want (ie.. Slacker Radio, Avatar player, GoGo)
18. Exit the File Explorer and open the Market
19. Get the BusyBox installer from Stephen and install
20. Open the BusyBox installer you downloaded and follow the instructions.
After all is done, the annoying system apps you didn't want will be gone. The phone will be rooted. It will have the clockwork recovery and still be the official ROM.
Click to expand...
Click to collapse
part 1 procedure after # 7, please indicate if disconnect cable or let cable stay. same as part 2 procedure after # 14 part 1, what happend next. let the cable stay until fully boot?thanks
step 1 procedure #14
After carefully followed the step 1 after procedure # 14 reboot and stuck at vibrant logo.
Related
Ok, so I know this will eventually get buried in the forums but I thought I would attempt to give a little basic info here. Right now the QA section is flooded with people that have flashed and are now soft bricked (have problems but can recover) or hard bricked (have problems and cannot recover). I'm hoping that I can help some people prevent these issues to an extent.
Terminology, the differences in my opinion.
Soft brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your hardware buttons work or ADB works and you are able to boot into DOWNLOAD mode.
Hard brick- Your flash didn't go right, something went crazy, etc, but either way you can't boot, stuck at ATT logo, boots into recovery no matter what, boots to phone--!--pc, BUT, your unlucky and hardware buttons do not allow access to DOWNLOAD mode or ADB is not downloading.
Also, after a new flash or flash to stock, it's a good idea to immediately enable USB debugging. Menu, Settings, Applications, Developement, check the box for USB debugging. It will make things easier later on.
1. First. BEFORE you flash, can you access download mode with your buttons??? Test it.
3 Methods.
Method 1: (ADB - from recovery or normally booted with usb debugging on)
Open a cmd prompt/console/shell
adb shell
adb reboot download
Method 2: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold Volume Up + Volume Down + Power
Method 3: (KEY COMBO)
Remove the battery, sim card, sdcard if you have one
Insert the battery
Hold both Volume buttons (from i9000 just down, don't touch the power button)
Plug in the USB cable and continue holding both Volume buttons
If not, use designgears fix. http://forum.xda-developers.com/showthread.php?t=812434
2. Second. Download the SDK, drivers for your PC, and learn some basic ADB commands, ie, adb reboot download, adb reboot recovery, adb shell. Here's my quick guide. ADB can be used when the OS is running, when in recovery, and when stuck on ATT boot screen.
Here's what I do. After you download the sdk and unzip. There is a folder called tools. I copy that to c:
Then open a command prompt and type,
C:
CD tools
Then issue adb commands.
adb reboot, adb reboot download or whatever command you need.
Of course make sure your phone is connected via USB and debugging is enabled.
Here's another method for using adb.
1) start-> run-> sysdm.cpl
this will start the system properties. you can reach this from right clicking "My Computer" and hitting properties. Windows 7 though is different. The above method is most universal.
2) Move to Advanced Tab that pops up. From there click the "Environment Variables" button.
http://wtfokc.com/sef****/sysdm-1.gif
3) In the window that pops up, find the "PATH" area in the "System Variables" listbox at the bottom:
http://wtfokc.com/sef****/sysdm-2.gif
4) Click edit again, put in path to the AndroidSDK tools folder. Do it like shown otherwise you can biff something up. DO NOT REMOVE ANYTHING. Just add a SEMICOLON ( ; ) to the last of the line that's already there, then the path to the folder.
http://wtfokc.com/sef****/sysdm-3.gif
5) If on Win7 you shouldnt have to reboot. XP however will. Then you are set. You can now just load a CMD prompt and do ADB without having to CD TOOLS.
3. Third. Install Clockwork Recovery! Root your phone and download ROM Manager from market. Install Clockwork recovery from ROM Manager. BOOT into recovery to make sure it works. You will have to choose reinstall packages from stock recovery. What ROM Manager does, it put an update.zip on the root of your SDcard, then when you choose reinstall packages from stock recovery it install update.zip. I personally leave the update.zip file on my sdcard at all times, just in case.
Once you have clockwork installed, make a Nandroid backup of a good running rom. In case something happens, if you can boot into recovery, then you can possibly restore your nandroid to at least get you up and running quickly, and without the need of a pc.
NEW Info!!! You can recover from a hard brick, maybe. Here's how to create a USB Jig to reproduce the button download mode for you folks who don't have it.
http://forum.xda-developers.com/showthread.php?t=841512
Here's another thread about the USB Jig method.
http://forum.xda-developers.com/showthread.php?t=819551&highlight=USB+jig
If my captivate was one that had the missing button recovery/download out of the box, I would probably know how to make a USB jig or have one already before flashing. Even with the 3 button fixes that are out, it looks like some people are still bricking.
****Disclaimer****
This is just from personal exprience. I have flashed most roms available, and I have experienced every variation of soft brick mentioned above and have recovered.
I find that being able to get your phone into download mode and knowing how to use Odin will be your 2 biggest life savers after something bad happens.
This will not keep you from getting a bad flash or something else, but having this knowledge ahead of time may help you recover from issues more quickly and without asking a question on the forums that have been asked dozens of times.
Also, personally, if I cannot perform step 1, access download mode with buttons, I personally would be VERY cautious about flashing! ADB reboot download is nice, but if you are stuck at ATT logo or phone--!--PC mode then ADB doesn't work, YOU HAVE TO USE BUTTONS.
Just my 2 cents, take it or leave it.
Edit. Added some new info to post. Thanks for extra info guys. I'll mirror the links to the images later when not at work.
+sticky
excellent write up. a must-read for anyone even thinking about flashing
Original Post updated to add my information
bobbylx said:
ADB reboot download is nice, but if you are stuck at ATT logo
Click to expand...
Click to collapse
Ok first off something that should be added to this is always may sure you have usb debug mode Settings>Applications>Development>USB Debugging enabled on your phone. Don't take it out of debug mode. This will allow you to issue adb commands if you have.
If you are getting to the att logo screen and not beyond that and you have debug mode enabled then you can use adb to reboot into either recovery or download mode.
Steps
1: Get the command prompt up and que up the adb command you want to issue either reboot download or reboot recovery. Don't press enter yet.
2: When the att screen comes on your pc should make a notification sound that the device is connected.
3: On the second notification sound issue your adb command and the phone will reboot into the mode you selected.
Mileage may vary but should work.
This has saved me a few times.
STICKY
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks for the extra info. Malfuncion, awesome write up with pics, I'll add to first post later. I always forget about adding a system variable.
Sparker366, thanks, I always thought that at the ATT screen adb didn't, but you know what, I never tried.
I figured since I'm not a dev and don't have that knowledge I would try to help start this up to contribute a bit. And honestly, if you hop over to the QA sections there are so many threads that could be solved by knowing this info ahead of time. I doubt everyone will read it, but I hope it helps the ones that do.
bulletproof1013 said:
STICKY
Click to expand...
Click to collapse
+1
This is my first smart phone and first experience with Android. I also don't have any experience with linux. Fortunately, I was able to avoid problems when I first started by reading, reading, reading. This type of information would have been invaluable. In fact, the tip on keeping debug mode on all the time is great to know, and I never saw that before.
Sent from my SAMSUNG-SGH-I897 using XDA App
This thing is getting buried in the BS posts....BACK TO THE TOP!
definitely sticky
Bump Bump Bump
Great Info
Updated original post with extra info.
Shameless bump here. New version of Cog uploaded, so that means there will be questions soon.
Thanks, great info.
FWIW........
I feel like I am of average intelligence, and would think I could nail download mode everytime by the 3 button method, but damn if it is hit and miss for me every other time.
One way I found (I didnt discover it, but read it somewhere) to nail it EVERYTIME is to remove sd and sim. Plug the usb to the phone AND THE PC, while odin is sitting and waiting. Then while holding both up and down volume buttons, insert the battery. It works every time with no fuss.
Thanks for the post, my vote for sticky as well.
+1 sticky
Sent from my SAMSUNG-SGH-I897 using XDA App
Moving this to the top. More questions in QA that can be helped by reading these tips first.
I would also suggest that anyone who wants to flash actually test their phone's USB transfer ability before flashing.
The best way is to find a large file, perhaps one just under 2G in size and transfer it to the internal SD storage.
Test md5 checksums on the source and this file and make sure these match.
(you can use the 'md5sum <filename>' command from the terminal app, from Windows you can use a md5sum port for the source file win32 md5sum).
This will ensure your USB connection is stable enough for long, error free transfers to the phone.
Also important: it's useful to disable any powersave actions on your PC while using an app like ODIN.
Sorry all, moving this to the top. There are about 6 or 7 bricked phone Questions in Q & A now.
Awesome, clear and concise. Been trying to figure out how to make nandroid backups and this explained it very simply Thank you!
thanks for the reminder
there's so many steps to install a rom...
specially with download mode keycomb, i tend to not to remove sim and memory card cuz i dont want to lose or damaged my mcard. now i will remove each time!
another good reason flashing stock with odin before flashing new rom
I would also say its a good idea to back up your efs folder. Mine got all borked up when that jpc rom came out a while ago and it is a ton of work to fix. Sgs tools copies your nvdata.bin and. /nvdata.bak files to your sd card if you do a product code check. Or you can use root explorer.
Before you Begin:
This guide is a basic how-to for installing a custom ROM & its update for the Galaxy Tab 10.1v… For all those who struggled (like me)
Also, this is for Windows… If requested, I’ll dig up the Linux method.
REMEMBER: This is all done at your own risk.None of the people mentioned, or myself, can be held responsible for any damages caused! Following these steps will void your warranty.
If you are not comfortable, don’t do it!
Always keep a backup of your data; it will get lost at some point during this!
(Titanium Backup, Rom Manager etc can create backups… use ‘em!)
This guide assumes you’ve already unlocked & rooted your Tab. If you haven’t, check these threads:
(Much thanks to these gents!)
Bcmobile’s unlock thread
Chainfire’s unlock thread
Bcmobile’s rooting thread
I recommend Chainfire’s method to unlock – you get a stock ROM (unlocked) + ODIN3 in case something goes pear-shaped…
PM me if there is something I’ve missed, need to take down or redo.
I do not provide support for the ROM(s)/ programs mentioned; go to the appropriate thread (list at the end).
Above all: have fun and thank the devs who put in so much time!
Required Packages:
Java SDK – found here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Android SDK – Found here:
http://developer.android.com/sdk/index.html
USB Drivers – install via Android SDK Manager. See here:
http://developer.android.com/sdk/installing.html
(USB Package r4)
USB Note:
After installing the drivers via the Android SDK Manager, navigate the folder where you installed the Android SDK, and look for a folder called ‘extras’. Open that, then open the folder ‘google’, then ‘usb_driver’. Edit the android_winusb.inf file and insert the following text under the section [Google.NTx86] (32bit Windows) or [Google.NTamd64] (64bit Windows):
========
;
;Galaxy Tab 10.1v
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&REV_9999&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_04E8&PID_6601
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
========
All other files needed are mentioned under their specific section.
Ok, now onto the good stuff…
===============================================================================
Installing a custom ROM:
(I’m using Seo’s ROM purely as an example, as it includes a wipe file and updates. You can use whichever rom you like/ want/ need. Just check the rom’s thread/ site for any special instructions)
This example uses the TB Galaxy ROM, it can be found here - http://forum.xda-developers.com/showthread.php?t=1155023
You’ll need to download V1.0 FULL ROM, whichever update you need/ want (this guide uses 1.0.9), and wipe.zip.
Place the downloaded .zip files in your Android SDK \tools or \platform-tools directory (whichever one has adb.exe in it)
[FONT="]1) [/FONT]Download and install Rom Manager from the Android Market (The free one is fine).
[FONT="]2) [/FONT]Open Rom Manager, and select ‘Flash Clockwork Mod Recovery’ (CWM). If you used bcmobile’s unlock method, you can use Rom Manager to back up your stuff, just remember to copy it off the Tab before moving on!
[FONT="]3) [/FONT]Once it has completed, connect the Tab (powered on) via USB (debugging enabled) and open a command prompt. Navigate to your Android SDK’s \tools folder and type:
adb devices
[FONT="]4) [/FONT]Now, push TB-Galaxy-1.0.zip to /sdcard/:
adb push tb-galaxy-1.0.zip /sdcard/
Copy the 1.0.9 OTA update zip as well as the wipe.zip using push.
Check the attached file for the pic...
(Mine has nothing listed after devices, as I didn't connect my Tab...)
NOTE: Seo’s instructions call for copying the file(s) to /sdcard/media/, but for some reason CWM does not let myself see that folder…
[FONT="]5) [/FONT]After it has copied, type:
adb reboot recovery
[FONT="]6) [/FONT]Once in Recovery, navigate with the volume keys, and select ‘Install Zip from sdcard’ with power button (TAP to select). Browse for the wipe.zip and select it. Select ‘Yes’.
[FONT="]7) [/FONT]After the has been completed, install TB-Galaxy-1.0.zip.
[FONT="]8) [/FONT]After it completes, navigate back to the first CWM menu and restart/reboot the tab. Be aware that the first boot may take a while.
[FONT="]9) [/FONT]If all is well, you should be seeing your new home screen… Check it out!
========
If you’re stuck in an endless bootloop or it gets stuck at the Samsung logo screen, go to chainfire’s unlock thread (link at top of page) and follow the steps there. You’ll have the stock ROM loaded back on, with the bonus of the bootloader being unlocked.
========
[FONT="]10) [/FONT]Update time… Connect the Tab via USB, enable debugging, open a command prompt and navigate to the Android SDK tools folder and reboot into recovery: adb boot recovery. Follow step 6, but select the OTA zip instead of wipe.zip.
[FONT="]11) [/FONT]Once that completes, reboot & enjoy. Done!
List of links/ threads:
Rom Manager:
https://market.android.com/details?id=com.koushikdutta.rommanager&feature=top-free
Packages/ Drivers:
Java SDK – found here:
http://www.oracle.com/technetwork/java/javase/downloads/index.html
Android SDK – Found here:
http://developer.android.com/sdk/index.html
USB Drivers – install via Android SDK Manager. See here:
http://developer.android.com/sdk/installing.html
(USB Package r4)
ROMs: (some to play with )
TB Galaxy thread by Seo:
http://forum.xda-developers.com/showthread.php?t=1155023
ISI-Galaxy thread by isimobile
http://forum.xda-developers.com/showthread.php?t=1223131
Rs HDBlog Galaxy thread by Rs125
http://forum.xda-developers.com/showthread.php?t=1200985
Thanks for this.
However to Windows users who just can't get the proper drivers to work (like my case, I tried every method for a week), just install Ubuntu. Way easier...
DannyBiker said:
Thanks for this.
However to Windows users who just can't get the proper drivers to work (like my case, I tried every method for a week), just install Ubuntu. Way easier...
Click to expand...
Click to collapse
You're welcome.
The fix by modifying the android_winusb.inf and pointing Windows to it cleared the problem for me, as did installing Samsung Kies and letting it auto-install the driver.
Otherwise, Ubuntu could work...
Yeah I know it works for most of people but check the latest posts in all the guids topics, I tried almost everything, doing things right but Xp or 7 could never connect to the tab.
I'm just saying, as an info, that if someone encounters the same issue, Ubuntu (or Linux) is the answer...
Works like a charm. Can I remove the .zip files afterwards?
Fadawah said:
Works like a charm. Can I remove the .zip files afterwards?
Click to expand...
Click to collapse
As long as you've checked that everything is working 100%... if it is, go ahead and remove them
Hi guys, time to cry for a little help here...
today I've managed to get 3.2 loaded on my p7100. everything went well and I was really enjoying it, until I got a crappy app that started to freeze the tab before I could remove it (AVG 2.9). I tried everything I could and after a "fastboot -w" the tablet entered in an endless loop mode, restarting all the time. I've fixed that flashing the stock rom using ODIN, but now I cannot get into clockworkmode to reload the 3.2 rom. every time I enter "fastboot boot recovery.img" (clockworkmode recovery image), it displays on the tab "Booting downloaded image" but doesnt go any further... dont know what to do now... it is working fine with 3.0.1, but I cant get 3.2 back.
thanks a lot for your help, it is much appreciated !!!!
Cheers
S.
Forgot to mention: trying to boot into recovery mode leads to a screen with the android dude and a big yellow exclamation mark (adb reboot recovery) and nothing else happens.
sitani said:
Hi guys, time to cry for a little help here...
today I've managed to get 3.2 loaded on my p7100. everything went well and I was really enjoying it, until I got a crappy app that started to freeze the tab before I could remove it (AVG 2.9). I tried everything I could and after a "fastboot -w" the tablet entered in an endless loop mode, restarting all the time. I've fixed that flashing the stock rom using ODIN, but now I cannot get into clockworkmode to reload the 3.2 rom. every time I enter "fastboot boot recovery.img" (clockworkmode recovery image), it displays on the tab "Booting downloaded image" but doesnt go any further... dont know what to do now... it is working fine with 3.0.1, but I cant get 3.2 back.
thanks a lot for your help, it is much appreciated !!!!
Cheers
S.
Forgot to mention: trying to boot into recovery mode leads to a screen with the android dude and a big yellow exclamation mark (adb reboot recovery) and nothing else happens.
Click to expand...
Click to collapse
Is your bootloader unlocked?
Sent from my GT-P7100 using Tapatalk
yep, I think so
Hi Isimobile, thanks for your help.
I believe it is unlocked (can see the open padlock when I turn it on, fastboot mode says unlocked and I even tried "fastboot oem unlock" once again to make sure). dont know what else to do. It seems there's something wrong with the restore partition (hope Im not saying anything nonsense here).
Cheers
S.
Thanks for the tip.
will someone please tell me why clockwork recovery is messing up my Tab? I rooted and unlocked, then went to install it through ROM manager. it says installed correctly I click the option to reboot into recovery and my Tab is suddenly bricked please help I have no backups and my Tab says the update failed and I need to select recovery in Kies. however Kies won't recognize my device
automaddux said:
will someone please tell me why clockwork recovery is messing up my Tab? I rooted and unlocked, then went to install it through ROM manager. it says installed correctly I click the option to reboot into recovery and my Tab is suddenly bricked please help I have no backups and my Tab says the update failed and I need to select recovery in Kies. however Kies won't recognize my device
Click to expand...
Click to collapse
Did you flash or boot recovery. Img
I had the same problem using rom manager when trying to get in cwm, exept i got the exclamation mark with the android.
I Let it rest for a while and it booted fine.
Don't know wich rom your on but you should first flash recovery then reboot in recovery..
Sent from GT-P7100 running android 4.0.3
Great ! Thank you ! It will help me to level up my 10.1v !
My tab after flasing doesnt wake up. Its mean that ot start and stock on boot samsung animation
I try flash it again but i still have the same sitiation
There is any option to upload all factory soft agaon. I eant to mantion that i wad try to recovery from backup but i get error for data files
Thanks in advance
Sent from my GT-I5800 using XDA App
Tab 2 10.1
Hi, does this same method work for the Samsung Galaxy Tab 2 10.1? I am trying to install the infected ROM on it. I would appreciate the help, as you can tell, I am new here!
Rooting your Samsung Galaxy S2 i9100
This guide is thanks to capaxdoli, I have just modified it slightly to make it easier to read
If you use this guide to root your phone please go and thank him here - http://forum.xda-developers.com/showthread.php?t=1126522
Also please give this page a read it is the basics of rooting and should be considered the starting point for all learning to root - http://forum.xda-developers.com/showthread.php?t=1125282
Also another thanks should go to Chainfire - For his great work on kernels http://forum.xda-developers.com/showthread.php?t=1103399
1. Make sure your phone has kies 2 and have it install all the drivers.
2. Connected phone for the first time to computer and kies 2 and it recognized it fine.
3. Make sure Kies 2 is also fully updated.
4. The details of my phone are as follows: (please check what yours are)
Samsung Galaxy S2 i9100 (only use on i9100)
Fireware – 2.3.4 (it will work on all 2.3.x Firmware)
Kernel = XXKI4 (the important bit is the Ki4)
You can find all this info out in Settings – about phone
5. A prayer to My Lord for safe rooting
6. Go to this page and read all, then select the Kernel that is a match to yours – here – http://forum.xda-developers.com/showthread.php?t=1103399
7. Since I have Ki4, i had chosen to download this file [CF-Root-SGS2_XW_ODD_Ki4-v4.0-CWM4.zip]
8. Downloaded odin3-v1.85.zip here - http://www.mediafire.com/?wezzl287wb9v9hu
Extract and open the file (no installation...gasp!)
Open and run Odin ready to root your phone
Now select PDA and find the kernel that you downloaded and select
9. You might need to extract the kernel to select it in the PDA
10. Put your phone in download mode (press volume down + ok key + power on), a warning about custom OS flashes, press volume up key to continue.
11. You have pressed volume up key and the phone says that it has entered ODIN mode. it also says the following:
a. product name: GT-i9100
b. Custom Binary Download : No
c. current binary : Samsung Official
d. it also shows the android logo (the robot - big size) and says downloading...Do not turn off target !!
12. After this connected the phone to the computer (remember it is in download mode) and the drivers were installed again.
13. Go to Odin and you should see that under ID.com, there is a yellow background box and it says 0:[COM13]. in the message box (lower left corner) it says <ID:0/013> Added!!
14. Make sure the re-partition box is not checked in odin.
15. Clicked the start button...
16. The phone should install your new kernel and then re-boot it should show a yellow exclamation mark when it reboots.
17. That’s it your phone is now rooted –
Please visit these pages to –
See what you can now do with your rooted phone – http://android.stackexchange.com/qu...my-phone-now-what-what-do-i-gain-from-rooting
How to remove the yellow exclamation mark on when your phone starts - http://forum.xda-developers.com/showthread.php?t=1103399
This is on the first page only the 2nd post down
For anyone who is intrested if you want to install Ice Cream Sandwhich (ICS) then vist this page here.
Most of your links are not working.
rutgerhoorn said:
Most of your links are not working.
Click to expand...
Click to collapse
Links fixed
How many more threads on this topic?
If people to time to search and read we would not need yet another thread on the subject...
Still thanks on your time
s.d.oconnor said:
Rooting your Samsung Galaxy S2 i9100
This guide is thanks to capaxdoli, I have just modified it slightly to make it easier to read
If you use this guide to root your phone please go and thank him here - http://forum.xda-developers.com/showthread.php?t=1126522
Also please give this page a read it is the basics of rooting and should be considered the starting point for all learning to root - http://forum.xda-developers.com/showthread.php?t=1125282
Also another thanks should go to Chainfire - For his great work on kernels http://forum.xda-developers.com/showthread.php?t=1103399
1. Make sure your phone has kies 2 and have it install all the drivers.
2. Connected phone for the first time to computer and kies 2 and it recognized it fine.
3. Make sure Kies 2 is also fully updated.
4. The details of my phone are as follows: (please check what yours are)
Samsung Galaxy S2 i9100 (please only use this guide for this phone)
Fireware – 2.3.4
Kernel = XXKI4 (the important bit is the Ki4)
You can find all this info out in Settings – about phone
5. A prayer to My Lord for safe rooting
6. Go to this page and read all, then select the Kernel that is a match to yours – here – http://forum.xda-developers.com/showthread.php?t=1103399
7. Since I have Ki4, i had chosen to download this file [CF-Root-SGS2_XW_ODD_Ki4-v4.0-CWM4.zip]
8. Downloaded odin3-v1.85.zip here - http://www.mediafire.com/?wezzl287wb9v9hu
Extract and open the file (no installation...gasp!)
Open and run Odin ready to root your phone
Now select PDA and find the kernel that you downloaded and select
9. You might need to extract the kernel to select it in the PDA
10. Put your phone in download mode (press volume down + ok key + power on), a warning about custom OS flashes, press volume up key to continue.
11. You have pressed volume up key and the phone says that it has entered ODIN mode. it also says the following:
a. product name: GT-i9100
b. Custom Binary Download : No
c. current binary : Samsung Official
d. it also shows the android logo (the robot - big size) and says downloading...Do not turn off target !!
12. After this connected the phone to the computer (remember it is in download mode) and the drivers were installed again.
13. Go to Odin and you should see that under ID.com, there is a yellow background box and it says 0:[COM13]. in the message box (lower left corner) it says <ID:0/013> Added!!
14. Make sure the re-partition box is not checked in odin.
15. Clicked the start button...
16. The phone should install your new kernel and then re-boot it should show a yellow exclamation mark when it reboots.
17. That’s it your phone is now rooted –
Please visit these pages to –
See what you can now do with your rooted phone – http://android.stackexchange.com/qu...my-phone-now-what-what-do-i-gain-from-rooting
How to remove the yellow exclamation mark on when your phone starts - http://forum.xda-developers.com/showthread.php?t=1103399
This is on the first page only the 2nd post down
For anyone who is intrested if you want to install Ice Cream Sandwhich (ICS) then vist this page here.
Click to expand...
Click to collapse
nice and thanks =)
York666 said:
nice and thanks =)
Click to expand...
Click to collapse
Not a problem - dont forget to thank the revelent people
This Work in 2.3.5 Too, i tested.
Does it work on 2.3.6?
Yes. 10 cha
abbadipod said:
Does it work on 2.3.6?
Click to expand...
Click to collapse
abbadipod said:
Does it work on 2.3.6?
Click to expand...
Click to collapse
Yes it will work on 2.3.6
Yes there already are A LOT of threads about rooting ... AND there are much easier way to get root than the one you explain!
This is especially handy if you'r new to this and just want root access to your stock SGSII:
[ROOT]How to ROOT Galaxy S2! [1-Click Root][Video Tutorial][No Odin required]
Seems pretty complicated with all those steps and there are easier methods i think.. but thanks anyway =]
I used the Easy rooting toolkit (v4.0) made by DooMLoRD. It works and as it is named really easy.
- install driver on PC
- download odin
- download rooted kernel
- open odin and select PDA and find the kernel
- put your phone in download mode
- start
But some of us don't like ODIN, or would prefer to do it in another way, or want to keep our existing ROM.
Like me for example... I'm quite happy with the regular SGS2 ROM, doubt that I have anything to gain with a custom ROM, and just want to be rooted...
chanrocky said:
- install driver on PC
- download odin
- download rooted kernel
- open odin and select PDA and find the kernel
- put your phone in download mode
- start
Click to expand...
Click to collapse
very sumple way like it +1
Where can i find the Samsung drivers for Galaxy S II ? In my windows 7 its doesn't recognize usb drivers.... It shows CDC SERIAL MISSING AND ALL...
Sent from my GT-I9100 using Tapatalk
chanrocky said:
- install driver on PC
- download odin
- download rooted kernel
- open odin and select PDA and find the kernel
- put your phone in download mode
- start
Click to expand...
Click to collapse
Then use jig to get rid of triangle and reset flash counter to 0.
Might seem like a few steps but after you have done it once the next times will only take a minute or two.
Don't like Odin or don't want to use it? Well I bet at some time you do use it. Odin doesn't use an exploit, it's a flashing tool so you can be more confident that the flashed kernel will work to root your phone.
Once you have root don't forget to do a nandroid backup using CWM. Restoring a backup is the easiest way to downgrade from things like ICS.
Happy rooting and flashing....
Sent from my GT-I9100 using XDA App
does this also install CWM ? thanks.
slamming_sammy1 said:
does this also install CWM ? thanks.
Click to expand...
Click to collapse
Yes it comes with CWM and super user, providing you use one of chainfire's kernels.
I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell
bennatpjose said:
I lost my root after the official firmaware upgrade now i cannot root it . Please help I have tried everything in XDA please help..... frustrated as hell
Click to expand...
Click to collapse
have you tried to flash a pre-rooted JB?
Sabyn said:
have you tried to flash a pre-rooted JB?
Click to expand...
Click to collapse
is there a guide somewhere
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
to flash a version of JB? come on my page , i can give you a link to my dropbox , there is anything you need
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
i also have an e617g on 4.1.2 bell network id like to root and unlock the bootloader so i can install cwm and finally swap roms, this is a nice phone but it barely exists on the web any help would be greatly appreciated, thanks in advance
Never mind figured it out myself. I may post a guide here soon. Seeing as any help I ask for is ignored. I'd rather help than hold back
Turn your lG-e617g into an LG-e610 then root it and install cyanogenmod.
bennatpjose said:
is there a guide somewhere
Click to expand...
Click to collapse
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
I had already tried that but i keep getting the bloody error in KDZ
03:58:19 : Launching SW update
03:58:19 : Unpacking KDZ
03:58:21 : KDZ file extraced
03:58:21 : Extract file error
03:58:23 : ===FINISHED===
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse
That happens when the kdz file is corrupted. Redownload the firmware and try again
its more than likely a bad connection causing a bad download also are you starting off with an e617g or e610?
Will all app data, contacts, etc. be lost using this method? Thanks in advance!
r4nd0m14m said:
this is my first tutorial so message me if something on here isnt clear.
step 1: download things, this is crucial, you need to download this stuff, it took me a while to find everything that ACTUALLY WORKED so i have it all in a nice little package to download.
step 2: make sure your phone is NOT plugged in the computer, install drivers if you do not have them. i have the drivers that worked for me in the package via direct download links. if they dont work for you somethings screwy with your computer and youll have to scour the internet to find drivers that'll work, google is your friend.
step 3: make sure your phone is recognised with your lappytop or computer. thats right i said lappytop, so sue me.
step 4nce all the drivers are installed and your phone is connected to the computer youll want to open up the folder labled: "LG FlashTool and Accessories" inside youll find "KDZ_FW_UPD.exe" open that right up.
step 5: next youll see a modded lg tool made by some guy on the internet, im not sure who but he/she did a good job thanks man/wo-man!!
ok youll want to leave all settings to default dont touch any thing, its good to go as is.
step 6: make sure phone is plugged in and usb debugging is enabled, use the kdz updater to browse for this file (download it via links in the package) "V10D_downgrade.kdz" then click on "Launch software update" this takes a while go make a coffee.
step 7: when its done its magic, your phone will boot up and youll see the LG logo for about 10 minutes any longer and your in a boot loop remove battery put it back in and hold both volume buttons down and power at the same time. time it carefully the lights on the soft keys will come on and a split second later the phone will slightly vibrate, the second you feel that press the home and hold it for about 10 seconds and the phone will do a hard reset, the phone will turn on now and initiate the first time use wizard, its in russian at first so just change your language to whatever, assuming english here. the phones software is now rooted just no su/superuser installed download from play store and update binary in settings of su app.
step 8: Unlocking bootloader time! after you flashed the software using kdz updater your phones ID is now technically an e610 now instead of an e617g, so unlocking the bootloader is now possible, connect your phone to computer, turn usb debugging on and drag and drop "emmc_appsboot.bin" into the root of your INTERNAL SD, also kill 2 birds with one stone here by also copying the recovery-clockwork-6.0.2.8-e610.img you downloaded via links in the txt document to the same place just rename it "recovery.img to make it easier also make sure you place the cm rom in the external sd. we need the bootloader unlocked to allow for cwm installation and good ol' rom swapping, open the folder "ADB" hold shift right click any where in the folder and select open "command window here",
type in the cmd window obviously without quotations: "adb shell" hit enter, then type "su" enter again then type "dd if=/sdcard/emmc_appsboot.bin of=/dev/block/mmcblk0p5" your bootloader is now unlocked, now type in "dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p17" this just installed clockwork mod. to boot into recovery and install cyanogen (the one im using. btw its a powerhouse compared to stock!!!) type in "reboot recovery"
step 9: factory reset, clear partition, wipe dalvik cache, install cyanogen, reboot, ENJOY.
seems i cant upload the programs needed so all i can do is this:
http://199.91.154.133/15ihz730pw2g/qwyqbfcp9fe7uhu/cm-10.1-20130725-UNOFFICIAL-e610.zip
this is the cyanogenmod rom.
http://199.91.154.102/r595o5bou5eg/bb2s0ohuj3jnflo/V10D_downgrade.kdz
this is the pre-rooted rom that allows su access to unlock bootloader this also
changes the phones id from e617g to e610, startup wizard is in russian at first simply change to english.
http://csmgdl.lgmobile.com/swdata/c...981MAN38AP22_ML_WHQL_Ver_3.8.1(0)_4.9.8.1.zip
this contains the correct drivers for phone.
http://dl.xda-developers.com/attach...65/51fc133a/1/7/5/6/7/5/9/CWM6_24-03-2013.rar
this is recovery image for cwm
and youll have to google search everything i quoted thats missing sorry about this but you need: 1) LG FlashTool and Accessories.
2) some form of adb for an adb shell.
3)emmc_appsboot.bin specifically for e610
4)lg drivers for e610/e617g
5)recovery.img for clockwork for e610
6)lastly the V10D_downgrade.kdz
Click to expand...
Click to collapse
yes definitely back up
r4nd0m14m said:
yes definitely back up
Click to expand...
Click to collapse
Does this method actually unlock the network too? Can I use fido sim card? would it work?
I have a Verizon Note 3 running Android 5.0, non-rooted (never had luck getting it rooted). As far as I know, the bootloader is locked. Here is all the information that I thought might be pertinent:
Model #: SM-N900V
Baseband version: N900VVRUEOF1
Android version: 5.0
Kernel version: 3.4.0
Build number: LRX21V.N900VVRUEOF1
Although I work in IT and am fairly comfortable with this sort of stuff, I have almost no experience when it comes to working with Android development / phones, etc.
The phone does not have a valid SIM card, nor do I have service for it. I use it just as a WiFi device and I don't care if it ever works for phone/SMS/MMS again. That being said, I would really like to be able to (a) root the phone and (b) load the Resurrection firmware that I've read about that would allow me to run Marshmallow.
Is there someone who is willing to take me "under their wing," so to speak, and take me through what I need to do, step by step, to make this happen. I've read several posts, but they all assume a prior level of knowledge that I just don't possess. I'm confident that I could do this if I have a clear list of instructions and and understanding of what steps I need to follow to do this. Thanks in advance to anyone who could give me a hand.
Same problem here. Would appreciate help
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download USB Drivers and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download THIS tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download Samsung Unlocker N3
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Sczar said:
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download USB Drivers and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download THIS tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download Samsung Unlocker N3
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Click to expand...
Click to collapse
I tried this root method and all it does is put me in a boot loop.Goes to somethingiin recovery and just stays there until I manually reboot phone then get boot loop.Tried both 1 click versions.
Sent from my LG-D851 using XDA-Developers Legacy app
AtrixHDMan said:
I tried this root method and all it does is put me in a boot loop.Goes to somethingiin recovery and just stays there until I manually reboot phone then get boot loop.Tried both 1 click versions.
Click to expand...
Click to collapse
Try to do a factory reset in recovery mode. It will wipe all your apps and data and restore it to factory settings. The instructions you got from @Sczar are very good , so try again step by step if factor reset doesn't work to get you out of the boot loop.
S2_brickmaker said:
Try to do a factory reset in recovery mode. It will wipe all your apps and data and restore it to factory settings. The instructions you got from @Sczar are very good , so try again step by step if factor reset doesn't work to get you out of the boot loop.
Click to expand...
Click to collapse
I got it figured out.Had to use a different twrp and flash Samsung lollipop 01.
Sent from my LG-D851 using XDA-Developers Legacy app
Very new to this. Have a technical background but confused on the above steps. Completed all listed Note3 connected,odin started on phone, then progress stopped at 28 sec. Waited over an hour then crossed fingers and unplugged phone removed battery and restarted. Luckily it came back up. Any ideas on went wrong with root process? Help!!
Thanks in advance.
Sczar said:
Alright,
*First thing you need to do is enable USB debugging:
How?
On your phone Navigate to Settings > About Phone > scroll to the bottom > tap Build number seven (7) times. You'll get a short pop-up in the lower area of your display saying that you're now a developer. Then Go back (to the settings menu) and now access the Developer options menu, check ‘USB debugging’ and click OK on the prompt.
------------------------------------
(DONT plug your phone to your PC yet)
Download and Install.
------------------------------------
*2nd thing to do is Rooting your phone:
Download tool on PC > Run. then plug your phone to PC > Choose Version OF1 > Click Read phone info (Your phone will ask if the program can access your phone press YES on your phone)> Root. wait until its done. now you are Rooted.
------------------------------------
Here is the fun part (Unlocking your bootloader) All through the phone no PC required for this.
You need to use an SDCard for this and
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD)) So backup your MicroSD or use another one.
* Install Busybox on your phone (you can get it from the Playstore)
* Download
1. Install SamsungUnlockerN3.apk
2. Grant SU access
3. Click On Install SamBootloader Unlocker
4. Grant SU access
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
Keep in mind this method ((WILL WIPE YOUR EXTERNAL SD CARD))
Thats all. your N3 is rooted and bootloader unlocked
Click to expand...
Click to collapse
OK, made it to rooted. It came back up the first time while connected to the computer. I shut down to swap sd cards to put in an older one that isnt used and when I start back up all I get is Process System isnt responding in a white box. If I do nothing, the white square asking to quit or wait will disappear, I get the top bar with 4G, bars, battery level, and time, but black screen. If I swipe the screen with my finger, the desktop (for lack of better word) flashes on, then goes all black. In about 3-5 minutes it will restart again. Before it restarts on its own, I can hold the power button and it will give me the power off, restart, etc menu and allow restart.
EDIT: Nevermind... If it warns Process System is not responding, wait for the notification bar to appear, use the power button to get the restart menu and choose restart. Then it starts normally and is Rooted! THANK YOU! I will work on the rest tomorrow!
Oldguy64 said:
Very new to this. Have a technical background but confused on the above steps. Completed all listed Note3 connected,odin started on phone, then progress stopped at 28 sec. Waited over an hour then crossed fingers and unplugged phone removed battery and restarted. Luckily it came back up. Any ideas on went wrong with root process? Help!!
Thanks in advance.
Click to expand...
Click to collapse
Why are you using Odin?
Sczar said:
Why are you using Odin?
Click to expand...
Click to collapse
It just started, I assume, as a result of running the root program. I downloaded program from the suggested link. I ran it which installed files on my pc and made a desktop shortcut. I double-clicked the shortcut, the program started, I connected the phone via usb, and selected the scan button in the program. It found the phone and I selected install root. I then had a progress bar start in the program and a window opened on the task showing odin 3.10. The phone indicated that odin had started and said it was downloading, however, progress stopped at 28 seconds. Did I do something wrong? I would really like to get this thing rooted so I have control over it.
Thanks immensely for your help.
Oldguy64 said:
It just started, I assume, as a result of running the root program. I downloaded program from the suggested link. I ran it which installed files on my pc and made a desktop shortcut. I double-clicked the shortcut, the program started, I connected the phone via usb, and selected the scan button in the program. It found the phone and I selected install root. I then had a progress bar start in the program and a window opened on the task showing odin 3.10. The phone indicated that odin had started and said it was downloading, however, progress stopped at 28 seconds. Did I do something wrong? I would really like to get this thing rooted so I have control over it.
Thanks immensely for your help.
Click to expand...
Click to collapse
Are you on OF1 baseband and Build?
Sczar said:
Are you on OF1 baseband and Build?
Click to expand...
Click to collapse
Yes on both accounts. Because I had no intent to flash a new ROM and only wanted to root I did not have an SD card in the phone. Could this be affecting the process?
Oldguy64 said:
Yes on both accounts. Because I had no intent to flash a new ROM and only wanted to root I did not have an SD card in the phone. Could this be affecting the process?
Click to expand...
Click to collapse
If you just want to root your phone you only need to run the root program on your pc. You DO NOT use odin. If I'm reading your post correctly you are saying the odin program is starting automatically? That should not happen. SD card should not matter if you just root.
Yes it is starting automatically. Any ideas why. Going to search registry on computer to see if it might be on there. Does Samsung Kies use Odin in any manner. I do have Kies on the computer. Grasping at straws I know. Thanks for the help you folks are great.
Oldguy64 said:
Yes it is starting automatically. Any ideas why. Going to search registry on computer to see if it might be on there. Does Samsung Kies use Odin in any manner. I do have Kies on the computer. Grasping at straws I know. Thanks for the help you folks are great.
Click to expand...
Click to collapse
I have no idea why odin would start on its own. If you would like to, uninstall Odin so you can root your phone without any interference from Odin. Samsung Kies DOES NOT use Odin. Samsung Kies is its own separate program from Odin.
If all you want to do is root the phone follow Sczar post and run the root program again it should only take about 1 minute tops to root phone.
Tried one more time. Stopped in exactly the same place as multiple times before. As far as Odin goes; after downloading the root file and running it, it extracted a number of files and created a directory in my program files directory on my pc. One of the files extracted was Odin.exe. Also the program does not automatically detect my phone or ask me to select OF1. I have to select a scan button and it then populates the fields showing the build. I select install root and all goes good,like I have mentioned until 26 or 27 seconds of progress has occurred the the program stops. My phone shows Odin has started and says it is downloading not to turn off, but nothing ever writes to the phone. I have to get into the task manager on the pc to stop the processes dealing with the root program as it becomes totally unresponsive. I have to kill adb also. I am totally baffled and about ready to give up. Wish I had stayed with Motorola at least that phone I was able to root. I have been holding off the new software update for days but may just let it fly unless someone has any other ideas about why this thing stops. Thanks to those who have tried so far.
Oldguy64 said:
Tried one more time. Stopped in exactly the same place as multiple times before. As far as Odin goes; after downloading the root file and running it, it extracted a number of files and created a directory in my program files directory on my pc. One of the files extracted was Odin.exe. Also the program does not automatically detect my phone or ask me to select OF1. I have to select a scan button and it then populates the fields showing the build. I select install root and all goes good,like I have mentioned until 26 or 27 seconds of progress has occurred the the program stops. My phone shows Odin has started and says it is downloading not to turn off, but nothing ever writes to the phone. I have to get into the task manager on the pc to stop the processes dealing with the root program as it becomes totally unresponsive. I have to kill adb also. I am totally baffled and about ready to give up. Wish I had stayed with Motorola at least that phone I was able to root. I have been holding off the new software update for days but may just let it fly unless someone has any other ideas about why this thing stops. Thanks to those who have tried so far.
Click to expand...
Click to collapse
I'm starting to figure out what you are saying is going on (I think).
1. Forget about Odin you do not use it, at all for root.
2. If I'm right your "phone" is going into DOWNLOAD MODE automatically that is what it should do.That is not Odin running. That's how your phone programs itself.
Quick checks
1.Make sure you have latest drivers from Samsung installed.
2. check USB debugging is on.
3. Install Arabic Tool For rooting on PC.
http://www.mediafire.com/?pvm1reerboz2c25
4. Open Arabic tool,
5. plug phone into PC make sure you connect as MTP not installer mode.
6. Click on Version, select OF1 (make sure your firmware is running on OF1)
7. Click Read Phone Info. (Your phone info should fill in the blanks)
8. HIT ROOT.
Your phone should go into "Download Mode" not Odin (a little green dude should be on the screen) automatically. Let the program do its thing. Then it will reboot your phone automatically, and if everything goes correctly it should say your rooted!.
9. It should take about 1 or 2 minutes to complete.
10. If it doesn't work try it again. It took me 2 tries for it to work right.
Everytime I've tried rooting my SM N900V with this Yemen tool I get hard bricked. To fix that issue I just put phone in odin mode and flash the OF1 firmware and everything is back to normal but still no root. Any suggestions?
mdj8606 said:
Everytime I've tried rooting my SM N900V with this Yemen tool I get hard bricked. To fix that issue I just put phone in odin mode and flash the OF1 firmware and everything is back to normal but still no root. Any suggestions?
Click to expand...
Click to collapse
Try the Arabic tool I posted above ^^^. I rooted my phone 3 times with no problems. I've not used the Yemen root method.
I made it to root, but the bootloader is not replacing so I am evidently missing an obvious step.
Samsung Note 3 SM-N900V 0F1 firmware
1. Install SamsungUnlockerN3.apk
2. Grant SU access (How do I do this? It is not asking anything)
3. Click On Install SamBootloader Unlocker
4. Grant SU access (Again, how do I do this? It is not asking anything)
5. Type Yes Hit enter wait for device to power off. Then pull the battery out > Battery back in then power on the phone.
6. Should be unlocked
It says it works, it shuts down and I remove the battery, and I reboot. However, as soon as I install TWRP and allow it to reboot I get the unauthorized software message from Verizon, use Kies to save, use Odin to reflash 0F1, root again, and now what? Why is the actual bootloader not being installed? How do I enable superuser?