first I would like to say all i did is to re-write instructions with help from booker-t for the nexus files and others narrowed down the steps
also cant forget the people who made this possible
Paul O'Brien:
Koushik K. Dutta:
unrevoked.com OTA Spoofing Method
ChiefzReloaded Brain Storming Guru
Prerequisites
- First from what I found is only able to work with frf72 (atleast in my tests may work on others but definatly did not on erd) so if need be first go and get on that version which I will not cover here plenty of steps
- newest sdk from developer.android.com
- class 6 sdcard (what worked for me)
- micro usb cable
1) download the N1_Root.zip attached from below (thanks booker-t for the work on that) and extract all of the files to the sdk/tools folder
2) now we need to make sure all is detecting drivers right go to applications >> development >> usb debugging
this establishes that we have the adb driver necessary in the pc already
also
3) here is a trick you need to see or find a way of inserting the media card while the battery is still in the phone and make sure you can (i trimmed down the little lip on the battery and allowed me to tightly squeeze the card in)
4) remove battery and sd card and plug phone back in
5) open command prompt to tools folder and type loop
6) connect device and power on in bootloader via vol - and power
7) then go to recovery only on triangle screen leave it there - keeping an eye on phone screen when on triangle screen in a few seconds computer will beep and will see in the running loop that is in recovery mode adb
use ctrl + c on pc to stop that loop
(you may need to reboot the phone a few times with the process to have it seen)
8) now with still just on regular triangle screen slip in the media card
9) on device use power and vol + to see options and click apply update (this will fail since not on media card which is good)
10) in the command line run the following commands:
adb push busybox /sdcard
adb push flash_image /sdcard
adb push ota.zip /sdcard/update.zip
11) in command line type but do not run yet this command:
adb push update /sdcard
12) on device click to apply update and as soon as you do and start seeing the line on screen run the above command. May need a few times to take You will know when it does and screen will clear itself
13) once that completes you can try the following command
adb push flash_image /system/bin
(you may get permission denied errors if you do get the root explorer app from market to copy sadly su file manager did't work for it)
- if it didn't work we need that there so you can reboot and copy if command not working
14) when get got that part your phone is rooted then with flash_image where it needs to be
grab your favorite recovery either amons or clockwork and use a terminal editor to apply and make a nandroid backup
15) apply your new rom and have fun
permission denied on frf83 bummer... this method was working on frf72
elite67 said:
permission denied on frf83 bummer... this method was working on frf72
Click to expand...
Click to collapse
permission denied for pushing the files? i get that on frf72 as well.
still unable to mount the card lol. will reformat card and try again
When do you get the error "permission denied" with using the flash_image command? That is what I ran into and root explorer app let me copy the flash_image file from the sdcard to /system/bin/
hit and miss, my card reads pny class 6, 8gb however not all the time just keep rebooting and trying, one thing I did was remove all my android drivers and let windows reinstall them again, seems like it made it read all the time, I was able to push files in frf72
help .. im done with part 13 .. but i dont understand part 14.!!
help plz!! im sooo close!
I am getting permission denied on FRF83 also.
BUT
why isn't flash_image inside the update.zip with su and superuser.apk?
That way we wouldn't have to push it!
That would be the only possibility for us stuck on FRF83?
(Unless there is a way to revert back to FRF72 from FRF83, but I don't think there is.)
Ok, getting ADB to recognize my device in recovery mode but getting "permission denied"
Using an 8gb Nokia (assuming class 2) card on FRF83.
A good question would be, can you do this on a 2.1 device? Or does it require 2.2
torchedlh said:
Ok, getting ADB to recognize my device in recovery mode but getting "permission denied"
Using an 8gb Nokia (assuming class 2) card on FRF83.
Click to expand...
Click to collapse
select apply update.zip one time before pushing
Can anyone CONFIRM being able to do this on FRF83? Dang, I guess I missed my chance while I was still on FRF72...
Nevermind -- looks like this has been addressed on another thread:
http://forum.xda-developers.com/showthread.php?t=710351
M9x3mos said:
3) here is a trick you need to see or find a way of inserting the media card while the battery is still in the phone and make sure you can (i trimmed down the little lip on the battery and allowed me to tightly squeeze the card in)
Click to expand...
Click to collapse
It might be easier to get a few wires and carefully connect the battery to the pins so that the battery is out but powering the device.
I was thinking of the same thing and would have been easy enough on the phone to use stripped ethernet wire wrapped arround but holding the leads on battery itself would be a little harder. Zipping the little lip off of battery and gently forcing the memory card in was easier for the 3 times I needed to do it to get the process right.
M9x3mos said:
I was thinking of the same thing and would have been easy enough on the phone to use stripped ethernet wire wrapped arround but holding the leads on battery itself would be a little harder. Zipping the little lip off of battery and gently forcing the memory card in was easier for the 3 times I needed to do it to get the process right.
Click to expand...
Click to collapse
This. I found that simply blocking the ports on the SDcard doesnt work. It has to click in to mount
shaving that little part off is very simple and the sd goes straight in. after 5-6 hours of trying over 3 days....this worked immediately
Using a small strip of paper to block the microSD card's contacts works very well. just slide it in the slot, slide the card in there, click it in, and you're good to go.Just make sure the peice of paper isn't too wide and that it goes all the way in.
PS - i have been trying to flash update.zip before running the ADB push commands.
torchedlh said:
Using a small strip of paper to block the microSD card's contacts works very well. just slide it in the slot, slide the card in there, click it in, and you're good to go.Just make sure the peice of paper isn't too wide and that it goes all the way in.
PS - i have been trying to flash update.zip before running the ADB push commands.
Click to expand...
Click to collapse
.....it doesnt work lol.....
youll get mount errors in recovery if you simply remove the paper. youll get adb. actually inserting the card will eliminate the error
Related
HOW-TO Root the Slide
(MAC OSX FLAVORED) KAPOWWW!!!!
&
Android SDK on Mac
STEP 1.
Download Android SDK from here.
STEP 2.
Unzip it. Place the folder it creates in your Documents folder and rename it AndroidSDK or SDK. (Something Easy)
SUCCESS!!! Android SDK Installed… //WTF!!??!!
STEP 3.
Download This Package > Slide Root.zip
Place the Contents of "Slide Root.zip" into your Android SDK Tools folder.
(These five files need to be placed DIRECTLY into the AndroidSDK/tools/ folder)
STEP 4.
RENAME Loop.bat to Loop.sh, then right click, open with TEXTEDIT.
Delete it’s contents and replace it with
#!/bin/bash
while [ 1 ]
do
adb devices
done
Save and Close the File.
STEP 5.
On your Slide, GO TO Settings > Application > Development and turn on USB Debugging.
This should save you headaches.
NOW… Power Off the Slide
STEP 6.
OPEN Terminal
(APPLE + SPACE and type Terminal, press enter.)
Now, CD to the SDK/Tools Directory.
It should be where we left it.
/Users/YOURUSERNAME/Documents/AndroidSDK/tools/
Terminal SHOULD open with it already in your USERNAME
Type cd Documents/AndroidSDK/tools/
STEP 7.
Power On the Slide into the Bootloader by Holding Down ( Volume Down + Power Button )
STEP 8.
NOW run your loop file (the one we made earlier)
The Terminal should be all queued up to the Tools folder.
Type in ./loop.sh
(The Terminal should be blowing up with List of Devices Attached over and over)
STEP 9.
Once your loop is running, select Recovery from the bootloader menu.
(Volume UP & DOWN to change selection and POWER to Select)
STEP 10.
When recovery loads, you should Have an Offline Device.
The Slide’s screen will have a picture of a Phone and RED triangle around a !
(Don’t freak out, this is a good thing.)
Hit Ctrl + C to stop your script & see.
If this doesn't happen, Power Off and try again from STEP 7.
STEP 11.
Un-plug your USB cable from your Slide & Plug it back in for it to Detect ADB Correctly!!!
IMPORTANTE!!!
At this point you can adb devices to see if it detects your device and that it is in recovery mode.
Type into Terminal ./adb devices
If it says recovery you are golden and move onto STEP 12 to kick the habit.
If not, rinse and repeat from STEP 7.
STEP 12.
Select Update.zip from the menu. (This will fail, but we already know that! Select it anyway).
STEP 13.
Type into Terminal
./adb push ota.zip /sdcard/update.zip
STEP 14.
Type into Terminal
./adb push slideroot.zip /sdcard
STEP 15.
MUY IMPORTANTE!!!
Have this Command ready in your Terminal before applying update.zip again!!
./adb push update.zip /sdcard
STEP 16.
On your Slide, Hit run update.zip
As soon as you see A Little Bar appear behind the text
Push ENTER to execute the Terminal command
(./adb push update.zip /sdcard )
STEP 17.
If successful, you should see Clockwork Recovery.
If unsuccessful, repeat steps 13-16.
STEP 18.
In Clockworkmod Recovery,
Go to the Partitions menu and Mount System
(It should be at the top and the only one not mounted.)
STEP 19.
Go one level back & select install any zip from sdcard.
Select slideroot.zip & apply update from zip
(This will finish the Root process).
STEP 20.
Reboot your phone & wait for it to load completely.
To confirm that your slide is connected as a device use the command ./adb devices
If this works, you will see it as a device. Your prompt will say something like:
$ ./adb devices
List of devices attached
HT05YUP12710 device
STEP 21.
./adb install Superuser.apk
(If it says it cannot locate directories, make sure you can find your device
using ./adb devices… If things still don't work, my best advice is to start over)
STEP 22.
After Superuser is installed try to use adb to shell to your device.
Type in Terminal
./adb shell
you will get a $
Then type su
On the Slide, Superuser should pop-up asking if you give permission, do so.
In Terminal, your $ should turn into a #. If so, you have root. WOOT!!!
Original SHOUT OUTS!!!
Special Thanks to:
Paul O'Brien:
Koushik K. Dutta:
&
The Guys using the Incredible OTA Spoofing Method
&
ChiefzReloaded for Huge amount of Suggestion & Brain Storming.
But most of all, you should thank eugene373 for rooting the slide and not sleeping for two days.
His original post is here.
sk8rbebop said:
STEP 14.
Type into Terminal
./adb push slideroot.zip
Click to expand...
Click to collapse
should it not be:
./adb push slideroot.zip /sdcard
Also...
sk8rbebop said:
STEP 15.
VERY IMPORTANTE!!!
Click to expand...
Click to collapse
Should be:
MUY IMPORTANTE!!!
I don't understand the need for a separate post when the only difference between osx and windows is that osx uses a shell script and windows a batch file and osx is discussed in the post about rooting.
nerdcorerising said:
I don't understand the need for a separate post when the only difference between osx and windows is that osx uses a shell script and windows a batch file and osx is discussed in the post about rooting.
Click to expand...
Click to collapse
Five different people asked for it so they got it.
Thanks!
Thanks a bunch for the tutorial! We really do appreciate it. I just had a couple questions about 2 of the steps.
STEP 6.
OPEN Terminal
(APPLE + SPACE and type Terminal, press enter.)
Now, CD to the SDK/Tools Directory.
It should be where we left it.
/Users/YOURUSERNAME/Documents/AndroidSDK/tools/
Terminal SHOULD open with it already in your USERNAME
Type cd Documents/AndroidSDK/tools/
I got lost where it says "Now, CD to the SDK/Tools Directory." I do not really know what the CD means and what I should be typing into Terminal?
Also should my phone already be plugged in to my Mac?
Please let me know and thanks!
Thanks a bunch for this tutorial. I am about to try to ROOT, it should go over smoothly. Now from the ROOT what else have you guys been doing to you're Slide? I know Cyanogen has not said much, that is who I used for my myTouch 3G and my G1.
Click to expand...
Click to collapse
I flashed the Eng Build, then SlideMEROOT2 and then the new radio (you need this). Just follow the how-to's already posted, but remember to type ./ before the commands in Terminal.
Ex. ./adb devices Instead of adb devices.
There were a couple people who were trying to keep their original stock rom, but slidemeroot2 is basically the original rom. Plus, someone posted the original stock backup, so flash away.
-------------------------------------
Sent via the XDA Tapatalk App
this is wrong
#!/bin/bash
while [ 1 ]
do
adb devices
done
it should be
#!/bin/bash
while [ 1 ]
do
./adb devices
done
shadowleo85 said:
this is wrong
#!/bin/bash
while [ 1 ]
do
adb devices
done
it should be
#!/bin/bash
while [ 1 ]
do
./adb devices
done
Click to expand...
Click to collapse
It's no more "wrong" than your code...
The first assumes that you've configured your shell to link the "adb" command to the adb "app" in the sdk/tools directory. Your code assumes that you will be activating the script while "within" that very directory.
The code, IMHO, should read:
Code:
...
[PATH TO SDK/TOOLS/]adb devices
...
And the OS X user should be instructed to insert their own path.
HebrewToYou said:
It's no more "wrong" than your code...
The first assumes that you've configured your shell to link the "adb" command to the adb "app" in the sdk/tools directory. Your code assumes that you will be activating the script while "within" that very directory.
The code, IMHO, should read:
Code:
...
[PATH TO SDK/TOOLS/]adb devices
...
And the OS X user should be instructed to insert their own path.
Click to expand...
Click to collapse
WRONG the code running in the shell is to continuously run adb devices... which to do so correctly would have to be implemented with ./ in front to run correctly on a mac... dont try to correct what is right i will school u
and seeing as he clearly instructs u to place those apps within the tools folder and "cd" to it... means that the user should have those commands ready at hand which is included in the folder...
shadowleo85 said:
this is wrong
#!/bin/bash
while [ 1 ]
do
adb devices
done
it should be
#!/bin/bash
while [ 1 ]
do
./adb devices
done
Click to expand...
Click to collapse
Ur right.. that is the right way..
also for those of u having problems with the loop step where it never sticks... try a different memory card... i was having problems with the stock card... so i tried a different card and it worked perfectly... with no problems
shadowleo85 said:
and seeing as he clearly instructs u to place those apps within the tools folder and "cd" to it... means that the user should have those commands ready at hand which is included in the folder...
Click to expand...
Click to collapse
LOL. Okay, tough guy.
The fact is that the active directory in your terminal is irrelevant to the actual rooting process. If you want to argue about it, have at it. I really don't care.
Yes, in terminal you must type ./adb devices, but within the .sh you can just issue adb devices and it works just fine. It is because you are issuing a command from within a script and OS X understands you better when you use them.
As for the memory card trick everyone is perpetuating, tis but a superstition and whatever floats your boat, while you attempt to get adb to stick. When I rooted mine, it took five to ten tries. Rooting my girlfriend's, on the other hand, took nearly 15-20 min for it to catch.
sk8rbebop said:
Yes, in terminal you must type ./adb devices, but within the .sh you can just issue adb devices and it works just fine. It is because you are issuing a command from within a script and OS X understands you better when you use them.
As for the memory card trick everyone is perpetuating, tis but a superstition and whatever floats your boat, while you attempt to get adb to stick. When I rooted mine, it took five to ten tries. Rooting my girlfriend's, on the other hand, took nearly 15-20 min for it to catch.
Click to expand...
Click to collapse
within the shell command command it has to be ./adb devices or it fails at command line 4 which is the problem i was having until i changed it in the shell and it worked... along with a few others...
and as far as the memory card thats the issue... i tried 5 different memory cards one always worked the others never stuck... it may have something to do with the way the memory card is coded... my 16gb mem card out my hd2 is the only one that worked... not really a superstition
shadowleo85 said:
within the shell command command it has to be ./adb devices or it fails at command line 4 which is the problem i was having until i changed it in the shell and it worked... along with a few others...
and as far as the memory card thats the issue... i tried 5 different memory cards one always worked the others never stuck... it may have something to do with the way the memory card is coded... my 16gb mem card out my hd2 is the only one that worked... not really a superstition
Click to expand...
Click to collapse
The memory card has nothing to do with the rooting process whatsoever. With that said, a lot of the memory cards shipping with the slides are misformated. The first thing I did was backup my card, swap it out with a class 10 16 GB card and set up a 1GB ext4 partition. Then I copied the files back to the FAT partition and all was well.
HebrewToYou said:
The memory card has nothing to do with the rooting process whatsoever. With that said, a lot of the memory cards shipping with the slides are misformated. The first thing I did was backup my card, swap it out with a class 10 16 GB card and set up a 1GB ext4 partition. Then I copied the files back to the FAT partition and all was well.
Click to expand...
Click to collapse
yet with all the cards i tested which are formatted correctly and running perfectly on all my devices... and even tried useing my class 6 8gig with is partitioned for my og mytouch didnt work... dude stop trying to correct me i got this... worry bout ya own lil world
shadowleo85 said:
yet with all the cards i tested which are formatted correctly and running perfectly on all my devices... and even tried useing my class 6 8gig with is partitioned for my og mytouch didnt work... dude stop trying to correct me i got this... worry bout ya own lil world
Click to expand...
Click to collapse
Oy vey. Seriously? The rooting process is a hit or miss operation. Your sdcard doesn't even come into play for a second. You could probably remove the darn thing and be successful.
Please, for heaven's sake, just listen to sk8rbebop, myself or any of the numerous other people saying in no uncertain terms that the sdcard issue is a myth. Don't perpetuate something that is entirely unrooted in reality.
Sheesh...
HebrewToYou said:
Oy vey. Seriously? The rooting process is a hit or miss operation. Your sdcard doesn't even come into play for a second. You could probably remove the darn thing and be successful.
Please, for heaven's sake, just listen to sk8rbebop, myself or any of the numerous other people saying in no uncertain terms that the sdcard issue is a myth. Don't perpetuate something that is entirely unrooted in reality.
Sheesh...
Click to expand...
Click to collapse
how can it be unrooted in reality when in reality it works and im proving that... its mighty funny that it doesnt stick unless this specific memory card is in my device... and u stating that it doesnt come into play is wrong... when u load ur phone into bootloader it does check ur "memory card" for an nbh image which is where i believe the problem lies... it accesses ur memory card just like the og mytouch did to locate a gold card... dont argue with me when it is just another work around that just may work seeing as IM PROVING THAT IT DOES INDEED WORK
shadowleo85 said:
how can it be unrooted in reality when in reality it works and im proving that... its mighty funny that it doesnt stick unless this specific memory card is in my device... and u stating that it doesnt come into play is wrong... when u load ur phone into bootloader it does check ur "memory card" for an nbh image which is where i believe the problem lies... it accesses ur memory card just like the og mytouch did to locate a gold card... dont argue with me when it is just another work around that just may work seeing as IM PROVING THAT IT DOES INDEED WORK
Click to expand...
Click to collapse
Oy vey. Fine, believe what you want. What's *actually* helping you root the device is sticking gum on your nose, turning your baseball cap backwards, rubbing your lucky rabbit foot and reciting the pledge of allegiance. You just haven't realized it yet.
Stay crunchy.
HebrewToYou said:
Oy vey. Fine, believe what you want. What's *actually* helping you root the device is sticking gum on your nose, turning your baseball cap backwards, rubbing your lucky rabbit foot and reciting the pledge of allegiance. You just haven't realized it yet.
Stay crunchy.
Click to expand...
Click to collapse
dude wtf is ur problem... if it can possibly help someone whose having the issue y r u having such an issue with it
I followed all of the instructions on this post:
forum.xda-developers.com/showthread.php?t=442480
No problems at all doing any of it.... BUT I have a G1 that had 1.6. Now it's 1.0. Everything seemed to work fine, but when I try to update with any ROM it does not seem to work... still 1.0.
When I restart it by holding the power and the home button I do not get the menu screen that all tutorials seem to have, I still get the Exclamation mark and have to hit Alt S.
Any suggestions? I have tried loading Cyanogen and 2 different JesusFreak versions. But no changes. ???
EDIT: Ok I just found this ...
to see is you are "rooted" download or use terminal app
At the $ prompt type su <enter>
should return a prompt now of
#
I downloaded the terminal app and it says permission denied when I type in su.
SO I guess it's not rooted...BUT everything I did with the instructions went off without a hitch. Did the telnet instructions with no problems....??? AHHHH!
NEW EDIT! OK I found this video "Rooting the G1 to Amon RA's Recovery " on you tube. Followed the simple instructions, everything worked great. So now I have 1.5.2, booted pressing home and power and got the menu screen for the first time ever. Tried to run an update and that menu screen is gone, I'm back to the exclamation point. And still su does not work in the terminal. And telnet only gives me a connection error now. PLEASE HELP!!!!
Ok I started over did ALL OF THIS:
If you have US-RC30/UK-RC8 or higher, you will first need to downgrade your phone to a previous version. (Skip these steps otherwise)
1. Format your phone's SD card to FAT32 mode:
* Hook your phone up to your computer using a USB cable and then wait for the notification to show up in your title bar of your phone.
* Click the notification, and then click "Mount".
* A new removable disk should show up on your computer. Right click it and select Format, and select FAT32 as the file system type.
2. Download and unzip the RC29 or RC7 image file. Copy the DREAIMG.nbh file to the SD card. (RC29 for US, RC7 is for UK)
3. Turn the device power off.
4. Hold Camera button, and press Power button to entry boot loader mode. You should see a gray/white screen with instructions to flash your phone with the update on your SD card. If you don't see that, make sure you followed the instructions properly.
5. As per the on-screen instructions, press the Power button to start upgrade procedure. DO NOT DO ANYTHING TO INTERRUPT THIS PROCESS.
6. After it is finished, perform the restart your phone.
Rooting your RC29 or lower phone:
On RC29 phones and lower, anything you type into your keyboard is also being run in a hidden console with root permissions. More information regarding that at the bottom of this post. But, to get root access, do the following:
Instructions:
1. Download recovery.img or the new version by Amon recovery-RA-dream-v1.5.2.img and copy it to your SD card (see the previous instructions on how to copy from your computer to your Phone's SD card).
2. Download the Hard SPL and copy the zip file to the SD card.
3. All files must be on the root of your SD card.
4. Restart your phone. Wait for your phone to start up fully and show the home screen.
5. After your phone starts up, hit the enter key twice, type "telnetd" and press enter. (Yes, it will start up a contact search, don't worry. Just type it.)
6. Download an Android "Telnet" application from the Market and connect to localhost.
7. If you connect successfully, you will have a root prompt "#".
8. Type the following into Telnet (these commands will give you root access easier in the future):
* mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
* cd sdcard
* flash_image recovery recovery.img
* cat recovery.img > /system/recovery.img
Now you have root!
SO, it says I should have root now. I downloaded the terminal, typed in su and it says access denied. ???
Wow. I cant believe that not as single person is willing to help me on a forum about this subject.
So I started over for the 4th time. Again did everything, it all goes smoothly. But still do not have permission when I type in su to a terminal.
I loaded Amon Ra Recovery, then loaded signed killa 1.5.
It worked, I see 1.5, but when I reboot I do not get the menu, I still get the exclamation point..... I only get the menu on the first reboot after loading the Amon Ra Recovery.
PLEASE ANY HELP I'M DYING OVER HERE!!!
fellow g1 er
Theunlocker ddoott coom
For g1 Has two part video about going bqack to early version and then flashing foward to get root
It worked for me.
However you should be aware that their procedure uses something other than dangerecovery which cyanogemod requires. To use froyo 2.2 android.
I found this out AFTERFLASHING FROYO so now oi have to backtrack.
Thunlocker also links to a g1 android version with root whiicch what you flash last from the sd
card using amonra recovery.
I do however haave root. And the unlocker basic root rom worked well until I flash cyanogen mod rc3
But rc3 does still have root on my phone. It just doesn't run well because only danger recovery can partition the nand chip properly apparently and I haven't done that yet.
Furthermore be aware if you install gapps that there are two versions mdpi and hdpi and no one tells you but I think only mdpi works on g1 .
I found out after flashing hdpi myself.
Wish others would help.
We are the blind leading the blind.....
If you find something that gets you cyanogenmod worling with google apps market then please tell me how.
At least if you follow the unlocker videos you will have root.
Get it from their webpwage not you tube because the webpage has the steps written out as well.
like this!
i thought a purely ubuntu method would be helpful for those just starting out [like me] and the linux methods haven't been updated [to my knowledge].
1. charge your phone to at least 50%.
2. get adb.
BEARTARD said:
Install adb. Download it here: developer.android.com/sdk/index.html . adb is a little program distributed as part of the Android software development kit (SDK). Its job is to communicate with the phone from a shell (terminal). To install adb, I strongly suggest you copy the adb file from the tools directory into your system's /usr/local/bin directory. This way, it will always be in your path. If you don't intend to do development work on Android applications, feel free to delete the rest of the SDK after installing adb.
Click to expand...
Click to collapse
so, download that ^ . open it up and extract the adb file from the tools folder onto the desktop. now open up the terminal and type in:
gksu nautilus /usr/local/bin
drag the adb file in there and close nautilus.
3. pick a rom from the rom bible: forum.xda-developers.com/showthread.php?t=704567
i like the ota updated one from CR, the froyo ones were "too lacking" for me. although still awesome*
place the rom on your phone's sd card. don't unzip it. and remember where you put it.
4. download this 4shared.com/file/J6i52nwy/slideroot.html
make a folder somewhere [i use the desktop] and name it something, like "root". extract the downloaded files into that folder.
5. set the phone up to be rooted:
-unplug it from the computer if it is plugged in
-again, make sure it is charged to at least 50%
-settings > applications > development > USB debugging (check mark here)
-settings > connect to pc > charge only
-settings > wireless & networks > wifi unchecked (important)
-settings > sound & display > screen timeout > never
-now plug it back in
6. minimize all other windows.
open up a terminal and type:
cd
now drag the folder you extracted all the stuff from step 4 into the terminal window [faster than typing it all out ]. click the title bar of the terminal. press enter. don't close this terminal. we should now be inside the folder.
7. copy and paste these commands in order.
they make some time to complete, so be patient or risk KILLING YOUR PHONE TO DEATH. [also, i'm not sure which commands actually require sudo to run so i just included it in all of the commands, forgive my noobishness].
commands:
sudo adb devices
-to start it up and make sure your phone is recognized the first time, if not, try again:
sudo adb devices
sudo adb push exploid /sqlite_stmt_journals
sudo adb push flash_image /data/local
sudo adb push mtd0.img /data/local
sudo adb push update.zip /sdcard
sudo adb push esprimg.zip /sdcard/ESPRIMG.zip
-you might want to get a drink or say hi to some friends at this point; takes a while. just wait until it says it's done like the rest.
adb shell
cd /sqlite_stmt_journals
chmod 0755 exploid
./exploid
-at this time go to settings and turn wifi on and then back off before continuing
./exploid
-the password is : secretlol
you should now have a # instead of a $
cd /data/local
chmod 04755 *
/data/local/flash_image misc /data/local/mtd0.img
8. turn off the phone.
9. press and hold volume down and then power up; hold both buttons.
let go when see the 3 skateboarding androids.
10. wait until the bar on the side of the screen loads.
if you don't see the bar wait about 4 minutes and something should happen.
11. when it is finished, press volume up, when prompted, to apply the update.
wait some more!~
DON'T REBOOT when it is done.
12. DON'T REBOOT!
13. press volume down.
press volume down once to highlight recovery and select with the power/lock button to boot recovery.
on the recovery screen you will see a device with a red warning triangle.
hold volume up and power together for a second or so.
14. ignore the warning at the bottom.
press volume down and then power to select apply update.zip.
you will now be loaded into the clockwork recovery and will be able to flash the rom of your choosing from your sd card.
you can use your touchpad at the bottom now and select with it.
otherwise: volume butttons=navigation power/lock=select
15. do a backup of your phone with nandroid.
-pretty self explanatory > press backup >wait >??? >profit!
16. wipe the device.
this won't wipe your sd card though, so don't worry.
17.install a custom rom
scroll down and select "install zip from sd"
select choose "zip from sdcard"
find your rom and apply!!!
wait!!!!!!.....
reboot!
18. complain on the dev forums about how bad the roms are, how dead the phone is, and speculate about newer phones. also, make sure to start your own thread even if it is a question, general banter, or to post pictures .
/sarcasm
19. seriously don't do step 18.
>_O
20. update the radio if it is not the newest one.
forum.xda-developers.com/showthread.php?t=705064
sources/more info:
exploid method:
forum.xda-developers.com/showthread.php?t=754669
ubuntu set up:
forum.xda-developers.com/showthread.php?t=710056
rom bible:
forum.xda-developers.com/showthread.php?t=704567
go donate money to the active devs now.
Oh crap. I got quoted. Good job, man!
thanks! i didn't know how else to so eloquently explain adb, so i just quoted you. hopefully this will be of help to all three of those linux users out there on this forum!
It's kind of funny, I came on here to write a thread like this one. I noticed that there wasn't a single thread that combined the new root method with flashing the ENG build into one. You saved me some time.
I noticed that you don't have the part about updating to the newest Radio after the ENG build. Do the newer ROMs come with a Radio update in them?
@slughappy1: i reccomended updating to CR's OTA rom since going from stock to updated stock with root is the most logical step. therefore, a radio updatre is included.
to my knowledge, the nicer devs include the newer radio, other wise they make a mention of updating it. anyways, i'll include it in my tutorial for completeness sake. now if only i could figure out how to take non-blurry distance pictures with my slide >_>. sadly, i'll probably sell this off for a g2 =\.
Why sudo? I don't think adb need super user permission. Is it needed because you put it in /usr/local?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
arifwn said:
Why sudo? I don't think adb need super user permission. Is it needed because you put it in /usr/local?
Click to expand...
Click to collapse
Some systems are setup incorrectly to handle giving users permission to write to the ADB device file when the phone is plugged in. The correct process is to fix the permissions on the dev file that udev creates. Here's a link to do that: http://forum.xda-developers.com/showpost.php?p=5300224&postcount=6.
Please ALWAYS refrain from using 'sudo' or 'su' unless you're ABSOLUTELY sure that it needs root and there's no (more) proper way to do it.
(On a side note, I'm always available to answer any simple or complicated Linux questions anyone may have. You can PM me to get my attention or GTalk: nbetcher at gmail dot com.)
Thanks for the post about not using sudo. It was a quick way to make sure users on various linux distros can get it to work without a whole bunch of rigmarole.
On another note about the udev rules mentioned, the "SYSFS{}" call is being deprecated and a revision will be needed soon.
So i tried to follow the intstruction but once i booted in recovery mode nothing happend
10. wait until the bar on the side of the screen loads.
if you don't see the bar wait about 4 minutes and something should happen.
this is the step where nothing i happening on my phone
huh!! no one cares to help me
You didn't give much information to learn where the problem might be. If you didn't get the loading bar on the side of the screen, your recovery didn't see the ESPRIMG.zip file in the root directory of your sd card. Mount it on the computer and see if it's there.
beartard said:
You didn't give much information to learn where the problem might be. If you didn't get the loading bar on the side of the screen, your recovery didn't see the ESPRIMG.zip file in the root directory of your sd card. Mount it on the computer and see if it's there.
Click to expand...
Click to collapse
Alright let me check if the sd card has ESPRIMG.zip. but i have a question no where in the instruction it says if i need to transfer the zip file to the sd card ?
Step number seven is one of the most important ones. Check those commands you pasted. Most of them copy files to various places on your phone.
So i recently installed urukdroid 1.0 on my A101IT.
I've been loathing the stock battery icon and though I'd install the batterymod found here:
http://forum.xda-developers.com/showthread.php?t=982529
(took the 2.3.20 firmware one)
Now I don't have ADB on my pc anymore so I thought I'd just use root explorer and drop both files in /system/framework/
After i copied the framework file however i'm stuck in the endless booting animation. (didn't copy services.jar yet)
Anybody that can help me resolve this issue ?
Why didn't you copy both files while doing it, or did it reboot as soon as you over-wrote your framework? One would assume that you need both of them copied (because the instructions say to).
Copying through root explorer with Android running could have been the problem. That's why the instructions have you issue a stop command first.
Rebooted as soon as i copied the framework.
(even trying to acces the uruk partition with a linux and recovery usb msc didn't work, only got to see my internal storage)
Well I guess I'll just have to reinstall urukdroid.
Greenthy said:
Well I guess I'll just have to reinstall urukdroid.
Click to expand...
Click to collapse
This s the fastest and best thing you can do about soft problems
Greenthy said:
Rebooted as soon as i copied the framework.
(even trying to acces the uruk partition with a linux and recovery usb msc didn't work, only got to see my internal storage)
Well I guess I'll just have to reinstall urukdroid.
Click to expand...
Click to collapse
You should really get an SD card reader. It's 5 bucks, and lets you fix things like this very easily. Or you can use an Android phone to mount it.
In the future, use adb and the "stop, copy, sync, start" method. If you get stuck in a bootloop, you will still be connected through ADB, and can restore the original framework very quickly.
I have an sd reader
It's just that :
- it's ext4 so my windows 7 is failing
- on ubuntu i don't have ownership : no write :s
(that last can be fixed i read with sudo nautilus)
messed it up again and even dropped my tablet : croocked mini-usb :S
Fail I hope it's just the cable that's giving me somewhat of a loose-contact now though, i have another mini-usb -just not at hand atm- but not another archos
Greenthy said:
So i recently installed urukdroid 1.0 on my A101IT.
I've been loathing the stock battery icon and though I'd install the batterymod found here:
http://forum.xda-developers.com/showthread.php?t=982529
(took the 2.3.20 firmware one)
Now I don't have ADB on my pc anymore so I thought I'd just use root explorer and drop both files in /system/framework/
After i copied the framework file however i'm stuck in the endless booting animation. (didn't copy services.jar yet)
Anybody that can help me resolve this issue ?
Click to expand...
Click to collapse
Strange since i had no problems doing it with root explorer, though i might have done int the other way round, might have copied services.jar first and then the framework-res.apk after that
TjaXanK said:
Strange since i had no problems doing it with root explorer, though i might have done int the other way round, might have copied services.jar first and then the framework-res.apk after that
Click to expand...
Click to collapse
Using Root Explorer will give you a boot-loop 40-50% of the time. You really shouldn't use it. Processes start terminating immediately after you start overwriting the framework. If the copy process terminates before it's done, you get a boot-loop. The only way to avoid that is to issue a "stop" command through ADB first. Use ADB to do the "stop, copy, sync, start" method.
Greenthy said:
I have an sd reader
It's just that :
- it's ext4 so my windows 7 is failing
- on ubuntu i don't have ownership : no write :s
(that last can be fixed i read with sudo nautilus)
messed it up again and even dropped my tablet : croocked mini-usb :S
Fail I hope it's just the cable that's giving me somewhat of a loose-contact now though, i have another mini-usb -just not at hand atm- but not another archos
Click to expand...
Click to collapse
I had to resolder my usb back onto the board. Ripped it completely out.
msticninja said:
Using Root Explorer will give you a boot-loop 40-50% of the time. You really shouldn't use it. Processes start terminating immediately after you start overwriting the framework. If the copy process terminates before it's done, you get a boot-loop. The only way to avoid that is to issue a "stop" command through ADB first. Use ADB to do the "stop, copy, sync, start" method.
Click to expand...
Click to collapse
Actually now that i think about it I didn't use root explorer I moved the files with the terminal on the deivce
TjaXanK said:
Actually now that i think about it I didn't use root explorer I moved the files with the terminal on the deivce
Click to expand...
Click to collapse
Terminal is a bad idea as well! It has the same issue, it can terminate in the middle of copying. You must put the system into "stop" to avoid that, but you cannot use the device itself when in "stop" mode, thus ADB.
Alright, so this is going to take a bit of explaining, please bear with me.
I got this phone a couple of weeks ago, subsequently rooted it, and shortly thereafter decided upon Viper for my ROM. After playing around for a bit, I took a look at Beastmode kernel yesterday. I backed up my phone, installed the new kernel, and everything went to hell shortly thereafter. Upon rebooting, my phone no longer detected a mounted SD card. Along with this, it also doesn't have working audio. I tried rolling back to my restoration point, but I cannot find it now. While digging through directories in recovery, I've found two things out.
1: There is now a storage/emulation/legacy folder with (almost) every folder that was in mnt/sdcard.
2: My restore point is gone, and I don't have the original kernel on my phone
I figured this wouldn't be THAT big of a problem, connect my phone to my PC, go into ADB and try to push the stock s-off kernel. Next set of problems.
1: /mnt/sdcard is showing as a non-directory, insists it doesn't exist.
2: storage/emulation/ shows as read only, and all lower subdirectories are coming up as not existing (I believe it to be an issue with folder naming, legacy is actually 0 on my file explorer on the phone, I think?).
Where I stand now::
At this moment, I have the HTC Droid DNA Toolkit running, the stock s-off Kernel, and a phone that doesn't cooperate with anything.
Also; I tried downloading the .zip directly on my phone, but because it doesn't think there's an SD card, it's refusing to let me download it. It lets me download apps from the market, though.
Any ideas?
PS! Forgot the biggest SNAFU in all of this. On my phone are about 200 pictures from my vacation which I hadn't put onto my computer yet because I am an imbecile. This is keeping me from wiping the phone down to brass tacks and starting all over. If someone can find a way for me to pull said pictures from my device, I can wipe it and see if that helps.
Killerkendolls said:
Alright, so this is going to take a bit of explaining, please bear with me.
I got this phone a couple of weeks ago, subsequently rooted it, and shortly thereafter decided upon Viper for my ROM. After playing around for a bit, I took a look at Beastmode kernel yesterday. I backed up my phone, installed the new kernel, and everything went to hell shortly thereafter. Upon rebooting, my phone no longer detected a mounted SD card. Along with this, it also doesn't have working audio. I tried rolling back to my restoration point, but I cannot find it now. While digging through directories in recovery, I've found two things out.
1: There is now a storage/emulation/legacy folder with (almost) every folder that was in mnt/sdcard.
2: My restore point is gone, and I don't have the original kernel on my phone
I figured this wouldn't be THAT big of a problem, connect my phone to my PC, go into ADB and try to push the stock s-off kernel. Next set of problems.
1: /mnt/sdcard is showing as a non-directory, insists it doesn't exist.
2: storage/emulation/ shows as read only, and all lower subdirectories are coming up as not existing (I believe it to be an issue with folder naming, legacy is actually 0 on my file explorer on the phone, I think?).
Where I stand now::
At this moment, I have the HTC Droid DNA Toolkit running, the stock s-off Kernel, and a phone that doesn't cooperate with anything.
Also; I tried downloading the .zip directly on my phone, but because it doesn't think there's an SD card, it's refusing to let me download it. It lets me download apps from the market, though.
Any ideas?
PS! Forgot the biggest SNAFU in all of this. On my phone are about 200 pictures from my vacation which I hadn't put onto my computer yet because I am an imbecile. This is keeping me from wiping the phone down to brass tacks and starting all over. If someone can find a way for me to pull said pictures from my device, I can wipe it and see if that helps.
Click to expand...
Click to collapse
Have you tried using an OTG cable to mount a flash drive? That's what I do when I backup/flash anything, I keep all my roms, kernels, backups, basically anything flashable on a flash drive, and use an OTG cable in CWM.
For the pictures:
Step 1; adb reboot recovery
Step 2; adb devices (to make sure it's detected)
Step 2.1: If your phone isn't detected, open sideload in recovery, adb devices again, then close sideload
Step 3: adb pull /sdcard/ C:\<username>\Desktop\sdcardbackup\
To fix everything else you'll probably need to wipe everything and flash a new rom.
EDIT: For future "snafus" the sdcard is on /sdcard/ not /mnt/sdcard/ because it's on internal memory, not mounted memory.
walther1337 said:
For the pictures:
Step 1; adb reboot recovery
Step 2; adb devices (to make sure it's detected)
Step 2.1: If your phone isn't detected, open sideload in recovery, adb devices again, then close sideload
Step 3: adb pull /sdcard/ C:\<username>\Desktop\sdcardbackup\
To fix everything else you'll probably need to wipe everything and flash a new rom.
EDIT: For future "snafus" the sdcard is on /sdcard/ not /mnt/sdcard/ because it's on internal memory, not mounted memory.
Click to expand...
Click to collapse
Well, I feel silly for that confusion. I've pulled everything from the sdcard, which honestly mattered more to me than fixing the phone. I'll putter around with getting the ROM and kernel operating correctly in the next couple of hours.
UPDATE!
Once I had the adb pull command corrected for me, pushing the new ZIP on there was an instant success in recovery. SD card exists correctly once again, installed Viper ROM over, full functionality once more.
Killerkendolls said:
Well, I feel silly for that confusion. I've pulled everything from the sdcard, which honestly mattered more to me than fixing the phone. I'll putter around with getting the ROM and kernel operating correctly in the next couple of hours.
UPDATE!
Once I had the adb pull command corrected for me, pushing the new ZIP on there was an instant success in recovery. SD card exists correctly once again, installed Viper ROM over, full functionality once more.
Click to expand...
Click to collapse
you can always do this too as long as the device is recognized by adb
Code:
adb shell
this will get you into the actual device where you can navigate around by using the " cd /dir_name " command and to go back up a dir use " cd .. " (a space and 2 "."s are needed) or just " cd " to get back to the starting point... if you know how to navigate through a unix terminal then you will know what to do here...
some other useful commands
Code:
ls, ls -a, ls -l, cd, cp, mv
ls = list (lists files/folders) "-a" means all, "-l" just makes it look neat and laid out better.
cd = change directory aka "dir"
cp = copy /path/to/file.ext /path/to/where/you/want/to/save/it/file.ext
mv = move (same as ^ ) except it just moves it and doesn't copy
oh and to exit adb shell just type "exit"
Honestly, just grab a working kernel. And use fastboot. Especially since you're s-off
fastboot flash boot boot.img should get you back in working order.
Sent from my HTC6435LVW using XDA Premium 4 mobile app