FORUMS

On Qualcomm’s Damage Control: Marketing and Rumors?

The Heated Snapdragon chronicles seemingly see no end, and 5 months into 2015 … more

Xiaomi Mi Note Pro With SD-810 Goes On Sale In China

The Xiaomi Mi Note Pro, announced on 15th Jan 2015, is Xiaomi’s attempt at … more

Project Fi Invites Are Rolling Out

Google is now sending out the first wave of invites to its new wireless service, Project Fi. … more

Vinsic 20,000mAh Ultra Slim Power Bank Giveaway

We have covered a lot of Android Accessories here on XDA TV. Mostly because we realize … more
Post Reply Subscribe to Thread Email Thread

How do I root the frk76 OTA update?

22nd November 2011, 03:08 PM |#1  
OP Junior Member
Thanks Meter: 1
 
More
I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.
 
 
22nd November 2011, 09:38 PM |#2  
OP Junior Member
Thanks Meter: 1
 
More
SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.
The Following User Says Thank You to sir_lunatic For This Useful Post: [ View ]
2nd December 2011, 11:48 PM |#3  
Junior Member
Thanks Meter: 0
 
More
SuperOneClick 2.2.2 Will Work With FRK76 if...
I took the rageagainstthecage exploit file from SuperOneClick 1.7 and placed it in the "Exploits" sub-directory of SuperOneClick 2.2.2 and it worked as well after a reboot. Note: You'll get a warning message about it's incompatibility with Android 2.3 + (not an issue as FRK76 is 2.2.3)
8th December 2011, 12:23 PM |#4  
Junior Member
Thanks Meter: 0
 
More
Don't know what the above means
Does 2.3.1 work without modification?
11th December 2011, 10:17 PM |#5  
Junior Member
Thanks Meter: 0
 
More
While I still have my 2 year old droid, I don't have my windows computer any more. Is there any way to do this with a Mac?
13th December 2011, 04:55 PM |#6  
industrialight's Avatar
Junior Member
Flag Springfield MA
Thanks Meter: 0
 
More
Noob needing help
Quote:
Originally Posted by sir_lunatic

I don't run any roms just root. I received the OTA update lastnite and without thinking, I allowed it to update. I usually use SuperOneClick but that doesn't seem to work with this update. I have searched high and low and can't find any information on rooting this. Any help is appreciated.

Good day, I've scoured the xda dev & android forums, and haven't been able to come up with a resolution to this: I let the OTA [FRK76 - 2.2.3] update slip through, and now i'm having issues rooting.

Besides the fact i'm running linux, i refuse to use any of the one click methods.. Would rather root manually so i know what's happening.

I'm running Ubuntu & doing this all through ADB / terminal, following the instructions listed in android forums [Rooting the Droid without rsd lite up to and including FRG83D], i get to step 13 and i still see the $ & not #.

As there anyone out there who can assist?

Thanks much in advance!
1st February 2012, 12:30 AM |#7  
Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by sir_lunatic

SOLVED. I reverted to SuperOneClick 1.7 and used rageagainstthemachine and it worked after a reboot. zergRush in 2.2 doesn't seem to work against this update.

how does one get an older version of SuperOneClick 1.7?
3rd February 2012, 04:09 AM |#8  
Senior Member
Thanks Meter: 26
 
More
Quote:
Originally Posted by envoy510

Does 2.3.1 work without modification?

As per i know it does not.
12th February 2012, 08:40 PM |#9  
Member
Thanks Meter: 8
 
More
Pete has a stock rooted FRK76 Rom on his website, fyi
15th February 2012, 10:06 PM |#10  
Junior Member
Thanks Meter: 0
 
More
My D1 seems remarkably resistant to rooting. I downloaded SOC 2.3.3, added rageagainstthecage to the exploits folder, and it still won't even really get to the "Waiting for Device" command. It kills/boots the ADB daemon then hangs. If I kill one of the ADB processes manually, I can get it to skip the automatic version check and get to "Waiting for Device" but then nothing happens there, either.

Any help (or hell, an alternate rooting method- I'd do it the long way too) would be great.
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes