• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root 2.2less

Upvote 0
It seems there are many people who may not know exactly what they are doing are bricking or almost bricking phones when one reads the entire thread @ http://androidforums.com/ally-all-things-root/263285-guide-froyo-2-2-1-root-users.html

Are you saying more people are bricking phones with SuperOneClick Death? Just wondering about the numbers behind the claims?

I've seen a number of both cases where the person gets "bricked" from doing something after superoneclick as well as doing the guide. This is based on people that come asking for help.
 
Upvote 0
It seems there are many people who may not know exactly what they are doing are bricking or almost bricking phones when one reads the entire thread @ http://androidforums.com/ally-all-things-root/263285-guide-froyo-2-2-1-root-users.html

Are you saying more people are bricking phones with SuperOneClick Death? Just wondering about the numbers behind the claims?
Deffinately a Fair question.
One worth looking into.

Why doesnt someone Go talk to short fuse the author of this method on XDA and see what he says about it. I would like to see him defend his method. If it is defendable.

I have used both ways of Rooting. I see no difference with exception of Fastboot. Everyone that I have using the SOC method has been using it for over a month and are happy as clams. There has been no issues as of yet.

P.S. There is a Rage Against the Cage option for exploit. This is the one that I have used on many peoples phones.
I just dont have time for doing all of those Ally's by Tridents method. This seems to be a very good option for me.
 
  • Like
Reactions: DoctorZaius68
Upvote 0
I still don't understand how breaking the property service and messing up dns is acceptable. The guide our dev's worked on is by far the safest method.

A question I have, for those rooting stock 2.2 OTA with SOC, how do they plan to flash a recovery? No fastboot, no recovery, no custom roms etc. That means users that used SOC are stuck with a broken property service, and the only way out is to use Trident's guide.
 
Upvote 0
I still don't understand how breaking the property service and messing up dns is acceptable. The guide our dev's worked on is by far the safest method.

A question I have, for those rooting stock 2.2 OTA with SOC, how do they plan to flash a recovery? No fastboot, no recovery, no custom roms etc. That means users that used SOC are stuck with a broken property service, and the only way out is to use Trident's guide.
Well unfortunately your not entirely correct.
On all of those that I have used the SOC method with I have put Recovery on them just fine. Also they are using Velocity 1.0
I have made Back ups with it and Restored them. It really is simple to do.
Who on earth convinced you that they couldnt have The Aloha Amon-Ra Recovery 1.2.5 or flash Roms with it?

**Edit** I dont mean any Disrespect by this post Flick.
 
Upvote 0
I still don't understand how breaking the property service and messing up dns is acceptable.

What does "messing up DNS" mean anyway? I assume DNS still stands for Domain Name Server in the Android world?
Is a phone on which SuperOneClick is used unable to connect to the internet? Translate a I.P. Address into a Domain Name or vice versa ? Just wondering....
 
Upvote 0
What does "messing up DNS" mean anyway? I assume DNS still stands for Domain Name Server in the Android world?
Is a phone on which SuperOneClick is used unable to connect to the internet? Translate a I.P. Address into a Domain Name or vice versa ? Just wondering....
Well I have sent a message to Short Fuse

I am anxious to hear his answers.... Although his Thread has like Blowed up... A gillion people have asked him stuff.
I wonder about an answer being given in a timely manner....

Poor guy.
 
Upvote 0
It will kill a mapping in the memory to the properties. ADB checks whether it has root permissions. This neuters the property service (aka psneuter). When you reboot, it should be fine. The is because /dev/ashmem/system_properties isn't an actual file you're deleting. You're deleting a mapping. It's recreated when the system reboots (really when system_properties is initialized again.)

The problem with the G2 is that you can't inject Superuser because the way objects are written to /system in the G2.

The root method for all other phones is:
Neuter property service
ADB into device with root
Install su and superuser into /system
Reboot (to fix property service)

With the G2, on step #4, you'll lose what you did in step #3 and won't have root. (since writing to actual /system is constricted by the mmc).

So what you do is

Neuter property service
ADB into device with root
Downgrade

Since rebooting the device loses your root, then you simply downgrade instead. This goes around trying to fix the mmc issue and just reflashes a rom that'll play nicer with /system access.

If you understood how ashmem worked, you'd understand that you're not permanently crippling anything. What Scott is saying in his source code is: "We have root in G2, but we don't have anything that relies on the property service like the DNS. But that should be okay, since we don't need it to downgrade." Remember that rebooting isn't an option for rooting the G2.
 
Upvote 0
i tried the guide posted by trident about nine times, then did it the fast way and ended up just like flick said. after that i used tridents guide again and it worked, turns out i was either being impatient with LGMU or misspelling things in the command prompt. now i have velocity 1.0 and it feels 200% better than 0.4. the trick on the guide is take breaks, if you fail a couple of times before or during LGMU, just go back and restore a nandroid and try tomorrow.
 
  • Like
Reactions: Nemesiis
Upvote 0
It will kill a mapping in the memory to the properties. ADB checks whether it has root permissions. This neuters the property service (aka psneuter). When you reboot, it should be fine. The is because /dev/ashmem/system_properties isn't an actual file you're deleting. You're deleting a mapping. It's recreated when the system reboots (really when system_properties is initialized again.)

The problem with the G2 is that you can't inject Superuser because the way objects are written to /system in the G2.

The root method for all other phones is:
Neuter property service
ADB into device with root
Install su and superuser into /system
Reboot (to fix property service)

With the G2, on step #4, you'll lose what you did in step #3 and won't have root. (since writing to actual /system is constricted by the mmc).

So what you do is

Neuter property service
ADB into device with root
Downgrade

Since rebooting the device loses your root, then you simply downgrade instead. This goes around trying to fix the mmc issue and just reflashes a rom that'll play nicer with /system access.

If you understood how ashmem worked, you'd understand that you're not permanently crippling anything. What Scott is saying in his source code is: "We have root in G2, but we don't have anything that relies on the property service like the DNS. But that should be okay, since we don't need it to downgrade." Remember that rebooting isn't an option for rooting the G2.

HOLY COW!!!
Talk about Service.
Short Fuse. Thankyou for coming in and Clearing this up.

So For the record This Does do what everyone Has been sayin. It
Neuters property service.... BUT!!!!
"When you reboot, it should be fine. The is because /dev/ashmem/system_properties isn't an actual file you're deleting. You're deleting a mapping. It's recreated when the system reboots (really when system_properties is initialized again.)"

This is directly From SOC's Creator. This shows it is Safe and EFFECTIVE!!! :D

In My Oppinion Everyone on this Forum should Go to XDA Forum and Donate to Short Fuse.
Short Fuse agian A BIG THANK YOU!!
 
  • Like
Reactions: dautley
Upvote 0
I'm so lost lol. I knew I should have gotten a degree in a computer field instead of criminal justice & business lol. I just didn't feel comfortable with Tridents method bkuz of it's length & chances of bricking. I've tried going back to stock as well with no success. it's just frustrating bkuz I've never ran into a software update problem like this on my OG Droid or DX so maybe it's this particular ally. I've pretty much accepted no 2.2
 
Upvote 0
I'm so lost lol. I knew I should have gotten a degree in a computer field instead of criminal justice & business lol. I just didn't feel comfortable with Tridents method bkuz of it's length & chances of bricking. I've tried going back to stock as well with no success. it's just frustrating bkuz I've never ran into a software update problem like this on my OG Droid or DX so maybe it's this particular ally. I've pretty much accepted no 2.2
Bnitt you pmed me
I pmed ya back.
Lets chat over Gmail. If you still have a recovery there is always hope.
So go check your pms and give me a buzz.
Were going to get you 2.2 Somehow. :cool:
 
Upvote 0
Short fuse thank you for your input, I am glad we were able to get to get a better understanding of how your 1 click root program works.

Thank you also to everyone who joined the debate. Without input from the Ally community, we will never know if and how alternative methods of root will work on our devices.

Also thank you to everyone who put up with me. I hope I din't frustrate anyone too much, but I think we all have to understand that everyone does not always have the same amount of knowlege, expertise or skill as everyone else does and sometimes you need to dumb down your answers to reach the masses.

DZ
 
  • Like
Reactions: swc2001
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones