Root [How To] Root 2.3.4/downgrade and Get S-off

[scotty85]

question, i am considering using this thread...

[HOW TO] Fix the "Low on space" problem (in plain English) - xda-developers

it's the beginnings of your process of getting to 2.2 and then getting s-off.

i want to run this MOD, (located on a link on the thread)
"Convert2Ext4_no_data_limit_normal_dalvik.zip"

so that i can fix the Low Data Notification.
i see in your thread, post 629,

http://androidforums.com/incredible...2-3-4-downgrade-get-s-off-13.html#post3623666

how to put in some code in mac's terminal program. is that step in the rooting process how you actually get from 2.3.4 gingerbread back to 2.2 froyo? yes. the adb commands in a cmd or terminal window are re-writing the misc image of the phone,to trick the RUU into thinking that the phone has older software than what it is. thus allowing it to "upgrade" (downrade to froyo)

questions:

1. it looks like the directions on that thread work to simply gain root, is that correct? (but w/ s-on, right? that means that it's not a "permanent" root, correct?) wich thread? the one here on AF is s-off,permanent root.

2. i downloaded a md5 checker, and the "recovery-clockwork-5.0.2.0-inc.img" seems to verfiy w/ your numbers, but my "Reflash.dmg," the unrevoked 3.22 seems to be different. is that because i got the mac version?

prolly so. the mac version will have some different files,drivers,etc.

3. does anybody have the mac version's md5 numbers, just in case? i just don't want to mess up this root. (first time rooting)

when i download the mac reflash package on my pc,this is that i get:
Reflash.dmg 281308e1ed17dffd3d64ea68cb674406

not sure if that will be the same as what you got. if it is,you can pretty sure the download is complete and uncompromised. if it is different,i wouldnt say its bad-may just be something about downloading to a pc,not a mac.

3.5 how important is it that i double check the md5 numbers?
its definately a good habit to get into. as sdraw said,its not too big a deal in this particular situation. if youre flashing something like an hboot,radio,or a file that contains both(like an RUU) id place checking the numbers pretty high on the importance list

4. how "important" is it that i get s-off? will i notice a difference or anything like that? it's my first time rooting, period, so maybe i don't need to try this step yet?

i also feel s-off is well worth the effort,and of pretty high importance,as long as you use caution in what you flash. one thing you can do is wait a few days between root and downgrade,so you can become more comfortable. the task may not seem as overwhelming if you break it down into the smaller parts

 

[funkpod]

thank you! SO, from what i can gather...

i can't really "harm" my phone during the actual rooting process, using unrevoked 3.22.

Like, it might not work the 1st time, but there is no real danger of bricking my phone during the root process, correct?

most of the dangers come from flashing a ROM that isn't working right, or messing up the flashing process, correct? or a bad radio ROM, etc?

Most of the time, the common problems are boot loops, and they are easy enough to fix, right? flashing back to the original ROM, the stock HTC 2.3.4 ROM will fix it, right?

and bricking, in actual usage means that it's messed up enough that it just lies there on your desk like a brick, right? so actual bricking is not common, right?

so the actual part about rooting, I don't need to worry about so much, right? am i missing anything out?

 

[scotty85]

thank you! SO, from what i can gather...

i can't really "harm" my phone during the actual rooting process, using unrevoked 3.22.

Like, it might not work the 1st time, but there is no real danger of bricking my phone during the root process, correct? there is always that "slight" chance,but this process using unrevoked 3.22 and some adb commands to change the misc image, the likelyhood of damaging your phone beyond repair are slim to none.

most of the dangers come from flashing a ROM that isn't working right, or messing up the flashing process, correct? or a bad radio ROM, etc? correct. sometimes partitions can get damaged and repair can be complicated to impossible,but 99% of the time an unrecoverable phone comes from a bad hboot or radio flash. biggest thing you can do to protect your phones internal partitions are check md5s of everything you download. i personally believe amon recovery to be a lil safer than clockwork,but thats just my opinion. making sure to verify your files by checking md5s is your top defense.

Most of the time, the common problems are boot loops, and they are easy enough to fix, right? flashing back to the original ROM, the stock HTC 2.3.4 ROM will fix it, right? correct. those are the most common issues,along with simply "hangning" at a splash screen,and occasionally booting to a non-working,unfunctional rom. all are easily repaired by restoring a backup,or flashing a new rom,or in some extreme cases,running an RUU.

and bricking, in actual usage means that it's messed up enough that it just lies there on your desk like a brick, right? so actual bricking is not common, right? correct

so the actual part about rooting, I don't need to worry about so much, right? am i missing anything out? correct. and no,i cant really think of anything you are missing. just download everything,get organized,gl slow and make sure outputs match by looking at my adb session. if you do get goofed up,dont panic,we havent lost one in this thread yet

 

[funkpod]

thanks the only tough part is that i am on a mac, (no jokes, haha), and the session will be slightly different, right? thanks for the advice though, i think i'll try this tonight...

 

[gutte169]

I'm having quite a bit of trouble rooting my inc 2.3.4 (thought it would be a lot easier). I had numerous hang-up problems while using revoked, namely that I was continuously getting stuck at "waiting for reboot". I tried a lot of different things (updating drivers, uninstalling dropbox, etc.) and I eventually got to ClockworkMod Recovery v5.0.2.0 (not sure how it eventually worked). However, SuperUser is not in my apps drawer, and I am unsure how to progress.

Thanks in advance.

 

[funkpod]

hey, i get that low storage notification, and it's still there... do i need to try and get the Low Storage Notification off of my phone before rooting? Unrevoked has a warning that if my phone is not working perfectly, it could ruin phone. just checking.

 

[KingScilla]

Hey guys I'm new here. just signed up actually. mainly thanks to this badass sticky! thanks to everyone!
Well my question is for scotty85...
I'm all good right now, completed all of the steps, but I was hoping you could give me a tip on where to go from here. I'm looking for a mod to all around improve my inc(obviously), but wanna focus on battery life, texting, and internet as I use them the most. I tried messing around with it on my own and it blew up in my face! had to start ALL over. so now I'm kinda apprehensive. if you could just point me to the "roms", "kernals" etc that would best suit my needs and with a little direction to how to install it all I'd gladly give you a tip! beats spending another 20 dollars on a card reader, and a new microSD...
THANKS AGAIN EVERYONE!

BTW, I had incredible HD XL when my droid crapped out last time. I liked it, but I think I messed up the process some how...

 

[funkpod]

okay, cleared lots of stuff, no more low storage warning...

plugged it in, clicked OK, (it was on the warning message).

then... i get this screen. doesn't seem to be doing anything...

is this normal? what should i do?

my phone seems to be acting normal, i just sent myself a text, and i heard the notification, and i can interact w/ unrevoked 3.22, like, i can click file, and click open...

 

[scotty85]

thanks the only tough part is that i am on a mac, (no jokes, haha), and the session will be slightly different, right? thanks for the advice though, i think i'll try this tonight...

correct. hopefully ginskellas directions will help you with the mac-specific adb commands

I'm having quite a bit of trouble rooting my inc 2.3.4 (thought it would be a lot easier). I had numerous hang-up problems while using revoked, namely that I was continuously getting stuck at "waiting for reboot". I tried a lot of different things (updating drivers, uninstalling dropbox, etc.) and I eventually got to ClockworkMod Recovery v5.0.2.0 (not sure how it eventually worked). However, SuperUser is not in my apps drawer, and I am unsure how to progress.

Thanks in advance.

check post#1269

hey, i get that low storage notification, and it's still there... do i need to try and get the Low Storage Notification off of my phone before rooting? Unrevoked has a warning that if my phone is not working perfectly, it could ruin phone. just checking.

lol prolly most folks whove used the guide have had low space errors

Hey guys I'm new here. just signed up actually. mainly thanks to this badass sticky! thanks to everyone!
Well my question is for scotty85...
I'm all good right now, completed all of the steps, but I was hoping you could give me a tip on where to go from here. I'm looking for a mod to all around improve my inc(obviously), but wanna focus on battery life, texting, and internet as I use them the most. I tried messing around with it on my own and it blew up in my face! had to start ALL over. so now I'm kinda apprehensive. if you could just point me to the "roms", "kernals" etc that would best suit my needs and with a little direction to how to install it all I'd gladly give you a tip! beats spending another 20 dollars on a card reader, and a new microSD...
THANKS AGAIN EVERYONE!

BTW, I had incredible HD XL when my droid crapped out last time. I liked it, but I think I messed up the process some how...

sorry,the inc hasnt been my daily driver for awhile now,and im a bit out of touch with the available roms/kernels.

i personally like to run AOSP or "desensed" roms when possible,so i would check out cm7,wich is pretty stable,or even some cm9 based roms. tho be forwarned once youve tasted ICS its hard to go back to GB

the guys in the forum should definately be able to help you find a good rom/kernel combo. alot of it is just trial and error,to find something that works good for you,on your phone

okay, cleared lots of stuff, no more low storage warning...

plugged it in, clicked OK, (it was on the warning message).

then... i get this screen. doesn't seem to be doing anything...

is this normal? what should i do?

my phone seems to be acting normal, i just sent myself a text, and i heard the notification, and i can interact w/ unrevoked 3.22, like, i can click file, and click open...

no idea.... sorry. not sure if thats something related to being on a mac,or drivers,or what. maybe PM ginskella or post a topic in the forum about running unrevoked on a mac.

the other options,that i can think of are:
1)borrow a windows laptop or PC
2)you could try the "htc supertool" in place of unrevoked,tho it will not install a recovery
3)you can use the "zergRush" directions in post 2,wich do not utilize unrevoked,or any other rooting programs. only disadvantge is that you wont be able to install a recovery and make a backup,nor will you be able to use titanium to backup app data.

sorry i cant be of more help than that,i dont know anything about macs.

 

[metaldestiny]

I'm having quite a bit of trouble rooting my inc 2.3.4 (thought it would be a lot easier). I had numerous hang-up problems while using revoked, namely that I was continuously getting stuck at "waiting for reboot". I tried a lot of different things (updating drivers, uninstalling dropbox, etc.) and I eventually got to ClockworkMod Recovery v5.0.2.0 (not sure how it eventually worked). However, SuperUser is not in my apps drawer, and I am unsure how to progress.

Thanks in advance.

Please scroll up and read all of MY posts, where I had the same hang up and solved it with the help of guys here.

 

[funkpod]

hel!P okay, finally got unrevoked 3.22 to run, but now it says "done" on my computer, but i get this message on my phone...

"clockworkmod revovery v5.0.2.0...
wating for sd card to mount...
sd card mounded...
verifying sd card marker...
sd card marker not found...
checking internal sd card marker...
error verifying extendedcommand.
error processing rom manager scipt. please verify that you have ROM manager v.4.4.0.0. or higher installed
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log Please open ROM manager to report the issue.

what do i do now?

reboot system? agh!

 

[funkpod]

ROOT! okay, rooted! now... i just have to flash the MOD... tomorrow...

and then... after i rest... i'll play w/ maybe getting s-off........


thanks for everything so far, i'll be in touch!

 

[scotty85]

glad you got it. as you figured out,the error on your phone is no big deal. it comes somehow from installing the newest CW without the newest rom manager.

also,are there any tips or tricks you can share about getting 3.22 to run on your mac? what did you finally do to make it work? this info may help future mac rooters

 

[funkpod]

hey! okay, this is what happened last night when rooting my phone w/ these directions,

[HOW TO] Fix the "Low on space" problem (in plain English) - xda-developers,

basically the first part of the directions here. i'll post this in case it happens to anyone else, so that they know what to do. and don't freak out, like i did, cuz i'm a noob.

i followed the directions for rooting, Step 8. i was doing the directions for 2.3.4.
after i clicked "OK," to root (DON'T unplug your phone and replug your phone when you see the warning screen, btw. that will mess up unrevoked. I am using 3.22, btw. just start the process over again from the beginning if you do.)

i waited and waited, like... 10 minutes? maybe not even that. you see Unrevoked go through a bunch of notifications and techno-mumbo-jumbo.

after that, unrevoked 3.22 said "done." however, when i looked at my phone, it was this strange screen that was black, had Turquoise Blue menu options up at the top, and white script on the bottom. There was this error message...

"clockworkmod revovery v5.0.2.0 (other stuff...)
wating for sd card to mount (other stuff...)
sd card mounded...
verifying sd card marker...
sd card marker not found...
checking internal sd card marker...
error verifying extendedcommand.
error processing rom manager scipt. please verify that you have ROM manager v.4.4.0.0. or higher installed
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log Please open ROM manager to report the issue."

i was a little worried, cuz it said ERROR! but i knew something "good" had happened, because It said Clockworkmod up (recovery?) top. after consulting my friend, he assured me that that was a good thing. i was in Recovery, and I wouldn't be in that if i was not rooted. Also, after reading the error message, it looked like it was saying simply that it could not find ROM manager. so, due to my awesome friend's suggestion, i made a back up of my current ROM, aka my current the Stock ROM, aka it's like backing up every single file and setting on your phone, from there, right in ClockworkMod Recovery.

I sat through all the back up stuff. from there, your phone reboots, and this takes a while, almost 10 minutes.

After it rebooted, I was back, baby! Stock everything showed up, all of my launcher settings and everything showed up, it was great! I proceeded to follow the directions using ROM Manager (I did have to try making a backup twice, the first gave me a permission error, but after that it was smooth sailing).

So, thank you!

I am 2.3.4 still, I haven't downgraded to 2.2 or gotten s-off yet, but i will, one day... I only just got my Rooted feet wet

NOW, if you have the low Storage Notification problem, you can try this mod. The thread i mentioned will contain information about how to fix it. it's called "Convert2Ext4_no_data_limit_normal_dalvik.zip".


again, thanks for the help, hope this post helps.

 

[ned4spd8874]

I give up. I've tried everything and can't get my phone to root. I get to these steps:


-extract the contents of the unrevoked 3.22 .zip. open the folder, right click on "reflash" and run as administrator if possible.
-click on "file" in the corner of the relfash window
-click custom recovery
-navigate to,and select your "recovery-clockwork-5.0.2.0-inc" image and select it. at the bottom of your reflash app window, it should now say "recovery:custom" and "waiting for device"
-make sure usb debugging is checked ON in settings/applications/development.
-plug in your phone and place it in charge only mode. assuming you installed the drivers correctly,unrevoked 3.22 will start. let it do its thing. it will reboot a couple of times. when its finished,it may leave you on a blank screen. if this is the case,pull the battery and reboot.

and I get the error "Failed to flash recovery image.". Then the phone reboots a bunch of times and I have to struggle to get it to become stable again.

I just realized that I have a SLCD screen. Could that be the problem? I don't know. I've been trying to root this thing for about 5 hours now....

EDIT: Also, it appears that somewhere along the way I "upgraded" the hboot to 1.02.000. sigh...

 

[scotty85]

not sure why youre having trouble with unrevoked. might be something on your PC thats interfering with it. you can try uninstalling htc sync,and anything else tthat has the ability to interact with your phone,and try it again. folks that have had similar issues have mostly just given up and used different computers,and then had success. wish i knew what was confusing unrevoked,or had some better advice to make it work.

failing that,you can simply follow the directions in post 2 "zergRush method". it does not utilize unrevoked 3.22 for the downgrade.

option #2 would be the htc supertool to try and get temp or perm root,then follow the directions to downgrade: HTC Super Tool: The Latest All-in-One for Your HTC Device | xda-developers

option#3 would be to htcdev unlock,use that to root,then downgrade(see my respoce to one of your other posts). if you want to go the htcdev route,lets keep the posts and help in zamkats thread.

dont worry,we will get you there

for now,im off to work.

 

[chrisgoad3882]

I need help. I'm getting so frustrated with my phone. I've tried both methods and did the exact commands, but in the end I always get the same problem. I keep getting a [1] followed by permission denied and the command. This always happens when I enter ./flash_image misc /sdcard/mtd0.img . I don't know what to do so........HELP!

 

[PapiRico]

I have the same problem

I get
Verifying file system type...
unsupported radio version
(status 42)

hboot.92
microp-0417
touchpanel-atmel224_16ab
radio-2.15.10.07.07
july 23 2010

about
hardware 3
soft
2.3.4
base
2.15.10.07.07
sofware
4.08.605.2

Do i need flash a new radio ?

Any Help will be greatly appreciated

 

[scotty85]

I need help. I'm getting so frustrated with my phone. I've tried both methods and did the exact commands, but in the end I always get the same problem. I keep getting a [1] followed by permission denied and the command. This always happens when I enter ./flash_image misc /sdcard/mtd0.img . I don't know what to do so........HELP!

you have not provided near enuff information for us to help you. if you had unrevoked problems,then post 2 should have worked fine. if it didnt,you missed some steps or commands.

permission denied is becasue you dont have root access.

I have the same problem

I get
Verifying file system type...
unsupported radio version
(status 42)

hboot.92
microp-0417
touchpanel-atmel224_16ab
radio-2.15.10.07.07
july 23 2010

about
hardware 3
soft
2.3.4
base
2.15.10.07.07
sofware
4.08.605.2

Do i need flash a new radio ?

Any Help will be greatly appreciated

no,you do not need to flash a new radio(its not possible with s-on). you need to follow the directions a lil more closely,you are trying to run unrevoked 3.32 on GB,wich will not work.

you need to

-use 3.22 on GB,as per directions in post 1

or

-use directions in post 2

or

-use my other guide wich uitizes htcdev,and not any finicky root tools like unrevoked 3.32 or 3.22

 

[chrisgoad3882]

Here is my Unrevoked method

Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd C:\android-sdk-windows\platform-tools\

C:\android-sdk-windows\platform-tools>adb
Android Debug Bridge version 1.0.29

 -d                            - directs command to the only connected USB devic
e
                                 returns an error if more than one USB device is
 present.
 -e                            - directs command to the only running emulator.
                                 returns an error if more than one emulator is r
unning.
 -s <serial number>            - directs command to the USB device or emulator w
ith
                                 the given serial number. Overrides ANDROID_SERI
AL
                                 environment variable.
 -p <product name or path>     - simple product name like 'sooner', or
                                 a relative/absolute path to a product
                                 out directory like 'out/target/product/sooner'.

                                 If -p is not specified, the ANDROID_PRODUCT_OUT

                                 environment variable is used, which must
                                 be an absolute path.
 devices                       - list all connected devices
 connect <host>[:<port>]       - connect to a device via TCP/IP
                                 Port 5555 is used by default if no port number
is specified.
 disconnect [<host>[:<port>]]  - disconnect from a TCP/IP device.
                                 Port 5555 is used by default if no port number
is specified.
                                 Using this command with no additional arguments

                                 will disconnect from all connected TCP/IP devic
es.

device commands:
  adb push <local> <remote>    - copy file/dir to device
  adb pull <remote> [<local>]  - copy file/dir from device
  adb sync [ <directory> ]     - copy host->device only if changed
                                 (-l means list but don't copy)
                                 (see 'adb help all')
  adb shell                    - run remote shell interactively
  adb shell <command>          - run remote shell command
  adb emu <command>            - run emulator console command
  adb logcat [ <filter-spec> ] - View device log
  adb forward <local> <remote> - forward socket connections
                                 forward specs are one of:
                                   tcp:<port>
                                   localabstract:<unix domain socket name>
                                   localreserved:<unix domain socket name>
                                   localfilesystem:<unix domain socket name>
                                   dev:<character device name>
                                   jdwp:<process pid> (remote only)
  adb jdwp                     - list PIDs of processes hosting a JDWP transport

  adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
                                 ('-l' means forward-lock the app)
                                 ('-r' means reinstall the app, keeping its data
)
                                 ('-s' means install on SD card instead of inter
nal storage)
  adb uninstall [-k] <package> - remove this app package from the device
                                 ('-k' means keep the data and cache directories
)
  adb bugreport                - return all information from the device
                                 that should be included in a bug report.

  adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
                               - write an archive of the device's data to <file>
.
                                 If no -f option is supplied then the data is wr
itten
                                 to "backup.ab" in the current directory.
                                 (-apk|-noapk enable/disable backup of the .apks
 themselves
                                    in the archive; the default is noapk.)
                                 (-shared|-noshared enable/disable backup of the
 device's
                                    shared storage / SD card contents; the defau
lt is noshared.)
                                 (-all means to back up all installed applicatio
ns)
                                 (-system|-nosystem toggles whether -all automat
ically includes
                                    system applications; the default is to inclu
de system apps)
                                 (<packages...> is the list of applications to b
e backed up.  If
                                    the -all or -shared flags are passed, then t
he package
                                    list is optional.  Applications explicitly g
iven on the
                                    command line will be included even if -nosys
tem would
                                    ordinarily cause them to be omitted.)

  adb restore <file>           - restore device contents from the <file> backup
archive

  adb help                     - show this help message
  adb version                  - show version num

scripting:
  adb wait-for-device          - block until device is online
  adb start-server             - ensure that there is a server running
  adb kill-server              - kill the server if it is running
  adb get-state                - prints: offline | bootloader | device
  adb get-serialno             - prints: <serial-number>
  adb status-window            - continuously print device status for a specifie
d device
  adb remount                  - remounts the /system partition on the device re
ad-write
  adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
  adb reboot-bootloader        - reboots the device into the bootloader
  adb root                     - restarts the adbd daemon with root permissions
  adb usb                      - restarts the adbd daemon listening on USB
  adb tcpip <port>             - restarts the adbd daemon listening on TCP on th
e specified port
networking:
  adb ppp <tty> [parameters]   - Run PPP over USB.
 Note: you should not automatically start a PPP connection.
 <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
 [parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
  <localdir> can be interpreted in several ways:

  - If <directory> is not specified, both /system and /data partitions will be u
pdated.

  - If it is "system" or "data", only the corresponding partition
    is updated.

environmental variables:
  ADB_TRACE                    - Print debug information. A comma separated list
 of the following values
                                 1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
  ANDROID_SERIAL               - The serial number to connect to. -s takes prior
ity over this if given.
  ANDROID_LOG_TAGS             - When used with the logcat option, only these de
bug tags are printed.

C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
HT05WHJ04431    device


C:\android-sdk-windows\platform-tools>adb push flash_image /data/local/
1579 KB/s (75805 bytes in 0.046s)

C:\android-sdk-windows\platform-tools>adb push mtd0.img /sdcard/
593 KB/s (655360 bytes in 1.078s)

C:\android-sdk-windows\platform-tools>adb push PB31IMG.zip /sdcard/
2202 KB/s (180864972 bytes in 80.195s)

C:\android-sdk-windows\platform-tools>adb shell
$ su
su
# cd /data/local
cd /data/local
# chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
[1]   Illegal instruction     ./flash_image misc /sdcard/mtd0.img
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
[1]   Illegal instruction     ./flash_image misc /sdcard/mtd0.img
#
[LEFT]I know for a fact that i have root I ran unrevoked and it worked fine
Also here is my zergRush method
[CENTER]Microsoft Windows [Version 6.2.8250]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Windows\system32>cd C:\android-sdk-windows\platform-tools\

C:\android-sdk-windows\platform-tools>adb
Android Debug Bridge version 1.0.29

 -d                            - directs command to the only connected USB devic
e
                                 returns an error if more than one USB device is
 present.
 -e                            - directs command to the only running emulator.
                                 returns an error if more than one emulator is r
unning.
 -s <serial number>            - directs command to the USB device or emulator w
ith
                                 the given serial number. Overrides ANDROID_SERI
AL
                                 environment variable.
 -p <product name or path>     - simple product name like 'sooner', or
                                 a relative/absolute path to a product
                                 out directory like 'out/target/product/sooner'.

                                 If -p is not specified, the ANDROID_PRODUCT_OUT

                                 environment variable is used, which must
                                 be an absolute path.
 devices                       - list all connected devices
 connect <host>[:<port>]       - connect to a device via TCP/IP
                                 Port 5555 is used by default if no port number
is specified.
 disconnect [<host>[:<port>]]  - disconnect from a TCP/IP device.
                                 Port 5555 is used by default if no port number
is specified.
                                 Using this command with no additional arguments

                                 will disconnect from all connected TCP/IP devic
es.

device commands:
  adb push <local> <remote>    - copy file/dir to device
  adb pull <remote> [<local>]  - copy file/dir from device
  adb sync [ <directory> ]     - copy host->device only if changed
                                 (-l means list but don't copy)
                                 (see 'adb help all')
  adb shell                    - run remote shell interactively
  adb shell <command>          - run remote shell command
  adb emu <command>            - run emulator console command
  adb logcat [ <filter-spec> ] - View device log
  adb forward <local> <remote> - forward socket connections
                                 forward specs are one of:
                                   tcp:<port>
                                   localabstract:<unix domain socket name>
                                   localreserved:<unix domain socket name>
                                   localfilesystem:<unix domain socket name>
                                   dev:<character device name>
                                   jdwp:<process pid> (remote only)
  adb jdwp                     - list PIDs of processes hosting a JDWP transport

  adb install [-l] [-r] [-s] <file> - push this package file to the device and i
nstall it
                                 ('-l' means forward-lock the app)
                                 ('-r' means reinstall the app, keeping its data
)
                                 ('-s' means install on SD card instead of inter
nal storage)
  adb uninstall [-k] <package> - remove this app package from the device
                                 ('-k' means keep the data and cache directories
)
  adb bugreport                - return all information from the device
                                 that should be included in a bug report.

  adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|-nosy
stem] [<packages...>]
                               - write an archive of the device's data to <file>
.
                                 If no -f option is supplied then the data is wr
itten
                                 to "backup.ab" in the current directory.
                                 (-apk|-noapk enable/disable backup of the .apks
 themselves
                                    in the archive; the default is noapk.)
                                 (-shared|-noshared enable/disable backup of the
 device's
                                    shared storage / SD card contents; the defau
lt is noshared.)
                                 (-all means to back up all installed applicatio
ns)
                                 (-system|-nosystem toggles whether -all automat
ically includes
                                    system applications; the default is to inclu
de system apps)
                                 (<packages...> is the list of applications to b
e backed up.  If
                                    the -all or -shared flags are passed, then t
he package
                                    list is optional.  Applications explicitly g
iven on the
                                    command line will be included even if -nosys
tem would
                                    ordinarily cause them to be omitted.)

  adb restore <file>           - restore device contents from the <file> backup
archive

  adb help                     - show this help message
  adb version                  - show version num

scripting:
  adb wait-for-device          - block until device is online
  adb start-server             - ensure that there is a server running
  adb kill-server              - kill the server if it is running
  adb get-state                - prints: offline | bootloader | device
  adb get-serialno             - prints: <serial-number>
  adb status-window            - continuously print device status for a specifie
d device
  adb remount                  - remounts the /system partition on the device re
ad-write
  adb reboot [bootloader|recovery] - reboots the device, optionally into the boo
tloader or recovery program
  adb reboot-bootloader        - reboots the device into the bootloader
  adb root                     - restarts the adbd daemon with root permissions
  adb usb                      - restarts the adbd daemon listening on USB
  adb tcpip <port>             - restarts the adbd daemon listening on TCP on th
e specified port
networking:
  adb ppp <tty> [parameters]   - Run PPP over USB.
 Note: you should not automatically start a PPP connection.
 <tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
 [parameters] - Eg. defaultroute debug dump local notty usepeerdns

adb sync notes: adb sync [ <directory> ]
  <localdir> can be interpreted in several ways:

  - If <directory> is not specified, both /system and /data partitions will be u
pdated.

  - If it is "system" or "data", only the corresponding partition
    is updated.

environmental variables:
  ADB_TRACE                    - Print debug information. A comma separated list
 of the following values
                                 1 or all, adb, sockets, packets, rwx, usb, sync
, sysdeps, transport, jdwp
  ANDROID_SERIAL               - The serial number to connect to. -s takes prior
ity over this if given.
  ANDROID_LOG_TAGS             - When used with the logcat option, only these de
bug tags are printed.

C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
HT05WHJ04431    device


C:\android-sdk-windows\platform-tools>adb push zergRush /data/local
1098 KB/s (23060 bytes in 0.020s)

C:\android-sdk-windows\platform-tools>adb shell
$ chmod 755 /data/local/zergRush
chmod 755 /data/local/zergRush
$ /data/local/zergRush
/data/local/zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[-] Cannot copy boomsh.: Permission denied
$ exit
exit

C:\android-sdk-windows\platform-tools>adb devices
List of devices attached
HT05WHJ04431    device


C:\android-sdk-windows\platform-tools>adb shell
$ chmod 755 /data/local/zergRush
chmod 755 /data/local/zergRush
$ /data/local/zergRush
/data/local/zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[-] Cannot copy boomsh.: Permission denied
$ rm /data/local/tmp/booms
rm /data/local/tmp/booms
rm failed for /data/local/tmp/booms, No such file or directory
$ rm/data/local/tmp/sh
rm/data/local/tmp/sh
rm/data/local/tmp/sh: not found
$ /data/local/zergRush
/data/local/zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[-] Cannot copy boomsh.: Permission denied
$ rm /data/local/tmp/booms
rm /data/local/tmp/booms
rm failed for /data/local/tmp/booms, No such file or directory
$ rm /data/local/tmp/sh
rm /data/local/tmp/sh
$ /data/local/zergRush
/data/local/zergRush

[**] Zerg rush - Android 2.2/2.3 local root
[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00000118
[*] Scooting ...
[*] Sending 149 zerglings ...
[+] Zerglings found a way to enter ! 0x10
[+] Overseer found a path ! 0x000151e0
[*] Sending 149 zerglings ...
[+] Zerglings caused crash (good news): 0x401219c4 0x0054
[*] Researching Metabolic Boost ...
[+] Speedlings on the go ! 0xafd1950b 0xafd395f7
[*] Popping 24 more zerglings
[*] Sending 173 zerglings ...

[+] Rush did it ! It's a GG, man !
[+] Killing ADB and restarting as root... enjoy!

C:\android-sdk-windows\platform-tools>adb push flash_image /data/local/
1613 KB/s (75805 bytes in 0.045s)

C:\android-sdk-windows\platform-tools>adb push mtd0.img /sdcard/
997 KB/s (655360 bytes in 0.641s)

C:\android-sdk-windows\platform-tools>ab shell
'ab' is not recognized as an internal or external command,
operable program or batch file.

C:\android-sdk-windows\platform-tools>adb shell
# cd /data/local
cd /data/local
# chmod 0755 /data/local/flash_image
chmod 0755 /data/local/flash_image
#

# cd /data/local
cd /data/local
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
[1]   Illegal instruction     ./flash_image misc /sdcard/mtd0.img
# ./flash_image misc /sdcard/mtd0.img
./flash_image misc /sdcard/mtd0.img
[1]   Illegal instruction     ./flash_image misc /sdcard/mtd0.img
#

What am I missing????????????????????????

 

[scotty85]

i am not 100% sure,it looks like all your code is correct,and the files were pushed where they were supposed to,and run.

i suspect that its something with the sdk file youre using. maybe something is missing? did you dump your "tools" into platoform tools?

only think i can think of off the top of my head is use the mini-adb_inc folder instead of your sdk folder.

 

[chrisgoad3882]

So use the mini-sdk that you provided? I just don't see how it could be the program. But I'll give it a shot!

 

[EI2468]

-can i update my phone after rooting it?

 

[scotty85]

So use the mini-sdk that you provided? I just don't see how it could be the program. But I'll give it a shot!

any luck??

-can i update my phone after rooting it?

if you follow the full process to dowgrade and get s-off,you can run RUUs or OTA(providing a few things are correct) and s-off will still remain,so you can easily re-root any rom or ota you come across by:
1)installing recovery
2)flashing superuser

does that answer your question?

 

[bicyclemacgyvr]

My phone was once rooted and Unrevoked Forever had been used. Then I got the OTA which has cause myriad of problems. I have tried Hard Resets and soft and I cannot remove files or apps. I remove them or erase everything and when I reboot it is all back. I tried both methods. The first method I couldn't get the img to load. the ZeroG method got the img to load, but now the phone is stuck in reboot. It shows the droid red eye, then reboots, Quietly Brilliant, then says "Droid" and back to eye. Over and over.