-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
swc2001
Android Expert
Well you can always give the easy way a shot.
http://androidforums.com/ally-all-t...nteer-who-wants-go-back-completely-stock.html
This will take you back to a stock setting and walk you up throught the OTA's and then you can use Super One Click to Root. After wards you can put a Recovery on and then use Roms.
swc2001
Android Expert
as far as fastboot goes.... It depends.
Do you have fastboot now?
If you have fastboot currently you will keep it.
Basically when you take the OTA for 2.2.1 it doesent get rid of Fasboot if you already have it.
If your phone originally came with V6 then you should have fast boot.
Dont know what you have or if you have fastboot.
Download Quick boot try to boot into fast boot.
Or do it the old fashioned way. ADB
Now with all of that said the only reason for fastboot is if you are really destructive with computers. In essence its there in case you screw up your phone and screw up your Recovery at the same time.
Let me say this.... it takes some real talent to be that dumb. Most people that do basic things with Root will NEVER encounter a situation like that.
So with that it basically is your choice. A. do you already have fastboot. B. are you handy at destorying computer devices.
If the answers to those are positive answers then you have nothing to worry about.... Take the easy way. If the answers are to those are negative... keep trying "Tridents" method.
hope that helps
AndroidKris
Android Enthusiast
You need to press the home button on the slide out keyboard like The Flash fast...I ended up having to hit it repeatedly as soon as I knew the "!" Screen was about to show up...just keep retrying untill you get into recovery. It'll work.
swc2001
Android Expert
Start splainin Lucy
Zoandroid
Android Expert
When you get to step 27, the elusive one where so many people have trouble timing the button push, you would be forcing the Ally to accept the Froyo update from a copy of it in a file you downloaded during the operation setup.
Since Froyo is now being pushed OTA to Ally users, you can simply dial the CHECKIN process one more time at that point instead, and it will be offered as an update in your Notifications bar. Accept the update, download it, and follow the prompts. IIRC it is a 52.3MB file.
Once installed, return to the Guide and pick up after where step 27 had led you to installing it manually, and continue on. This worked just fine for me the night I was doing the guide, which was some time ago.
So it is no longer necessary to wrestle with step 27.
Since Froyo is now being pushed OTA to Ally users, you can simply dial the CHECKIN process one more time at that point instead, and it will be offered as an update in your Notifications bar. Accept the update, download it, and follow the prompts. IIRC it is a 52.3MB file.
Once installed, return to the Guide and pick up after where step 27 had led you to installing it manually, and continue on. This worked just fine for me the night I was doing the guide, which was some time ago.
So it is no longer necessary to wrestle with step 27.
dautley
Android Expert
I heard this a while back, i wish they would update the guide to reflect that, and add Toggle Signature Verify to step 34.
34. Finally, select "Flash zip menu" in recovery and choose Toggle Signature Verify then choose "su-2.3.6.1-ef-signed.zip". Then return to the main menu and reboot your device.
Zoandroid
Android Expert
Well, no disrespect intended to the dev team, but the only way I was able to use that guide was to read the whole thread, and make a list of all the 'differences' people pointed out, and then refer to BOTH as I worked my way through it. Plus I had to ping the Ally IRC several times to answer issues not mentioned in it. I agree, it would be nice if they would update it with all the information learned since it was posted.
I have noticed that most of the chatter on this thread and others regarding this topic is now being posted by users with less than 6-10 posts under their name. Some have only 1 or 2 posts. I am guessing they are not reading the whole support thread, and that is why they are having difficulties.
I have noticed that most of the chatter on this thread and others regarding this topic is now being posted by users with less than 6-10 posts under their name. Some have only 1 or 2 posts. I am guessing they are not reading the whole support thread, and that is why they are having difficulties.