[Q] Kernel installed, but phone not rooted? - Verizon Droid Charge

(Posted elsewhere but not answered.)
Okay, I'm relatively new to rooting. Working on a Samsung Charge, SCH-I510, baseband i510.06 V.EE4.
I had the phone rooted (via Gingersnap) on ED1, but then an OTA update moved me up to EE4 and undid my root.
I've since flashed my kernel (via CWM and Odin) to 2.6.32.9 (PeanutButta Jelly Time w/VooDoo lag fix) courtesy of imnuts, and it seems to be working great now. I'm clocking around 1490 on a Quadrant benchmark.
However, when I try to use Barnacle wifi tether, it says I'm not rooted "Barnacle requires 'su' to access the hardware! Please, make sure you have root access."
Titanium backup also shows that I'm not currently rooted.
Did I miss a step? Any suggestions?
Sorry for the noobage, let me know if you need further details.

well no you didn't miss a step. you need to flash a new rom using cwm or odin to get root back. EE4 to my knowledge is not rootable as of now.( i could be wrong.) I rooted and updated like you, then used odin to flash stock ee4 deboated.

sense the boot loader is unlocked. What should be done to get root is just flash a ee4 odin image for any one new to rooting or the charge.

I had to install busybox to make Titanium Backup work. Perhaps it's the same thing with Barnacle?

Related

[Q]flashing OTA update via Clockwork Recovery?

Ok.. I bought my Nexus S with 2.3.1 installed. I rooted it shortly after deciding I would keep the phone for awhile. According to all the guides I looked through, Clockwork Recovery won't stick unless that one file is renamed..
Well, come to find out, when I tried accepting the OTA update for 2.3.4, I somehow lost stock recovery and have Clockwork still installed. I've been running the stock software, stock kernel, with the bootloader unlocked and superuser installed. I never renamed the file in order to keep my stock recovery, just in case, but somehow still lost it.
I want to update my phone from 2.3.1 to 2.3.4 but I don't want to lose my app data and whatnot so I want to know if it is possible to install the OTA updates via Clockwork.. I managed to find the zip file for the update that will bring my phone from 2.3.1 to 2.3.3 and then the zip file for 2.3.3 to 2.3.4 from Google.
I don't want to flash a ROM, just looking to keep everything mostly stock but with root. I've searched for an answer but must be looking up the wrong terms, as I can't seem to find any info on doing this under the circumstances
Any help would be appreciated, thanks in advance!!
Phone: i9020t
Android: 2.3.1
Baseband: I9020XXJK8
Kernel: 2.6.35.7-g7f1638a / [email protected] #1
Build: GRH78
hkt03 said:
Ok.. I bought my Nexus S with 2.3.1 installed. I rooted it shortly after deciding I would keep the phone for awhile. According to all the guides I looked through, Clockwork Recovery won't stick unless that one file is renamed..
Well, come to find out, when I tried accepting the OTA update for 2.3.4, I somehow lost stock recovery and have Clockwork still installed. I've been running the stock software, stock kernel, with the bootloader unlocked and superuser installed. I never renamed the file in order to keep my stock recovery, just in case, but somehow still lost it.
I want to update my phone from 2.3.1 to 2.3.4 but I don't want to lose my app data and whatnot so I want to know if it is possible to install the OTA updates via Clockwork.. I managed to find the zip file for the update that will bring my phone from 2.3.1 to 2.3.3 and then the zip file for 2.3.3 to 2.3.4 from Google.
I don't want to flash a ROM, just looking to keep everything mostly stock but with root. I've searched for an answer but must be looking up the wrong terms, as I can't seem to find any info on doing this under the circumstances
Any help would be appreciated, thanks in advance!!
Phone: i9020t
Android: 2.3.1
Baseband: I9020XXJK8
Kernel: 2.6.35.7-g7f1638a / [email protected] #1
Build: GRH78
Click to expand...
Click to collapse
Yes, you can install the OTA with CWM.
Why don't you just install a stock, rooted rom.
It is just the stock rom, rooted and packed in zip ready to be flashed in clockwork rec.
Sent from my Nexus S using Tapatalk
deeren said:
Why don't you just install a stock, rooted rom.
It is just the stock rom, rooted and packed in zip ready to be flashed in clockwork rec.
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Don't really feel like setting up my phone again and losing my app data.. I didn't mind too much with my G1, but I've got so much junk on my NS that I don't want to lose. Just want to update like normal..
i guess you have two options update:
1 - you could flash original ota from cwm, but you will lose the root and cwm recovery, then you will need to root again, but to root in 2.3.4, you will need to unlock booloader, and that gonna make you lose everything...
2 - you also could try to flash stock, deodexed and rooted zip, but i really don't know if it gonna work (although i don't see why it wouldn't)...
thiagodark said:
i guess you have two options update:
1 - you could flash original ota from cwm, but you will lose the root and cwm recovery, then you will need to root again, but to root in 2.3.4, you will need to unlock booloader, and that gonna make you lose everything...
2 - you also could try to flash stock, deodexed and rooted zip, but i really don't know if it gonna work (although i don't see why it wouldn't)...
Click to expand...
Click to collapse
My bootloader has been unlocked, flashing the ota doesn't lock it back up does it? I always thought I only lost root access, but not lock up the bootloader
hkt03 said:
My bootloader has been unlocked, flashing the ota doesn't lock it back up does it? I always thought I only lost root access, but not lock up the bootloader
Click to expand...
Click to collapse
well, if your bootloader is unlocked you don't have any problem at all! =o)
since you said that you rooted in 2.3.1, i thought you followed the guide to make it without unlocking bootloder.
with unlocked bootloader, that's what i would do:
- reboot in recovery (cwm recovery)
- nandroid backup
- wipe cache / dalvik-cache
- flash official zip OTA for your specific model. you can find it here: http://forum.xda-developers.com/showthread.php?t=1056062
- boot and see if everything is okay
after that, you will lose root and cwm recovery! now you have to root just like you had done before (flashing cwm from bootload and applying su file).
hope it can helps!

Will someone help me - trying to get EE4 Debloated V4.2.1 installed

I have flashed the stockrootedED1 file dated 20110517 - I have root access. I'm trying to get CWM to work so that I can flash the subject rom.
After I flash it, it just sticks at the samsung screen-I end up having to go back to the stockrooted file.
TIA
Were you previously on stock EE4? If so there was no need to root back to ED1. Did you take the OTA EE4 update?
Figured it out - thanks though.
Awesome, enjoy!

[Q] My current Charge setup, Need help Please.

First, I want to say hello to everyone and t hank you for all the great information on this forum. I am a new droid user and the Charge is my first phone. I gained a solid knowledge base over the past couple of months on many root commands and how to use Odin or boot recovery tools.
My current phone is rooted with the voodoo lag fix and the debloated ee4 rom. My firmware is 2.2.1, base bands are eg2 and build number is ee4.
I am looking to get the new base bands and be completely on EE4 and install the new OC kernel.
What steps do I need to take to achieve this setup?
Thank you
Flash Imnuts Debloated EE4 4.2.1 rom then flash PB&J OC Kernel. Your done.
Both can be found in Dev section.
You have to return to stock ED1 or ED2 and take the OTA to ee4 to update your baseband. Then you can flash CWM and you rom/kernel of choice.

Is it possible to root and still get OTA?

This is my daughters xoom. I really only want to root it to use Titanium Backup.
Is it possible to rooted with normal method by flashing cwm and flashing root from there using this http://forum.xda-developers.com/showthread.php?t=1242241
and then somehow reflash the stock boot/recovery images.
Would this allow a rooted device with OTA updates?
You can flash stock ROMs on a rooted device: yes.
However: during the process of rooting all of your data will be wiped, so you might want to check with your daughter if that's okay with her!
If you want to stay up-to-date with your Xoom (even before the stock ROMs come out!) my advice to you is to flash team EOS 2.0 on it.
It is extremely stable, runs ICS (even if you have the 3/4G model!)
I think that it's possible to get OTAs if you flash the stock ROM.
Watch out however! If you haven't installed VooDoo OTA RootKeeper, you will lose your root!
So: Install Voodoo OTA RootKeeper if you want to keep your ROM up to date with stock images, while remaining rooted!
Hope this helped, if so, please thank my post, sothat I start my sunday morning with a great feeling!

[Q] Stock LF2, rooted, CWM Recov to Jellybean

I need advice on what you would do in my situation. I am on stock rom LF2, rooted, CWM recovery and bootloader unlocked and I want to upgrade to JB. What would you recommend be my upgrade path without wiping data? Just doing a dirty flash using CWM or upgrade via OTA and then rooting using the ODIN packages? As an added complication, I recently acquired the copy/paste bug. Thanks for your input.
Use the pre-rooted no-wipe version here:http://forum.xda-developers.com/showthread.php?t=1984436. Then you can just boot up the phone and flash CWM recovery using EZ-Recovery and unlock with EZ-Unlock version 1.2. There is another guide stickied at the top of the development section but I think it is a little more work to get the same result. Make sure to take a backup first of course. Then if you want the latest CWM recovery you can flash it with ROM Manager. I used this method to go from stock rooted and unlocked VRALG1 to the J1, K1 and then K3 leaks all without wiping data and everything has worked great. No media drain or anything else.
Thanks, I was confused about which method to use. I just finished flashing and everything seems to be working.

Categories

Resources