I have tried to root this firmware but I cant seem to be able, unless I flash a kernel. Id like a kernel that roots my device. I used semaphore but that gives me a black screen on the camera, so basically, id like a solution, to flash on odin for example that only roots my device while leaving everything else on stock.
Thanks in advance.
damian's kernel will work
some of the newer stock firmwares do not have enough system space for busybox and superuser to install -- the kernel needs to have a script that removes enough bloat to allow the root software to install
the kernel by itself will leave you rooted and with stock rom in place
lgsshedden said:
damian's kernel will work
some of the newer stock firmwares do not have enough system space for busybox and superuser to install -- the kernel needs to have a script that removes enough bloat to allow the root software to install
the kernel by itself will leave you rooted and with stock rom in place
Click to expand...
Click to collapse
Can you provide me a link my friend? I cant seem to find this kernel in xda.
EDIT: Found it, and also read about the history. Anyways, flashed it, same problem, black screen on camera. Man, Im destined to be unrooted forever...
Related
Hey Guys.. I'm looking for a "how to Root " on Bell's Stock UGKG3.
It seems in order to get root you must use CWM 2.5 and higher but KG3 overwrites with 3e Recovery. If I flash CF-roomt 1.3 through 4.1 I get looping boot screens.
Many searches later.. I'm here.
Can anyone help me out?
I9000M with UGKG3 flashed via ODin (I9000UGKG3-homebinary.tar) with stock 3e recovery BMC CSC.
Yes use the tornado kernel
Sent from my GT-I9000 using XDA App
haloimplant said:
Rooted KG3 kernel: http://www.megaupload.com/?d=410SOQHD or http://www.megaupload.com/?d=8DH9UR4L (first one comes up unavailable sometimes?)
Odin 1.82: http://www.megaupload.com/?d=1IKLKDPB
Just open Odin, put the tar file as PDA, put the phone in download mode, plug it in, wait for the box under ID:COM to go yellow and the 'added!' message and hit start. It will be done in a few seconds. Install superuser and busybox from the market to see if it works.
Like I said earlier it didn't work right away for me, superuser just FC'd on the first boot. Not sure if it was reflashing or rebooting that fixed it. Just a warning that some tinkering might be required.
Click to expand...
Click to collapse
10charrrrr
lgsshedden said:
Yes use the tornado kernel
Click to expand...
Click to collapse
It would be great if you could provide a link to this kernel, as it is not on XDA.
I found a link...
http://www.mediafire.com/?31hw11agky62dr2
PW: damiangto
But don't even bother.. once again I'm stuck on a boot loop!
haloimplant said:
10charrrrr
Click to expand...
Click to collapse
Thank you!
Root with no FC on SU.
haloimplant said:
10charrrrr
Click to expand...
Click to collapse
Sorry to bump an older thread, but I just have something else to add that might help someone else out.
I re-flashed stock UGKG3 to an i9000M, then grabbed the rooted kernel you linked to root. However, I had to manually download superuser and busybox installer from the Android Market - something I thought would happen automatically.
Hope this helps someone else!
hi brahmy
were you able to root your i9000 on this firmware?
managed to grab the file. thanks.
just wonder if you were successful after flashing this kernel
just lookin for some reassurances
Yes you do need to superuser and busybox from the market.
I'm seeing over 900 downloads of that kernel from megaupload, I didn't make it but I'm glad my instructions and download link helped so many.
haloimplant said:
Yes you do need to superuser and busybox from the market.
I'm seeing over 900 downloads of that kernel from megaupload, I didn't make it but I'm glad my instructions and download link helped so many.
Click to expand...
Click to collapse
thanks for the link.. going to try rooting now.
Am not getting root ... UPDATE: have root, but not busybox
So I re-installed the stock Bell UGKG3 kernel which worked great.
Then I installed this rooted one, more than once between reboots. I also got Busybox and TiShell from Market but I have no root
What might be going wrong?
Before I put the stock kernel back on, I was playing around with various kernels and with one of these kernels, I also updated the CSC and MODEM. Will this cause issues with this rooted KG3? I seem to not have problems with the stock KG3 that I re-installed using Kies.
Please help! No idea why everybody seems to be getting root with this kernel except me.
EDIT:
Ooooops looks like I may have had an out-of-date/dysfunctional Superuser app that was there from an old kernel update. I deleted it, re-installed from Market, and now I have root!!!
Now I have another problem: Looks like my busybox is also out-of-date. D/l'd busybox installer, it asked me if I wanted to install the latest, I said yes, but then it said I still have a version hanging around and I couldn't install.
So I opened my terminal and found one in /system/xbin. Did:
su
rm busybox
... but says the it's a read-only filesystem
How can I remove my old one that apparently exists somewhere and won't let the newly-downloaded busybox installer install a new one??
Stock ugkg3
I had the same problems with rooting my ugkg3, I used Darkyrom 10.2 Re. It rooted, put voodoo lagfix in, busybox, superuser. I didn't have to add any of those apps. I used odin to put it in. The only thing you have to do is reconfig your apn settings. Here is the link for darkyrom http://www.darkyrom.com/community/index.php?threads/odin-darkyrom-10-2-resurrection-gt-i9000.4272/, here is the link for the original stock firmware http://www.samfirmware.com/, and here is the link for the apn settings http://forum.xda-developers.com/showthread.php?t=799559, enjoy.
haloimplant said:
10charrrrr
Click to expand...
Click to collapse
The links you provided no longer work. Does anyone have any others?
Hi all this is my first post on this forum!
I would like to say that all the rest was very helpful but im having problems understanding few things and i wasnt able get any easy answer yet.
I am running on 2.3.4 and i have installed Kernel Speedmod K15T10 on my Samsung I9000 the version is XXJVR. I havent done anything else.
I understand from different programs that i try to install - that my phone is not rooted yet (i thought the kernel will root it).
My first question is, is it safe (by using the update file) to root my phone on this existing kernel or i need to do something special?
My second question is about ROM's can I install any ROM on this phone, or i need something that says in it's name XXJVR? because i saw that Darky doesnt have JVR but rather something else.
My final question if i decide to uninstall the ROM is it possible without damaging the Speedmod Kernel.
Thank you all ahead for the answers.
Your kernel does support root, you just need to activate it from the recovery.
go to recovery and there you will see advanced speedmod options (something like that - i dont remember) there you have the option to root your phone - root and install busybox i think it is called.
with this kernel you can flash other rom with out any problem. keep in mind to read the installation guides of each new rom you try.
each rom has it own kernel that comes with it, you can change it to another kernel.
I wanted to install the MUMI ROM over this kernel but i want to keep the speedmod kernel is it possible?
Installin the mumi ROM means that it will wipe all the apps in my phone? or?
modesty1987 said:
I wanted to install the MUMI ROM over this kernel but i want to keep the speedmod kernel is it possible?
Installin the mumi ROM means that it will wipe all the apps in my phone? or?
Click to expand...
Click to collapse
No you will not be able to keep the speedmod kernel if you flash muiu. I'm guessing you mean muiu. If you are keen to keen your current apps, look for titanium backup in the market.
If you are interested in the miui rom, I suggest that you do a lot more reading as its meant for experienced users at this stage.
Hey,
I want to revert back to stock 2.3.4 but I want to keep root and clockwork etc, so anyone know where I can get a stock 2.3.4 flashable zip?
Right now I am on CM7 latest
Thanks
i found this thread
http://forum.xda-developers.com/showthread.php?t=1061648
if i download this rom from the thread:
GRJ22 OTA (stock vanilla - odexed, unrooted):
http://www.mediafire.com/?shsmauak48b8hc4
MD5: 3B2B7B0BAAAA803365A573FC3864A150
is that the original stock 2.3.4?
anyone?........
The mediafire one is linked to a stock 2.3.4 that is deodexed that is still unrooted. If you want to read up on what deodexed means, check out this article.
http://www.addictivetips.com/mobile/what-is-odex-and-deodex-in-android-complete-guide/
You will still need to root this ROM.
In the thread, the top link is "stock" 2.3.4 but rooted and deodexed (along with the other things he mentions in the thread).
Basically, you have two options. Use PASSIMG to get your phone back to stock and update to 2.3.4. Then, if your bootloader is unlocked, you can flash a custom recovery and flash one of the many su.zip files out there that give you root access. This will truely be a rooted stock 2.3.4 install. If you want the easier route, use the link in the thread you referenced above.
I built one about a month ago for someone who wanted the same thing, but I'm struggling to find it...
EDIT: I've just thrown something together, if you still need it? Basically, I removed the stock recovery from the GRI40 and GRJ22 updates, so that you can flash them without losing recovery. You can then flash the su zip, and you will be updated, with root...
Tested, and it works...
The OTAs were just updates (about 5mb) from previous versions so there is not stock full system zip. You would probably need to flash stock 2.3.3 then you can flash the 2.3.4 update. Now there is also a 2.3.6 update that is flashed from 2.3.4.
danger-rat said:
I built one about a month ago for someone who wanted the same thing, but I'm struggling to find it...
EDIT: I've just thrown something together, if you still need it? Basically, I removed the stock recovery from the GRI40 and GRJ22 updates, so that you can flash them without losing recovery. You can then flash the su zip, and you will be updated, with root...
Tested, and it works...
Click to expand...
Click to collapse
Danger-rat,
please can you upload it.
I currently have 2.3.3 rooted somehow :S and it keeps FC sometimes and the default music app cant read my songs... but rootexplorer can. So i want to get a clean rom see if it all works. and ofc keep recovery.
As noted in the thread, this is something I've just thrown together. It's basically the full GRI40 update, and the GRJ22 update patch with the stock recovery and recovery restore scripts removed from both- this means your custom recovery will not be over written.
Backup your apps (Titanium, or whatever)
Boot into recovery.
Make a backup of your current ROM
Do a full wipe
Flash GRI40
Flash GRJ22
Flash the su zip
Reboot
Restore your apps...
Here are the files:
http://db.tt/mmzlv77
http://db.tt/VG9IVBgJ
http://db.tt/BJudP0L
xD
danger-rat said:
snip
Click to expand...
Click to collapse
sorry i just pm'd you and you've already replied ages ago. That tea break took longer than expected... thanks again !
/edit just figured it out i think. gonna give it a shot.
/edit2 i think i screwed it up, i was trying another stock rom i found and it seems to have done something, so i cant run my apps and do an app back up, which is no biggie from what i remember it just takes AGES to re-download. and set up settings etc. also no rom back up atm
but as long as i get back i hope its ok
YES thanks Danger-Rat
Brilliant help, absolutely no errors. just gotta restore apps and settings now.
Thanks again
How do I know if Boog's KI1/KI2 Kernel 2 was flashed?
Kernel version says: 2.6.35.7-I897UCKI1-CL607313
init.d folder contains only: S99complete
I have CWM so I'm assuming that Kernel 1 flashed properly through Odin3
I came from S7
flashed AT&T bootloaders and stock KI2
then flashed emunee's rooted/deodexed/zipaligned KI2
then flashed Boog's kernel 1 .tar with odin
now I'm trying to flash Boog's kernel 2 using CWM....
What am I doing wrong? any help would be appreciated
The name of the kernel will not change because no source released yet. Since u have CWM ur doing good. The kernels are flashing for u. No worries.
Sent from i897ucki2
Thanks for all the help, I have 2.3.5 w CWM and i know boog has an updated kernel w root. Should I put that in my sdcard directory and restart in recovery and install package? Would that root me? Thanks, Im pretty new to this and just flashed for the first time and am very happy but wanna get rid of all the ATT crap
Thank you for the prompt attention, what about the init.d folder shouldn't the scripts show up after flashing kernel 2?
Would it be advisable to simply flash U.A.S.?
El Niche said:
Thanks for all the help, I have 2.3.5 w CWM and i know boog has an updated kernel w root. Should I put that in my sdcard directory and restart in recovery and install package? Would that root me? Thanks, Im pretty new to this and just flashed for the first time and am very happy but wanna get rid of all the ATT crap
Click to expand...
Click to collapse
I think people have been having issues with boog's root kernel actually taking root from them rather then giving them root. I would advise the kernel swap method over flashing boog's rooted kernel for now.
NamDark said:
Thank you for the prompt attention, what about the init.d folder shouldn't the scripts show up after flashing kernel 2?
Would it be advisable to simply flash U.A.S.?
Click to expand...
Click to collapse
If done correctly in the proper order (kinda difficult not to) only one script should appear in the init.d folder. As for the USAS I recommend reading the link in my sig about Android Optimizations first.
Kyuta Syuko said:
I think people have been having issues with boog's root kernel actually taking root from them rather then giving them root. I would advise the kernel swap method over flashing boog's rooted kernel for now.
Click to expand...
Click to collapse
Thank you! For now I will wait a bit, I am using GO launcher so I hid all the ATT stuff.
Kyuta Syuko said:
I think people have been having issues with boog's root kernel actually taking root from them rather then giving them root. I would advise the kernel swap method over flashing boog's rooted kernel for now.
If done correctly in the proper order (kinda difficult not to) only one script should appear in the init.d folder. As for the USAS I recommend reading the link in my sig about Android Optimizations first.
Click to expand...
Click to collapse
I had come across the link to Pikachu's article in the Adrenaline Shot thread but in my laziness/arrogance I never took the time to read it!
Thank you guys for the help and information!
Hey guys, so I just recently updated my Cappy from 2.3.4 to 2.3.5 KK4 using a couple of the forums found here on XDA. Question, though:
I attempted to apply the Fugu Root Mod before flashing to 2.3.5. When flashed, it showed the red Fugu fish, and then bootlooped on me until I pulled the battery. After that, I flashed the 2.3.5 update. Apparently, Fugu has failed on part of my own error, because I don't have SU, BusyBox, or any of the Fugu mods, and the kernel in the phones "About" section shows "2.6.35.7-I897UCKK4-CL614489."
The question: I don't really care to give rooting another go, and I've discovered the "fugumod" folder in my SD's directory. Of course, the file tells me not to delete it, but is it safe to do so being that the root was not applied?
Thanks in advance!
Try installing SU app? At any rate I believe Corn kernel and samurai kernel have SU installer on cwm. I could be wrong but check it out
prbassplayer said:
Try installing SU app? At any rate I believe Corn kernel and samurai kernel have SU installer on cwm. I could be wrong but check it out
Click to expand...
Click to collapse
Installed the SU app from the market, but Root Check Basic still reports that my phone isn't rooted. Is it safe to just delete the "fugumod" folder in my SD directory, or is it worth a shot at reflashing Fugu? I pretty much manually restored my phones contacts, apps, etc before I noticed root was missing (I wasn't rooted before) and don't want to risk losing all my data.
Like I said, I don't mind not having root, I just figured I'd throw Fugu in there since I was wiping and updating my phone anyway.
You can try it. Odd it didn't work first go. But like I said there are 2 KK4 kernels that offer (or might) SU installer with CWM and tweaks.
Any risk in bricking if I delete the "fugumod" folder? It's telling me within the file that my phone won't reboot if deleted...but I'm not even Fugu rooted in the first place!
EDIT: Hmm...I didn't notice a KK4 with an SU installer. Could you point me in the right direction?
I honestly don't know never deleted that folder... like ever lol.
Hahaha that's what I was trying to find out in the first place, though! If I don't need the folder, I don't want it on my phone.
Searching would have found your answer, but here it is.
After flashing the fugumod kernel, you did the right thing pulling the battery. That kernel isn't designed to boot completely, just give you root. Where you were wrong was flashing the whole update. You should have flashed just the kk4 kernel. Once rebooted, you have the stock, rooted ROM.
mrhaley30705 said:
Searching would have found your answer, but here it is.
After flashing the fugumod kernel, you did the right thing pulling the battery. That kernel isn't designed to boot completely, just give you root. Where you were wrong was flashing the whole update. You should have flashed just the kk4 kernel. Once rebooted, you have the stock, rooted ROM.
Click to expand...
Click to collapse
Ahh, I see, thanks! So flashing the update removes the root, correct?
EDIT: Went ahead and just deleted the fugumod folder. No problems whatsoever, since I'm not rooted, of course.
Yomaster91 said:
Ahh, I see, thanks! So flashing the update removes the root, correct?
EDIT: Went ahead and just deleted the fugumod folder. No problems whatsoever, since I'm not rooted, of course.
Click to expand...
Click to collapse
Yeah, reflashing the update will wipe out the root, as well a factory reset.