What's new
DroidForums.net | Android Forum & News

This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Leaked FRG22 Update Available for Rooted Droid 1

I just updated to this from FR84B. I tried using P3's 1.0 Low V kernel, and I got an error on boot, and it was sluggish.

I am now using Chevy's 1.0 Low V and it seems smoother than ever.

1331 Quadrant score
 
So I am dizzy and thoroughly confused with all the files going around here. I am running stock 2.1 and think I should root because after 2.2 comes out, I am told it might be impossible to root after installing. SO, I am looking to root. Should I install SPRecovery and then install FRG22 in order to root or do it another way? Is FRG22 safe to install or not? I am hearing conflicting viewpoints. Some people say they are fine and others say they are having problems. What should I do?

It will never be imposible to root your Droid. Take a breath. If you decide to root, do it for the right reasons. Do not do it because rumor has it you may never get to do it again.

Nate
 
So I am dizzy and thoroughly confused with all the files going around here. I am running stock 2.1 and think I should root because after 2.2 comes out, I am told it might be impossible to root after installing. SO, I am looking to root. Should I install SPRecovery and then install FRG22 in order to root or do it another way? Is FRG22 safe to install or not? I am hearing conflicting viewpoints. Some people say they are fine and others say they are having problems. What should I do?

It will never be imposible to root your Droid. Take a breath. If you decide to root, do it for the right reasons. Do not do it because rumor has it you may never get to do it again.

Nate

You know, I have wanted to take the plunge for a long time and was just chicken to do it. I really think the Froyo stuff has put me over the edge where I want to jump. After speaking to HookBill I will probably install FRG22 tonight. The time is now :)
 
So I am dizzy and thoroughly confused with all the files going around here. I am running stock 2.1 and think I should root because after 2.2 comes out, I am told it might be impossible to root after installing. SO, I am looking to root. Should I install SPRecovery and then install FRG22 in order to root or do it another way? Is FRG22 safe to install or not? I am hearing conflicting viewpoints. Some people say they are fine and others say they are having problems. What should I do?
If you want to root, root now. There's no point in putting it off because it might not be possible later. Any of the ROMs/updates/whatever (barring the leaked DMUpdater, which is no longer linked to anyway) you'll find in the news section are safe as long as your Droid doesn't have an unknown condition or fault. What's not safe is the procedure for rooting. Even the one-touch methods might damage your phone. The risk is minimal as long as you know what you're doing, however, and FRG22 is as good as any other ROM to start your rooting experience on. In fact, the stock look, feel, and experience might make the transition easier on you.

What is this "Risk" you speak of? You're reading too much into those disclaimers the devs make you read before installing their roms. LOL

The risk is that the user might skip a step in the rooting process. If you can read and follow instructions not much can go wrong. But if you're lazy or just too ***** to follow the directions, well...then you deserve what might happen. But the worst thing I have witnessed to date is a screwed up install leading people to freak out until someone from the rescue squad shows them how to fix what they screwed up. And that usually takes about a half hour...unless your posting in the rescue squad at like 4am Eastern Time...LOL

We really need to quit scarring the noobs. I remember when I first researched root I was amazed at all the scare tactics. I'm sharp enough to wade through all that mess but a lot of folkls who are perfectly capable of rooting (read, follow instructions) run away from this project when they could be having fun with ther rest of us.

Nate
 
I am running Chevy's latest 800mhz Ulta Low V kernel without any problems on this build...it varies with each droid - it's kind to some, and not so much to others!
 
Just playing around with stuff, and I noticed that google translate does not work.

I have installed the black glass theme, so it may be cause by that. I will uninstall it and test again.
 
i think i found something new with this build or at least i was never asked this before. when i booted and it updated things i got a screen asking about activating Device Administrator. I have my work email (Exchange) syncing with my phone and this looks like some new management features. It talks about what looks like a remote wipe, password policies etc... see drocap pic. Did anyone else see this? Has anyone ever seen it before?
 
I just installed Chevy's ULV 1200 kernel and is running maybe just a tad slower than P3's LV 1200. P3 quad score was 1560 and Chevy's is 1390.
My question: will an ULV kernel always use less battery than a LV one?
 
I'm currently running 2.1 stock rooted build ESE81 and would like to go to 2.2 stock rooted. Would I have to wipe or is this a stock rooted 2.2?
 
I thought that this rom didn't need the market fix? I installed it and p3s 1.2lv kernel and my build number went to an older rom.
 
Kernels?

Isn't the kernel in FRG22 g874c292? This FRG22 has kernel g103d848 which is the same as the FRG01B? Does anyone have kernel g874c292?
 
i think i found something new with this build or at least i was never asked this before. when i booted and it updated things i got a screen asking about activating Device Administrator. I have my work email (Exchange) syncing with my phone and this looks like some new management features. It talks about what looks like a remote wipe, password policies etc... see drocap pic. Did anyone else see this? Has anyone ever seen it before?

New for 2.2 is support for MS Exchange security policies. The device administrator allows the security polices to make changes to your phone.

For example, if your corp exchange requires PIN security, the email client will instruct the phone to enable PIN security at the phone level.
 
I re-installed the stock FRG22 and google translate was working again.

Installed Chevy's 1.0 LV kernel, and it stopped working. It is the OC kernel, not the OS, causing the problem.

I did notice that wifi tethering will not work with security turned on if I use the black glass theme. I guess I will go with Vanilla android for now.
 
So I am dizzy and thoroughly confused with all the files going around here. I am running stock 2.1 and think I should root because after 2.2 comes out, I am told it might be impossible to root after installing. SO, I am looking to root. Should I install SPRecovery and then install FRG22 in order to root or do it another way? Is FRG22 safe to install or not? I am hearing conflicting viewpoints. Some people say they are fine and others say they are having problems. What should I do?
If you want to root, root now. There's no point in putting it off because it might not be possible later. Any of the ROMs/updates/whatever (barring the leaked DMUpdater, which is no longer linked to anyway) you'll find in the news section are safe as long as your Droid doesn't have an unknown condition or fault. What's not safe is the procedure for rooting. Even the one-touch methods might damage your phone. The risk is minimal as long as you know what you're doing, however, and FRG22 is as good as any other ROM to start your rooting experience on. In fact, the stock look, feel, and experience might make the transition easier on you.

What is this "Risk" you speak of? You're reading too much into those disclaimers the devs make you read before installing their roms. LOL

The risk is that the user might skip a step in the rooting process. If you can read and follow instructions not much can go wrong. But if you're lazy or just too ***** to follow the directions, well...then you deserve what might happen. But the worst thing I have witnessed to date is a screwed up install leading people to freak out until someone from the rescue squad shows them how to fix what they screwed up. And that usually takes about a half hour...unless your posting in the rescue squad at like 4am Eastern Time...LOL

We really need to quit scarring the noobs. I remember when I first researched root I was amazed at all the scare tactics. I'm sharp enough to wade through all that mess but a lot of folkls who are perfectly capable of rooting (read, follow instructions) run away from this project when they could be having fun with ther rest of us.

Nate
How many actually bricked phones do you need to see before you understand why we warn people that they need to know exactly what they're doing before they attempt to root/mod their phones, and if they have any doubts to not try? The easier it is the more people are going to try it -- and I'm all for everyone rooting who is capable of rooting despite the added security risk root is -- and the more headaches people are going to have trying to help the slew of people who, as you pointed out, didn't read or skipped a step.

Why do you think the updated DMUpdater was pulled by the devs? In their words, "it could brick phones".

There is a risk. There's always a risk. What if the cable gets pulled out during an RSDLite flash? What if the power goes out? What if they're trying to flash in a corrupted file and, when things don't go perfectly, they panic do something that DOES brick the device? Some of these are user error, some of these are "acts of God", and some of these risks are inherent in the variable nature of the phones we're working on. If an OTA update bricks someone's phone VZW replaces it, but if there's a flaw in the phone that trying to flash in, say, Clockwork Recovery triggers, the user is out $600 (replacement cost of the Droid 1). How much of this will be tolerated before Verizon stops turning a blind eye to rooting and starts filing lawsuits against forums such as this? Admittedly, this is a long shot, but nothing is impossible. Well, except someone shoehorning a 32nm Intel chip into one of these blasted things. :)

Having said all that, I agree with a lot of what you said. If you're serious about rooting and are willing to take the time to read up on the procedures, double-check everything, and commit yourself to it, rooting is a simple process that reaps many rewards. It's not some exclusive club that we rooters want to keep for ourselves -- but there is an initiation. :-D
 
Back
Top