Database Info

For extreme noobs like myself info reg rooting & clockwork recovery

About a day ago I didn't know anything about rooting and what it was but now I know to a degree from many hours of reading.
These are the steps I did.
You have to make sure that you choose the correct one click root method for the DI07 patch. Obviously you need to put the epic in debugging mode and click on the appropriate run.bat command and let the batch run. That part wasn't to hard for me, pretty much self explanatory.
Also to check for "root", to make sure your epic is rooted, download titanium backup from the android market and if it launches your epic is rooted and plus it will say root status "ok"..
The part I had issues with was with the one click clockwork recovery. Especially when people started talking about typing in commands in the dos prompt. I'm ok with doing that but it wasn't explained in full detail regarding what to do.
So first thing that I had to figure out was what they meant by c:/android-sdk-windows/tools and where was this located. I didn't have this file on my cpu on the c: drive and i was lost at this point being that I didn't know where to get it. I later found out and if im wrong please tell me you had to create your own folder on your c: drive so you can point to it from the c: prompt in dos. So I went ahead and did that.
In the tools folder from android-sdk-windows folder you would go ahead and place the contents of the clockwork recovery files in the tools folder. So wahla I now have a folder I can point to in the dos prompt. At this point I still didn't know if this is going to work or not but I felt like I was close.
Next step was to follow "open up command prompt and redirect it to your C:/android-sdk-windows/tools folder and then run the following code."
adb devices
adb shell
su
remount rw
exit
exit
first you need to type cd C:/android-sdk-windows/tools and press enter to point to that folder. And run subsequent commands from there.
If when you type in adb devices and a device does not pull up that means that the usb drivers are not installed properly for the epic phone and you need to look into that first.
After you run those commands now you can go ahead and run the run.bat file for the clock works recovery. But also make sure your still in debugging mode.
This might take a few tries but it will eventually work and if it does not work after trying to flash the recovery and the epic reboots pull the battery (reinstall battery) and then try to go into recovery by pressing the vol down--camera--and power button at the same time and you should see a green recovery screen.
I wish someone had typed something like this sooner so I wouldn't of had issues.
I hope this helps at-least one person.

Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305

Whosdaman said:
Good idea except it's already been done :-\
http://forum.xda-developers.com/showthread.php?t=786305
Click to expand...
Click to collapse
I know I was trying to follow that but there was parts missing that I didn't understand for ex. the part where I had to create the actual folder it never stated to create a folder but it wanted you to point to it in the dos prompt. And yes that tutorial did help out tremendously but i was still a little lost. My explanation fills in the missing gaps or parts. But thank you for pointing that out.

Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?

jimmyz said:
Maybe with noobnl latest version of the clockwork installer (version 32 with mount rw included in the script) you no longer need to go into adb?
Click to expand...
Click to collapse
That is correct. Version 32 is truly one-click.

mattallica76 said:
That is correct. Version 32 is truly one-click.
Click to expand...
Click to collapse
Thats true

I'm not quite as noobish as the OP but I'm a complete noob to Android and -nix os's in general (besides a tiny bit of unix experience and a non-fear of command-line interfaces). Still, I have enough fear of the process to wait until Epic ROMs are a little further along and more refined to the degree that that's possible. If I weren't quite so noobish I'd dive right in.

[GUIDE][10/5/10]Comprehensive Guide to Rooting, Flashing, and Android Basics!

1.0 – WELCOME AND DISCLAIMER
So, it seems like a lot of people are having problems with their new Samsung Epic 4G. I thought I'd take a minute and throw together a little comprehensive guide on, well, everything. I'll be updating this periodically, so be sure to check it out.
I'll also be working on formatting it to improve readability... I'm not so good with this markup language that forums make you use, so bear with me. If I can figure out some basic tricks, we'll be in business.
And, just so you know, this is just a guide. As long as you follow it and do research, everything should go fine. That being said, I am not responsible for what happens to your phone. This is all elective and I am not forcing you to do any of this. You brick your phone, you own up to it. I'm only trying make it as easy as possible for your to avoid that.
2.0 – GETTING STARTED
New to Android? Need to root? Just got your phone? Not totally clear on everything? Start here. Even if you have experience with Android, had your Epic since day one, or whatever, you'll still want to check this section out.
2.1 – TERMINOLOGY
First of all, you need to familiarize yourself with the terminology. This is vital to understanding what you are doing, so I'll outline as many as I can.
Brick – Not a term that should be thrown around as much as it is. If you have a bricked device, it is worthless. Like, completely. It is literally as useful as a brick. You CANNOT fix a brick. Everything else is just just breakage.
Root – a)This term comes from Linux/UNIX. To obtain root access means that you have elevated privileges. Look at this like administrator rights in Windows. It's what allows you to run custom software and access administrator setting in Android.
b)The uppermost folder. Such as “/”, “C:\” , et cetera.
Rooting – Gaining elevated root admin access.
Kernel – A kernel is the base of an operating system. For Android, it's where all the drivers and system information resides. A custom kernel can contain undervolting instructions, overclocking instructions, and many other battery-saving, power-giving, phone-enhancing features. There are several options, so make sure you do your research and choose the kernel that offers what you are looking for.
Shell – The shell is the part that you see. It's the interface that interacts and allows you to interact with the kernel.
ROM – A ROM is the combination of a kernel and a shell. Think of this like an operating system.
Dev – Dev is short for developer. These are the people who spend their days and nights writing code and bug testing to bring you the ROMs you love. These guys are the reason you're here, so show your appreciation!
Chef – Chefs and devs are essentially the same thing.
Recovery – A system that allows basic phone function. You can flash from this, clear data, and do very basic debugging. As long as you can boot to this, your phone is NOT bricked.
Flashing – The act of installing a ROM or fix to your phone through recovery.
Wiping – The act of performing a factory reset or cache clear from recovery. Your settings are gone, your apps are gone, your phone is as it was when you you got (to an extent). Formats /system/. This is not reversible.
CPU – Central Processing Unit. The brain of the phone. All data travels through this at some point.
Overclocking – Pushing your CPU to its limits. The CPU has a stock clock speed (1GHz for the Epic), and overclocking is pushing it past that.
Undervolting – Making the phone use less power. This saves battery.
AOSP – Android Open Source Project. Frequently referred to as “Vanilla”. The actual people who make Android. Go here for more information.
Theme – A cosmetic change to the user interface.
One-Click – A script or program that does everything for you.
Busybox – A collection of scripts that allow deeper editing of the system while it is running.
Remount – An easy method of mounting /system/ for writing.
Stock – Samsung-released, no editing, as-is stuff. Basically, how the phone came.
OTA – Over the air. Updates that automatically come to your phone, through your service.
adb – “Android Debug Bridge” A debug program for accessing your phone.
deODEX – Combining the ODEX file and the APK files for all the items in the /system/ folder. Allows for easier theming and customizing.
FC/Force Close – When a program or app crashes.
2.2 – WHY SHOULD I ROOT MY PHONE?
Rooting offers several great things including, but certainly not limited to, access to hidden features, total customization, better battery life, and overclocking. It gives you control over the device that you paid money for in the first place. The devs here are great at finding features that the manufacturers left out or disabled and making them work.
It also is a great hobby. Even if you aren't a developer yourself, flashing ROMs and trying out new features can be a lot of fun and definitely kill boredom. And who knows? Maybe you'll end up learning something and start coding yourself.
2.3 – ROOTING
Great! Now you know some words! So, what next? Well, we need to achieve root access on your phone. There are a few ways to accomplish this on the Epic. Please note that the one-click methods are hit and miss and are affected by several factors, including computer speed, cable, USB ports, and, for all intents and purposes, random chance. I HIGHLY recommend you open the .bat files and run every command in adb manually. I'll update this guide, eventually, with how to do this.
If you're running Windows, you're going to need the drivers for this phone. Install them BEFORE connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
You'll also need to put your phone into debug mode. After you turn this on, you can just leave it on. To do this, go to settings, and then to applications, then to development, and then tick the “USB debugging” check box.
I also recommend using a cable other than Samsung's cable that came with the phone. Really, that cable is hardly good for anything more than charging. It's low quality and has caused a lot of users more than a headache. If you are unable to get another cable for whatever reason, run each command individually from adb. Check the section about adb and the Android SDK later in the guide for more information on how to do that.
2.3.1 – The Jokeyrim temporary root with noobnl's one-click script method – DO FIRST
Let it be known that I don't recommend relying on this method. It's janky and can cause problems once you get deeper into Android modification. Use it to get your remount scripts and then quickly do the kernel mods in the steps in 2.3.2.
Go here and download the .zip file. Extract the .zip contents to your desktop. Open the folder, run “run.bat” and let it go.
NOTE: This is just root, this is temporary, and this DOES NOT give you access to a recovery. All this will allow you to do is run applications that require root or busybox and adds the remount script.
2.3.2 – The rooted kernel and recovery method method – DO SECOND
I do recommend that you use this method. This gives you true, permanent root.
There are a couple of ways to do this. I actually suggest you follow both guides, too. This will help prevent you ever getting to Samsung's stock recovery, which is worthless for your purpose.
The first is noobnl's recovery method, and definitely the one you should do first. You can find it here. Download the .zip file and extract its contents to your desktop. There is an issue with this .bat file, so you're going to have to do some extra steps. With adb (go to the section about the Android SDK and adb further in the guide if you do not know what this is) and type:
Code:
adb shell
su
remount rw
exit
exit
(the two 'exits' is not a typo)
After running those commands, open your extracted folder and run the run.bat file. Should be smooth sailing.
The second is koush's method. koush's thread is here, but I that's a complicated method. After you do noobnl's method above, go to this thread and download the .zip from that. Put that .zip on the root of your SD card. Boot into the Clockwork recovery by turning the phone off, holding down the camera button, the volume down button, and pressing the power button until the phone turns on. Once in there, do this:
1. BACK UP YOUR PHONE. I cannot emphasize this enough. Backups are sooo important in your Android modding quest. Backup and do it often. (Backup and restore → Backup).
2. Go to “Flash zip from SD card”
3. Choose zip from sd card
4. Select the zip we put there earlier
5. Click “Yes”
6. Let it do its thing
Once you've done this, you need to boot into the phone, go to the market, and download “ROM Manager”. From that, click “Flash recovery” (the top option) and select the Epic. This will take a minute. From this point on, you can use ROM Manager to boot into the Clockwork Recovery.
2.3 – FLASHING ROMS/KERNELS/FIXES
This is the fun stuff. This is why you're here. Now that you have root and a recovery, we can get some work done. First, you have to select a ROM that you want. Always pick a ROM that is designed for the Epic. ROMs designed from other phones can and will brick your phone!
You can find ROMs for the Epic in the Epic 4G Android Development section of XDA. Do some research to each ROM to make sure it's what you want. If you want a kernel, make sure your ROM supports other kernels and that the kernel supports your ROM.
Once you've picked your ROM, put it on the root of your sd card and then boot into Clockwork Recovery using your method of choice, then:
1. BACKUP. I seriously cannot stress this enough.
2. Wipe everything. Factory reset and clear cache.
3. Go to “Flash zip from SD card”
4. Choose zip
5. Choose “Yes”
6. Let it run
7. -OPTIONAL- To ensure it worked, repeat steps 2-6. This is just to make sure everything worked. Problems with this can be intermittent and this helps to avoid them.
8. Reboot.
3.0 – ERRORS
Stuff goes wrong. You have to understand, EVERYTHING in this is experimental. The devs here do not have access to EVERYTHING that is required to make these phones work and have to guess at some things and, basically, just do their best (And their best is pretty damn good!).
Basically, just be sure you have backups that you can restore from, and this will all be fine.
3.1 – BLACK SCREEN
Oh no! I flashed ROM X and now my phone won't boot and I hate everything!!!
Worry not! As long as you can boot in to recovery, you have nothing to fear. Just restore the backup that I told you to make and you're back in business. Easy fix.
3.2 – CONSTANT FORCE CLOSES
You boot up your phone and are immediately greeted with force closes. Chances are that you didn't wipe OR that the ROM you're using isn't ready for show time. Again, just restore your backup from Clockwork.
3.2 – CAN'T GET TO RECOVERY, CAN GET TO DOWNLOAD MODE
Well, looks like you'll be returning your phone to stock using Odin. Read later on in the guide how to use Odin in the section about Odin.
3.4 – PHONE WON'T TURN ON AT ALL
Welcome to bricksville, population you. Sorry, but you're phone is a $500 paperweight... Probably shouldn't have flashed that GSM ROM, huh? Not even Odin can save you at this point...
4.0 – THE ANDROID SDK AND ADB
The Android SDK (Standard Developer Kit) is a tool freely available to everyone. You can find it here and it is available for Linux, Mac, and Windows.
4.1 – INSTALLING THE SDK
So, the first step is going to be how to install the SDK on your system. I have experience with Linux and Windows, so that's what I have for now. If someone with a Mac can help write the set up instructions for that, I'd be very appreciative.
4.1.1 – Windows
First, download android-sdk_r07-windows.zip from here to your Desktop. Once it has downloaded, double-click the file and extract it to the root of your C:\ drive (this is optional, but it will make things a lot easier in the future). Rename the extracted folder “android-sdk-windows” to just “android” to make your life easier.
Open the new folder, then run the SDK Manager. If you run into an error about Java, go to java.com and get the latest version of the Java JRE (pretty much just click whatever the biggest “download” button is that you first see).
Once you have the SDK open, it will ask you to install packages. Just tick the “Accept All” radio button on the bottom right and press install. Depending on your internet connection, this can take a long time. Just be patient. Once they are all installed, you're good to go.
How you use adb is simple. Open a command prompt (press the Windows key + r and type “cmd” in the box that shows up, or go to Start → All Programs → Accessories → Command Prompt) and type in “cd C:\android\tools\” and type your commands (list of common commands at the end of this section.
-OPTIONAL- This step is optional, but HIGHLY recommended. Now that we have the SDK set up, we're going to adb to the Windows paths so that you can use adb from anywhere you can open a command prompt.
First, click the start menu and then right-click “My Computer” (Just “Computer” in Vista and 7. You'll also need to click the “Advanced System Setting” on the left side of the window that appears.). Click “Properties” and the Properties window appears. Now, click on the “Advanced” tab and the the “Environment Variables” button. A new window appears with two scrollable boxes. In the lower box, scroll until you find a “path” option and select it. Click “Edit” underneath the box. Move your cursor to the very end (Press END on your keyboard, just to be safe) and type “;C:\android\tools\”” (That leading semi-colon is important and may already be there. Check to be sure).
And you're done! Open a command prompt and type “adb devices” and see what comes up. If a list of devices (phones; will be empty if your phone isn't connected in debug mode) comes up, you've succeeded! Congrats.
4.1.2 – Linux
I use Ubuntu personally, but most of this information should be universal. If anyone running anything else sees anything missing or wrong with other distributions, let me know and I'll update or fix it.
First, you need to acquire the SDK. The file is android-sdk_r07-linux_x86.tgz from this site. Once downloaded, extract the contained folder to your home folder (/home/*USERNAME*, using your username) and rename the folder “android' for later ease of use.
Use terminal and cd to the android folder your created. Use the command “tools/android update sdk” to make the SDK updater come up. Just tick “Accept all” in the bottom right and then click install. This can take a while depending on your internet connection.
Once you have all of the files installed, you're ready to use adb. Using terminal, navigate to /home/user/android/tools and type (For Ubuntu):
Code:
sudo chmod 777 adb
This will allow the adb file to be read as an executable. Note that this only has to be done once. Then, use this code:
Code:
sudo ./adb start-server
(replace 'sudo' for 'su' for distros other than Ubuntu)
This is necessary every time you use adb (in Ubuntu, at least). You only have to do it once per session, but if the adb process is ever killed during your session, you must do it again. I've just gotten into the habit of doing it every time I log into my computer. You could also create a boot script that does this for you... which I've been meaning to get around to. After you have the process running, you won't have to use su/sudo or ./ to use adb.
Note that one-click scripts written for Windows will have to be opened and run manually. There are scripts for Linux floating around, but I can't seem to find the thread.
-OPTIONAL- This isn't a needed step, but you'll probably want to do it. Here we're going to add adb to the paths folder so that after you have started the process as an administrator, you can run it from any folder.
Open terminal and use these commands:
Code:
echo $PATH (should return the directories associated with $PATH)
export PATH=$PATH:/home/user/android/tools (replace with path to your tools directory, you may need to add 'sudo' or 'su' to the beginning of this cmd)
echo $PATH (you should now see your tools directory added to the end of the $PATH variable)
Once done, you're set. Once you have the process started, you can run adb commands from any terminal window.
4.1.3 – Mac OS
-I don't own a Mac, never have, and I have zero experience with Mac and Android... If someone else can help with this section, I'd appreciate it -
4.2 ADB COMMANDS
This isn't a complete list, but it should be enough to get you by for your purpose.
adb shell – opens a terminal on your phone. Terminal is like the command prompt of Linux.
adb push – pushes a file to the phone. The syntax is ”abd push *file location on your PC* *Location you want it on your phone*”
adb pull – pulls a file from your phone. The syntax is “adb pull *file location on the phone* *location to be placed on your PC*
adb shell rm – deletes a file from your phone. The syntax is “adb shell rm *location and name of the file to be deleted*. NOTE: adb shell rm -r is a recursive deletion and can cause damage to your ROM and phone. Make sure you know what you are doing if told to do an rm -r.
adb devices – lists all connected Android phones.​
5.0 - ODIN
(I don't have a ton of experience with Odin, so if someone can refine this section, let me know and I'll update it)
Odin is a tool that was created for previous Samsung phones. It is a powerful tool and very useful for saving your phone from many malfunctions. As long as you can boot your phone into download mode (Hold down the “1” key on the slide-out keyboard while powering the phone on) you can almost always save your phone.
That said, Odin is also fairly experimental in its implementation on the Epic. There have been several reports of failed flashes and intermittent errors. This guide will hopefully help prevent that from happening.
5.1 – SETTING IT UP
If you haven't already, you need to get the drivers for the phone. Install them BEFORE Odin and before connecting your phone to your computer. You can get them here:
32-bit: Click here
64-bit: Click here
After that, you're going to need to get Odin. You can find that, as well as a basic guide and the stock files from noobnl, here (External link to SDX). Odin is the .rar file from the first link fo the post.
5.2 - USING ODIN
After you have it downloaded, extract the files somewhere (I recommend a folder on your desktop). From the extracted files, double-click “Odin3_v1.0.exe” and the Odin window opens. Have it completely ready to go before connecting your phone. Put all your files in the spots they belong (refer to the post where you got the Odin files for instructions on that... it seems to vary a lot depending on the purpose). Make sure that no other check boxes are ticked besides “Debug En.” and “Auto-reboot”. All the others can have very negative effects.
Before connecting your phone, put it into download mode by holding down the “1” key on your slide-out keyboard while powering the phone up. Once it is in download mode, connect the phone. The first box in Odin should come up as something akin to “COM4”. If it doesn't say exactly that, don't worry. Make sure all your files are placed correctly, and then click “Start”. It should take up to a few minutes, so be patient. Cutting this process off early can have negative effects. When it is finished, the phone should reboot.
6.0 – CLOSURE
I hope this guide helped you. If you have any questions, you can contact me, but I can't guarantee I can help you. Most devs are willing to help, too, so you can shoot them a PM and they'll try to get back to you.
Good luck and happy flashing!!

[Update Log]
*10-5-2010 - Added sections for Odin and adb/Android SDK. Updated sections, fixed typos and mistakes, reorganized a little. Fixed links.

None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling of the web address or search above."

Thanks a bunch, this was a very useful tutorial on the basics and for me helped out greatly with understanding where and what you need to do to be getting the best out of these awsome phones!
blasted across the interwebs by the Epic 4g!

Lonewuhf said:
None of those links are working for me. I get sent to a page with a message saying "Sorry, we can't find "xn--http-fb7a". We suggest that you check the spelling qof the web address or search above."
Click to expand...
Click to collapse
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?

DevinXtreme said:
Weird. I just went through and checked them all and everything is working on my end. All the URLs are correct. Maybe try clearing your browser cache?
Click to expand...
Click to collapse
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/

dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
That is so weird... It's showing up like that for me now, too. I've checked the source, and it stills is showing the right links in my post.... It's something on XDA's end right now... I'll look into getting it to work a little later.

Good work! This should be a sticky!
Sent from my Epic 4G

dwyw42 said:
None of them work for me either. The urls all start: http://xn--http-fb7a//forum.xda-developers.com/
Click to expand...
Click to collapse
yeah same here, i just cleared everything before "forum" from address bar and page loaded.

You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App

mysteryemotionz said:
You might wanna ad that you need done battery life when flashing a kernal. If your phone dies during the flash your phone will be a useless brick.
You might also wanna adds the odin steps for flashing back to stock
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Unless whatever you're flashing messes with the recovery partition, an incomplete flash shouldn't cause a brick. As long as you can boot to recovery or download mode, you can save your phone.
And I'm working on an Odin section for my next update to this. A lot of things will be added next time I update the main post.
Sent from my SPH-D700 using XDA App

i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?

The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.

dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=770388
for the proper thread

^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App

bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.

you might wanna add how to set adb

Spunkzz said:
i've got the first part of your guide done by completing noobnl's method but i cant get koush's method down. you say to hold down the volume, camera, and power buttons to boot into clockwork recovery, but it seems like it goes into the stock samsung recovery? how do i get the clockwork recovery?
Click to expand...
Click to collapse
bitbang3r said:
^^^ I have the same problem he did: I followed the instructions to root, but when I tried to restart with the "Epic 3-finger salute", it went into what appeared to be the stock bootloader, not clockwork.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Vanquish46 said:
Same with me. I selected "Flash ClockworkMod Recovery" and after a number of tries it was successful. Yet when I boot with the 3 buttons it still goes into the stock recovery.
Click to expand...
Click to collapse
I think I know the issue here. It's that /system/ isn't being mounted as rw. Run the jokeyrim root method and then go into adb and type this:
Code:
adb shell
su
remount rw
exit
exit
If you don't know how to use adb, just wait until a little later tomorrow. I've got a whole section about it to add to the guide, but I don't have it completed yet (did some work on my laptop in the middle of writing it, forgot to reconnect my WLAN card and was baffled for most of the day...)
dsummey30 said:
The link for noobnl's easy method always takes me to Koush page not noobnl's might want to check your links there.
but very great idea and should be sticked on the front page.
Click to expand...
Click to collapse
Sorry about that. Should be fixed now. Thanks for pointing it out
mysteryemotionz said:
you might wanna add how to set adb
Click to expand...
Click to collapse
All in the works I expect to have the guide updated early tomorrow, if not tonight.

Updated the guide with a lot of new info. Two new sections for adb/the SDK and Odin as well as a general update to the whole thing. Some of the sections changed (HARD and EASY mode are now both required, unfortunately...) and some things got a little moved around.
Also, all of the links should now work correctly. Something about the way XDA was handling quotations... So I just stripped them all from the forum code stuff...
If anyone has any experience with Mac, I could use your help for the adb/SDK section, and I could also use some help from someone more experience with Odin for that part.
Thanks, guys! I really hope this guide helps some people.

not to be a pain Devin but the two links for noobnl's programs goes to the same page for the easy and hard method don't know if that's right or not but wanted to point it out to you.
Thanks again for the great guide.
David

{GUIDE} Rooting an HTC EVO Shift for Dummies!

First of all I noticed there is not an individual post that gives the entire root process for those that have never used ADB and probably don't have the SDK installed. In other words people that have never rooted a phone before and didn't think they ever would because they think it looks SUPER complicated.
There are several tutorial threads on this subject but I can guarantee that these are the most simple and detailed, START to FINISH, instructions regarding the root process of a HTC EVO Shift that you will find on the web. My information is compiled together from numerous sources and my own personal experience to give less confident people what they need in order to root their phone and remain at ease.
RED-REALLY IMPORTANT INFORMATION THAT YOU NEED TO READ
BLUE-Notes from my experience and further explanations
Purple-File names color coded for easy identification
NOTE: I'm not responsible if you mess up your phone, however this process worked perfectly for me and it is pretty hard these days to brick your phone unless your trying.
Rooting Process
1. First, on your computer download the program "SDK" from Here. Download the file called "installer_r10-windows.exe". Install it. When prompted for the install path paste "C:\AndroidSDK" over the default path. Once finished, open it from the Start Menu. It should be right on your "C:\" drive. Now, select "Install Packages" and make sure you install "Android SKD Platform-Tools". Once finished, close out of Android SKD and AVD Manager.
2. ONLY FOLLOW THIS STEP IF PROBLEMS INVOLVING LOADING SDK OCCURS. Next, Go to the start menu and right click on "My Computer". Select "Properties", then select "Advanced"/"Advanced System Settings", then "Environment Variables", now go to the lower box (system variables) and select "path" then "Edit". Paste the following as your path "C:\AndroidSDK\platform-tools", then select OK. This seems to have fixed most peoples problems.
3. Now, on your phone, press "Menu", then "Settings", then "Applications", then "Development". Check the box that says "USB Debugging" and press "OK" when the confirmation box appears.
4. Now, install HTC SYNC. There should be a folder on your SD card that came with the phone that has a HTC SYNC Setup in it. Just drag this to your desktop and run it. Otherwise download HTCSync. After installation, plug your phone into the computer and select "Disk drive" on your phones prompted menu.
5. Next, download the VISIONary app from Here and save it on your desktop. Once downloaded, Copy "com.modaco.visionaryplus.r14.apk" and Paste it to the SD Card root. Or in other words, drop the file in the first folder of the SD card on your phone.
6. Next, switch your phone's connection status back to "Charge Only". Use any file manager (free from the android marketplace "ES File Explorer") to install the VISIONary app on your phone. On your phone just find the visionary installer in the file manager and click to install. (Icon should look like a caution sign). Once complete, open VISIONary on your phone and click "Temproot Now". Wait for the rooting process to take place. Shouldn't take long at all. At this point your phone is rooted. However, you may noticed that your phone is running slower than normal. Go back into VISIONary and put a check next to the box that says "temp root on boot". Now power off your phone and then turn back on. This will root your phone before background apps are running, thus making it much faster.
7. Next, Download the root file Here. Once installed, connect your phone to your computer as a disk drive and right click on the "shift-root.zip", select extract here, then use browse to locate your phone, more specifically the root of your SD card. If you are having trouble extracting, download 7-Zip. Now change your connection type back to "Charge only" again.
8. Next, Open the command prompt (Start > Run > type "cmd") and paste the following...
Code:
cd C:\AndroidSDK\platform-tools
Hit enter, and type the following...
Code:
adb
If adb runs you're golden. Type this...
Code:
adb shell
Hit enter, you will see this...
Code:
$
Now type...
Code:
su
Hit enter... Now switch back to your phone. Superuser (an automatically installed program) will prompt you to "Allow" on your phone. Click it quickly to allow permissions! Now you will see this in the command prompt...
Code:
#
You have root permissions. If you didn't click allow fast enough just retype "su" and click enter again.
9. Next you have to Verify md5sum. Basically just make sure you copy and paste this EXACTLY...
Code:
md5sum /sdcard/Shift/hboot_orig.bin
Then hit enter.Your result should look like this...
Code:
386c19451e8dd18f9b98fad6b11be4c0 hboot_orig.bin
Make sure the numbers match. You may have some extra path in front of hboot_orig.bin.
If a message saying that the md5sum is not found, paste this code before verifying the md5sum. If it worked in the first place then ignore all this red...
Code:
busybox md5sum /sdcard/Shift/hboot_eng.nb0
It should work now...
Next copy and paste this exactly...
Code:
md5sum /sdcard/Shift/hboot_eng.nb0
Then hit enter.Your result should look like this...
Code:
60ec1006e6ec2e8acb370d6aad35b17e hboot_eng.nb0
Make sure the numbers match. You may have some extra path in front of hboot_eng.nbo. If these do not match do not proceed. Delete the "shift-root.zip" file on your sd card and redownload.
10. Now we're going to flash the "eng spl." This is where the unpleasant things can happen. Make sure you are in "adb shell" with superuser root permission (Granted a "#" symbol). This was explained in Step 8. If you are not in "adb shell" with root permissions (Granted a "#" symbol) then DO NOT proceed.
Now DO NOT REBOOT until you are instructed to do so!!! In the command prompt, paste this EXACTLY...
Code:
dd if=/sdcard/Shift/hboot_eng.nb0 of=/dev/block/mmcblk0p18
Hit enter. You have flashed the "eng spl." Now we need to make sure it flashed properly.
11. Run this command to pull the newly flashed "hboot" to your sdcard. Copy and paste this EXACTLY...
Code:
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check.nb0
Hit enter. Next you need to check the "md5" to see if it matches. In the command prompt, Copy and paste this EXACTLY...
Code:
md5sum /sdcard/Shift/hboot_check.nb0
Hit enter. It should read...
Code:
60ec1006e6ec2e8acb370d6aad35b17e
if the "md5sum" matches then congratulations its safe to reboot!! you can skip the next bit and continue on to step 12.
If you absolutely cannot get the eng hboot to flash right then copy and paste this into the command prompt...
Code:
dd if=/sdcard/Shift/hboot_orig.bin of=/dev/block/mmcblk0p18
Hit enter. Then pull it to check "md5". Copy and paste this exactly...
Code:
dd if=/dev/block/mmcblk0p18 of=/sdcard/Shift/hboot_check1.bin
Hit enter. Then check the "md5sum" by copying and Pasting this exactly...
Code:
md5sum /sdcard/Shift/hboot_check1.bin
Hit enter. It should read...
Code:
386c19451e8dd18f9b98fad6b11be4c0
If it doesn't, keep trying the previous 2 codes until it does but DO NOT!! reboot till it matches.
12. Now we can Perm root!!! First you need to reboot your phone into "bootloader". Do this by turning off phone and hold (power + volume down) till it boots into bootloader. Look at the top and make sure it says "s" off. If so, reboot the phone back into android by turning off and then back on.
13. Next Put the phone into airplane mode (hold down power and then click "airplane mode"). Go to setting, applications, manage applications and uninstall superuser.
14. Next, temp root with visionary. After you are temp rooted then attempt to perm root with visionary. Your phone will reboot and you are now officially perm rooted any changes you make will now stick on reboot. If it didn't stick, try doing steps 13 and 14 again.
YOUR PERMROOTED
Simplified Backup (with WiMax Backup!)
1. Find "ROM Manager" in the Market (free or paid) and install the app.
2. Open it and select "Flash ClockworkMod Recovery".
3. Click on "HTC Evo Shift 4G" and then give the app root permission if it prompts you.
4. Once the flash is successful, you should see a dialog box that says "Successfully flashed ClockworkMod recovery!"
5. Press OK.ClockworkMod should now be installed on the HTC Evo Shift 4G.
6. Before you backup your phone, open the ROM Manager application and select "All Clockwork Recoveries".
7. Select the most recent version, currently it is v.3.0.1.4 (If you already have the most current version skip to step 6)
8. Press OK.
9. Your phone will flash the most current recovery image.
10. Now once your phone finished, open ROM Manager and select "Backup Current ROM".
11. Press OK.
12. Your phone will begin the backup process, including backup of your WiMax Partition.
13. Once finished your phone will restart. DONE! A backup is now on your memory card.
UnRooting
1. Be sure HTC Sync is installed on your computer. (Link to download near top of first post)
2. Download the sprint RUU Download.
3. Plug your phone in to your PC, select "charge only", then run the RUU File
Sources:
More Detailed Perm Root Instructions
Beginner's Guide to Installing the SDK and Getting Started with ADB
ADB/Fastboot Easy 5 Minute Setup
All About Rooting the HTC Shift: FAQ's & How To's
IF YOU THINK ANY OTHER INFORMATION SHOULD BE ADDED FEEL FREE TO SHOOT ME A PM AND I'D BE HAPPY TO ADD IT.
ADDITIONALLY IF THIS GUIDE HELPED YOU OUT FEEL FREE TO LEAVE A THANK YOU.

There's already a guide and its pretty basic
Sent from my PG06100 using XDA App

JKILO said:
There's already a guide and its pretty basic
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
I understand there are already guides but they are not necessarily for people that have never rooted a phone before... And that is what this guide is for.
Other guides assume people have all the required software preinstalled and that they know what the guide is referring to when it says to "flash" certain things. They also assume people know how to Temp root using VISIONary and how to check the md5sum. This is for people that have done absolutely nothing to an android phone before and have no clue what the other guides are even talking about.
And yes I understand there are simplified guides that involve individual steps but this is a BEGINNING to END guide for Dummies so there is no need to jump across multiple threads.

To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App

i did. thanks

nice work - seems to be the one from either androidforums.com or Androidcentral forums.
This sort of does exist, maybe not so colorfully, but here is Brando's thread
http://forum.xda-developers.com/showthread.php?t=934165

JKILO said:
To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
The process in the first Perm Root guide seems simple now, but when I was first looking at the guide it was a foreign language. Did my research by looking through about 6-7 other threads and finally had some idea as to what it was talking about.
Completed a successful root on my own phone and made the first draft of this tutorial along the way. More and more info has been added to this guide as I learn more and more. Now its about a month later and I've learned quite a bit about my phone and whole rooting process in general. I've once again updated the guide to make it as simple as possible with my newly acquired knowledge. This guide has over 2500 views on another thread I initially posted and numerous people have used it to root their phone so I figured I'd post it up here as well in order to help more people.

Nice A-Z guide. When I rooted mine a month ago, I needed to get info from 2 or 3 threads and tie missing pieces together. This ends that. It is a great start to finish guide. The other ones assume that you have done this before or only provide half of the entire solution needed to get everything done.
Only suggestion, clockwordmod backs up wimax after a particular version, you may want to state that as a disclaimer...else someone may grab an old version, assume they are fine, and will/could be screwed...

riggsandroid said:
nice work - seems to be the one from either androidforums.com or Androidcentral forums.
This sort of does exist, maybe not so colorfully, but here is Brando's thread
http://forum.xda-developers.com/showthread.php?t=934165
Click to expand...
Click to collapse
I initially posted it on androidforums.com
Similar, but I went one step further than Brando and explained every process in detail. For instance, rather than saying "setup adb" and "temproot your phone using visionary" I explained the process. I know that I myself looked up how to setup adb and temp root my phone when I got to those steps. Figured I'd put everything in one thread to make it easier for people that have never touched an android before.

umrico said:
Nice A-Z guide. When I rooted mine a month ago, I needed to get info from 2 or 3 threads and tie missing pieces together. This ends that. It is a great start to finish guide. The other ones assume that you have done this before or only provide half of the entire solution needed to get everything done.
Only suggestion, clockwordmod backs up wimax after a particular version, you may want to state that as a disclaimer...else someone may grab an old version, assume they are fine, and will/could be screwed...
Click to expand...
Click to collapse
Thankyou.
I stated that clockwork can backup wimax but I'll be sure to add that it is clockwork mod version 3.0.1.4 in the OP.

JKILO said:
To each their own..maybe someone will find a use
Sent from my PG06100 using XDA App
Click to expand...
Click to collapse
IF you don't have something constructive to share.....! STFU

bash78 said:
IF you don't have something constructive to share.....! STFU
Click to expand...
Click to collapse
The threads aren't for flaming..I was just pointing out it had been done but hey you go girl
Sent from my PG06100 using XDA App

Small complaint, but kinda a big deal. You need to make sure to actually list your sources especially when you're taking directions word for word out of other threads. You must give credit where credit is due. That said, it is a great writeup, though a bit overwhelming. I wrote a guide that looks very similar to this at SDX: http://forum.sdx-developers.com/evo-shift-development/(guide)-root/
Not quite as detailed as yours, but informative nonetheless. Overall, great work, just site your sources in the OP and you'll be good to go.

tambourineman86 said:
Small complaint, but kinda a big deal. You need to make sure to actually list your sources especially when you're taking directions word for word out of other threads. You must give credit where credit is due. That said, it is a great writeup, though a bit overwhelming. I wrote a guide that looks very similar to this at SDX: http://forum.sdx-developers.com/evo-shift-development/(guide)-root/
Not quite as detailed as yours, but informative nonetheless. Overall, great work, just site your sources in the OP and you'll be good to go.
Click to expand...
Click to collapse
My sources are, and always have been, at the bottom of my post...?
And basically everything has been changed rather than just taken word for word due to the fact that I wanted it to be as understandable as possible. Most of it I wrote myself using other guides as a framework but the steps are all the same...

Sorry about that. I read through the whole thing but totally missed it. I apologize profusely for missing that and the post that resulted from it. I guess I'm just used to seeing credits at the top. Again, my bad, I'll be more careful in posting criticisms in the future.

Lol. No hard feelings. I was just really confused.

Thank you !!!! Im a dummy and this helps alot!! I thought my phone wasnt getting temp root because it was running so slow using visionary,and now i know why!!!!
Soon to be shifty rooted!!!

Stuck at installing the "installer_r10_windows.exe"
I get the message of the JDK is not found. I have installed/reinstalled 3 times with only the same results.
Steps 3-7 went through without any problems at all.
Any thoughts?

Your going to need to install the Java Developement Kit (JDK) in order for the android SDK to be able to install.
Download
It will prompt you to register it and make a Oracle account after it installs.
It should have prompted you to download the JDK during the SDK install if you don't have it on your computer already?

SHMaRiM said:
Your going to need to install the Java Developement Kit (JDK) in order for the android SDK to be able to install.
Download
It will prompt you to register it and make a Oracle account after it installs.
It should have prompted you to download the JDK during the SDK install if you don't have it on your computer already?
Click to expand...
Click to collapse
I assumed that it would have been, but it wasnt. I've done it a couple of times already, but was not successful. Even after it was registered. It still keeps telling me that I need to install the JDK as it was not found.

[Tutorial] Proscan PLT-7035-PL Root and install GAPPS

Rooting and installing Google Play on the Proscan PLT7035-PL ** UPDATED **
*** Disclaimer ***
I am not responsible for bricked tablets, voided warranties, crashed computers and/or global thermonuclear war! This is what worked for me if you are unsure of anything in the following steps STOP NOW! There is no factory rom released for this tablet. If you brick it your possibly stuck until if and when they release an update!
These instructions assume you are competent to do the folling: get files on and off of your device using the mass storage driver, able to edit and understand changes to inf files, use command prompt, edit system user files and have enough patence to read all of the steps without skipping any. There are a few gotcha's that if are skipped will leave you pulling your hair out. Also these instructions are written for Windows. If your using Linux you shouldn't need my help anyways ..​
Click to expand...
Click to collapse
This tutorial may also work on other Chinese generic tablets. You would only need get the hardware vendor and product ID's from the device info for step 2. For the purpose of this post I wont be getting into that but the information is out there.. GOOGLE IS YOUR FRIEND
Introduction
Its likely if you are reading you have recently visited Big Lots and scored a $69 7" tablet. Only to get home and find virtually NO information on rooting it or installing Google Play or GAPPs. I know I was in that boat but after a few hours of messing around I got it. I am writing this to hopefully help the hundreds of others I see out there asking for help on this.
Step 1 Download Stuff (Things to round up before you even think about starting)
Root with Restore by Bin4ry v15 - http://forum.xda-developers.com/showthread.php?t=1886460 .** UPDATE ** I attached the version I used to this post
ADB Drivers - You have several options here, milage may very.** UPDATE ** I attached USB drivers to this post. I had to seperate the 64 and 32 bit drivers to get the files under the 8 mb limit for uploads
install android SDK http://dl.google.com/android/android-sdk_r21-windows.zip and follow instructions to get the google usb drivers. Search XDA there are several guides, I couldn't find the one I used as of writing this article but there are many out there.
Search google and find a zip with just the ADB drivers.
Download Super One Click Root and use the drivers in the tools directory of the zip. http://forum.xda-developers.com/showthread.php?t=803682
Root Explorer - quick way to move and remount file systems rw with ease. I used v2.13.1. Google around and find an APK to install, just be careful there is another completely differnent package out there called "rooted explorer" it may work but I have not tried it. ** UPDATE ** I attached the version I used to this post
Google Apps for ICS - gapps-ics-20120429-signed.zip is what I used from http://goo.im/gapps/gapps-ics-20120429-signed.zip ** Update ** I replaced the URL with a direct download link from goo.im enjoy!
**NOTE** SUPER ONE CLICK ROOT WILL NOT ROOT YOUR TABLET SO DON'T BOTHER TRYING!
Step 2 install and configure your ADB USB Drivers (Let the fun begin)
Extract your zip file containing the ADB USB drivers or Install the Android SDK and follow instructions on how to use the SDK manager to download the lastest drivers from google.
Once downloaded edit the inf file (usually named android_winusb.inf)
Add the following under the [Google.NTx86] heading and again under the [Google.NTamd64] heading: (one is for 32bit systems and the other is for 64 bit Systems)
Code:
;ProScan plt-7035
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&REV_0222&MI_01
After saving and exiting. Turn on USB Debugging on your tablet. It is under Settings => Developer Options and is the first option at the top make sure it has a check in the checkbox. Exit the developer screen by pressing back or the home key and plug in your tablet to a usb port on your computer using a micro-USB cable.
Device detection should at this point detect a few devices but at least 1 will fail without drivers. Possibly more on XP systems..
Under Device Manager => Other Devices you should have a device called "PLT7035-PL" use the usb drivers modifed above to install the ADB USB Drivers.
*** Important Note ***
At this point even with the ADB Driver installed ADB will not see the tablet. We have to create or edit the file c:\users\whatever your username is\.android\adb_usb.ini
If you have already run ADB at any time on your system the file and directory should already exist. If not you will need to create the directory and the file.
on a single line simply add this to a blank line in the file and save and exit:
0x2207
This tells ADB to look for that vendor code. (if you allready have ADB on your computer 'adb devices' should now show your tablet.
** UPDATE ** This is still necessary even if using the drivers attached to this post!​
Click to expand...
Click to collapse
Step 3 Root your Tablet!
*** Warning ***
I almost bricked my tablet on this step due to an error with a faulty PlayStore I had tried to install just using the APK. It kept the tablet from rebooting properly during the root process! I recommend erasing all user data before continuing YOU HAVE BEEN WARNED!
Click to expand...
Click to collapse
Extract Root with Restore by Bin4ry v15 to the directory of your choosing.
From explorer on your pc double click the RunMe.bat and select option one.
This particular root uses the system restore function to gain root access. If everything goes right you should get a prompt on the table to restore an image.
Click to expand...
Click to collapse
Press restore ON THE TABLET without entering a password or changing anything else and after a minute or two (maybe more) it should reboot.. Do some more stuff then reboot one more time and you should now have a rooted tablet.
Step 4 Copy root explorer and gapps-ics-20120429-signed.zip to the internal storage of the tablet.
Make sure the tablet is plugged into your computer and turn On USB Storage.
Copy rootexplorer.apk and gapps-ics-20120429-signed.zip to the Downloads folder via windows explorer and the removeable drive from the tablet.
Step 5 Install root explorer
ON THE TABLET: to applications => explorer => Internal memory => Download => rootexplorer.apk
This should bring up the apk installer and ask for permission to install rootexplorer. Follow the prompts until rootexplorer is installed.
Open root explorer. The first time you open it if everything is right you should get a prompt from SU to allow root access, hit grant. After that you might get a message that you need to close and reopen root explorer again, this is completely normal.
Step 6 Remount File Systems r/w
Once root explorer is open and has root access you should be in the root directory of the device.At the top you should see a message that says "Mounted as r/o" and a button to the right of it that says "mount as r/w".
Click to expand...
Click to collapse
Click the button to mount / as rw.
The message at the top should change to "mounted as r/w" and the button should change to "mount as r/o"
Click to expand...
Click to collapse
Scroll to the system folder and open it.
At the top you should see a message that says "Mounted as r/o" and a button to the right of it that says "mount as r/w".
Click to expand...
Click to collapse
Click the button to mount /system as rw.
The message at the top should change to "mounted as r/w" and the button should change to "mount as r/o"
Click to expand...
Click to collapse
Now click on the ../ Parent Folder icon on the top to go back to the root directory,
Step 7 Extract GAPPS
Scroll to and tap sdcard
Scroll to and tap Download
You should see the google apps file we copied earlier.
Click to expand...
Click to collapse
tap and hold on gapps-ics-20120429-signed.zip until the menu comes up and select "extract all" this will extract the zip file to /sdcard/extracted/gapps-ics-20120429-signed/
Step 8 Copy Google APPS to /system
Scroll to and TAP .. Parent folder at the top to go back a directory to /sdcard/
Scroll to and TAP extracted
Scroll to and TAP gapps-ics-20120429-signed
You should see 5 items, install-optional.sh, META-INF, optional, system and the ../ Parent Folder link.
Click to expand...
Click to collapse
*** WARNING *** Do not click on the install-optional.sh bad things might happen!
Click to expand...
Click to collapse
TAP and hold on the system folder until the menu comes up and select copy.
This will place a paste button on the bottom of the screen be careful not to hit it yet or you will have problems.
Click to expand...
Click to collapse
TAP ../ Parent Folder until the directory at the top says / (you should have to go back 2 or 3 folders)
You should now see a bunch of folders in the root directory as well as the tablets system folder. There should NOT be a ".. Parent folder" visible.
Click to expand...
Click to collapse
Now hit the paste button on the bottom left. You should get a warning massage saying "system already exist. Do you want to overwrite it?" hit yes
The file copy takes 1 to 2 minutes when it is done all that is left is to remount the / and /system folders r/o and reboot the tablet
Click to expand...
Click to collapse
Step 9 Remount file systems r/o
At the top you should see a message that says "Mounted as r/w" and a button to the right of it that says "mount as r/o".
Click to expand...
Click to collapse
Click the button to mount / as ro.
The message at the top should change to "mounted as r/o" and the button should change to "mount as r/w"
Click to expand...
Click to collapse
Scroll to and TAP system
At the top you should see a message that says "Mounted as r/w" and a button to the right of it that says "mount as r/o".
Click to expand...
Click to collapse
Click the button to mount /system as ro.
click the back icon on the bottom left until you have exited root explorer.
Press the power button on the top of the tablet and turn it off and back on.
If everything went right you should now have a fully functioning rooted tablet with Google Playstore...
Click to expand...
Click to collapse
WASN'T THAT FUN!!?!?!

Ive tried this several times. It hasn't worked yet. Maybe I am doing it wrong, not sure. Ill keep trying but I am losing hope.
I am trying with a Proscan PLT7035-PL

worked ... Many thanks to amjtech ...
Here's how to do it:
Install Android SDK, then install Android SDK Tools, Android SDK Platform-Tools, Google USB Driver (download from google)
Install PdaNet for Android on PC.
Attach Proscan pad, check Settings->Developer options->USB debugging to on
XP install adb driver - if unsuccessful, need modify registry
regedit under HKLM/SYSTEM Permissions -> Advance, check replace permission entries on all child
(http://www.tomshardware.com/forum/252428-45-installation-failed-access-denied)
Install USBDeview, run to see usb device attached, get device ID of PROSCAN pad (0x2207)
Add device ID to file adb_usb.ini in c:\docume~1\<user>\.android, also add google's id:
0x2207
0x18d1
(http://forum.xda-developers.com/showthread.php?t=1479311)
(http://androidforums.com/kindle-fir...k-how-get-adb-running-root-superoneclick.html)
Now device will show running
Install ICS Root Unlocker 1.0, run ... got rooted.
Download Root Explorer (2.21.1).apk, Google Play Store (3.8.16).apk, and gapps-ics-20120429-signed.zip from 4shared
http://www.4shared.com/folder/k86VyEKK/_online.html
follow the rest of the instruction (http://forum.xda-developers.com/showthread.php?t=1993013)
... reboot proscan ... voila !!!

Help me!! please!!
I pushed the reset button then right now it's stay at recovery mode ever and I don't what firmware name it's using.. Someone help me find the link to download firmware and teach me how to restore it!! thanks very, very much!!

Factory ROM
tnan0906 said:
I pushed the reset button then right now it's stay at recovery mode ever and I don't what firmware name it's using.. Someone help me find the link to download firmware and teach me how to restore it!! thanks very, very much!!
Click to expand...
Click to collapse
Unfortunately as stated above there is no factory rom available for these tablets yet... I am looking into using rkflash or rkflashtool to download my rom prerooted so I have a backup and also can post a rooted rom for everyone. Most likely later this week I should have some time to figure out the rkflashtool and get it dumped.
I will post it here once it is done.
I'm going to say this now. I have a very busy schedule so I cannot guarantee when I will get this accomplished.
Also if this works for you please hit the thanks button.

Stuck
Humphrey1989 said:
Ive tried this several times. It hasn't worked yet. Maybe I am doing it wrong, not sure. Ill keep trying but I am losing hope.
I am trying with a Proscan PLT7035-PL
Click to expand...
Click to collapse
How far are you getting? Were you able to get root?

Rom Backup
amjtech said:
Unfortunately as stated above there is no factory rom available for these tablets yet... I am looking into using rkflash or rkflashtool to download my rom prerooted so I have a backup and also can post a rooted rom for everyone. Most likely later this week I should have some time to figure out the rkflashtool and get it dumped.
I will post it here once it is done.
I'm going to say this now. I have a very busy schedule so I cannot guarantee when I will get this accomplished.
Also if this works for you please hit the thanks button.
Click to expand...
Click to collapse
Thanks thanks thanks!! Please upload your backup from you for me! I think it will work because same products!! please as soon as possible!! Thanks you, thanks you very very much!!!

Confused as heck !!
OK, I am confused as heck here. I have the SDK installed. I have the USB Drivers installed. The PC sees the phone just fine, I can browse the internal storage and the external sd card with no problem. Windows XP Device Manager shows Android Phone, and under that the Android Composite ADB Interface.
PDANet works with the phone, no problem. However, adb devices never shows the device, and the Root program cannot find it either. At this point, I'm stumped. Any ideas what I need to do? I have put the android_usb.ini file in c:\Documents and Settings\myusername\Android with the necessary hex codes for the device and for Google. I'm going nuts here!
I know ADB is installed properly, because I can plug my phone into the PC and run adb devices, and it's detected just fine. It's just this tablet it can't find.
FIX: Not as obvious as it might have been, but here is the solution to my problem. I used the Search function to find the adb_usb.inf file - umm... it's in .android, not android. Once I added those ids, everything was fine.

No Market?
Achieved root, copied over the system folder from the zip, but no market. Did I miss something?

What about Recovery?
Just wondering if there is a recovery option as yet? That would be so helpful!
---------- Post added at 08:13 AM ---------- Previous post was at 07:28 AM ----------
spycom773469 said:
Achieved root, copied over the system folder from the zip, but no market. Did I miss something?
Click to expand...
Click to collapse
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.

Good instructions! But failure... and then success
The instructions were great above! The pointer to the version of google play was bad, but I found this link http://forum.xda-developers.com/showthread.php?t=1934441 and after using Root explorer to do the appropriate permissions at / and /system, and on the renamed file, it works!
---------- Post added at 06:17 AM ---------- Previous post was at 06:06 AM ----------
Now that I got Google Play to work...
I am having an odd problem however - the installation of apps stalls at 0% for about 30 seconds, and then continues. And as the percentage is updated, I see app screens cycling. And little google play shopping bags start to stack up in my "task tray" area of the tablet.
Does anybody else have that problem? It's very annoying! It seems like the downloaded apps not only install but open, eating up precious memory.
Speaking of which, how is the flash memory used? (4 GB), and not having apps take up the 500 MB that's available?

jmasters said:
Speaking of which, how is the flash memory used? (4 GB), and not having apps take up the 500 MB that's available?
Click to expand...
Click to collapse
It is 4GB shared. I haven't tried looking at the partition table.
There is only 2GB usable, it's on the TF card, I moved the apps there.
Not sure how to access the SD card to put apps there.
netizenmt said:
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.
Click to expand...
Click to collapse
My GAPPS are working fine. I thought about killing that /system/system folder and manually placing the files via adb.
Try checking the permissions too, I think they need to be 644 or better.
I've put the Tablet away for now, I will tinker again later probably.
Sent from my DIRTY Jelly Bean EVO 3D

How to move apps internally to TF card?
spycom773469 said:
It is 4GB shared. I haven't tried looking at the partition table.
There is only 2GB usable, it's on the TF card, I moved the apps there.
Not sure how to access the SD card to put apps there.
How do you move your apps there? I'm aware of the app called something like app2SD, but the TF card isn't an SD card.
Click to expand...
Click to collapse

jmasters said:
spycom773469 said:
How do you move your apps there? I'm aware of the app called something like app2SD, but the TF card isn't an SD card.
Click to expand...
Click to collapse
If you go to the Apps tab under the system settings you will see a button that says "Move to TF Card"
Sent from my DIRTY Jelly Bean EVO 3D
Click to expand...
Click to collapse

netizenmt said:
Just wondering if there is a recovery option as yet? That would be so helpful!
---------- Post added at 08:13 AM ---------- Previous post was at 07:28 AM ----------
Yeah, this happened to me too. And for some reason, when you go to the \system folder and look in apps there is another apps folder in there. I think there is something really odd going on with root manager possibly. I don't know what the deal is, but none of the Google Apps are running.
I've tried several older 4.0.x versions of GAPPS, and I will be danged if I can get any of them to work. I'm rooted OK, but that's all that worked thus far.
Click to expand...
Click to collapse
You have to extract the zip file, remount the file systems as rw and copy the /system folder from the zip into the / of the device so that all the files goto their proper places... if you have /system/system it was not copied correctly...
as far as those not getting ADB to reconize the tablet.. a) make sure you have usb debugging turned on and b) you put the hardware id in the adb_usb.ini file.. See the ** important note ** in Step 2!

Unzipping Files
I have read and followed your directions to download the files, but, my unit keeps saying it can not open any zip files.
Do you have any idea why it may say this or how to get around this problem so I can continue as instructed?

unzip on your computer and transfer over, or use root explorer
bluetxsteel said:
I have read and followed your directions to download the files, but, my unit keeps saying it can not open any zip files.
Do you have any idea why it may say this or how to get around this problem so I can continue as instructed?
Click to expand...
Click to collapse
You can unzip them on your computer and then transfer them over, or use root explorer on your tablet. You'll have to hold your finger on the .zip file for a few seconds and then the unzip option pops up.

Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.

my bricked too
netizenmt said:
Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.
Click to expand...
Click to collapse
I hope you do so or some body find a way to unbrick this thing as for me i still have 26 days to return mine.i got to the part where I was about to paste the system I hit yes then everything locked up. I noticed before I hit yes it said do you want to merge and copy the files over not do you want to overwrite it but I still hit yes bad idea. can anybody tell me why I said merge and copy. well this is the second one I have bricks follow the steps perfect got all the way to the end and this is what happens so I took the first 1 back guess I'm going to take a second back also and try again until i figure out what I'm doing wrong.has anybody maked a rkimage or a .zip. update that will work to re cover this thing. I would be willing to try it out for you because I can.

netizenmt said:
Well, everyone be careful! When my Google Play would not install properly, I tried to clean the tablet up, ie, put it back to its original condition. Somehow, I managed to cause something to crash, and from then on, the tablet won't boot past the Android startup screen, although I can adb into it and it is still rooted, etc. What I've got now is a project tablet - HOW TO UNBRICK THE BRICK.
Click to expand...
Click to collapse
try doing an ADB shell
then the following commands
su
wipe data
this will reset the user partition. I had something similar happen on mine.. BTW 'wipe all' will definitly brick your tablet so be carefull
If you still cannot get it I was almost in a car accident yesterday and my tablet went flying and broke the screen... If you confident with a soldering iron I now have a plt-7035 mainboard prerooted and playstore installed for sale for $25 including shipping.. it would involve soldering 6 wire and the wifi antenna if your up to it pm me,, I know its good as I was able to ADB into it and run su and wipe data to reset it..
-Andrew

Possible root method?

I just came across this possible root method while searching for one on the Fire 8. It's dated for April 4 so it's recent. Though it's for 5.3.2.1, if it does work, maybe can be modified for 5.3.3.0?
https://www.quora.com/How-do-I-root-Kindle-Fire-HD-8-6th-Gen-2016
I'm on my tablet so can't copy and paste the steps. If someone else could?

DragonFire1024 said:
I just came across this possible root method while searching for one on the Fire 8. It's dated for April 4 so it's recent. Though it's for 5.3.2.1, if it does work, maybe can be modified for 5.3.3.0?
https://www.quora.com/How-do-I-root-Kindle-Fire-HD-8-6th-Gen-2016
I'm on my tablet so can't copy and paste the steps. If someone else could?
Click to expand...
Click to collapse
How interesting. I wonder if it will work on the earlier firmware versions too like 5.3.1.0 and 5.3.1.1. That way, don't have to mess with Kingoroot and anything that was put in there that will help the Chinese cyber-attack capability..lol. I'm on 5.1.1, but I'm too lazy to wipe it and try it..maybe later. Unless someone else wants to give it a go?
As far as I know, no root exists for 5.3.3.0. Alexa is a whore.

smokejumper76 said:
How interesting. I wonder if it will work on the earlier firmware versions too like 5.3.1.0 and 5.3.1.1. That way, don't have to mess with Kingoroot and anything that was put in there that will help the Chinese cyber-attack capability..lol. I'm on 5.1.1, but I'm too lazy to wipe it and try it..maybe later. Unless someone else wants to give it a go?
As far as I know, no root exists for 5.3.3.0. Alexa is a whore.
Click to expand...
Click to collapse
I may give it a go. I don't stand to lose anything really. I'm working on a project at the moment regarding Wireless Display (Miracast) though and I don't want to lose any of that so I have to make a back up. No root is supposed to exist for 5.3.2.1 either

DragonFire1024 said:
I may give it a go. I don't stand to lose anything really. I'm working on a project at the moment regarding Wireless Display (Miracast) though and I don't want to lose any of that so I have to make a back up. No root is supposed to exist for 5.3.2.1 either
Click to expand...
Click to collapse
Note there have been reports 5.3.3.0 can be rolled back to 5.3.2.1 on the 5th gen Fire. Not sure if this also applies to 6th gen HD 8. Typically a failed/invalid rollback results in a non-recoverable brick; not something to mess around with lightly.
---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------
DragonFire1024 said:
I just came across this possible root method while searching for one on the Fire 8. It's dated for April 4 so it's recent. Though it's for 5.3.2.1, if it does work, maybe can be modified for 5.3.3.0?
https://www.quora.com/How-do-I-root-Kindle-Fire-HD-8-6th-Gen-2016
I'm on my tablet so can't copy and paste the steps. If someone else could?
Click to expand...
Click to collapse
Don't get your hopes up. This is a generic tool that lacks favorable references (recent or otherwise) in trusted Android communities. Good luck.

Davey126 said:
Note there have been reports 5.3.3.0 can be rolled back to 5.3.2.1 on the 5th gen Fire. Not sure if this also applies to 6th gen HD 8. Typically a failed/invalid rollback results in a non-recoverable brick; not something to mess around with lightly.
---------- Post added at 08:40 PM ---------- Previous post was at 08:33 PM ----------
Don't get your hopes up. This is a generic tool that lacks favorable references (recent or otherwise) in trusted Android communities. Good luck.
Click to expand...
Click to collapse
I won't give up hope. I'm pretty convinced we'll eventually get root or the bootloader's unlocked. Something tells me Amazon's stock wasn't soaring because of these things or for that matter their so called FireOS. It's only a matter of time.
Just an observation when bricking my XT907 a few days ago (being flashed as we speak...drum roll) I noticed more than one recovery mode. Two for sure, maybe three. There is the generic black screen and white font...you can choose reboot, recovery, wipe partition and fastboot or what not. Well there's also an Android 'Droid Master Reset.' Would that reset to factory or to stock prior to Motorola customization? I've always done it through the first screen. I'm just wondering in case there might be something to exploit in those options. Does a real total Master Reset exist at all for these tablets? Prior to FireOS?

DragonFire1024 said:
I won't give up hope. I'm pretty convinced we'll eventually get root or the bootloader's unlocked. Something tells me Amazon's stock wasn't soaring because of these things or for that matter their so called FireOS. It's only a matter of time.
Click to expand...
Click to collapse
Much has happened over the past 12-15 months to bolster Android security some of which undoubtedly has made it to FireOS. Past techniques used to secure root will be far less effective moving forward.
DragonFire1024 said:
Just an observation when bricking my XT907 a few days ago (being flashed as we speak...drum roll) I noticed more than one recovery mode. Two for sure, maybe three. There is the generic black screen and white font...you can choose reboot, recovery, wipe partition and fastboot or what not. Well there's also an Android 'Droid Master Reset.' Would that reset to factory or to stock prior to Motorola customization? I've always done it through the first screen. I'm just wondering in case there might be something to exploit in those options. Does a real total Master Reset exist at all for these tablets? Prior to FireOS?
Click to expand...
Click to collapse
Never heard of or seen a low level "Master Reset" function in an Amazon device (dating back to 2nd gen Fire HD) or any Android device for that matter.

DragonFire1024 said:
I may give it a go. I don't stand to lose anything really. I'm working on a project at the moment regarding Wireless Display (Miracast) though and I don't want to lose any of that so I have to make a back up. No root is supposed to exist for 5.3.2.1 either
Click to expand...
Click to collapse
Wishing for your success! Really hoping to have new root for this. :fingers-crossed:

Where is the download for this? When I do a search for "SuperOneClick" I get a tool for Gingerbread or older.

ShapeShifter499 said:
Where is the download for this? When I do a search for "SuperOneClick" I get a tool for Gingerbread or older.
Click to expand...
Click to collapse
Here's their site http://www.superoneclickdownload.com/
I've seen the method before in other forums ranging from a few months to a few years. I don't recall which ones or if they worked.
If anyone does try, I recommend following the steps here: http://www.pcworld.com/article/244303/how_to_root_your_kindle_fire.html At least the source is a little bit more 'legit' for lack of better terms.

Is it available for all firmwares??
I've been waiting on 5.3.2.1 for a root strategy on Kingroot and Kingoroot, but after about one year, They can't root my device.
And what is the advantage of using this method? Is it better than Kingroot?

Someone tried this method? It works? Thanks in advance for your responses.

behrad said:
Is it available for all firmwares??
I've been waiting on 5.3.2.1 for a root strategy on Kingroot and Kingoroot, but after about one year, They can't root my device.
And what is the advantage of using this method? Is it better than Kingroot?
Click to expand...
Click to collapse
Didn't work for me but I may not have done it right.

The Steps Are As Follows:
"
Step 1: Turn on your Kindle Fire and tap the top bar, near the battery and Wi-Fi icons; press More... from the drop-down menu, then Device, and tap Allow Installation of Applications to On.
Step 2: Download the Android SDK from the Android Developer site. Get the version with an installer app (installer_r15-windows.exe).
Step 3: Download the Java Development Kit (version 7, at the time of this writing). Make sure to download the appropriate version of the Java Development Kit for your PC--I'm on a 32-bit Windows 7 PC, so I downloaded the Windows x86 version.
Step 4: Install the Java Development Kit. Make sure you do this before you install the Android SDK. All you need to do is to open the installer file you downloaded (mine was called jdk-7u1-windows-i586.exe) and click through the installer wizard.
Step 5: Install the Android SDK. Simply open installer_r15-windows.exe and follow the instructions. Once the Android SDK is finished installing, the SDK Manager app will automatically open with a list of software packages you can download. Go ahead and install all the prechecked packages, but make sure that the Google USB Driver package (listed under Extras) is checked. You'll need this file to let your PC communicate with the Kindle Fire. Wait for SDK Manager to download install and all the packages, and don't panic if it asks you for permission to kill a server or process. Just click OK until it's all done with the install process.
Step 6: Now that you have the SDK installed, you'll have to make two quick modifications to it before you can root the Kindle Fire. First, open up your User Account folder in Windows (C:\Users\(Your Account Name), find the new ".android" directory, and find a file called adb_usb.ini. Open it up in Notepad, add a new line at the bottom of the document, and type 0x1949. Make sure that string is on its own line in the document, save it, and close it. Next, go to wherever you installed the Android SDK itself (probably C:\Program Files\Android\android-sdk), and navigate to the \extra\google\usb_driver\ directory. Find the file called android_winusb.inf and open it in Notepad. There, you'll want to take the following lines and paste them immediately underneath the [Google.NTx86] and [GoogleNTamd64] headings in the document:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Save the file and exit Notepad. If Notepad doesn't let you overwrite android_winusb.inf when you're saving it, save the edited version to your desktop, and then drag the edited version over to the usb_driver directory to replace the old version with your edited version. Windows may ask you for Administrator permission to replace android_winusb.inf--don't worry, it's fine.
Step 7: Plug your Kindle into your PC. You'll need a micro-USB cable to do this, which the Fire doesn't ship with, so you'll have to buy that cable if you don't already have one that you use with your phone or camera. Windows will probably automatically attempt to install a driver for it, fail, and then mount it as a normal storage device. That's fine, though we may have to change something there later.
Step 8: Now that your PC and Kindle are connected, we're going to open up the Android SDK to make sure it recognizes the Kindle. Open up Command Prompt in Windows (Start Menu, All Programs, Accessories, Command Prompt) and navigate to wherever you installed the Android SDK.
Don't remember your DOS commands? That's okay--just open up the Command Prompt and type cd followed by the file path to the platform-tools directory (for example: cd C:\Program Files\Android\android-sdk\platform-tools\). Once you're there, type adb kill-server, press Enter, type adb devices, and then press Enter again. You should see the Command Prompt return with "List of devices attached" and a string of numbers followed by "device"--that means the Android SDK recognizes the Kindle is attached, and you're ready to proceed to the next step.
However, if you don't have any devices listed, it probably means that Windows isn't using your Android SDK USB driver to communicate with your Kindle Fire. Go to Control Panel in Windows, open Device Manager, and scroll down the list of devices until you find your Kindle listed. Right-click the listing and select Update, then click Browse my computer for driver software, Browse, and navigate to the directory that holds the file you edited earlier called android_winusb.inf--probably C:\Program Files\Android\android-sdk\extras\google\usb_driver. Click Next; Windows should now switch over to the Android SDK USB driver for your Kindle. Go back to the Command Prompt; type adb kill-server, press Enter, then type adb devices, and press Enter again. You should see something show up under the list of attached devices.
Step 9: Now you're ready to root your Kindle. All you have to do is download SuperOneClick (and Microsoft's NET 2.0 Framework, if you don't already have it installed), install both apps, open up SuperOneClick, and click Root.
Let SuperOneClick do its thing--the entire process takes a few minutes--and when it's done, go back to the Command Prompt, type adb kill-server, and press Enter. Then, just to be sure, click on the Safely Remove Hardware and Eject Media icon in the Windows Notification Area (usually a picture of a plug with a green checkmark on it), eject the Kindle, and unplug it. Congratulations--you have root access!
" - Qoura, Anya General
---------- Post added at 01:00 PM ---------- Previous post was at 12:54 PM ----------
DragonFire1024 said:
Just an observation when bricking my XT907 a few days ago (being flashed as we speak...drum roll) I noticed more than one recovery mode. Two for sure, maybe three. There is the generic black screen and white font...you can choose reboot, recovery, wipe partition and fastboot or what not. Well there's also an Android 'Droid Master Reset.' Would that reset to factory or to stock prior to Motorola customization? I've always done it through the first screen. I'm just wondering in case there might be something to exploit in those options. Does a real total Master Reset exist at all for these tablets? Prior to FireOS?
Click to expand...
Click to collapse
So you mean to find a way to factory reset the kindle to before it had fire OS, when it still had an unmodified android os(or whatever they came with first)?
If so, that sounds like a possible exploit, though I think Amazon has probably made sure that it was impossible without a brick.

So this giant post is simply and advert for SuperOneClick which is an old rooting method that hasn't worked for years.

Davey126 said:
So this giant post is simply and advert for SuperOneClick which is an old rooting method that hasn't worked for years.
Click to expand...
Click to collapse
Not to mention a lot of links I found in the near past, redirect to Kingroot who I suspect either bought OneClick or put them out of business.