yashsingh1/xdaforums huggingface dataset:
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] mdfzhi:
each cpu is different and unique even for the same model. what is working with me doesnt mean it'll works with u too, and the other way around.

what is safe for me doesnt mean it'll be safe for u too.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] chepoz:
do experiment. try all which is most stable.

but remember, set more clock than standart is shortening cpu life.

sent from my Walkman
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] dumraden:
Shortening CPU life? Lol... No, it only shortens your battery life...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] ginryu:
It will shorten the CPU life if it constantly stays in higher than recommended temperatures.
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] melander:
always remember,

with great power lies great responsibility,

overclock responsibly...
[Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A] chepoz:
just like uncle ben parker said before he died....lol

sent from my Walkman
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
Sent my phone to Square Trade

before

I got the 4.0.4 update (was previously on 4.0.2 with T-Mobile). They put a new "main circuit board" in my phone (sent it in for power button inop).

Well when I got my phone back the first thing I noticed was an "unlocked lock" symbol during boot up. Then I found that that it was updated to 4.0.4 and in my app drawer the Superuser app (which I updated to v3.0.7 (41)) is present.....

Here is the specs under the "about phone" section in Settings:

Build number: IMM76D

Baseband version: I9020XXKI1

Kernel version:

3.0.8-g6656123

android-build@vpbs1 #1

Thu Feb 2 16:56:02 PST 2012

I've never rooted before -so I don't know how to confirm that I am. However I noticed that in the Superuser app, when I go to check for updates it says that my installed version is LEGACY -and it says a new version of SU BINARY was found. When I tap on "update" it says: CHECKING FOR BUSY BOX... NOT FOUND, and then GAINING ROOT ACCES... FAIL!

Also when attempting to try out Droid Wall and Adblock they both say that I am not rooted.

Does this mean that I am not rooted?? -even though that "unlocked lock" symbol is present at start up??

If they rooted my phone wrong, what can I do to root it correctly??

-and-

How to I return to stock un-rooted 4.0.4 if I ever need to??

Any help would be GREATLY appreciated.
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
The unlocked symbol when you start up your phone (under the Google logo, right?) just means your bootloader is unlocked, which is the first step in actually rooting the phone.

As for Superuser, even non-rooted phones can install it from the Market/Play Store (like you have), doesn't necessarily mean you're rooted.

Did you install Superuser or did they put it on the phone?
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
They put it on my phone. I just updated it from the Play Store when I was putting all my apps back on my phone.
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
Maybe they just wanted to see whether or not you were rooted?
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
So I can go ahead and follow the "how to root i9020T" guide under the stickied General section of this Nexus S forum? ....and I should be ok?

I figure that if my bootloader is already unlocked I might as well go all the way and finally root this phone, right? That or lock it up again.

My main concern is since I didn't know where they left of, I wasn't sure where to begin/pick back up in finishing the root process.

If I follow the guide from the top I should be safe though, right?
[Nexus S Q&A, Help & Troubleshooting] simms22:
if you already have a custom recovery, just flash any of the custom roms(or kernels) and youll have root. if not, flash a custom recovery then a custom rom(or kernel). all the custom roms come with su binaries. yea, its that easy.
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
So I'm not sure if they put custom recovery on my phone.... how can I tell??
[Nexus S Q&A, Help & Troubleshooting] TH3JUNK13:
power off>hold volume up+power>volume rocker to select recovery>power to select
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
OK, when I do that process I got what looked like a dead Android??
[Nexus S Q&A, Help & Troubleshooting] simms22:
ha! dead android, lol.

youll need to flash a recovery via fastboot(probably clockworkmod recovery).
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
Ok.... flashing recovery is ALWAYS where I get lost when I read up on rooting.

Could you/someone point me in the right direction please?? (via instructions or a link to some GOOD & CURRENT instructions and files).

Can I just follow instructions from http://xdaforums.com/showthread.php?t=895545 and start from the top -so that I get a feel of how to do this from the beginning????

-and if I follow the instructions from this post, will I still be running 4.0.4??

This dead android really concerns me a bit!!
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
That guide is perfect. If you use, it will install a custom recovery on your phone, which can then be USED to install 4.0.4 on your phone again. If you don't really want root access, I'd stay where you are right now.

Anyhow, if you DO decide to follow the guide, you can skip the part where it says to type "fastboot oem unlock" (beginning of part 2) because that command unlocks the bootloader, and your phone already has an unlocked bootloader (shown bythe unlocked lock you see when you turn your phone on).
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
OK.... so I'm following the guide, BUT when I go to "update driver software" I point it to where I downloaded the "android-sdk_r13-windows.zip" file, but it won't let me select it. I also tried extracting the file directly onto my C:\ drive, but it won't let me select it there either.

What am I missing here??

(running Windows XP 32 bit, by the way)
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
Do you have either WinZip, Winrar, or 7-zip installed on your computer? You need them to extract the file, which will give you a folder. Point the driver installer to that folder after you've extracted it
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
Well I got the file extracted just fine. Problem is that when it won't let me select ANYTHING when I try to update the driver (the "OK" is dulled out when I point it to where I extracted the file to).

BTW, at the current state, next to "Android 1.0" in my Device Manager it shows a yellow "question mark & exclamation mark", and it is a sub of "other devices" (with a yellow "question mark" next to that as well).

Did I miss a step????
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
Try picking just the folder where the extracted folder is, that might work. As for the yellow exclamation mark, it's normal. That's what the drivers you install are going to fix
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
Still won't let me chose anything.....

One thing I noticed is that in the instructions it says to point it to "(..\android-sdk-windows\google-usb_driver)" .....but I don't have anything that says "\google-usb_driver" at the end of the file name. I only have "android-sdk-windows" -even after I extracted the file.

All I have inside the "android-sdk-windows" folder are: add-ons, platforms, tools, SDK Manager, and SDK Readme. None of them have anything that say "google-usb_driver" in them.

Where do I find this "google-usb_driver"??
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
Scroll down on this page

http://developer.android.com/sdk/win-usb.html

Actually, it might be easier to try this out

http://xdaforums.com/showthread.php?t=1589251
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
Hmmm... that one-click root method looks awesome, but since it was only uploaded yesterday I'm a little bit weary of it.

I tried to get that google-usb_driver, but with the sdk r13 it won't let me unless I update to r17. I'm thinking of just going to http://developer.android.com/sdk/index.html and getting the latest sdk r17 exe file & trying to go from there. Only concern is that on the guide here on xda it says "from sdk r14 forward Google removed the fastboot command so I'd have to make the fastboot command myself" -will this be an issue or is that easily done??

(I seriously can't believe I'm running into wall after wall with this.

I REALLY appreciate all the help thus far, by the way)
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
See the first link from my last post for a driver

Sent from my Nexus S 4G
[Nexus S Q&A, Help & Troubleshooting] simms22:
go to pdanets website, www.junefabrics.com/android , download the free download, install it, open it. follow the onscreen instructions and itll instal the latest driver for you. its the easiest way to get the driver installed.
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
OK. From a combination of the advice from gullu101 and simms22, I got "A" driver installed. But unlike in the guide it's named "Android ABD Interface" instead of "Android Bootloader Interface"

-is this OK????

[update]

- Alright so I tried to go ahead with the process even though the driver was called "Android ABD Interface" instead of "Android Bootloader Interface"

- I downloaded "recovery-clockwork-5.0.2.0-crespo.img" moved it into C:\android-sdk-windows\tools and renamed it to "recovery.img"

- I opened a command prompt & typed in "cd \android-sdk-windows\tools"

- Then typed in "fastboot flash recovery recovery.img"

- BUT then a window popped up saying the following:

"This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem"

......so I tried repeating all the steps again, but I still come to the same result.

What is causing this AdbWinApi.dll to not be found and/or what does this mean??
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
Is your phone in the Bootloader Interface (the first screenshot in the guide)?

If so, try continuing the guide from the third phone screenshot, right after where you see the words "LOCK STATE - UNLOCKED" in red letters in the guide

If it works, that means the driver is installed. If it doesn't work...well, it won't do anything to your phone, so don't worry about messing up...
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
Yes, I am in the Bootloader Interface.

I just tried continuing from where it tells you to "Download clockwork recovery...."

but when I type in "fastboot flash recovery recovery.img" a window pops up saying:

This application has failed to start because AdbWinApi.dll was not found. Re-installing the application may fix this problem

-and this is where I'm stuck at right now.....
[Nexus S Q&A, Help & Troubleshooting] Harbb:
You can get that file from here, it also includes adb, fastboot and drivers. It just needs to be placed in the same folder as your current fastboot/adb files.

I think there is a recent fastboot and adb update recently too, might even be required for 4.0.4+ ROMs. If this is the case, setup the android SDK (look for the rooting guide) and let it install/update platform-tools.
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
Ok.... the NexusSHacks website that Harbb sent me looks promising.

Two questions though......

1 - This guy doesn't use clockwork recovery. Instead he uses something called TWRP. Can I still use clockwork instead (because it seems more popular/well known)??

2 - Should I just download the most current SDK (r18) directly from http://developer.android.com/sdk/index.html?? (because the r13 from the guide seems to be MAJORLY outdated & missing key required components)
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
Yeah, idk why I said this guide was perfect. I'm going to try and write another guide...

Anyhow, you can just download the files from the link harbb gave you and just use that guide completely. If you want to use Clockwork, just copy the clockwork recovery into the folder of the FILES FROM THE NEW GUIDE and replace the step "fastboot flash recovery twrp-crespo-2.0.0RC0.img" WITH "fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img", which will give you clockwork mod instead...
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
And finally.... I am rooted!!

THANK YOU ALL for bearing with me & helping me out to get this done!!

I ended up just following the instructions COMPLETELY from the NexusSHacks YouTube video from his site. I figured if I follow it entirely then there should be no way for things to go wrong (again) lol.

THANKS AGAIN EVERYONE!!!!

Rock on!!
[Nexus S Q&A, Help & Troubleshooting] Rimmir:
Enjoy root access! :D

We definitely need a new guide of some sort...
[Nexus S Q&A, Help & Troubleshooting] MotorcycleKopp:
Lol most definitely :-)
[Acer Iconia A500] Euclid's Brother:
This is a beta release of the latest Acer Recovery Installer. Once the beta is finished, it will be release on the android market as version 3.0.

This release supports Acer Iconia A100, A200 and A500/A501. A100 and A200 must be using the ICS bootloader from the A200. Currently, there are no custom ROMs listed for the A100 and only one for the A200. More to come soon. There is a version of thor's 1.7 recovery for all devices. And all the included custom recoveries are GPL compliant. They all use stock kernels.

Since this version is not on the android market, it cannot validate any premium licenses, although it will use one if you already have a local license file. Therefore, this beta version will allow you to access the premium features w/o purchasing.

Some Notes:

It will create a folder in the internal sdcard called ".AcerRecoveryInstaller", which is where it will store the downloaded custom recovery files. Premium user license is also stored here.

Much of the code on the main page was rewritten and modularized to help facilitate support of new devices. When the A510 and A700 come out, it should be fairly easy to support those as well (assuming we can unlock the bootloader on them.)

Recovery files are no longer embeded in the apk you download from the market, which makes the apk MUCH smaller. Supporting multiple devices would have made the apk much too large if they were still included in the apk. The recovery files will be downloaded the first time you run this version. If you install it over a previous version, it will try to copy them from the old location first.

Download

http://www.interphaze.com/ROMs/Beta/Acer_Recovery_Installer.apk

md5: f0a03b50e08faa09e8d49e7224b0cd0f

After downloading, the file will probably end up with a .zip extension instead of a .apk. Just rename it to .apk to install it.

As I release new versions, I'll updated this OP.

EDIT: A number of users have been confused by the red outlined banner at the bottom. This banner replaced the links to my other apps a few versions back (2.7 something). The presence of that banner does not mean you've lost your premium license. The next beta will probably display a thank you banner instead of the one shown now if the premium features have already been purchased.

EDIT: V2.99beta3 is available at the link above. Much of the underlying code was changed and needed much testing. I believe it is pretty stable now. It supports TWRP 2.1.1!
[Acer Iconia A500] Euclid's Brother:
For me (future changelog)
[Acer Iconia A500] dincdoes.me:
Looks Awesome I purchased this as as soon as walked out of bestbuy 8month ago:) this app has come a long way I just want to thank you for all you work its really a great app!
[Acer Iconia A500] civato:
I will make custom rom for A100 , give me some time.

Just been very busy.

EDIT

Full A100 custom rom is in A100 section
[Acer Iconia A500] anikiup:
Can I install it on top of the market version or Should I uninstall that first?
[Acer Iconia A500] Euclid's Brother:
I think you probably can, but have not tried it. Give it a shot and let us know. Worst case is that it will say you have to uninstall the previous version.
[Acer Iconia A500] elborak:
Yes.

---------- Post added at 05:12 PM ---------- Previous post was at 05:07 PM ----------

Any idea if TWRP 2.1.0 supports the extendedcommand file?
[Acer Iconia A500] Euclid's Brother:
Unfortunately, it does not. I will add recognition to my app for TWRP, but it will not work with the premium features unless the dev add support for extendedcommand.
[Acer Iconia A500] pimpmaneaton:
Extended command actions are locked down to clockwork mod based recoveries. There is a key need to use that function. But there are other apps that work with twrp that basically do the extended command goodies.
[Acer Iconia A500] FloatingFatMan:
^ In what way are they "locked down" to CWM?
[Acer Iconia A500] Euclid's Brother:
@pimpmaneaton

In which version of CWM did they lock it down? It works fine in thor's 1.7, and in hbwelches version that was built for the A200 (can't remember which version he based it on).

It also works on fine on my Sprint Epic Touch 4G using a custom built CWM (not from ROM Manager). I created a test script myself and it ran fine. That was based on 5.0.2.4 I believe. I have 5.0.2.8 installed now, i'll try it again with that one and see.

extendedcommand support really isn't much more than looking for the file and executing it like any edify script. package_extract type commands shouldn't be allowed, since it's not part of a package, but things like ui_print, format, run_program, install_zip, set_permission, symlink, etc.. shouldn't be too hard to do.

I've been trying to find more info on how Open Recovery Script works. To see if i can use that.
[Acer Iconia A500] dibb_nz:
installed fine on top of v2.74 -paid version - couple root beers on their way:-) 0158-3554-2226-2151-1639
[Acer Iconia A500] Zatta:
If you find some interesting documentation/websites, would you mind sharing them here?

Although i would prefer normal extendedcommand support in twrp because seen the comments on review.cyanogenmod there is no change open recovery script will get merger to cwm. Besides that, if I understood it correctly, extendedcommand is not limited at all to rommanager. Kouch just changed his licence statement in the code to stipulate that.

Taptalked u see
[Acer Iconia A500] Euclid's Brother:
If anyone has used the beta2.99 from the OP, I'd love some feedback. Any problems? Working fine? Please be specific. Thanks.
[Acer Iconia A500] Zatta:
I just tried it, works fine although i had to read the op here again to realize i needed to put the recovery image in the correct directory. A small embedded browser would be nice. Or at least a help function/about under the overflow menu.

I used it to flash thor 1.7 cwm over twrp, without auto reboot to recovery. I have used the free market function only once before so i can't really tell you the differences/improvements.

Acer A500 btw.

Taptalked u see
[Acer Iconia A500] micky387:
I'm use bêta 2.99 . I've tested 3 time full backup . 2 on 3 are working without problème. 1 time,reboot to recovery and reboot système without backup.

I've thor 1.7 cwm with flexreaper R11.

Your app are perfect.

Thanks
[Acer Iconia A500] bog3nator:
just installed and upgraded from thor 1.3.4 to 1.7...updating and flashed fine, rebooted into recovery and everything went perfect...thanks so much!
[Acer Iconia A500] Euclid's Brother:
I forgot to this mention in the OP. To install a recovery that's not automatically downloaded by the app, you place it in the root of your external sdcard and name it "recovery.img" (just like the old version). HOWEVER, if you don't have an external sdcard, then it looks in /sdcard/.AcerRecoveryInstaller instead.

I'm going to work on this more for beta2 and have it able to use multiple custom images. So you can have one or more additional recovery images instead of just "recovery.img"
[Acer Iconia A500] Euclid's Brother:
I guess it's possible, for whatever reason, the sdcard didn't mount that one time. If that happens again, please PM me the file located at /cache/recovery/last_log after it boots back into android.

Thanks!
[Acer Iconia A500] micky387:
ok.

Your app is fantastic so i've purchas the premium version .

Thanks

Best regards

Envoyé depuis mon A500 avec Tapatalk
[Acer Iconia A500] burbank:
Please let me know if I can help test the A510 for support when the times comes. I would love to have this running on the A510.

Thanks!
[Acer Iconia A500] NoSudo:
I'm trying it out today so far so good. It's the easiest way to get cwm on the A100 that I have tried so far. I was able to create a backup on the external sd card without a problem. I like the green text color too.:)

Nice work man. I'm glad I tried it out.:)
[Acer Iconia A500] macia10:
hm I've got 2 messages.

1) Your Iconia A501 may not be supported! If you are running a custom rom, it may be reporting a different model.

2)Unable to download latest list of recoveries.

but after changing the model name in build.prop from Iconia A501 to A501 the first message is gone. Second is still there.
[Acer Iconia A500] Euclid's Brother:
Are you connected to the internet when you run it? Not sure why it wouldn't be able to download the list.

My apologies to for not having another update ready yet. I haven't had much time to work on it the past couple of weeks. I should be able to work on it some this week for a possible weekend update.

If someone can send me a stock recovery for the A510, I'll repack thor1.7 cwm using that kernel.
[Acer Iconia A500] elborak:
I assume this

is why I'm getting this

---------- Post added at 05:00 PM ---------- Previous post was at 04:37 PM ----------

This is not new to ARI 2.99beta1, but I thought this would be a good thread to report this issue.

One problem I noticed after I updated my ROM to FlexReaper 12.5 is that when I would go into ARI and select "Backup all partitions" is that it would reboot into recovery and then almost immediately reboot without running a backup. /cache/recovery/last_log didn't show any useful error.

I finally figured out it was because in FR 12.5, the ro.display.id property contains a ':' character. This was then used in the default filename for the backup, which fails as colon is an illegal character in the FAT32 filesystem. Manually changing the ':' to '_' resolves the problem.

You should probably filter this character out by default in your next release.
[Acer Iconia A500] nocoment07:
when the version 3?
[Acer Iconia A500] hatefuel19:
Will this allow me to flash a working gpl compliant recovery on unlocked bl v3?
[Acer Iconia A500] Euclid's Brother:
Thanks, I'll definately do that!

Been doing alot of updates on the licensing. Beta2 is in the link of the OP, but I just haven't had a chance to make a changelog. It supports A510, but not sure how stable the cwm is for it. Will be working on adding twrp support soon.

Beta3 should come hopefully sunday night (may not have twrp support yet).
[Acer Iconia A500] Euclid's Brother:
yes. If the cwm is listed in the app, then it is GPL compliant. It does support the ICS bootloader.. Doesn't matter if it's the .11-ICS or the .12-UNL
[Acer Iconia A500] hatefuel19:
I think I should clarify. I don't want thors recovery so will this allow me to flash a working RA or twrp with ics boot loader.
[Acer Iconia A500] nocoment07:
Anything new?
[Acer Iconia A500] Euclid's Brother:
Yes, if it's names "recovery.img" and in the root of you micro sdcard, then it will install it. However, those are not compatible with the backup/restore and download/install roms features.

I'm working on adding support for twrp's OpenRecoveryScript. But currently, TWRP doesn't boot on the new ICS bootloader (for me, anyway). I don't know when team win will put out a version that will boot on the ICS bootloader. Hopefully soon.
[Acer Iconia A500] Euclid's Brother:
I decided to go ahead and start adding in the OpenRecoveryScript support and to do more testing before releasing beta3. Hope to have it ready this weekend.