Database Info

OBSOLETE.

I've combined toastcfh's and TheBiles how-to's in this tutorial, so if you've already rooted using TheBiles previous method, skip to step 9. I'll make this a bit more presentable when I get home from work today. I just thought this would be helpful to those who aren't comfortable with using adb.
I'm not responsible for damages to your phone, yada yada yada, you know the drill.
IF YOU HAVE A PROBLEM THAT HASN'T BEEN ADDRESSES IN THE SECOND POST, LET ME KNOW. OTHERWISE, SEE SECOND POST FOR FAQ'S. Follow these directions exactly as they are written and you won't run into any snags. It'll save us both a lot of time.​This tutorial entails making the root process as fast and easy as possible, that means we won't be backing up any of your stuff (you can if you want, of course) nor will we be doing a nandroid backup, and even better, we won't be using adb to push files. With that being said, let's get started.​
Step 1. Connect your phone to your pc via usb, then pull down the notification bar at the top of your screen and open the tab that says Charge Only and select Disk Drive then click done.
Step 2. Download this file http://link.geekfor.me/rootedromzip and put it on the root of your sd card by going to the start menu of your computer and opening up My Computer, then drop the file into the icon that reads Removable Disk. This is the root of your sd card. Remember that if you don't already know.
Step 3. Right click on the Removable Disk icon and select Eject. We're gonna flash the debug image now, say goodbye to any pic's, music, apps, texts, etc that you may have.
Step 4. Power down your phone.
Step 5. Hold down the volume down and power key simultaneously and keep holding it down until you see 3 android dudes on skateboards.
Step 6. It's going to give you some options, whether or not to install the PC36IMG.zip, select yes (volume up is yes) for any prompt you get.
Step 7. Once you've rebooted you will officially have root access. Congrats, but that's not all. There's a few more steps to gain -full- root access.
Step 8. Navigate to the root of your sd card and rename the PC36IMG.zip file whatever you want, doesn't matter. Just don't name it update. To rename the .zip file, right click on PC36IMG.zip and select rename.
Step 9. Download these files:
PC36IMG.zip -http://sdx-downloads.com/sdx/evo/troot/eng-PC36IMG.zip
mtd-eng.zip - http://forum.xda-developers.com/attachment.php?attachmentid=342668&d=1276481802
flash_image.zip - http://forum.xda-developers.com/attachment.php?attachmentid=342667&d=1276481776
recovery.img - http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=recovery-RA-evo-v1.7.0.1.img
PLEASE NOTE SOME OF THE MIRRORS YOU ARE DOWNLOADING THESE FILES FROM ARE NAMED SOMETHING DIFFERENT, SO YOU WILL HAVE TO RENAME THEM ACCORDINGLY. The only one that I know of was the PC36IMG.zip file, it was named something else when I downloaded it. So name it accordingly. Right click, select Rename, then type in "PC36IMG" only, your pc adds the .zip.
Step 10. Extract the flash_image.zip and mtd-eng.zip files, do so by right clicking on them, then select Extract To flash_image\ and Extract To mtd-eng\ Open the newly extracted folders and take the flash_image file AND the mtd-eng file inside and drop them into the root of your sd card. (we remember how to do that, don't we.)
Step 11. Open up the Android Market and download the terminal emulator app by Jack Palevick, it's free.
Step 12. Make sure your sd card is no longer mounted to the computer, do so by pulling down the notification bar and switching Disk Drive to Charge Only.
Step 13. Open the terminal emulator app and type in these commands exactly as they are written. If you get an error, try again.
Note: After each line is completed, hit enter. A # sign means you've run the commands successfully.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image misc /sdcard/mtd-eng.img[/B]
Step 14. Remount your phone, and drop the PC36IMG.zip file onto the root of your sd card. MAKE SURE YOU USE THE CORRECT PC36IMG.ZIP FILE THAT YOU DOWNLOADED FROM STEP 9. Power down your phone.
Step 15.
Hold volume down and power to boot into hboot.
- It should now find and verify the PC36IMG.zip on the root of your sdcard. It'll show a blue status bar on the top right of the screen.
- After a minute or so it will ask u if u wanna flash Select YES.
- After it flashes the PC36IMG.zip it will ask if you wanna reboot. Select YES.
Click to expand...
Click to collapse
Step 16. Once your phone has rebooted, put the recovery.img file you downloaded earlier on the root of your sdcard.
Note: If the recovery image is named something other than "recovery.img" then rename it by right clicking and typing in "recovery" as the name.
Step 17. Still know how to use terminal emulator? Open it up and type in these commands. Make sure your USB connection is in Charge Only mode first.
Code:
[B]su
cat /sdcard/flash_image > /data/flash_image
chmod 755 /data/flash_image
/data/flash_image recovery /sdcard/recovery.img[/B]
*INTERMISSION*
Take uh break, eat uh cookie.
If you've made it this far and you've had no errors, then you now have full root access as well as a legit recovery.
Time to flash a ROM and the latest radio.
Step 18. Power down your phone and power it back on by holding down the Volume Up and Power key.
Step 19. Select BOOTLOADER then select Recovery.
Step 20. Select Wipe: Select wipe data factory reset then select wipe dalvik cache.
Step 21. Downlaod any ROM you'd like, I'm running BuglessPete's Bugless Beast ROM, here's the link if you want to run this one as well http://bit.ly/az4cWq
Step 22. Download the latest radio here http://link.geekfor.me/radio139000531
Step 23. In recovery mode, select the USB-MS toggle option, this mounts your sd card to your pc.
Step 24. Move your newly downloaded ROM and radio to the root of your sd card by dropping them onto the Removable Disk icon on your computer.
Step 25. Press the power key to disable USB-MS toggle.
Step 26. Select Flash Zip From Sdcard.
Step 27. Select the ROM you downloaded and you will be prompted whether or not you want to flash the file, follow through with the power key.
Step 28. Select flash zip from sdcard, then select the latest radio .zip file that you just downloaded and flash that mf'er.
Step 29. Try not to freak out when you see a static image of a phone with green arrows circling around it. Wait...
Step 30. Select Reboot System Now.
And that's it, you're done!
ALL CREDIT GOES TO THESE GUYS! toastcfh, keishou, maejrep, Paul, Amon_Ra, Koush, TheBiles, and anybody else I forgot.
Grammatical errors? I just worked a 12 hour shift and got right on this, I have to be in bed in about an hour, so **** you.

Problems flashing a ROM after you've completed the process?
This is more than likely on account of the Dev who made the ROM not signing it, tell them if they sign it that you'll love them forever. Or switch to Koush's recovery. This is pretty much guaranteed to work, as Koush's recovery has a toggle signature verification feature. http://forum.xda-developers.com/showthread.php?t=702214 Or, if you've the know-how, sign it yourself. http://forum.xda-developers.com/showthread.php?t=473580
ATTENTION: To the few getting the not enough space error when flashing the recovery image, Amon Ra has addressed the issue here, to no avail according to those who have tried his alternative recovery. At least we now know what the cause of the error is. Thanks again, Amon Ra.
Amon_RA said:
You have a bad block in your recovery (like a bad sector on your harddisk), these bad blocks are skipped when flashing. A bad block means you have less usable space on your recovery partition, hence the not enough space left to flash this recovery...
I made this recovery specially for you, it's 1MB less than the normal recovery (left out the evo charging stuff), all functions of the normal recovery should still work. Could you please give it a try and let me know?
Code:
fastboot flash recovery tiny-recovery.img
OR
flash_image recovery /sdcard/tiny-recovery.img
Click to expand...
Click to collapse
Bad block? Not enough space on sd error when trying to flash the recovery image? Try these.
Amon_RA said:
Could you please try to flash recovery-RA-evo-v1.7.0.2.img and use fastboot to flash :
Code:
fastboot erase recovery
fastboot flash recovery recovery-RA-evo-v1.7.0.2.img
I'll most likely not make my recovery compatible with Koush's rommanger because I would need to almost rewrite it fully.
Click to expand...
Click to collapse
tlisak25 said:
If people are still having problems tell them to unroot and start from scratch without doing system update from Sprint thanks for all or your help
Click to expand...
Click to collapse

In on this.
Will try this out right now and edit my post later.
[Edit]
Oh, so the only difference is instead of using ADB you're using the "terminal emulator" app.
It's a good guide and am sure it works. But if you know how to use ADB, I'd actually prefer ADB. It's much easier to type on your keyboard.
But GREAT guide none-the-less. For people who don't know how to use ADB.

It's not so much that people can't fiure out how to use ADB as it is they can't figure out how to install and run it. Even when I first got into Android I had no clue it was used through a cmd prompt for the first 2 weeks.

arozer said:
In on this.
Will try this out right now and edit my post later.
[Edit]
Oh, so the only difference is instead of using ADB you're using the "terminal emulator" app.
It's a good guide and am sure it works. But if you know how to use ADB, I'd actually prefer ADB. It's much easier to type on your keyboard.
But GREAT guide none-the-less. For people who don't know how to use ADB.
Click to expand...
Click to collapse
Exactly. Also, it's for those who rooted using TheBiles Idiot Proof method and were confused as to whether or not they could follow through with toastcfh's part 2nd part on gaining full root access.

Re: (How-To) FULL ROOT WITHOUT ADB.
ADB is just easier, in my opinion. I like bring able to easily copy and paste and type with a real keyboard. Plus, it's just good to know how to use. Not that I don't use the terminal on the phone, though! BTEP, for the win.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.

TheBiles said:
ADB is just easier, in my opinion. I like bring able to easily copy and paste and type with a real keyboard. Plus, it's just good to know how to use. Not that I don't use the terminal on the phone, though! BTEP, for the win.
-------------
Sent from my HTC EVO 4G using Tapatalk Pro.
Click to expand...
Click to collapse
Totally agreed. But this method is meant to make rooting as fast and easy as possible (for those who don't know how to neither set up, nor use adb, as setting it up as well as familiarizing yourself with it takes time) Although learning adb is a definite must.

i'm a "noob" and ive had my evo since the release and have been tring to acomplish full root without any luck using adb bs this is the easiest most well explaid way to do so and i am more greatful than words could express. if i can find a way to donate with out a credit card i will gladly help ur cause keep up the great work

bdd123456789 said:
i'm a "noob" and ive had my evo since the release and have been tring to acomplish full root without any luck using adb bs this is the easiest most well explaid way to do so and i am more greatful than words could express. if i can find a way to donate with out a credit card i will gladly help ur cause keep up the great work
Click to expand...
Click to collapse
I'm just glad it helped. Lol If there's anyone you should donate to, it's toastcfh. Without him, we wouldn't have root.

The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?

nol3n said:
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
Click to expand...
Click to collapse
Just a second, I'll get you a link.

the recovery.img link in step #9 is broken as well...

nol3n said:
The download link for the PC36IMG.zip in step #9 is broken...I am assuming that the PC36IMG.zip in step 9 is different than the PC36IMG.zip in step 2. If its no different, then I will just proceed downloading the rest of the files and go from there, but If so can I get a mirror link?
Click to expand...
Click to collapse
http://www.joeyconway.com/sdx/evo/troot/eng-PC36IMG.zip
Got it from toastcfh's thread. Should work. I'll update the link now.

Go damn it. -.- I'll update them all now. Thanks for the heads up.

thx for the hard work.

Lol Not really doing much but stealing links. They're all updated now.

evo root
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!

crpercodani said:
It's not so much that people can't fiure out how to use ADB as it is they can't figure out how to install and run it. Even when I first got into Android I had no clue it was used through a cmd prompt for the first 2 weeks.
Click to expand...
Click to collapse
Exactly! It took me 2 solid days of searching for the required driver for my laptop. I finally got it to work last night. None of the instructions on xda worked. The USB remover listed here didn't work, the driver in the SDK kit didn't work, nothing worked. I finally found another download for the USB remover and another link to a 32-bit driver that finally worked.

kevinniven said:
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
Click to expand...
Click to collapse
It's pretty much the fastest/easiest (if you don't have adb set up) way to get full root access on your Evo, so...yes, that'd be a good idea. Lol

S
kevinniven said:
I did the idiot guide but cant get ADB working on my windows 7. Should I go ahead and try this? Thx!
Click to expand...
Click to collapse
Oh yeah, start from step 9 since you're coming from the first part of TheBiles Idiot Proof guide.

Rom help and recovery

I'm extremely new to this and this website, sort of. So if any of this is wrong impression already sorry. A few weeks ago I rooted my myTouch_4G_Slide, using s-off. I'm pretty sure that went OK as my phone is still currently rootly rooted. Next I tried using a custom rom, i am not exactly sure what I did wrong but, I cannot boot into recovery and when i go into Hboot I get multiple "no image" popping up. I can't factory reset and when i try to boot into recovery my phone gets stuck at the mt4gs screen and i have to take out the battery. Is there anyway to fix this, easily hopefully.
Sent from my myTouch_4G_Slide using XDA App

You said your phone is s-off and "rootly rooted". I assume you meant "permanently rooted"? Did you use the right version of superuser (2.3.6.3 or above) and clockwork recovery image (4.0.0.9)? You can ignore the "no image" message, I get them all the time and I can still boot into recovery no problem.

I have the right superhero version but i don't think I have the right clockwork. How could I fix it, without having to boot into recovery.
Sent from my myTouch_4G_Slide using XDA App

imjames said:
I'm extremely new to this and this website, sort of. So if any of this is wrong impression already sorry. A few weeks ago I rooted my myTouch_4G_Slide, using s-off. I'm pretty sure that went OK as my phone is still currently rootly rooted. Next I tried using a custom rom, i am not exactly sure what I did wrong but, I cannot boot into recovery and when i go into Hboot I get multiple "no image" popping up. I can't factory reset and when i try to boot into recovery my phone gets stuck at the mt4gs screen and i have to take out the battery. Is there anyway to fix this, easily hopefully.
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Sounds like you need to reflash your recovery. Since you can get into fastboot still, this is an easy fix.
Just download the recovery image from here -
http://android.modaco.com/topic/343...e-mytouch-4g-slide-unofficial-modaco-edition/
once downloaded, enter hboot and select fastboot. Once your phone says "fastboot usb" on it enter the following command into fastboot -
Fastboot flash recovery c:/android/tools/recovery.img
The "c:/android/tools/recovery" portion of that command will be variable based on where the downloaded recovery image is contained on your computer.
Id say that has a pretty good chance of fixing your prollem =). Keep me posted
Sent from my myTouch_4G_Slide using xda premium

do i have to have adb to do it, because thats learning in progress

imjames said:
do i have to have adb to do it, because thats learning in progress
Click to expand...
Click to collapse
um, yeah. Fastboot is like ADB, but a different tool included in the SDK. Do you have the SDK? It's relatively simple, let me just break it down to maximize simplicity.
1) If you don't have the SDK, download it (in zip format) here. If you do have the SDK,
2) for simplicity's sake, create a Directory on your computer (the hard drive root) entitled "Android" (so that it's c:\Android).
3) If you didn't previously have the SDK, once it is is downloaded, extract the files.
4) assuming you run windows, navigate to the SDK, there's a subdirectory called "tools". Move that folder into the Android folder you created.
5) Now. take that recovery.img that you downloaded... (if you haven't done so yet, look to the link I provided in my previous post) move IT to the Android folder as well
6) open a command prompt and change the directory to the tools subdirectory of the Android folder (type cd c:android\tools), You'll now see a command prompt beginning with C:\Android\tools
7) make sure your phone is connected to your computer and in fastboot mode (select "fastboot" from the Hboot screen, it'll then say "fastboot usb" on the screen). I"m assuming your drivers are already properly installed since you were able to root your phone.
8) type in the following command into the commmand prompt - "fastboot flash recovery c:\android\recovery.img
That should do it =)

Sorry this took awhile, I am having trouble with the command prompt I can't get it to change
Sent from my myTouch_4G_Slide using XDA App

imjames said:
Sorry this took awhile, I am having trouble with the command prompt I can't get it to change
Sent from my myTouch_4G_Slide using XDA App
Click to expand...
Click to collapse
Because:
AndroidAutobot said:
... (type cd/c:android/tools) ...
Click to expand...
Click to collapse
Should be:
cd c:\android\tools
if you installed the SDK to a folder in your C: drive called android. That's what I did too because it makes life easier.
The rest of AndroidAutobots post is what you need to do, this one command was just typed wrong.

Blue6IX said:
Because:
Should be:
cd c:\android\tools
if you installed the SDK to a folder in your C: drive called android. That's what I did too because it makes life easier.
The rest of AndroidAutobots post is what you need to do, this one command was just typed wrong.
Click to expand...
Click to collapse
Oops lol. I cant believe i did that ha ha. Thanks for spotting that =)
I've corrected all the command lines in that particular post. Should be able to follow it step by step without any trouble now.
Sent from my HTC Doubleshot using xda premium

[SD CARD][HOW TO] Cant Mount SD Card or SD Card Corrupted

For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Preliminary Review - Check to see if you can mount in recovery or bootloader
First, go back to your bootloader screen and click on fastboot (reset your phone and hold the power and vol down button). Once in bootloader check your computer drives to see if the sd card is recognized
Your computer may be able to recognize the drive even if it cant open it. If thats the case, you may be able to format it from your computer (use FAT32 formatting).
Second, If you cannot see your SD Card in your ROM or from the PC, and you are using Clockwork Recovery (CW), try flashing TWRP recovery first. Do this by going through the following steps:
Step #1
Download TWRP recovery from http://teamw.in/project/twrp2/100 Make sure to download the correct version for your device
Step #2
Place the recovery file into a folder with fastboot.exe
Step #3
Reboot your phone and hold down the Vol Down Button and Power Button until your bootloader screen appears, then enter fastboot. Then connect to your computer. I find this method works best by holding down the buttons right away. If your phone is off, press the power button then immediately press and hold the power and vol off buttons again until bootloader screen shows up. Dont let go until the screen shows.
Step #4
Type
Code:
fastboot flash recovery twrp.img
but replace the twrp.img wording with the exact name of your downloaded TWRP recovery
Step #5
Enter TWRP recovery by selecting it from your bootloader screen. Then ensure the device is connected to your computer and select the Mount option and then mount your sd card.
IF you still cant see your SD Card from TWRP recovery or you get an error, proceed to the next steps. Your computer may be able to recognize the drive, even if it cant open it (if your lucky).
If your computer recognizes the drive but cant open it, you can try formatting it from your computer (make sure to format as FAT32)
If you really cant see your SD Card, and your fairly sure its corrupted, and you have no way formatting it from your computer, continue on below:
Basic Solution
Reflashing Stock Recovery to your device using fasboot, then doing a full factory reset. This would be using the method in post http://forum.xda-developers.com/showthread.php?t=1630459
PLEASE NOTE THIS METHOD WILL WIPE THE DATA FROM YOUR DEVICE AS WELL AS FROM YOUR SD CARD
This method works because custom recoveries cannot re format SD Cards on the HTC One S, only wipe data from them. However, the stock recovery does have a proprietary feature that will reformat the internal sd card if it has been corrupted.
Inotherwords:
Step #1
Download the stock recovery from: http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
*******Note that this file is a stock recovery for S4 devices, not S3.
Place the file into the same folder as your fastboot.exe
Step #2
On your device, go into bootloader and fastboot mode, connect your computer to the device, and type
Code:
fastboot flash recovery ville_recovery_signed.img
Step #3
Reboot into the bootloader and then choose to "clear storage" from the main screen and afterwards reset to factory defaults.
Step #4
Go back into the bootloader once step #3 is done and enter fastboot, connect your device and reflash your original custom recovery again. Your SD Card should be visible
Advanced Solution - If you do not want to wipe the data from your device
This method does not require reflashing the original recovery and factory reseting the whole phone. However, it still means that the info on your sd card will be lost. It also needs a rooted device.
This method does not require you to access your bootloader or use fastboot. You can do this while having your phone in custom recovery.
DO NOT ATTEMPT UNLESS YOU FEEL COMFORTABLE WITH THE INSTRUCTIONS. THERE ARE ALWAYS RISKS WITH FORMATTING. DO NOT HOLD ME RESPONSIBLE FOR BRICKED DEVICES. YOUR DEVICE IS LIKELY OUTSIDE OF WARRANTY ALREADY SINCE YOU WOULD HAVE UNLOCKED THE BOOTLOADER.
I have taken this solution from HTC One X forums namely from post 17 at http://forum.xda-developers.com/showthread.php?t=1647806&page=2
However, I have also confirmed (SneakyGhost's partition list for HTC One S) that the correct mmcblk0p for the HTC One S sd card is mmcblk0p36.
Step #1: Download the version of busybox listed below, unzip it and also put this in the folder with ADB before you get started. You only need to do this if you dont already have busybox installed on your HTC One S. Sometimes this busybox file can be found under /system/bin or /system/xbin if youve previously installed it. If so, replace the paths in the instructions below for that of your busybox. If you have busy box already installed in /system/bin , then you do not need to type in the paths since the adb shell automatically picks up programs in that folder
Step #2: Go to your command prompt in the folder with adb.exe . Connect your HTC One S to your computer and type
Code:
adb devices
and ensure your computer sees your HTC One S. This command should work even if you are in a custom recovery like TWRP or CW (but for gods sake, if your on CW, the first thing you should do is flash TWRP, but thats just an editorial opinion, lol).
Step #3: Type
Code:
adb push busybox /data/local/tmp
This pushes busybox to a temp folder on your HTC One S. Make sure you are pushing the busybox file and not the zip file. If you already have busy box installed you do not need to do this step. (you can delete it from this folder later if you like)
Step #4: Type
Code:
adb shell
to get into your linux shell. Then type
Code:
su
to get root access. Your command prompt should now be a # and not $.
Step #5: Type
Code:
chmod 755 /data/local/tmp/busybox
to fix permissions for busybox. You may not need to do this if you already have busy box installed with the correct permissions. If these instructions dont work with your version of busy box, try setting the permissions with this code but replace the path with the location of your busybox.
Step #6: Type
Code:
cat /proc/partitions
and just ensure you see mmcblk0p36. This is the sdcard partition for HTC One S
Step #7:Type
Code:
/data/local/tmp/busybox mkfs.vfat /dev/block/mmcblk0p36
Make sure you type this correctly. You dont want to format the wrong partition accidentally.
That should work. Pls let me know if it doesnt. If it doesnt work with your version of busybox just try using the one in the zip file below. Also remember, dont just push the zip file. Extract the busybox file from the zip and push that to your device instead.
Also, it may help to use adb through a custom recovery instead of being in your ROM (ie if it doesnt work when your phone is booted normally, try doing the steps with recovery loaded).
There are other methods to try too They would be:
Other Solutions
Other Method #1: Relocking your bootloader and using a compatible RUU with your phone. This will fully wipe your device
Other Method #2: If your computer sees your sdcard even if it cant open it when your device is connected, you can try formatting it that way (ie the way you would format any other drive on your computer)
Only use the busybox method if you are comfortable with it and if other methods have failed. You can learn more about the formatting command (ie mkfs.vfat) by googling it.

So if I got this right if I have busybox already I only have to do is step 7.

Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium

Step 4, a quicker way: adb shell su , get you into shell as root right away

AKToronto said:
Almost, but yes, that is the key step. Although you would still want to open a terminal Window, either an adb shell or from the phone, and type su to get root, and double check to ensure the shell sees the partition. Also, I did hear in the one X forums that not every version of busy box worked. I would imagine an updated version would likely work though.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.

Darknites said:
Oh right hope I don't need it lol.
I think this should be moved to Q&A and replace the other sticky that's there.
Click to expand...
Click to collapse
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?

AKToronto said:
Im thinking it would be helpful to have this post there. Im not sure how I request to do that though. Should I PM a moderator?
Click to expand...
Click to collapse
No idea but does sounds like a good start lol.

Darknites said:
No idea but does sounds like a good start lol.
Click to expand...
Click to collapse
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.

AKToronto said:
I asked a moderater to review by clicking on the ! in the post, but I havent heard back yet. I also updated the post to be more n00b friendly too, and tried to cover off all sd card related issues.
Click to expand...
Click to collapse
Nice update. Ya I wish they hurry up with sorting it, the other one is a load of crap and this really should replace it.

Updated with a link to another good tutorial about pushing ROMs to the phone

Its like they don't care about stickys any more, come mods its about time this replaced the crappy one.

Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.

AKToronto said:
Does your bootloaderscreen say "fastboot usb" anywhere? There is an option that you have to select in your bootloader called fastboot... If it says fastboot usb then you are connected, and you shouldnt get a waiting for device error.
Click to expand...
Click to collapse
yea I got into the bootloader and then fast boot. ive managed to sort it now, for some reason my pc was the problem, I had to reboot my computer after a command window prompt otherwise I just got the waiting for device screen.
typical really, my laptop and phone both conspiring against me.
eventually managed to flash another recovery which did see my sdcard so all is good now.
thanks for your reply though!

AKToronto said:
For those who may be flashing ROMs, cannot mount the SD Card any more, and may have accidentally corrupted their SD Card, here are some helpful steps.
Click to expand...
Click to collapse
Dude, this works flawless!
Thought I had a soft-brick, but your instructions bring back my sd-card!
I choose the "advanced Option", it works fine....
Typing su-command generated an error message, but the other steps still functioned....
I will place link in section "helpfull links" in my signatur
Big THX to you good sir, ...

Steveh8204 said:
Cant get past the
'fastboot flash recovery ville_recovery_signed.img'
step at the moment, just keep getting 'waiting for device'.
Click to expand...
Click to collapse
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium

$droyd$ said:
Just format your phone using your PC... That's all you need to do...all those steps are overkill... Bootloader on phone... Connect to pc .. Navigate to devices on PC and format your phone...then flash recovery like stated above..
Sent from my One S using xda premium
Click to expand...
Click to collapse
Some people had reported not being able to see their phone from their PC no matter what they tried... Hence the advanced steps

Dude add S3 stock recovery please.

Darknites said:
Dude add S3 stock recovery please.
Click to expand...
Click to collapse
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.

AKToronto said:
Good point Darknites. Thank you. Do you have a link to S3 stock recovery? I dont seem to have one handy... But I did edit the OP to make that point a bit clearer (that the link is for S4 devices). Thanks again bud. Good catch.
Click to expand...
Click to collapse
Nope but a RUU will have it.

[ROOT] Acer Iconia Tab A110 (All Things Root)

After lots of hard work by a great team of people (listed at the end), we have finally made a working Root for the Acer Iconia Tab A110.
Warning:
Code:
*I, nor any of the people involved in the rooting process of this
tablet are responsible for any damage you may cause to your device.
*If you brick your device, we are not to blame.
*Your warranty may be void after doing this.
*By using this guide, you acknowledge that you are fully responsible
for any damage you cause to your device and the device accessories.
ACER ICONIA TAB A110 ROOT GUIDE 4.1.2
UPDATED NOVEMBER 13, 2013; Most Recent Version​
You will need to download/install the following before starting:
Acer Iconia Tab A110 USB Drivers (Should install on first connect of tablet)
Android SDK
SuperSU
a110-412-CWM-recovery.img Mirror: a110-412-CWM-recovery.img mirror
___________________________________________________________________________
Once downloaded, extract the Android SDK to a known location, such as the Desktop. (Use an extracting application such as Winrar)
Next, install the Nexus 7 Toolkit.
___________________________________________________________________________
Once that is complete, you can begin the rooting process.
On your device go to:
Code:
Settings > Developer Option
Turn Developer Options on at the top, and enable USB debugging.
Navigate to your Android SDK folder:
Code:
adt-bundle-windows-x86_x64\sdk\platform-tools
Copy and paste the recovery file in this directory, and copy the SuperSU files to the Tablet's SD Card. This will make the process easier later.
___________________________________________________________________________
Bootloader unlock:
The next step will wipe all your data. Remember to create a backup of anything you want to keep before attempting this.
Open a command promt (CMD) window in the directory above by holding shift while right clicking in the window and selecting "Open Command Window Here."
Type in CMD:
Code:
adb devices
Code:
adb reboot bootloader
Wait for the tablet to load into the bootloader, then type:
Code:
fastboot oem unlock
Accept on the tablet via volume and power buttons.
Your bootloader should now be unlocked.
___________________________________________________________________________
Root:
Type:
Code:
fastboot reboot-bootloader
Wait for it to reboot, once again.
Next, type:
Code:
fastboot devices
Code:
fastboot boot a110-412-CWM-recovery.img
Wait for the "OK" notification.
___________________________________________________________________________
Now, you will be booted into the custom recovery.
Right click on the Acer A110, and select install driver. Choose to point to your own path, and point it at the path for the Nexus 7 Toolkit install. (Make sure you have include subfolders checked)
Now, the device should be recognized and the root can continue.[/Code]
___________________________________________________________________________
On the device, use the volume buttons to navigate and power button to choose.
Select Install from SD.
Now type:
Navigate to the CWM-SuperSU-v0.99.zip file.
You should receive a complete message.
Once that is complete, on the tablet, navigate to reboot, select yes at the prompt, and the tablet will reboot.
You are now successfully rooted on 4.1.2!
___________________________________________________________________________
Special Thanks to the following people for their ongoing hard work:
fringle
FriedBacon
Skellums
posterz
heX79
blokenfeffer (New Recovery Image)​

Stock Recovery
Here is a link to the Stock recovery pulled off of my tablet.
Not sure if it works or not, but if someone wants to try:
Stock Recovery
Installing Applications/Games to the External SD Card
I spent a long time looking for a program that allows me to do this, and finally found one that fully works.
DirectoryBind works wonders.
Here is a link to the guide:
DirectoryBind
Enjoy your extra storage space!

Reserved for further development..

Reserved for further development...

Reserved for further development

Thanks to the root method ? Could you tell me how to perform full system backup?
DjDom said:
Reserved for further development
Click to expand...
Click to collapse
I am a newbie to android. could anybody tell me how to perfrom full system backup for acer a110 4.1.2?

There is currently no way to make a full nandroid. However, if you want to back up the contents such as apps and data, use an app like my backup pro or titanium backup.
Make sure that it saves on external SD, not internal or you'll lose everything.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app

root error！ help！
DjDom said:
There is currently no way to make a full android. However, if you want to back up the contents such as apps and data, use an app like my backup pro or titanium backup.
Make sure that it saves on external SD, not internal or you'll lose everything.
Sent from my Acer Iconia Tab A110 using XDA Premium HD app
Click to expand...
Click to collapse
thanks!
it seems there is an error while i root：
-quote-
adb server is out of date. killing...
ADB server didnt ACK
*failed to start daemon*
error: unknown host service
-unquote-
give advise please.
thanks in advane.

cooltravis said:
thanks!
it seems there is an error while i root：
-quote-
adb server is out of date. killing...
ADB server didnt ACK
*failed to start daemon*
error: unknown host service
-unquote-
give advise please.
thanks in advane.
Click to expand...
Click to collapse
Did you download the most recent version of ADB?
Make sure you install all the drivers and follow the beginning of the guide.

Completed process but no root
I finished the process but it did not work with the first img I will try with the other one

francois2012morin said:
Does not work for my tablet. It does not unlock the bootloder so I don't get the recovery file to load.
Is it a problem with the version of my tablet software.
Here are the specifications
Android 4.1.2
Core 3.1.10
Image version Acer_AV051_A110_RV00RC09_WW_CUS1
BUILD NUMBER Acer_AV051_A110_1.049.00_WW_CUS1
Image ref FM.S1RA0.03E
Thank you if you can be of any help.
Francois
Click to expand...
Click to collapse
How did you try unlocking the bootloader?

after you type "fastboot oem unlock" look at your tab and use the buttons to select it. It gives you about 10 seconds until it reboots back to the bootloader
Oh and I can't get the sideload to kick in. I put in "CWM-SuperSU-v0.99.zip" but it doesn't do anything.
Im wondering if I can push it over using adb install bc adb sideload isn't working?
Thanks

running_onCode said:
after you type "fastboot oem unlock" look at your tab and use the buttons to select it. It gives you about 10 seconds until it reboots back to the bootloader
Oh and I can't get the sideload to kick in. I put in "CWM-SuperSU-v0.99.zip" but it doesn't do anything.
Im wondering if I can push it over using adb install bc adb sideload isn't working?
Thanks
Click to expand...
Click to collapse
I had the same problem with Sideload. Are you following the part where you need to install the drivers from the Nexus 7 toolkit?

DjDom said:
I had the same problem with Sideload. Are you following the part where you need to install the drivers from the Nexus 7 toolkit?
Click to expand...
Click to collapse
Yea. Everything. Anyway to get passed it?

Im trying to root my tablet with your guide but I can't find the A110 in the device manager after I boot the custom recovery

darthpilsner said:
Im trying to root my tablet with your guide but I can't find the A110 in the device manager after I boot the custom recovery
Click to expand...
Click to collapse
Yes i am having the same problem, mine does not see a110 but refers to google galaxy nexus adb interface. I have tried this about half a dozen times with the same result, no root. Oh well try try again. Do i need to factory restore after each failed attempt?

No Root....
Hello
I have tried this guide about 15 times... I factory reset after each try... I uninstall the drivers on the pc and make sure I install the Acer drivers.... Follow the guide to the letter... Install the google drivers... I do the sideload of su and it looks like works.... but not root... I am not sure why... Everything looks good... I am unlocked... the recovery image loads well... I replace the drivers..... I sideload.... no root.... So strange.... I guess I should just be happy it is not bricked .. .lol... Thanks for the work... Oh well... I am not looking for help... just making you aware.... thanks for all the work though...

rocy1971 said:
Hello
I have tried this guide about 15 times... I factory reset after each try... I uninstall the drivers on the pc and make sure I install the Acer drivers.... Follow the guide to the letter... Install the google drivers... I do the sideload of su and it looks like works.... but not root... I am not sure why... Everything looks good... I am unlocked... the recovery image loads well... I replace the drivers..... I sideload.... no root.... So strange.... I guess I should just be happy it is not bricked .. .lol... Thanks for the work... Oh well... I am not looking for help... just making you aware.... thanks for all the work though...
Click to expand...
Click to collapse
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.

Same
justinnickovtime said:
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Click to expand...
Click to collapse
Model a110
Android 4.1.2
Kernel 3.1.10
image acer_AV051_a110_rv00rc09_pa_cus1
Build acer_AV051_a110_1.049.00_pa_cus1
everytime I do it .... it looks like it will work... then check root with rootchecker or susuperuser.... no luck.....
If the root did work... would app2sd work... or do I have to wait for a custom rom?

Same result here!
justinnickovtime said:
I'm having the exact same problem as you. Not sure if it'll help, but my firmware version has PA in it.
Click to expand...
Click to collapse
Exactly the same results as the previous guys, every step appears successful, including sideload, but no SU after reboot. My Firmware has WW in name.
Only messages seen during sideload which imply errors are E: can't mount /cache/recovery/log etc etc.
Anyone any idea what may be wrong?

[Q] synergyRom plan B help

Hi i am trying to do this part
Part B (SynergyROM's "Plan B" manual backup):
1. Download the attachment at the bottom of this post. This is an update ZIP you can run right from recovery.
2. Reboot into recovery. On stock this can be done by turning off the phone and then turning it back on while holding UP and HOME.
3. CWM: Use VOL UP and VOL DOWN together with HOME to select "install zip from sdcard" then "choose zip from sdcard". Navigate to the folder you downloaded it to (most likely Download/). Select the zip you just downloaded to "flash".
Click to expand...
Click to collapse
my vzw s3 is stock and this is my first time trying to root and flash roms. so i downloaded the file in step 1 and put that zip file in my micro sd and enter recovery by hold vol up and home button and press the power button once in there i proceed to install file from external device (microsD) i run that file i downloaded in step 1 and i see green texts activity and after 3-4 lines of texts i see " E: Signature verification fail" in red texts and it continue to output 3-4 green texts after that and it auto reboot. i also want to make and go to my external sd to verify if anything wrriten in it and i dont see any new folder created..
anyone can help me? is this a problem or normal?
thanks

tainle said:
Hi i am trying to do this part
my vzw s3 is stock and this is my first time trying to root and flash roms. so i downloaded the file in step 1 and put that zip file in my micro sd and enter recovery by hold vol up and home button and press the power button once in there i proceed to install file from external device (microsD) i run that file i downloaded in step 1 and i see green texts activity and after 3-4 lines of texts i see " E: Signature verification fail" in red texts and it continue to output 3-4 green texts after that and it auto reboot. i also want to make and go to my external sd to verify if anything wrriten in it and i dont see any new folder created..
anyone can help me? is this a problem or normal?
thanks
Click to expand...
Click to collapse
This entire process must be done AFTER you have rooted and unlocked. You'll need CWM or TWRP recovery in order to flash those Synergy zips.
Sent from my SCH-I535 using Tapatalk 4 Beta

SlimSnoopOS said:
This entire process must be done AFTER you have rooted and unlocked. You'll need CWM or TWRP recovery in order to flash those Synergy zips.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
okay thanks for the help i will do that after roooted and unlocked bootloader

Step 1: Download these files to your pc:
Samsung Driver- http://tinyw.in/Fdoz
RootDebugFS- http://goo.im/devs/invisiblek/i535/Root Debug FS.7z
Step 2: Install samsung drivers to the pc and unzip the RootDebugFS tool to desktop.
Step 3: Connect the device with the oem usb cable to pc.
Step 4: On your device, Make sure USB Debugging(settings/developer options/usb debugging) and Install of Unknown Sources(settings/security/unknown source) is checked.(Also, make sure there are no other android devices, emulators, or any tethering programs running!!).
Step 5: From the PC, Open the Root Tool folder you downloaded in step 1 and Double click "RootDebugFS". press 1 then hit enter.
Step 6: Agree to all of the disclaimers by pressing Y after each one pops up.
Click to expand...
Click to collapse
i need help with this part. first i cannot download the samsung drivers in that link, error 404. so i got go on with the steps without the samsung drivers and run the rootdebugfs at step 6 and agree to all dislaimer and it start to run commands on it own and in end command line it said "Failed...." for every lines so i dont know why and the phone did reboot twices and now i am stuck at this screen and not sure what it mean in the command prompt. it say " Testing superuser... /system/bin/sh: /system/xbin/su: not found uid and gid should both be 0. Are they? <y/n>
should the uid and gid be 0? and i get all the failed when running the rootdebug is because i dont have the samsung drivers? or i am doing something wrong? thanks for the assistant

tainle said:
i need help with this part. first i cannot download the samsung drivers in that link, error 404. so i got go on with the steps without the samsung drivers and run the rootdebugfs at step 6 and agree to all dislaimer and it start to run commands on it own and in end command line it said "Failed...." for every lines so i dont know why and the phone did reboot twices and now i am stuck at this screen and not sure what it mean in the command prompt. it say " Testing superuser... /system/bin/sh: /system/xbin/su: not found uid and gid should both be 0. Are they? <y/n>
should the uid and gid be 0? and i get all the failed when running the rootdebug is because i dont have the samsung drivers? or i am doing something wrong? thanks for the assistant
Click to expand...
Click to collapse
Well, you need to use Open1your1eyes0 thread to root/unlock.
As for DebugFSRoot, just read the top of its thread and you'll see where you went astray.

SlimSnoopOS said:
Well, you need to use Open1your1eyes0 thread to root/unlock.
As for DebugFSRoot, just read the top of its thread and you'll see where you went astray.
Click to expand...
Click to collapse
i installed cwm 6.0.2.3 and in the recovery i cannot mount my sd, i believe that any sd 64gb+ class 10 will not work? and i have to use TWRP recovery? if so how do i install twrp recovery? just use odin and flash it and it will override the cwm recovery?

tainle said:
i installed cwm 6.0.2.3 and in the recovery i cannot mount my sd, i believe that any sd 64gb+ class 10 will not work? and i have to use TWRP recovery? if so how do i install twrp recovery? just use odin and flash it and it will override the cwm recovery?
Click to expand...
Click to collapse
Just use Odin. Or reformat the sdcard to Fat32 and lose ability to transfer >4gb files.
Sent from my SCH-I535 using Tapatalk 4 Beta

hey thanks for the help

SlimSnoopOS said:
Just use Odin. Or reformat the sdcard to Fat32 and lose ability to transfer >4gb files.
Sent from my SCH-I535 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I think you have become the noob helper. I gave up because it seemed like to many people was not reading and bricking. Never seen so many people bricking devices until the price of this phone went down.
Sent from my GT-P5113 using xda premium

bbqsfire said:
I think you have become the noob helper. I gave up because it seemed like to many people was not reading and bricking. Never seen so many people bricking devices until the price of this phone went down.
Sent from my GT-P5113 using xda premium
Click to expand...
Click to collapse
Nah, I'm just a part of the community my friend. It helps to pace yourself. Plus I learned at work, the hard way no doubt, that I don't have to do everything because there's plenty of folks capable of helping.
Sent from my SCH-I535 using Tapatalk 4 Beta