Thread Status:
Not open for further replies.
  1. Check out our companion app, Forums for Android! Download from Google Play

Root merge info on 2fastroms

Discussion in 'Android Devices' started by 2fast4u88, Dec 1, 2011.

  1. 2fast4u88

    2fast4u88 Well-Known Member
    Thread Starter

    Aug 22, 2011
    To do a prl update or activate a phone you have to be non roaming (aka *228). Otherwise you have to call your carrier to activate the phone manually.

    Also here is my guide for downgrading for froyo Windows Htc Merge Froyo Root, S-off & Sim unlock how-to • Guides • 2FastRoms There is a one click solution at the end of the thread on page 16 with non of the terminal commands needed.

    Gingerbread guide is here Windows Htc Merge Gingerbread Root, Soff & Sim unlock how-to • Guides • 2FastRoms one click solution not yet done. Need a tester.

    Turn s-off back on and other misc stuff here Htc Merge Return to Stock (s-on, cid, and simlock) • Guides • 2FastRoms Needs a bit off work to finish a full return to stock guide.

    Verify s-off, super-cid and sim-lock here Verify the success of S-OFF, Super-CID & SIM-unlock • Guides • 2FastRoms

    My rom based on the uscc gingerbread rom is here [ROM] Htc Merge xFuZiiOnZz-1.0.0 • Roms • 2FastRoms

    Drell's kernel is here Undervolt & oc to 1.8ghz • Kernels • 2FastRoms

    My kernel is here 2fast oc to 1.8 and undervolt • Kernels • 2FastRoms

    Merge radio collection Htc Merge Official Radios • Radio's/Hboot's • 2FastRoms

    My Clockworkmod recovery here Clockworkmod • Recoverys • 2FastRoms

    As for flashing the misc-image it isn't needed unless your carrier does ota or mms doesn't work. Which mms won't work on these carriers to name a few Alaska Communications, Appalachian Wireless, BlueGrass Cellular, Cellcom Wireless and nTelos. These carriers depend on strings in the misc image for mms to work. If you are on one of the carriers listed above or you have one that mms won't work on. Then you can restore the backup misc-image.


  2. chill0398

    chill0398 Active Member

    Nov 30, 2011
    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation. All rights reserved.

    C:\Users\Corey>cd c:\miniadb_merge

    c:\miniadb_merge>adb devices
    List of devices attached
    HT15XM800011 device

    c:\miniadb_merge>adb push zergRush /data/local/
    1407 KB/s (23060 bytes in 0.016s)

    c:\miniadb_merge>adb shell
    $ rm /data/local/tmp/boomsh
    rm /data/local/tmp/boomsh
    $ rm /data/local/tmp/sh
    rm /data/local/tmp/sh
    $ chmod 755 /data/local/zergRush
    chmod 755 /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 Froyo ! 0x00000108
    [*] Scooting ...
    [*] Sending 149 zerglings ...
    [+] Zerglings found a way to enter ! 0x10
    [+] Overseer found a path ! 0x000150e8
    [*] Sending 149 zerglings ...
    [+] Zerglings caused crash (good news): 0x401219e4 0x006c
    [*] Researching Metabolic Boost ...
    [+] Speedlings on the go ! 0xafd1598f 0xafd1adb3
    [*] Sending 149 zerglings ...

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

    c:\miniadb_merge>adb push busybox /data/local
    1774 KB/s (1062992 bytes in 0.585s)

    c:\miniadb_merge>adb shell
    # chmod 0755 /data/local/busybox
    chmod 0755 /data/local/busybox
    # exit

    c:\miniadb_merge>adb push busybox /data/local
    1718 KB/s (1062992 bytes in 0.604s)

    c:\miniadb_merge>adb shell
    # chmod 0755 /data/local/busybox
    chmod 0755 /data/local/busybox
    # dd if=/dev/block/mmcblk0p25 of=/sdcard/system.img bs=4096
    dd if=/dev/block/mmcblk0p25 of=/sdcard/system.img bs=4096

    Here is my coding but when I get it this point the prompt doesn't go back to a # instead it just keeps flashing an underscore. Am I doing something wrong?
  3. scotty85

    scotty85 Well-Known Member

    Jul 25, 2010
    Replied on the other thread. You didn't do anything wrong. System image is huge and it takes forever to back it up and check its md5 :)

Share This Page