Hi!
This kernel enables custom boot animations (/system/media/sanim.zip), adb root, init.d support, runs a script to auto-root your /system partition, and then you're on your merry way
You may need the USB Drivers available here. (Support & Downloads for SGH-I717)
Once the USB Drivers are installed, power off the phone, then hold volume down and power it on, you'll get a screen asking you to hit vol up to continue, do so. This puts the phone in download mode.
Stick the provided pda.tar in the PDA box of Odin3 1.85, flash away!
Install Superuser from the market after booting.
Note that this will increase your flash counter, which is presumably used by Samsung as a reason to decline warranty service (not aware of any reports of this occuring yet...?)
Don't forget the donate link in my signature if you found this useful and want to motivate me to work on overclock/undervolt
Thanks, Good job.
Sent from my LG-P925 using xda premium
nice work Da_G
Nice work!!! Im just waiting my Note...
Sent from my SGH-I727 using Tapatalk
Dang what a beast!
Sent from my Galaxy Nexus using Tapatalk
Da_G said:
Hi!
This kernel enables custom boot animations, adb root, init.d support, runs a script to auto-root your /system partition, and then you're on your merry way
You may need the USB Drivers available here. (Support & Downloads for SGH-I717)
Once the USB Drivers are installed, power off the phone, then hold volume down and power it on, you'll get a screen asking you to hit vol up to continue, do so. This puts the phone in download mode.
Stick the provided pda.tar in the PDA box of Odin3 1.85, flash away!
Install Superuser from the market after booting.
Note that this will increase your flash counter. Don't forget the donate link in my signature if you found this useful and want to motivate me to work on overclock/undervolt
Click to expand...
Click to collapse
This should work on the Canadian versions, right? Or would this be AT&T specific?
excellent job! Here a little something
Confirmation number: 0P6459745L809882G
@goalcam:
The kernel is built from AT&T source. I haven't examined the Canadian source yet, I'll take a look and see if it'll work.
@bkeaver:
Appreciated!
Any chance a jig from the SG2 will reset the counter?
More than likely not, due to the bootloader revision.. however since my counter is already up in the dozens I can look at putting some time into finding where the counter is stored, so that we can wipe it at will
OK what am I doing wrong. I installed super user from the market and this is what I am getting....
Sent from my SAMSUNG-SGH-I717 using xda premium
OK, followed directions precisely. Installed Superuser from Market and get the following:
su binary vnull
When trying to update:
Checking installed version = legacy
Fixing database... okay!
Checking for busybox... not found
Downloading custom busybox... okay!
Checking md5sum... okay!
Checking current install path... fail!
Failed to find currently installed su binary. Update cannot continue.
Checked, and the flash count shows 1 with new image, and the new boot animation is showing up.
If I can screw something up, I will.
Any ideas?
oops, let me revert my current root and try again, i'll have a fixed v2 up in two shakes!
in the mean time, if you are familiar with adb you should have root access in adb.
Odin
Thanks Gabe !
Thanks Da_G Works Perfectly.
eoh7678 run DoomLord's root after installing the kernel it installs superuser correctly.
Ajairola
ajairola said:
Thanks Da_G Works Perfectly.
eoh7678 run DoomLord's root after installing the kernel it installs superuser correctly.
Ajairola
Click to expand...
Click to collapse
Confirmed! Running doomlord's root correctly installed su/busybox.
Awesome job!
ajairola said:
Thanks Da_G Works Perfectly.
eoh7678 run DoomLord's root after installing the kernel it installs superuser correctly.
Ajairola
Click to expand...
Click to collapse
Thanks for the idea. This worked perfectly...
Sent from my SAMSUNG-SGH-I717 using xda premium
Ok, it was a simple typo in the root script that prevented su and busybox from being installed properly, oops!
Fixed now in the first post, back to regularly scheduled programming.. look for Overclock/Undervolt soon
Da_G said:
Hi!
This kernel enables custom boot animations, adb root, init.d support, runs a script to auto-root your /system partition, and then you're on your merry way
You may need the USB Drivers available here. (Support & Downloads for SGH-I717)
Once the USB Drivers are installed, power off the phone, then hold volume down and power it on, you'll get a screen asking you to hit vol up to continue, do so. This puts the phone in download mode.
Stick the provided pda.tar in the PDA box of Odin3 1.85, flash away!
Install Superuser from the market after booting.
Note that this will increase your flash counter. Don't forget the donate link in my signature if you found this useful and want to motivate me to work on overclock/undervolt
Click to expand...
Click to collapse
What does increasing a flash counter do? Forgive a noob.
@SPtheALIEN: Replied in first post.
Related
Hi
I looked around and saw a few ppl having trouble while rooting vibrant.
I've put update.zip on /sdcard, and when i reboot my phone in recovery mode it says something about my package not being signed.
So i googled and did this:
java -classpath "/home/ohai/Downloads/android-sdk-linux_86/tools/sign/testsign.jar" testsign update.zip file-signed.zip
(don't worry, i'm not that stupid, i DO have the sdk and the testsign installed here)
then renamed file-signed.zip to update.zip and replaced it on /sdcard, but still got the same message.
Does anyone have a link to a actually working update.zip to vibrant's froyo?
i'm using froyo.UVJL4, downloaded from samfirmware.com.
Thx in advance
?
Sent from my SGH-T959 using XDA App
Everyone's update.zip is usually different is what i'd think.
try getting titanium backup, click menu and click menu, and then CREATE update.zip
that might help you out.
Go to dec section and look for the jl4 rom from geodude(cant remember exact name...) His rom, odex or deodex both come prerooted with the 3e recovery fix as well. Flash that. KTB.
Sent from my SGH-T959 using XDA App
If you are comfortable using the voodoo lagfix you can flash the new voodoo 5 kernels. They come with the SU binary and clockworkmod recovery built in. Then download busybox and superuser from the market. You'd have to flash via ODIN though.
Thx for the tips, but i was not thinking about using modified roms... all i want is to root my default rom from samsung, is it possible?
You need the correct key to sign the zip file. My understanding is this key was not released by Samsung so you will not be able to sign your update.zip files to work with the 3e recovery.
The 2e recovery accepted a "test key" which is why we're able to use update.zip to root and use CWM.
The RATC method still works for rooting in the 2.2 Firmware. You can use SuperOneClick to root, and then replace the stock 3e recovery with the one from here. This is a modified 3e recovery which removes the signature checking.
How about trying the ALT METHOD in the Noob Guide (my signature)... then flash a stock rom with root?
http://forum.xda-developers.com/showthread.php?t=857974
personally, you are hurting yourself by not running a rom like Nero v3 or Eugenes Ginger Clones.
Rooting T-Mobile Vibrant Froyo 2.2 JL5
I have the T-mobile Vibrant US Phone. I upgraded to JL5 and have rooted my phone with a program from here:
http://forum.xda-developers.com/showthread.php?t=803682
Get the latest version and you might have to run the program 2 or 3 times for it to finish. Note on my phone these were the steps I took.
1. Put phone in USB Debugging Mode.
2. Plug usb cable to computer.
3. Run the rooting program above with windows administrator rights.
4. It will run then probably hang half way through and indicate WAITING FOR
DEVICE.
5. Shut windows program down.
6. Reboot phone (Turn Off then On).
7. Reconnect to usb.
8. Restart the Rooting Program and Root.
9. It should finish and ask if you want to test SU say yes.
10. That's It you should be good to go.
Hope this helps.
s15274n said:
How about trying the ALT METHOD in the Noob Guide (my signature)... then flash a stock rom with root?
http://forum.xda-developers.com/showthread.php?t=857974
personally, you are hurting yourself by not running a rom like Nero v3 or Eugenes Ginger Clones.
Click to expand...
Click to collapse
What's so good in those roms?
NihtSpi said:
I have the T-mobile Vibrant US Phone. I upgraded to JL5 and have rooted my phone with a program from here:
http://forum.xda-developers.com/showthread.php?t=803682
Get the latest version and you might have to run the program 2 or 3 times for it to finish. Note on my phone these were the steps I took.
1. Put phone in USB Debugging Mode.
2. Plug usb cable to computer.
3. Run the rooting program above with windows administrator rights.
4. It will run then probably hang half way through and indicate WAITING FOR
DEVICE.
5. Shut windows program down.
6. Reboot phone (Turn Off then On).
7. Reconnect to usb.
8. Restart the Rooting Program and Root.
9. It should finish and ask if you want to test SU say yes.
10. That's It you should be good to go.
Hope this helps.
Click to expand...
Click to collapse
JL5?
where did you get it?
atcasanova said:
What's so good in those roms?
Click to expand...
Click to collapse
You still can't get rooted & you want FroYo?
I attached cwm update.zip so just use that to get into CWM Recovery (Reinstall Packages, You may need to do it twice) and then just flash the following ROM
http://forum.xda-developers.com/showthread.php?t=881692
Master™ said:
You still can't get rooted & you want FroYo?
I attached cwm update.zip so just use that to get into CWM Recovery (Reinstall Packages, You may need to do it twice) and then just flash the following ROM
http://forum.xda-developers.com/showthread.php?t=881692
Click to expand...
Click to collapse
Sorry for being this dumb, but i don't have a clue of what is CWM
me too,
im desperately looking to root my vibrant from Bell canada. i just updated to JL2 using the kies pc software. i just got this phone for xmas so im quite new to it.
im hoping to find an app or website that can do most of the steps for me. or a youtube video with detailed step by step.
ive tried using the guide that s15274n wrote (btw, thanks for the awesome writeup) but i have the same problem of the update.zip file not passign the signature verifaction.
i would like to stay with a stock ROM for at least another couple weeks because of the super high chance of this phone bricking itself
my phone has a build date of 11.10
any thoughts?
thank you VERY much for any help
EDIT:
I have managed to root my phone! hurray!
heres how i did it:
i used the superoneclick method thanks to this link http://forum.xda-developers.com/showthread.php?t=803682
i used this guide to help me through the steps http://theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/
thanks to everyone to put in work to make this possible.
THANK YOU!
chucked said:
me too,
im desperately looking to root my vibrant from Bell canada. i just updated to JL2 using the kies pc software. i just got this phone for xmas so im quite new to it.
im hoping to find an app or website that can do most of the steps for me. or a youtube video with detailed step by step.
ive tried using the guide that s15274n wrote (btw, thanks for the awesome writeup) but i have the same problem of the update.zip file not passign the signature verifaction.
i would like to stay with a stock ROM for at least another couple weeks because of the super high chance of this phone bricking itself
my phone has a build date of 11.10
any thoughts?
thank you VERY much for any help
EDIT:
I have managed to root my phone! hurray!
heres how i did it:
i used the superoneclick method thanks to this link http://forum.xda-developers.com/showthread.php?t=803682
i used this guide to help me through the steps http://theunlockr.com/2010/10/11/how-to-root-your-android-phone-superoneclick-method/
thanks to everyone to put in work to make this possible.
Click to expand...
Click to collapse
So many people figure out what was wrong and they are done. Thank you for posting your finding, I have been trying to Root my Bell Vibrant for a while.
Use SuperOneClickRoot - http://forum.xda-developers.com/showthread.php?t=803682
Works all the time for Vibrant!
Instructions updated based on creepyncrawly's thread found here .
1.) How to root by using DooMLoRD's Easy Rooting Toolkit. (ZergRush Exploit) (Windows)
[*]Not working for KK6 2.3.6[*]
Download the "DooMLoRD's Easy Rooting Toolkit v3.0" package from this thread and extract it to a directory on your hard drive using WinZip or a similar program.
You need to have the USB drivers for SGH-I777 installed on your computer. (It will be "Samsung USB Driver for Mobile Phones" in Control Panel\Uninstall Programs.) Download and install the latest drivers from this thread. (x86 and x64)
Both USB Debugging (Menu\Settings\Applications\Development) and Unknown Sources (Menu\Settings\Applications) should be enabled on your phone.
Increase the screen timeout on your phone to 10 minutes. (Menu\Settings\Display\Screen Timeout) Remember to set it back to a shorter interval after you are done rooting.
Connect the USB cable to the phone and the computer. Go to the directory where you extracted the package and execute "runme.bat".
The toolkit will open a command prompt window where you will see the progress of the rooting process. It takes between 5 and 10 minutes for the process to complete.
Success. You're rooted.
2.) How to root by using SuperOneClick Root. (ZergRush Exploit) (Windows, Linux and Mac OS)
[*]Not working for KK6 2.3.6[*]
Download "SuperOneClick v2.3.1 - Automatic Driver Installation" from MultiUpload and extract it to a directory on your hard drive using WinZip or a similar program.
Please go the the SuperOneClick thread and read about the tool and how to use it. For Windows XP you need to have .NET Framework v2.0 or above installed. For Mac OS and certain flavors of Linux, you need to install Mono.
I have not tested this tool. It is included here because it claims to work for Mac OS and Linux, and provides a way to use the ZergRush Exploit on those operating systems. Since I am only familiar with Windows, I will be unable to support this rooting method. For problems, try posting questions in the SuperOneClick thread linked above.
If you try SuperOneClick on Linux or Mac, please post your (success or failure) results. Thanks.
3.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
I have prepared Odin3 One-click Downloaders for the Stock non-rooted and Stock + Root packages. Each One-click Downloader also contains the Modem. This will make flashing back to stock or flashing root in Windows easier. These were tested and flashed successfully on my device. These could be posted in the OP for convenience.
Odin3 One-click Downloader I-777 UCKH7 Stock + Root No Bootloaders
I777_UCKH7_OCD_Root_No_BL.7z
(This one-click downloader flashes: zImage, factoryfs.img with root, and modem.bin)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
How to Use:
Download the 7 zip package. Extract the contents of the zip file to a directory on your hard disk drive.
Start the Odin3 One-Click Downloader program by double clicking on "I777UCKH7 OCD No BL.exe" or "I777UCKH7 OCD Root No BL.exe".
Now Enter Download Mode:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
In Odin, the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]. The number could be different.
Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot.
Unplug the usb cable from you phone after it boots up. Success.
The above is from creepyncrawly, found here.
4.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from the command line using Heimdall (Linux and Mac OS)
Tested on Linux, should work on Mac OS
Download and install the latest version of Heimdall Command Line for your operating system from here. (Latest version 1.3.1 at this writing.)
Download Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package from here. Extract the PDA.tar file from this package to a directory on your hard disk drive, then extract the two component files from the tar - zImage and factoryfs.img.
Place zImage and factoryfs.img both in the directory where you have the Heimdall command line executable, and enter the following at the command prompt:
Code:
heimdall flash --kernel zImage --factoryfs factoryfs.img
Reboot the phone. Success. You're Rooted.
Super simple, Thanks!!
Do all the buttons and data connections work properly this kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App
dayv said:
Do all the buttons and data connections work properly this kernel?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Been running kernel for an hour no issues yet.
Cool should have my phone in a hour or two. Though I may hold off flashing till later on encase the development cause needs a virgin dump of something later on tonight.
Sent from my SAMSUNG-SGH-I897 using XDA App
dayv said:
Cool should have my phone in a hour or two. Though I may hold off flashing till later on encase the development cause needs a virgin dump of something later on tonight.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Yea sent them mine already. Have it on pc in case they need more.
Sent from my SAMSUNG-SGH-I777 using xda premium
Might wanna get rid of the screenshot that has the first app listed. Some may frown upon it... just saying. Anyways, thank you and I will have mine in 3 hours. Yay!
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
Probably a noob question, but pc drivers - are they the same as captivate or do I need to get new drivers? Link?
Thanks,
Bob
I can not for the love of God figure out why odin 1.8.2 is not recognizing my phone. I tried it first with debugging on, then off. Different ports. I know the drivers work because i can mount it and add or remove files from it. I get to downloading(do not turn off target) but Odin does not say COM1 or what not. Any suggestions/
I feel I missing something obvious, unless this driver is different then the captivate driver?
rbtconsultants said:
Probably a noob question, but pc drivers - are they the same as captivate or do I need to get new drivers? Link?
Thanks,
Bob
Click to expand...
Click to collapse
I'm pretty sure it uses the same drivers as the captivate. But I don't have the SGSII in my hands yet so I can't confirm.
---------- Post added at 10:15 AM ---------- Previous post was at 10:14 AM ----------
TheTodFather said:
I can not for the love of God figure out why odin 1.8.2 is not recognizing my phone. I tried it first with debugging on, then off. Different ports. I know the drivers work because i can mount it and add or remove files from it. I get to downloading(do not turn off target) but Odin does not say COM1 or what not. Any suggestions/
I feel I missing something obvious
Click to expand...
Click to collapse
What OS?
10 char
Windows 7.....
Did you open Odin as Administrator?
Graci, I haz rootz now.
Ok figured it out! Somehow the drivers were corrupted, I just re-installed them and all is good. I suspected it was causing the problem. Glad to get it fixed.
TheTodFather said:
Graci, I haz rootz now.
Ok figured it out! Somehow the drivers were corrupted, I just re installed them and all is good. I suspected it was causing the problem. Glad to get it fixed.
Click to expand...
Click to collapse
Do you mind linking to the drivers neccesary?
Done! not hard at all! thanks!!!
TheTodFather said:
Windows 7.....
Click to expand...
Click to collapse
Windows 7 sucks! I run it as parallel on my mac and I've had trouble with Odin many times. Whether its drivers,etc. Hopefully when I get home with my sgs 2 it won't give me any trouble
Sent from my SAMSUNG-SGH-I897 using XDA App
Super One Click doesnt seem to want to do the root. It attempts to start the daemon and then subsequently crashes.
Thoughts?
afroduck said:
Super One Click doesnt seem to want to do the root. It attempts to start the daemon and then subsequently crashes.
Thoughts?
Click to expand...
Click to collapse
Same for me... Odin goes smoothly but SuperOneClick crashes after closing and trying to restart adb
Hmm..
Two issues I am having with this. The first and most important is that I cannot seem to flash any other ROMs - or even other versions of Clockwork Mod with this. I get "signature verification failed". I've checked the MD5 of the downloaded files and it all seems to check out, so I'm unsure if this is intentional or not.
I've also now got an annoying big yellow exclamation point on boot. It doesn't really impede anything, but it is... absolutely infuriating how it stares at me with its yellowness.. It really isn't a big deal, though.
I'm going to try to reflash a third time, though, maybe it will solve itself.
Will this work with Heimdall?
Starting off i am a total noob when it comes to rooting…. so i followed a guide to root a galaxy s 2 but the i9100 model….so i rooted it and then i realized that i did the wrong model since the touch buttons werent working and all…so i looked for a i777 model and i followed that tut and rooted with the Clockworkmod and after i was done rooting evrything is fine….but the splash screen is still i9100 and yellow triangle and now i am also reading that u have to flash the roms back http://forum.xda-developers.com/showthread.php?t=1294574 like mentioned in there….....i dont know what to do now i just want my device to be a normally rooted device with everything working like before(EX. Splash Screen, Possibly Wrong ROMs?)….Please consider my noobyness and point me twords a step-by-step guide because i have already tried researching alot and i dont understand this stuff…. thank you so much for helping me.
dhaval33 said:
Starting off i am a total noob when it comes to rooting…. so i followed a guide to root a galaxy s 2 but the i9100 model….so i rooted it and then i realized that i did the wrong model since the touch buttons werent working and all…so i looked for a i777 model and i followed that tut and rooted with the Clockworkmod and after i was done rooting evrything is fine….but the splash screen is still i9100 and yellow triangle and now i am also reading that u have to flash the roms back http://forum.xda-developers.com/showthread.php?t=1294574 like mentioned in there….....i dont know what to do now i just want my device to be a normally rooted device with everything working like before(EX. Splash Screen, Possibly Wrong ROMs?)….Please consider my noobyness and point me twords a step-by-step guide because i have already tried researching alot and i dont understand this stuff…. thank you so much for helping me.
Click to expand...
Click to collapse
I did the Superoneclick as well and when I had the yellow triangle, you need a usb jig to get rid of it, but when I had the symbol my phone said SGS2 i9100 above the yellow triangle. The Yellow Triangle is just a counter on the phone from flashing a non stock kernel, the jig resets and it will say Samsung Galaxy S2 i777 again once it counter is reset. Just make sure when you buy one that it states for at least an sgs 2 i9100 *the one I bought from ebay said* and it will work.
HTH,
Charlie
Well thanks ... but I am a little worried about my Tom's and kernels..... I have no idea what they are but in the thread above he followed some steps to get his roms and kernels straightened out if I got of right.... but I have no idea what he is talking abt so how do I know if my rom and kernel are how they are supposed to be? And how do I fix them....? I feel like going back to factory firmware ( compleetely stock and then rooting again the right way...) please help me.....
Sent from my SAMSUNG-SGH-I777 using XDA App
Roms*
Sent from my SAMSUNG-SGH-I777 using XDA App
It's possible to get rid of the !/I9100 screen without a jig... Workarounds are linked from the first post of the FAQ.
Even if you have a kernel designed for our device, it will put up the I9100 screen if the last kernel flashed with Odin/Heimdall was something other than stock.
well i got that .... please verify what i am going to do before i sctually begin and mess up
1. Download The kernel + rooted system package from http://forum.xda-developers.com/showthread.php?t=1286432 (Does this also install busybox)
2. use Odin to flash it from download mode.
3.now this is the part i dont get in ur post here http://forum.xda-developers.com/showpost.php?p=18238883&postcount=106
U said:
Then flash this kernel using the method in http://forum.xda-developers.com/show...0&postcount=72
You may need to add "su" between "adb shell" and "dd" when on a stock kernel with rooted system.
Then always flash using CWM or the method above from then on.
Since i am a newbie, can u briefly tell me the steps i would do this... please? I really appreciate ur help.
Samsung Galaxy S II (SGH-I777)
Rooted stock + my kernel
Samsung Infuse 4G (SGH-I897)
CyanogenMod 7.1 (Built from source)
Galaxy Tab 10.1
Task650 KME v7.1 + Custom kernel based on Pershoot's OC kernel
Last device - AT&T Tilt2 (RHOD300) running XDAndroid FRX06
Click to expand...
Click to collapse
Also here in ur signature it says rooted stock+ my kernel... can u tell me what that means and the difference is between these methods:
--Method 1--Flash flashing codeworkx CWM then Super One Click(Method by jivy26)
http://forum.xda-developers.com/show....php?t=1285894
--Method 2--Flash through Odin(Method by Entropy512) *Flashes stock ROM with root*
http://forum.xda-developers.com/show....php?t=1286432
--Method 3--Flash codeworkx CWM then flashing through CWM(Method by Paulyhoffman)
http://forum.xda-developers.com/show...06&postcount=2
dhaval33 said:
….....i dont know what to do now i just want my device to be a normally rooted device with everything working like before(EX. Splash Screen, Possibly Wrong ROMs?)….
Click to expand...
Click to collapse
dhaval33 said:
well i got that .... please verify what i am going to do before i sctually begin and mess up
1. Download The kernel + rooted system package from http://forum.xda-developers.com/showthread.php?t=1286432 (Does this also install busybox)
2. use Odin to flash it from download mode.
3.now this is the part i dont get in ur post here http://forum.xda-developers.com/showpost.php?p=18238883&postcount=106
U said:
Then flash this kernel using the method in http://forum.xda-developers.com/show...0&postcount=72
You may need to add "su" between "adb shell" and "dd" when on a stock kernel with rooted system.
Then always flash using CWM or the method above from then on.
Since i am a newbie, can u briefly tell me the steps i would do this... please? I really appreciate ur help.
Click to expand...
Click to collapse
After you complete items 1 & 2 above, you will have returned the phone to stock, just like it was after it came out of the box, except it will also be rooted. If that is all you wanted to do, you can stop there. At this point, the yellow triangle will be gone, and the i9100 boot screen will be gone.
If you want to modify the phone further, you will need to add a kernel with clockwork mod recovery. However, if you flash a non-stock kernel with odin, the yellow triangle and i9100 boot screen will return. (I guess that's essentially what you did in the first place.) The method in item 3 above describes how to add a kernel without flashing in odin. You can actually do this one of two ways. 1) Using your pc, install the Android SDK, which will install adb.exe on you pc. (adb = android debug bridge). Then you can use adb from your pc to add the kernel to you phone over a usb connection. 2) From you phone, using Android Terminal Emulator. You can transfer the kernel image to your phone with usb, then use the terminal to add the kernel to your phone.
The advantage of adding a custom kernel is to make the phone run better, and to gain clockwork mod recovery. To educate yourself, you should read through Entropy512's Daily Driver kernel thread.
If you want to customize your phone further with a custom rom, you can flash anything from clockwork mod recovery without causing the yellow triangle or incrementing the flash counter.
Hope this makes things a little clearer. If you want to use adb or a terminal, you should be able to find lots of instructions in this forum, as well as elsewhere.
creepyncrawly said:
After you complete items 1 & 2 above, you will have returned the phone to stock, just like it was after it came out of the box, except it will also be rooted. If that is all you wanted to do, you can stop there. At this point, the yellow triangle will be gone, and the i9100 boot screen will be gone.
If you want to modify the phone further, you will need to add a kernel with clockwork mod recovery. However, if you flash a non-stock kernel with odin, the yellow triangle and i9100 boot screen will return. (I guess that's essentially what you did in the first place.) The method in item 3 above describes how to add a kernel without flashing in odin. You can actually do this one of two ways. 1) Using your pc, install the Android SDK, which will install adb.exe on you pc. (adb = android debug bridge). Then you can use adb from your pc to add the kernel to you phone over a usb connection. 2) From you phone, using Android Terminal Emulator. You can transfer the kernel image to your phone with usb, then use the terminal to add the kernel to your phone.
The advantage of adding a custom kernel is to make the phone run better, and to gain clockwork mod recovery. To educate yourself, you should read through Entropy512's Daily Driver kernel thread.
If you want to customize your phone further with a custom rom, you can flash anything from clockwork mod recovery without causing the yellow triangle or incrementing the flash counter.
Hope this makes things a little clearer. If you want to use adb or a terminal, you should be able to find lots of instructions in this forum, as well as elsewhere.
Click to expand...
Click to collapse
Wow thank you soo much thats exactly what i was looking for....that makes things a lot clear u have no idea...lol. What if i want to add themes and new boot screens in my phone would i still need to put clockworkmod ? what is the difference between the clockworkmod kernel and the entropy kernel? and finally wouldn't i just be able to flash the clockworkmod recovery from ROM manager? i also read on the faq not to use ROM Manager but that is how i boot into recovery so idk what to do. And would i be able to do this and still retain my apps, settings, my data and my unlock that i currently have?
dhaval33 said:
Wow thank you soo much thats exactly what i was looking for....that makes things a lot clear u have no idea...lol. What if i want to add themes and new boot screens in my phone would i still need to put clockworkmod ? what is the difference between the clockworkmod kernel and the entropy kernel? and finally wouldn't i just be able to flash the clockworkmod recovery from ROM manager? i also read on the faq not to use ROM Manager but that is how i boot into recovery so idk what to do. And would i be able to do this and still retain my apps, settings, my data and my unlock that i currently have?
Click to expand...
Click to collapse
Do NOT use rom manager on this phone. Clockwork Mod Recovery is built into the kernel. It is built into Entropy's Daily Driver kernels, and probably every custom kernel.
To enter clockwork mod recovery when you have a cwm kernel installed, just boot into recovery with the three button method.
Themes are usually added with cwm. Custom boot screen is done with a bootanimation.zip that is copied into the boot directory. Entropy's kernels also have boot animation support.
thanks i am going to do step 1 , 2 and then put entropy's kernel via adb.... but i didnt find any instructions on how to use adb to flash a kernel...
Download the kernel package and extract the zImage from it. After you install the SDK, put the zImage in the same directory as adb. Then run the commands in Entropy's post.
I suggest you read up on ADB first, so you have an understanding of the complete process.
Sent from my SAMSUNG-SGH-I777 using XDA App
thank you i got it now.... but i am still debating whether to use clockworkmod kernel or entropy daily driver kernel.... which one should i put on and what are the benefits in simple terms please... thanks
dhaval33 said:
thank you i got it now.... but i am still debating whether to use clockworkmod kernel or entropy daily driver kernel.... which one should i put on and what are the benefits in simple terms please... thanks
Click to expand...
Click to collapse
Entropy kernel includes clockworkmod.
Sent from my SAMSUNG-SGH-I777
Pirateghost said:
Entropy kernel includes clockworkmod.
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
codeworkx's goal with his CWM kernel was basically a "reference" kernel, as close to stock as possible but with CWM as far as I can tell.
Mine includes his CWM, but includes other features, look at my thread for details.
BTW, for some people, Droid Explorer happens to be an easy way to get adb working on Windows. I can't really provide any help beyond this as I'm a Linux user.
Entropy512 said:
codeworkx's goal with his CWM kernel was basically a "reference" kernel, as close to stock as possible but with CWM as far as I can tell.
Mine includes his CWM, but includes other features, look at my thread for details.
BTW, for some people, Droid Explorer happens to be an easy way to get adb working on Windows. I can't really provide any help beyond this as I'm a Linux user.
Click to expand...
Click to collapse
ok i got adb working by following adb for dummies guide but when i entered
adb push zImage /sdcard/zImage
it worked
but when i tried
adb shell dd if=/sdcard/zImage of=/dev/block/mmcblk0p5
it gave me permission denied
I searched for this but i found differenct phones not galaxy s 2 i777...Please help
anyone have a solution for permission denied.... i did go into terminal emulator and put in:
su
dd if=/sdcard/zImage of=/dev/block.mmcblk0p5
Recorded in
Recorded out
there was something else too but is that all i had to do? how do i know i put in that kernel?
What does settings, about phone, Kendal version say?
Sent from my SAMSUNG-SGH-I777 using XDA App
dhaval33 said:
anyone have a solution for permission denied.... i did go into terminal emulator and put in:
su
dd if=/sdcard/zImage of=/dev/block.mmcblk0p5
Recorded in
Recorded out
there was something else too but is that all i had to do? how do i know i put in that kernel?
Click to expand...
Click to collapse
Reboot and run CPU Spy. If the [email protected] for the build machine was [email protected], it's mine.
Access denied means you need root access. In adb shell you enter su and the prompt will change from $ to #. Then enter the dd command.
If you used terminal emulator you have to have the zImage on the root of the sd card or it won't work.
Sent from my SAMSUNG-SGH-I777 using XDA App
CF-Root is the root for "rooting beginners" and those who want to keep as close to stock as possible. CF-Root is meant to be used in combination with stock firmwares, and be the quickest and easiest way for your first root.
Donate
CF-Root has been available for many devices and has clocked over 16 million downloads. This is not even counting custom ROMs that already include it. Don't be a leech, buy me a beer (and use the "Thanks" button!). Imagine if every CF-Root user has donated me $1...
What's installed
- SuperSU binary and APK
- Nothing else, that's it.
Installation and usage
- Download the ZIP file (see post below for link)
- Extract the ZIP file
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolDown+Power to turn it on.
- Connect your device to your computer using USB
- Windows:
--- Run root-windows.bat
- Linux
--- chmod +x root-linux.sh
--- Run root-linux.sh
- Mac OS X
--- chmod +x root-mac.sh
--- Run root-mac.sh
- Follow the on-screen instructions - watch both the computer and the device !
Note that if your device had not been unlocked before, this procedure will wipe all your data !
Are you having fastboot driver issues? You can find fastboot drivers in many places, but the easiest way is probably just installing the Android SDK.
Did you see the red Android logo during rooting, but SuperSU does not appear? This may sometimes occur due to left-over files and settings, however, you can usually install SuperSU from Google Play at this stage and it'll just work.
Not included - adbd Insecure
As this CF-Root does not include a custom kernel, adb shell does not have root access by default (you can still get it by typing su inside the shell), nor is adb remount supported, nor will adb push and adb pull work on system files. adbd Insecure can be used to remedy this situation. (No idea what this is about ? Don't worry about it !)
CF-Auto-Root homepage
http://autoroot.chainfire.eu/
CF-Auto-Root main thread
[CENTRAL] CF-Auto-Root
For requests for new roots and generic discussion - please keep device specific discussion in the thread you are viewing now.
Download
flo (Nexus 2013 Wi-Fi): CF-Auto-Root-flo-razor-nexus7.zip
deb (Nexus 2013 LTE): CF-Auto-Root-deb-razorg-nexus7.zip
Very happy to see you here too. Thx for your work.
Sent from my Nexus 7 using xda premium
Chainfire said:
- Boot your device in bootloader/fastboot mode. Usually this can be done by turning your device off, then holding VolUp+VolDown+Power to turn it on.
- Connect your device to your computer using USB
Click to expand...
Click to collapse
For Flo, bootloader is volume down and power.
Newbie question - Once rooted with this method will I still get OTA updates? If so will it retain root?
Sent from my Nexus 7 using XDA Premium 4 mobile app
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
User_99 said:
Yes, you will get OTA
BTW, you will get OTA's also with custom recovery like CWM, but you cannot install it via custom recovery. For that you need Stock recovery
Click to expand...
Click to collapse
Thats not true... I got the 4.3.1 update for my deb and had root+twrp. After hit install it boot to twrp and installs the ota after boot up root is still there. No Problems here
Great that it works fine for you!
But that will work not for all customers. Some reported that after they recived and downloaded the OTA they got an error while installation in custom recovery.
I rooted my Nexus 7c LTE..
now i can see an unlock logo in startup... anywhere i can remove it?
thanks!
No, that's normal for unlocked bootloader. Only not shown when you close the bootloader again.
Thank you!
any idea how to close the bootloader?
http://www.wugfresh.com/nrt/
Nexus Toolkit - easy way to lock the bootloader. But, for Root, you need an Unlock Bootloader...
decide...
THANKS!!!
is the auto-root still working on new kit-kat update?
ritz_cal78 said:
is the auto-root still working on new kit-kat update?
Click to expand...
Click to collapse
Nope. Already tired twice.
so if i want to install TWRP recovery, i have to flash it after i install CF-auto root?
how do i get to the steps u mentioned using mac?
xdviper said:
Nope. Already tired twice.
Click to expand...
Click to collapse
It worked perfectly for me first try. I should say that I had just rooted my Nexus 7 LTE with Chainfire's method before I updated my N7 OTA. After the update, root was lost. I simply went through the steps again and re-rooted it. I should also state that I did not lose any of my data on during the 2nd root.
I'm going to donate to Chainfire.
same here, only difference,
I came from a factory image fash. Auto root worked
Send from the N7²
Will this work a stock n7 2 running KK?
xbs said:
Will this work a stock n7 2 running KK?
Click to expand...
Click to collapse
Worked OK for me.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
OP, is it okay if I don't have original factory sync cable in hands?
volibyro said:
OP, is it okay if I don't have original factory sync cable in hands?
Click to expand...
Click to collapse
Yeah its ok you just run into less issues with original cable.
**Working on updating links I have a slow upload speed though.
HideTheCookies said:
I got this device used and it had been updated to the newest firmware. It would not work with Kingroot, Framaroot, SRS, or Kingo. The only option was to attempt to downgrade to an older firmware with unpatched exploits. The Verizon J1 has a locked bootloader so it cannot flash full firmware packages with older bootloaders. Luckily it can be downgraded to older firmware of the same android version with older kernel. I just had to unpack the firmware and remove the bootloader and repack. I tried to make a rooted stock firmware but can't seem to repack the system.img.ext4 properly after mounting it.
Now let's get down to business
1. Download Odin 3.09
2. Download modified (by me) rootable firmware. Do not rename file it might mess up md5sum.
3. Boot phone to download mode. Hold power+vol down+ home.
4. Start Odin and connect phone with original factory sync cable.
5. Click on the AP button and select the firmware downloaded above. It will check the md5sum automatically when it finishes and passes then press the start button. Once the flash finishes it will reboot.
6. Enable usb debugging.
7. Download Kingoroot for PC (google) and let it run. The apk will not work to root. It should install drivers automatically.
8. Profit!!
I'm testing a method to reliably switch to Supersu but having trouble updating binary 100% of the time. I've tried to flash exposed but Flashfire doesn't seem to work properly with this device. If anyone can suggest a workaround please share.
Click to expand...
Click to collapse
If u want to switch to SuperSu from KingoROOT, the best and easiest method would be backing up ur phone and performing a soft reset. Afterwards simply install SuperSu, the superuser binary is already installed from kingroot - no worries, just update it normally via SuperSU and disable KNOX after the update is complete.
That switch idea of yours might get you bricked
Confirmed it works now we need a recovery so we can just flash su
SuperSUme works really really well lol, this phone is 32bit only any1 wanna try 4 a recovery?
Thxx bro
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
gravyd316 said:
I've tried porting a few times from the j100h twrp and keep getting a return to Verizon dealer screen. So I'd assume the bootloader is still locked. Im going to try the old safestrap and see if i can't get that working. But im kinda a noob so I'll do my best.
p.s. Don't try flashing any recovery until you backup your current one with rashr or flashify.BE SAFE.btw I've yet to see supersume actually work but hey it could happen. I'd much rather just flash the su from a recovery.
Click to expand...
Click to collapse
Agreed about flashing the recovery, but you need to be rooted with KingOroot to get SuperSUme to work, & it helps to just keep the screen timeout turned off thru this process , after it says "complete" I downloaded SuperSU & installed, updated, "disabled" knox, & I can also use flashfire although its pretty worthless for anything other than backups, as the little AROMA shell emulator thingy does run after the verizon logo is showing, which indicates to me yea its locked down pretty solid lol.
I tried Safestrap & it gave me a /SS folder in my /etc so I looked into that but I can't manage to figure out how I should go placing the files to make it work lol. But i do know this thing is 32bit ONLY, so compiling the j100H twrp for instance will NOT flash no matter what we do to the bootloader, it will bootloop since the architecture is for a 64bit SoC, we need someone to compile the j100H twrp in a 32bit only compatible architecture, & then you can easily flash it like cake, & TWRP should do the rest like all other Samsung phones O.O
its gotten to the point these are all the apps I have when i restore haha, if you wanna PM me about working together to get this thing a little more flexible I'm always open to ideas . I only use this thing as a hotspot but would totally like to see a recovery at least make it over & from there I could definitely start the ROM bringup
Will I get bricked by doing this with Verizon
Weegee1 said:
Will I get bricked by doing this with Verizon
Click to expand...
Click to collapse
you cant hard brick this device, restore with ODIN start over.
LilAnt530 said:
you cant hard brick this device, restore with ODIN start over.
Click to expand...
Click to collapse
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Weegee1 said:
I did it. I keep getting a notification that SE for Android has been turned off. What do I do
Click to expand...
Click to collapse
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
LilAnt530 said:
Download any terminal app & type in 'su' then 'setenforce 1'
---------- Post added at 12:42 AM ---------- Previous post was at 12:41 AM ----------
Download any terminal app & type in 'su' then 'setenforce 1' and you should be good.
Click to expand...
Click to collapse
THANKS! sorry last noob question, will I lose root if I turn my phone off
Weegee1 said:
THANKS! sorry last noob question, will I lose root if I turn my phone off
Click to expand...
Click to collapse
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
LilAnt530 said:
Haha believe it or not that's a pretty reasonable question! xD, you shouldn't, i cannot see why, if you have problems just restore i will help ya through it again, & if you want xposed ONLY use the material installer from xda
Click to expand...
Click to collapse
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Weegee1 said:
I'll get Xposed another time. I turned off my phone a couple times but the root stayed so that's a plus :victory:
Click to expand...
Click to collapse
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
LilAnt530 said:
If you havent used SUPERSUme to transfer it over to SuperSU, google the app, can't find the free one on play store anymore i guess.
Click to expand...
Click to collapse
And with SuperSU, is that one more stable