Related
How to Root the MyTouch Slide
v1.0 Brandt DeLorenzo 7/19/2010
(I tried to add links, but I couldn't because I was still a newbie on the forum...oh well)
Required Hardware
Windows, Linux, or Mac Computer
USB Cable
T-Mobile MyTouch Slide with SD card
Required Computer Software
ADB Drivers for your computer
The Android SDK
Command Line editor
Required Files
Root.zip
MyTouch Slide Rom(s)
Optional Apps
Rom Manager (by ClockWorkMod)
Any backup app from the market (like MyBackUp Pro)
Step 1: Install Required Software on the Computer
I. In order for your device to communicate with the computer, you will need the proper ADB drivers. ADB Drivers should install automatically when you attach your MyTouch Slide to your computer when using a PC. If you need to manually install the drivers for a PC, locate and install the HTC Sync Update program on your computer.
II. On the device, go to Settings > Application > Development and turn on USB Debugging.
III. Download the Android SDK and unzip the directory in your C: drive somewhere where you can easily find it. I’d also suggest renaming the SDK folder from android-sdk-windows to something shorter, like “asdk”. You do not need to install anything inside that SDK folder after you unzip it. Just move it to the C: directory and rename the folder to something short and easy to type, like “asdk”.
IV. You need to add the Android SDK Tool folder to your system path if you’re using a Windows PC. Go to Control Panel > System > Advanced > Environment Variables > In System Variables, highlight "Path" and click Edit. Add C:\asdk\tools to the end of the string. Be sure there is a semi-colon between the last entry and C:\androidsdk\tools. For example, it might look like this:
C:\WINDOWS\system32\WindowsPowerShell\v1.0;C:\asdk\tools
Then click OK on all of the windows and you're done with this step
V. Be sure that you have a working command line editor for your computer. For example, Windows users can go to Start > Run > (type CMD) > OK.
Step 2: Download and Move Some Files
I. Download the Root.zip file from Eugene's thread about rooting the Slide, unzip the contents (update.zip, ota.zip, and loop) and place them all in the C:/asdk/tools folder. This zip file contains all of the files that will unlock your MyTouch Slide and install the Recovery software to make everything easier in the future.
II. Find the MyTouch Slide Rom that you want to install. You may download as many as you want if you plan on switching between different versions of Android. You can find many of those Roms here or on AndroidSPIN. Download them to your computer and then move them to your SD card. They should be anywhere from 50MB to 150MB each.
Step 3: Preparing for Root
I. Before we begin the process, we need to test ADB to make sure your device can be seen by the computer. Connect your MyTouch Slide (it should be on right now) to your computer via the USB cable. Open up your command line editor and get to the Android SDK tools folder. If you named your SDK folder ‘asdk’, then you would type CD C:/asdk/tools and hit enter. You should see the prompt change from C:/ to C:/asdk/tools>. Type loop and hit enter.
II. If ADB is working, you will see a continuous loop of commands running up the screen. Hold down Ctrl+C to temporarily stop the loop and look for something that says:
List of Devices Attached
HT05RPS02484 Online
If you see something like this, type Y and hit enter. (Your device number may be different than display above)
If ADB is not working, go here to troubleshoot ADB and make sure that you can get the loop to detect your device before you go any further.
III. Perform a backup of any applications or data that you would like to restore. I’d suggest backing up applications, contacts, or any data that may not sync back to your device. You can find an application in the Android Market to complete these tasks. I prefer MyBackUp Pro.
*Mac and Linux users may need to put a ./ in front of anything that is typed in the command line. Like ./loop instead of loop.
Step 4: Beginning the Root Process
I. Power off your device. Hold the Volume Down Key and Press the Power button at the same time. Hold both buttons until the screen comes up in Bootloader mode.
II. In your command line editor, be sure that you are in the C:/asdk/tools> prompt. Type loop and then hit enter. You should see:
List of Devices Attached
HT05RPS02484 Offline
III. Select Recovery from the menu. Use the volume buttons to move up and down. Use the Power button to select the option. You should now see a dark screen with a black device and a red triangle with an exclamation point inside. Hold the Volume Up button and press the Power button. You should now see the Android system recovery (2e) screen.
If you kept the loop running, it should change to say:
List of Devices Attached
HT05RPS02484 Recovery
If it doesn’t change, unplug the USB cable from the device and plug it back in.
If your device number and “Recovery” appears, you can now stop the loop with Ctrl+C. If you do not see your device number and “Recovery”, you need to power off your device and try again. This may take a few tries.
IV. On the device, scroll down to Update.zip and select it using the Power button. It will display an error message that it failed. This should be expected and is part of the process.
V. In the command line editor, you should still be in the C:/asdk/tools> prompt. Type adb push ota.zip /sdcard/update.zip and hit enter.
VI. This is the most difficult part of the process. Type adb push update.zip /sdcard into the command line editor, but do not click enter yet.
VII. On the device, scroll down to Apply sdcard:update.zip and as soon as you select it with the Power button, click enter in the command line editor on your computer. The process should be all done within a second. If you did this properly, a new window in green text should appear with the title “Clockword Mod Recovery v2.5.0.1” or another version number.
VIII. Now you are in Clockwork Mod Recovery. First, scroll down to the partitions menu and make sure it does not say ‘mount system’. If it does say ‘mount system’, highlight it and hit the Power button to mount it.
IX. Scroll down to apply sdcard:update.zip and click the Power button to select it.
X. Power down the device. Follow the steps to get back into ClockWorkMod Recovery, but you won’t need to complete step VII. Simply select Apply sdcard:update.zip and hit the Power button to get back into ClockWorkMod Recovery in the future. (If a blank screen appears when you hit the Power button, press the Trackpad as the enter button.)
XI. On the computer, you should run the loop command to determine if the device is connected again. If it is, type adb install superuser.apk and hit enter. You have full root access.
Step 5: Installing a Rom
I. If you have already performed a backup of your files, you can now wipe the device from the ClockWorkMod screen. Scroll down to wipe data/factory reset and hit the Power button. You will be prompted with another screen with a Yes – delete all user data prompt. Select Yes – delete all user data and hit the Power button.
II. After the wipe has completed, scroll to install zip from sdcard and hit the Power button. Then scroll to choose zip from sdcard and hit the Power button. Now locate the Rom you want to install. Press the Power button to select the Rom and install it.
Managing your Roms
To make your life easy, download and install the Rom Manager application by ClockWorkMod. From this application, you can backup & restore your Roms, reboot into recovery with one click, partition your drives, and find new supported Roms for your device.
we already have a root and a simple root if a noob cant get root with either one they dont need root this thread is unnecessary and ,imo, more confusing especially w/o links
i agree, we've already got this pretty much in 2 different threads, in 2 different ways, one fully automated and the other manual. and i created a video and a tut that has more detail as far as how to install roms and such.. this is an unneccessary thread
Sorry man :/
where is my blow torch...prepare to flame
There is also ....
There is also a questionable step.
I cant get into Clockwork mod using the start update from the phone then push update.zip.
But if I adb push first, wait for the server to start, then updat from the power button on the phone, it works.
good luck.
nice guide! thanks
HighRidas said:
we already have a root and a simple root if a noob cant get root with either one they dont need root this thread is unnecessary and ,imo, more confusing especially w/o links
Click to expand...
Click to collapse
No offense, but I've tried many of the guides and they were difficult to follow when ADB was acting dumb on my laptop. The actual steps are easy, troubleshooting ADB on a Windows PC is a pain for most. Now that I have root and I'm using different roms, it's all easy and painless.
If there wasn't a no-linking rule on new user threads, it would have been much better...I agree.
between the fact that it doesn't need to be any easier, and the ROM bibke holds most of this, there is no need for this thread, i understand that you were probably trying tobe helpful but you are an idiot and made a perfectly useless thread with no links for no reason
tubaking182 said:
between the fact that it doesn't need to be any easier, and the ROM bibke holds most of this, there is no need for this thread, i understand that you were probably trying tobe helpful but you are an idiot and made a perfectly useless thread with no links for no reason
Click to expand...
Click to collapse
calm down bro !!! since i came to the slide side all i see is u going hard on people .. that ****'s not cool at all !!! it makes me wonder about u !!!
everybody got their pitch forks and torches out !!! just closed the thread that simple !!!!
i am helpful when stuff i posted in the correct forum, and when it is a new thread that has not been posted in th past. when people continuously post new threads to state stuff that has already been said, especially since without links this thread is pointless, then we xda devs are going to get upset, devs do not like to see pointless threads in the dev section, and certainly don't like it when people try to belittle the work that went into root by "making it easy" first requirement for having root is to know how to use a computer, after that you can learn to do some really cool stuff
Well I thought this guide WAS Helpful to be honest! Not to mention lesstalk was just trying to help. Tubaking is always busting peoples chops everytime he says something it ends up being rude! If you dont have anything nice to say then go to a diff thread dude cause your sorry azz attitude just makes it so people dont want to post cause their scared of getting verbally bashed by folks like you! Being rude is NOT doing anyone any good and Im sure im not the only one who feels this way about you!
in my opinion they should be afraid to post, if they aren't then they make crap like this. i stated that he was trying to be helpful but without links this thread just takes up space and makes people ave to search harder to root thier phone. i am a nice person IRL, but i do not like wasted space. if someone has come up with a "easier" way to root then fine, but there is already a thread for preparing to root your slide, two threads on rooting your slide, and the slide rom bible which includes all of those threads, a stickie should be more than enough for most people and if not then they need to think before hitting that new thread button. there is no need for repetitive threads in the developement section. if there had been links in this thread(which i know he can't do as he is a new member) then it would have been fine and i would have shut up and left it alone, but right now there are two ways to root, one for computer people and one for script kiddies, either way if you can't get it to work with either method then you probably don't need root. if you can't read the simple walkthroughs then you don't need root, if you don't know what you are doing then you don't need root
EDIT: Here is the link to the thread that already covers all of this, and guess where i found it
http://forum.xda-developers.com/showthread.php?t=708522
I did find this thread helpful, especially since i'm new to android. I want to know what i'm doing and the only way i can learn what i'm doing is from reading many posts and lots of trial and error.
I have read both of the rooting guides from the rom bible, and there is still some stuff left out. I actually like this guide better than the others because there is more help in the whole ADB part of the root process.
Now, i know what i'm doing with computers, it still freaks me out how much i can do with computers. But in new areas where i want to learn, it helps to have more info than needed because people have different viewpoints on the same process.
@tubaking182 - for most of the threads you come in bashing in the dev section, i agree with you. But on this thread, i think you're way out of line. Yes there are 2 threads already and yes this thread needs links. But it's not a waste of space. I've lurked on xda since i bought and returned my HD2 (~late april). And when the slide was released, i headed to this subsection. And i've only seen it go down hill with more people posting threads that needn't be posted, but also with "wanna-be" mods flaming the person who didn't think and posted the needless thread.
But now that animosity has taken a turn for the worst and i only seen bashing in this section of the slide section of xda. And it's really making me want to leave xda.
The whole rooting process can be easy to learn if you've come from a previous android phone and have previously used ADB commands. But when you're really lost about even the whole linux folder structure (i'm not totally lost with this, but i'm more used to the desktop linux folder structure), then some of the guides out there to do certain tasks seem like another language.
3 guides for the rooting process can't hurt, especially when someone who doesn't know what's going on in the process wants to figure it out step by step and is too afraid of members like tubaking182 are always going on about searching for previous posts and flaming for simple questions (not that people shouldn't search for previous posts and threads).
EDIT: i do commend all the devs for their hard work making anything like rooting the phone remotely possible.
tething is, when you want to post an issue about something you saw in another thread, the issue should be posted there, it will be answered when people see it or when the OP has time to get on and answer. i am not trying to be a "wanna-be" MOD as i don't ned to be on XDA any more than i already am regulating posts and mergng threads when they should be merged, this thread holds ZERO new info and therefore should not be posted. if this member found a simple one-click root(which i hope to god never happens with this phone) and he wanted to tell us about it and tell us what he searched to find it and whatever else then great i ould not care, but some things do not need a new thread, if users all searched the Q&A section, the General section, and the Dev section BEFORE clicking the new thread link at the top then we would probably have half as many pages in the dev section, we have 8 pages now that i have gone through in the dev section and i have seen way too many repeat threads and questions. if you wanna see who i am take a look through my posts, i am a very helpful person when people want HELP, but when people want ANSWERS and they want stuff easier and they post in the wrong section then i get irritated and my messages are less helpful.
the number one reason n00bs post in here is because more people will see it, unfortunately this means the devs have to deal with the BS threads that push their stuff to page 3-4 and most people don't read past page two to look for a thread
yes, but you have to remember this is a very publicized and a public forum. In another forum i belong to, this happens all the time even though we have clearly marked stickies in every section.
I bet you most of the pointless threads have the OP posting only once and never even commenting on the posts made after they got the answer. That is what happens when you have a forum that's known for phone customization (or any public forum for that matter).
EDIT: and i'm not saying you're mean, i'm just saying it's going a little too far.
EDIT 2: if someone makes a thread only looking for answers that have been previously posted, just don't respond to it as that person won't ever be back. it's as simple as that.
@lesstalk - Thanks for the guide, outside of the lack of links(out of your control) this is a wonderful guide that I have started pointing new MTS users to.
@tubaking182 - Fact is, the guide on this actual covers steps that were skipped over in the other root guides because they were assumed to be common knowledge. Its that assumption which will kill future android users desire to learn about the device, especially when its accompanied by such a poor attitude from the "regulars" of the forum.
Outside of the links being missing due to being a new user account on the forum, the guide was more complete and comprehensive than any of the other guides so far. It managed to cover step(s) that are easily overlooked by someone who has rooted other android phones before, but CRITICAL to function and not mentioned in the other guides. I cant count the number of people I pointed to the pre-existing threads on rooting for MTS, who completely missed the superuser.apk setup because there were not any steps written for it.
A well educated userbase is a happy and quieter userbase, and while there are alot of useless threads in this section, this one actually served a purpose.
^^^
Here here!!
This is the first guide that has explained it all, and now I feel like I can do it too. I've done my g1, and tons of wm phones, but this one is completely different. All depends on your background.
You should be trying to expand and diversify the user base, not alienate it. or would you rather lock up the keys and argue with your self all day?
Sent from my T-Mobile myTouch 3G Slide using XDA App
I agree that this guide might Hold your Hand & even ( Might have missed steps ).
It's not my Job, nor any others person job to make sure you have your driver's setup & adb working correctly. There is plenty of other threads that already cover this, easy to find by using Google..
regardless, Thank you to the OP for try to help make things a bit clearer
~Eugene
tubaking182 said:
i am helpful when stuff i posted in the correct forum, and when it is a new thread that has not been posted in th past. when people continuously post new threads to state stuff that has already been said, especially since without links this thread is pointless, then we xda devs are going to get upset, devs do not like to see pointless threads in the dev section, and certainly don't like it when people try to belittle the work that went into root by "making it easy" first requirement for having root is to know how to use a computer, after that you can learn to do some really cool stuff
Click to expand...
Click to collapse
i feel u on that u do have a point !!! some people just that "dumb" and can't help it. they should post in the right thread but at the same time just putting them down isn't always the best way !!
dcowboys2184 said:
i feel u on that u do have a point !!! some people just that "dumb" and can't help it. they should post in the right thread but at the same time just putting them down isn't always the best way !!
Click to expand...
Click to collapse
Ditto. This is a redundant and unnecessary post. There are more than four different guides and several other posts on preparation. Yes, they aren't written for a kindergartner, but rooting your phone isn't supposed to be easy. Do some research, read a post or several, and only post after your eyes start to bleed. Cluttering the forum makes it even harder for new members to the community.
TO GET TO THE POINT, AND TO AVOID MY *****ING, SCROLL DOWN
OK, imma recent migrating bird from the sinking WinMo ship.
Just got this phone from LG, nice phone, but the flashing guides here aren't so easy to understand
I'll quote a 6 line instruction from the Prime/Megatron ROM thread which is
http://forum.xda-developers.com/showthread.php?t=870640
How to flash:
First, reboot into recovery via 3-button-combo, ADB, terminal, w/e.
Partition SDcard (swap: 0, ext: 512), ext2-ext3, then ext3-ext4 it.
Wipe data (data,cache,dalvik-cache,ext).
Connect the device to PC, copy Megatron over to the SDcard, disconnect.
Flash it via "flash zip from sdcard"
Reboot
Read important notes below
That's it.
Click to expand...
Click to collapse
SERIOUS? THATS IT???????????
I have no idea what all that means, and so are millions of sad puppies who migrates from WinMo's or dreaded Dumb Phones like the ones they sell in 7-11
SO, the point is (you can stop scrolling now)
PLEASE PLEASE PLLLEEEEAAASE make a easy guide for flashing, possibily a video. Or you could make it easy enough for me to understand, and ill make the guide.
BTW, in the long term, it WILL educate FURTHER n00bs.
Thanks in advance. Sorry for the *****ing. Love u guys
OK, OK, OK, you have got me!! I will prepare some "dictionary" for all noobs. Maybe it will sounds crazy, but when I logged-in I had no idea what android is. OO is my first android phone. I have got everythink from whole this forum, but I was there since thread about P500 started so it wasn't too hard catch and read every post here. So, all informations are there, but sometimes is not possible find them.
So i just have to read everything? Optimus One Android Dev or General?
Great! Thanks a lot
But gonna go to sleep.. I'm sorry lol this is my last week of winter break and its midnight. Bye!
dongimin2 said:
So i just have to read everything? Optimus One Android Dev or General?
Click to expand...
Click to collapse
About 95% of posts it will be useless because there are also some question, helps, and another stuff. There is too much words and useless trash. You also need know basics of unix-like systems to understand what are guys (and you) trying to do in adb shell, what is root and for what it is, what # mean in command line, and so on.
custom ROM is mainly for experienced user. At least, experienced in unix-like system, because android is based on it. Tools like busybox bringing next tools known from unix and some programs needs it for running. And another and another words and name what is normal for advanced user, not for n00bs here.
Because that all stuff it takes some time that I will have some usable noob dictionary.
This is a good and pretty much complete guide.
forum.androidcentral.com/lg-optimus-s-roms-hacks/48543-idiots-guide-rooting-custom-roms-optimus-s-edition.html
Rooting is the same, you just have to change some commands for the custom recovery but once you get there you'll know. And I recommend rooting via Adb, its easier for later.
btw, don't know if its a problem posting the link, if it is, sorry.
One thread is enough!
Do not do this again or you will have an infraction for spam.
Cheers
MOD EDIT : As requested by OP, I'm closing this thread.
Everyone can continue the rooting related discussions on the other thread linked here. Full root for Nook Tablet. [11/20/11] [Yes this is a permanent root!].
All,
Here is a "one click" script to root your Nook Tablet AND install gapps (Market) all in one shot. It also includes the latest superuser binary and apk (automatically installed). MAD PROPS to Indirect for being the first to get root on the NT. This script builds off of his (and others) work to make it a bit easier.
I need people to test this. That being said, RUN THIS AT YOUR OWN RISK. It may work perfectly, or it may explode your Nook. You've been warned!
1. Download and extract the zip file located at https://rapidshare.com/files/3156164791/NT-One-Click-Root-by-anlog.zip (PLEASE MIRROR THE FILE FOR ME SO YOU DON'T KILL MY DROPBOX ACCOUNT).
2. Factory reset your Nook Tablet (just do it).
3. Run Windows 7 (32-bit or 64-bit). Sorry Mac and Linux, but that's not my arena.
4. Enable USB debugging and sideloading on your Nook (download an APK and try to install it with package manager. Hit settings and set the options). YOU MUST uncheck "auto mount USB" or debugging won't activate. There are also two checkboxes for debugging and staying awake - make sure both are set. DO NOT REBOOT your Nook once you enable these settings.
5. Plug in your Nook and point Windows to search for the drivers in the usb_drivers directory from the etracted file. The driver has been modified to work with the Nook Tablet and you don't need to mess with any adb.ini stuff. It's ready to go.
6. Once the driver loads, make sure you have a device called "ADB Composite Device" (or something similar) in Device Manager. As long as you don't have an item called "Nook Tablet" with an exclamation point, you're good. Once you are plugged in, check the status bar on your Nook and make sure USB debugging is enabled (there will be a little robot indicator).
7. This step is optional, since it is run at the beginning of the script, but you can open a command prompt AS ADMINISTRATOR and go to the folder where you extracted your files and run "adb devices". It should list your Nook serial number. If it doesn't, start over.
8. Run a command prompt as Administrator and then run the NookTabRoot.bat file to root your tablet and install gapps. Your tablet will automatically restart once the script finishes.
This script is ALPHA and probably won't work, but that's why I need people to test. If anyone finds a way to make it better, please feel free to modify it (as long as you credit me and Indirect).
Good luck!
MIRROR 1 - http://dl.dropbox.com/u/7364988/NT-One-Click-Root-by-anlog.zip
Thanks a lot, this is going to be quite helpful.
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Indirect said:
anlog, can you please remove the rooting script from yours as it will make it harder for me to provide support if they are in your thread as well. Im happy the gapps is there but I really don't want aanyone to be missed when they need help.
Note: Seriously not trying to be a **** but this is the early stages of rooting and I would HATE for someones system to be completely screwed and I don't know they need help.
P.S.: Just link to the original root thread saying you must have rooted before you proceed with this script.
After that, I'll happily help you work on this script and offer support for this as well.
Click to expand...
Click to collapse
Your root method is not easy enough for the average user, which is why I've posted this.
I'm not removing anything. It's up to the community to decide if they want to try my script or not. I will host it and setup my own mirrors if I have to.
conundrum768 said:
Thanks a lot, this is going to be quite helpful.
[Mirror removed in light of Indirect's post below]
Click to expand...
Click to collapse
Sorry to see you cave in so easily...
I'm not being disrespectful but my script really isn't too complicated. I was working on rewriting the thread anyway I just haven't gotten the time yet until now. I've been out all day.
This early in the process, it is great having multiple ways to achieve root.
Can't you each add a disclaimer in your package "If you use this method to root, don't use any other method without doing a full factory reset first" or whatever words would be appropriate?
Mostly - don't get ticked at each other.
It's not a multiple way, it's verbatim my script with his added to it.
This is not a glory or recognition thing. This is something that I think will greatly help the community of average users with little to no experience with things like ADB or Unix commands.
Many every day users are discovering XDA and it can be very difficult for them to navigate through the forums and find what they are looking for. My goal is to make it really easy.
The script will not blow up your Nook. The worst thing that can happen is that it just doesn't work.
Not sure what else to say, but this "only one user is allowed to help people root" nonsense doesn't work for me, nor the rest of the community. Sorry Indirect. If it helps, I've credited you at the beginning of my script.
OK - then I would say don't include an early version of a root script except by reference... Let the original author handle the bugs and enhancements.
I dont see a problem with useing each others method as long as the appropriate credit is given when you use someone else's work in your own.
Indirect said:
It's not a multiple way, it's verbatim my script with his added to it.
Click to expand...
Click to collapse
You mean your script with a bunch of STANDARD adb commands in it? Not exactly rocket science. Did you write zergrush? No, but you used it (and credited them accordingly).
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Indirect said:
"Your script" <-- I atleast want people to ask permission before blindly taking my work in the first place. I didn't say this is released under public domain for anyone to use, I would like you to ask before. Use it, whatever but seriously, It kind of upsets me that you didn't bother checking with me if it was alright to atleast use my script. If anyone wants support, come to this thread if you use it. I am not able to help you as I did not develop the addition to this.
Click to expand...
Click to collapse
YOUR SCRIPT IS A BUNCH OF STANDARD ADB COMMANDS. That means that 100% of all other ADB scripts out there use elements from the script you pieced together from other scripts.
Get over it. You obivously only care about recognition. My only goal is to help other people.
anlog, you have clearly not seen any of my other work. I'm not in it for recognition, I need to know if something goes wrong at all and if so, what caused it. That's it.
Indirect said:
I'm not in it for recognition
Click to expand...
Click to collapse
Then stop telling people to remove their work and instead write a better/faster/easier version.
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
okay, so not to get in the middle of anything, I will say I've successfully rooted my nook tablet with the original method. didn't have any luck installing the android market (and getting it running).
as such, I've done a factory restore and have downloaded the script here.
as someone who is fairly computer literate, but is VERY new to rooting (short of 1 click root), I will take the shortest path possible. no loss of credit to indirect. please guys, all your work is recognized.
will report back shortly.
Indirect said:
Enjoy this script anlog, I appreciate your help finding the driver fix and be sure to reference me in your thread as well for proper credits. Enjoy your evening, I'm no longer debating about this as it's stupid. I think we can both agree on that.
And before you think I'm just being a ****, I wrote a script for the evo shift that was ridiculously advanced for the job JUST to make it so people can't screw it up.
http://forum.xda-developers.com/showthread.php?t=1277793 <-- read about it there.
Click to expand...
Click to collapse
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
anlog said:
Dude we need people like you to build off other's work. We both agree that if there is a super easy way to root and get Market, more people will buy the NT. From the second I started this thread you were credited in the first line of my script. I will also credit you in the beginning of this thread. I am NOT about stealing other people's work. Your work here is GREATLY appreciated!
Click to expand...
Click to collapse
Sorry for getting annoyed and worked up but I already had to play "Dueling Batch Scripts" in the evo shift section when mine was CLEARLY superior to the other ones by far because I was still developing it. :| So again, my apologies for losing my head but don't wait too long for my REAL script to be thrown together sometime tonight and blow yours out of the water.
Hello everybody.
This is my first post, and while I am noob at XDA-Developers, I have spent more than 10 years writing and reading in forums, and I know what has to be done before writing on them. And I did. I have a couple of questions that I think they are not easy to answer. Indeed, I spent 8 hours yesterday searching through the interwebs and this forum to try to figure out the most thorough answer. And I think I figured out mine, but I don't know any people that can reinforce my toughts and tell me "Hey Gabriel: you are right, you did well, you are the man: go out for a beer, keep calm and carry on". I will ask the questions first, and later I will explain why I ask such questions, and finally what are the steps I did.
The questions are: How can I remove root from a custom rom, and how can I be sure that I properly did? I know that many of us think that "This is stupid / Why do you want to do such a thing / the power of your phone will... / go to stock / etc". But, any way, I have a deep concern on expanding concepts and knowledge, and I thing that root process, root means and rooted phone securing checklist are not as clear as I would like to find them. And more important: I *have* to remain in a custom rom but I *must not* be root.
So the why's are not the question but, just to add some reasonable context: I have a phone that does not fit my needs with the stock rom, because a hardware component is falling apart and I need a software workaround (YEAH, right LOL: a Nexus One with the power button falling apart and I need to be able to unlock / wake with the trackball; but this thread is Android-wide because it tries to find a deep insight into rooting itself). This software workaround does not work in stock rom when I configure the password / PIN / pattern. And the problem with custom roms is that they run into trouble with certain data-protection aware environments, which do not allow rooted terminals. And more important than all: I have no need at all to be root, at least by now.
So, I spent hours searching, and I figured out that I should remove "su" command and related APK's (ROM Manager, Superuser, ... and some others that I won't need). All by myself and with some posts (I don't remember if they were here or in "HTCMania", a good spanish smartphones board, either) that suggested it.
The exact process I did was to download CyanogenMod 7.2 RC1, check signature & md5 to make sure the zip was what it claimed to be (because later I found that I needed to shut down recovery signature check) open the .zip, remove "/system/xbin/su", install the rom, remove su-related ".apk" with adb, and try to check if it still had any sort of superuser permission scalation. It aparently does not have. I checked /data directory with Root Explorer, I downloaded and ran Root Checker Basic.
The results seem what I expected (and that's the question: they seem, and I don't know if they are): I am running on CyanogenMod, the workaround (wake on trackball) works, the PIN/password works fine with it, and it seems I am not able to gain root access.
But my question are deeper than that: is there any remaining technical mean that could be used to gain root access on my phone? Do I have to get rid of more su-companion tools to be sure and to be "non-root"-compliant? Is there any checklist we should follow to check both if our custom ROM is rooted-but-secure and if our ROM is properly un-rooted? And most important: did I miss / failed to find the correct resource in these forums?
Thanks to every body and congrats for this outrageous boards.
I can not find any sort of comprehensive guide on how one is supposed to do this. I know that there is a new temporary root to allow this, but the release page does not explain how to root the phone explicitly, just the command lines for the final step.
I know about the superuser and the various drivers and commands you need to do this (i.e. Google ADB), I have done plenty of research already, I'm not just coming from out of nowhere asking for aid.
Is there a step-by-step guide for how to root?