• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root root,s-off,simunlock,superCID htc merge

And this is what i get when i continiued with the first post from step 6th "6)gain s-off,simunlock,and superCID"

finished. total time: 105.928s

c:\miniadb_merge>fastboot flash zip PD42IMG.zip
sending 'zip' (240345 KB)... OKAY [ 42.706s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,31
INFO[RUU]UZ,boot,69
INFO[RUU]UZ,boot,99
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,22
INFO[RUU]UZ,recovery,43
INFO[RUU]UZ,recovery,72
INFO[RUU]UZ,recovery,97
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,1
INFO[RUU]UZ,system,3
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,7
INFO[RUU]UZ,system,9
INFO[RUU]UZ,system,11
INFO[RUU]UZ,system,13
INFO[RUU]UZ,system,15
INFO[RUU]UZ,system,17
INFO[RUU]UZ,system,19
INFO[RUU]UZ,system,20
INFO[RUU]UZ,system,22
INFO[RUU]UZ,system,24
INFO[RUU]UZ,system,27
INFO[RUU]UZ,system,29
INFO[RUU]UZ,system,32
INFO[RUU]UZ,system,34
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,38
INFO[RUU]WP,system,0
INFO[RUU]WP,system,3
INFO[RUU]WP,system,7
INFO[RUU]WP,system,11
INFO[RUU]WP,system,15
INFO[RUU]WP,system,19
INFO[RUU]WP,system,22
INFO[RUU]WP,system,26
INFO[RUU]WP,system,30
INFO[RUU]WP,system,34
INFO[RUU]WP,system,38
INFO[RUU]UZ,system,38
INFO[RUU]UZ,system,39
INFO[RUU]UZ,system,41
INFO[RUU]UZ,system,43
INFO[RUU]UZ,system,45
INFO[RUU]UZ,system,47
INFO[RUU]UZ,system,49
INFO[RUU]UZ,system,51
INFO[RUU]UZ,system,53
INFO[RUU]UZ,system,55
INFO[RUU]UZ,system,57
INFO[RUU]UZ,system,58
INFO[RUU]UZ,system,60
INFO[RUU]UZ,system,62
INFO[RUU]UZ,system,64
INFO[RUU]UZ,system,66
INFO[RUU]UZ,system,68
INFO[RUU]UZ,system,70
INFO[RUU]UZ,system,72
INFO[RUU]UZ,system,74
INFO[RUU]UZ,system,76
INFO[RUU]WP,system,38
INFO[RUU]WP,system,41
INFO[RUU]WP,system,45
INFO[RUU]WP,system,49
INFO[RUU]WP,system,53
INFO[RUU]WP,system,57
INFO[RUU]WP,system,60
INFO[RUU]WP,system,64
INFO[RUU]WP,system,68
INFO[RUU]WP,system,72
INFO[RUU]WP,system,76
INFO[RUU]UZ,system,76
INFO[RUU]UZ,system,77
INFO[RUU]UZ,system,79
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,84
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,88
INFO[RUU]UZ,system,91
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,94
INFO[RUU]UZ,system,96
INFO[RUU]UZ,system,99
INFO[RUU]UZ,system,100
INFO[RUU]WP,system,76
INFO[RUU]WP,system,79
INFO[RUU]WP,system,83
INFO[RUU]WP,system,88
INFO[RUU]WP,system,91
INFO[RUU]WP,system,95
INFO[RUU]WP,system,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[partition] unzipping & flushing...
INFO[RUU]UZ,partition,0
INFO[RUU]UZ,partition,100
INFO[RUU]WP,partition,0
INFO[RUU]WP,partition,100
INFOstart image[dzdata] unzipping & flushing...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
OKAY [182.649s]
finished. total time: 225.356s

c:\miniadb_merge>fastboot reboot-bootloader
rebooting into bootloader... OKAY [ 0.371s]
finished. total time: 0.372s

c:\miniadb_merge>fastbooot reboot
'fastbooot' is not recognized as an internal or external command,
operable program or batch file.

c:\miniadb_merge>fastboot reboot
rebooting...
finished. total time: 0.365s

c:\miniadb_merge>adb push psneuter /data/local/
cannot open 'psneuter': No such file or directory

c:\miniadb_merge>adb push psneuter /data/local/
2325 KB/s (585731 bytes in 0.246s)

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

c:\miniadb_merge>adb push wpthis /data/local/
2204 KB/s (679475 bytes in 0.301s)

c:\miniadb_merge>adb push gfree /data/local/
2094 KB/s (716548 bytes in 0.334s)

c:\miniadb_merge>adb shell
$ chmod 0755 /data/local/psneuter
chmod 0755 /data/local/psneuter
$ chmod 0755 /data/local/wpthis
chmod 0755 /data/local/wpthis
$ chmod 0755 /data/local/gfree
chmod 0755 /data/local/gfree
$ /data/local/psneuter
/data/local/psneuter
property service neutered.
killing adbd. (should restart in a second or two)

c:\miniadb_merge>adb shell
# /data/local/wpthis
/data/local/wpthis
Build: 25
Section header entry size: 40
Number of section headers: 45
Total section header table size: 1800
Section header file offset: 0x00014e90 (85648)
Section index for section name string table: 42
String table offset: 0x00014cc7 (85191)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000f80 (3968)
-- size: 0x000000c4 (196)
Kernel release: 2.6.32.17-g788be6b3
New .modinfo section size: 204
Loading module... OK.
Write protect disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a2884, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a2000
Kernel memory mapped to 0x40001000
Searching for brq filter...
- Address: 0xc02a2884 + 0x34c
- 0x2a000012 -> 0xea000012
Done.
# /data/local/gfree -f
/data/local/gfree -f
--secu_flag off set
--cid set. CID will be changed to: 11111111
--sim_unlock. SIMLOCK will be removed
Section header entry size: 40
Number of section headers: 44
Total section header table size: 1760
Section header file offset: 0x000138b4 (80052)
Section index for section name string table: 41
String table offset: 0x000136fb (79611)
Searching for .modinfo section...
- Section[16]: .modinfo
-- offset: 0x00000a14 (2580)
-- size: 0x000000cc (204)
Kernel release: 2.6.32.17-g788be6b3
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c02a2884, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc02a2000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc02a2884 + 0x34c
- ***WARNING***: Found fuzzy match for brq filter, but conditional branch isn't
. (0xea000012)
Backing up current partition 7 and patching it...
Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-1385140262.bin
...
Error opening backup file.
# exit
exit

c:\miniadb_merge>
 
Hey Scotty guess what :D i actually did it yes man i did it :D

thanks to Points Money - Smart Shopping with Smart Coupons: How to Bypass or Manually Program the HTC Merge Verizon ADR6325

S-off, pretty sure rooted to and Usc ginger bread is on :D Thankyou so much Scootyy.. you dont know how much im thanks full to you. :)

Salute you sir! :) you are doing a great job. when i read i read this thread and saw the date like 2010 i thought Its over but you my man made my day :) thankyou so much.

I will come back if i have any problem or any question.:) All Hail to Mr. Scooty :)
 
Hey Scooty! i have some questions about merge. CM11 is available for lexikon. Is Cyanogenmod is good for HTC merge?

and i think my Htc merge is still not rooted completely cause superuser app is not working perfectly.

Thanks man :)
 
Hello people I am a noob in this of HTC root, I need help rooting this, I followed all the steps, but I'm not root, after I followed all the steps I tried to install the merge tool kit but it won't install

I need help, I've been trying approx one year
 
RaxzNazar said:
Hey Scooty! i have some questions about merge. CM11 is available for lexikon. Is Cyanogenmod is good for HTC merge?

and i think my Htc merge is still not rooted completely cause superuser app is not working perfectly.

Thanks man :)
Click to expand...

i personally always prefered cyanogenmod over stock older sense versions,its really just a matter of wether or not you can deal with the things listed as "not working".

to make superuser work better on your current rom,you can always delete the app and binary(app will live in system/app and binary in system/bin or system/xbin) and use this one:
[2013.12.17] SuperSU v1.86 - xda-developers

the download you need is about halfway in the first post and labled: CWM / TWRP / MobileODIN installable ZIP

you will flash it in recovery

eritronix said:
Hello people I am a noob in this of HTC root, I need help rooting this, I followed all the steps, but I'm not root, after I followed all the steps I tried to install the merge tool kit but it won't install

I need help, I've been trying approx one year
Click to expand...

have you achieved s off?

if so,you can try the supersu app i mentioned above,in place of the merge tool kit. make sure you are leaving it zipped,and flashing it in recovery
 
Should i have to rename yhe .zip file to "PD42IMG" then Flash it via Recovery or just like that?

and How can i flash CM11 into merge? i tried but failed. i renamed the CM11's zip file to " PD42IMG" and Flashed it Via Fastboot but nothing happened.
 
scotty85 said:
have you achieved s off?

if so,you can try the supersu app i mentioned above,in place of the merge tool kit. make sure you are leaving it zipped,and flashing it in recovery
Click to expand...

Thanks!!!!!

be achieved if and root, but now I have another problem, by mistake I put a command in the terminal emulator and cause a hard brick, called qualcomm mode ........ there will be some solution???

(does absolutely nothing, only when I connect it to pc calls me the driver qualcomm)
 
And when i go to recovery my cell freezez. i have to put the battery out then in to turn on the cell.

PS. my cell is verizon but i im using USC Ginger bread Rom.
 
RaxzNazar said:
Should i have to rename yhe .zip file to "PD42IMG" then Flash it via Recovery or just like that?

and How can i flash CM11 into merge? i tried but failed. i renamed the CM11's zip file to " PD42IMG" and Flashed it Via Fastboot but nothing happened.
Click to expand...

you will flash the cm11 file in recovery. no need to rename it.

eritronix said:
Thanks!!!!!

be achieved if and root, but now I have another problem, by mistake I put a command in the terminal emulator and cause a hard brick, called qualcomm mode ........ there will be some solution???

(does absolutely nothing, only when I connect it to pc calls me the driver qualcomm)
Click to expand...
what command did you enter? :eek: chances are not good for recovery,im afraid :(
RaxzNazar said:
And when i go to recovery my cell freezez. i have to put the battery out then in to turn on the cell.

PS. my cell is verizon but i im using USC Ginger bread Rom.
Click to expand...
going to need a bit more info. what are you seeing on the recovery screen?
 
scotty85 said:
what command did you enter? :eek: chances are not good for recovery,im afraid :(
Click to expand...


use the command that is used to push cwm samsung almost all, I thought I could run, but in the end said failed. cwm5 to merge then download in zip format. so renowned for upload by hboot. when I turn off the phone and I try turning it does nothing.

excuse the language, I'm using google translator, my native language is Spanish. so will be able to understand what that translates comic.
 
eritronix said:
use the command that is used to push cwm samsung almost all, I thought I could run, but in the end said failed. cwm5 to merge then download in zip format. so renowned for upload by hboot. when I turn off the phone and I try turning it does nothing.

excuse the language, I'm using google translator, my native language is Spanish. so will be able to understand what that translates comic.
Click to expand...

Can you copy the exact command you entered here so I can see?

If you pull the battery for a few seconds,are you able to enter hboot by holding power/vol down?
 
scotty85 said:
Can you copy the exact command you entered here so I can see?

If you pull the battery for a few seconds,are you able to enter hboot by holding power/vol down?
Click to expand...

I already did. and did nothing. the command was:

-su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
 
Scotty85


the phone will not turn on. I will buy another merge, but no match for verizon. there only for uscelular. my doubt is the process the same?. just use another rom (uscelular.custom)?
 
Hello everyone. I am hoping that someone can help me here. I have been reading this thread over and over again all day and trying over and over to get this phone switched to my at&t sim card. It is a verizon HTC merge and it is driving me crazy. I have copied my code and this is where I am at. Please someone tell me what I am doing wrong.



Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Bill New>cd ..

C:\Users>cd ..

C:\>cd c:\miniadb_merge

c:\miniadb_merge>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT19TM802337 device


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

c:\miniadb_merge>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.

[+] 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
1663 KB/s (1062992 bytes in 0.624s)

c:\miniadb_merge>adb shell
# chmod 0755 /data/local/busybox
chmod 0755 /data/local/busybox
# dd if=/dev/block/mmcblk0p17 of=/sdcard/misc-stock.img bs=4096
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc-stock.img bs=4096
/sdcard/misc-stock.img: cannot open for write: Read-only file system
# /data/local/busybox md5sum /sdcard/misc-stock.img
/data/local/busybox md5sum /sdcard/misc-stock.img
md5sum: can't open '/sdcard/misc-stock.img': No such file or directory
# /data/local/busybox md5sum /dev/block/mmcblk0p17
/data/local/busybox md5sum /dev/block/mmcblk0p17
88490b1467c95a2019c49af713736d69 /dev/block/mmcblk0p17
# exit
exit

c:\miniadb_merge>adb push misc-downgrade.img /sdcard/
failed to copy 'misc-downgrade.img' to '/sdcard//misc-downgrade.img': Read-only
file system

c:\miniadb_merge>adb shell
# dd if=/sdcard/misc-downgrade.img of=/dev/block/mmcblk0p17
dd if=/sdcard/misc-downgrade.img of=/dev/block/mmcblk0p17
/sdcard/misc-downgrade.img: cannot open for read: No such file or directory
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
#
 
ok so I realized that I have to type in exit but I am not to sure about the stuff that I did before where I was stuck at. The phone is now verizon and I would like to make it at&t. I am now stuck in the same place but it tells me this now

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Bill New>cd ..

C:\Users>cd ..

C:\>cd c:\miniadb_merge

c:\miniadb_merge>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HT19TM802337 device


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

c:\miniadb_merge>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.

[+] 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
1663 KB/s (1062992 bytes in 0.624s)

c:\miniadb_merge>adb shell
# chmod 0755 /data/local/busybox
chmod 0755 /data/local/busybox
# dd if=/dev/block/mmcblk0p17 of=/sdcard/misc-stock.img bs=4096
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc-stock.img bs=4096
/sdcard/misc-stock.img: cannot open for write: Read-only file system
# /data/local/busybox md5sum /sdcard/misc-stock.img
/data/local/busybox md5sum /sdcard/misc-stock.img
md5sum: can't open '/sdcard/misc-stock.img': No such file or directory
# /data/local/busybox md5sum /dev/block/mmcblk0p17
/data/local/busybox md5sum /dev/block/mmcblk0p17
88490b1467c95a2019c49af713736d69 /dev/block/mmcblk0p17
# exit
exit

c:\miniadb_merge>adb push misc-downgrade.img /sdcard/
failed to copy 'misc-downgrade.img' to '/sdcard//misc-downgrade.img': Read-only
file system

c:\miniadb_merge>adb shell
# dd if=/sdcard/misc-downgrade.img of=/dev/block/mmcblk0p17
dd if=/sdcard/misc-downgrade.img of=/dev/block/mmcblk0p17
/sdcard/misc-downgrade.img: cannot open for read: No such file or directory
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
# adb push misc-downgrade.img /sdcard/
adb push misc-downgrade.img /sdcard/
adb: not found
# exit
exit

c:\miniadb_merge>adb push misc-downgrade.img /sdcard/
failed to copy 'misc-downgrade.img' to '/sdcard//misc-downgrade.img': Read-only
file system

c:\miniadb_merge>adb shell
# exit
exit

c:\miniadb_merge>adb push misc-downgrade.img /sdcard/
failed to copy 'misc-downgrade.img' to '/sdcard//misc-downgrade.img': Read-only
file system



 
raxznazar use the htc site to unlock the bootloader and install custom recovery and superuser. After that go to step 6 of the tuturial. I ended up getting it working last night but it took till 4AM. one thing to remember is that if you have root access and you type adb shell and get the $ sign then you are not actually using root access. so you type su from the $ prompt and it changes to # showing that you now have root access. you would then have to type exit then hit enter when you are done and it will go to $ then type exit again to get out of the shell. Hope this helps. I should have done a video but I would have sounded like crap and woke everyone in the house up. I am now on at&t network with everything working. My phone is a verizon model.
 
Hey scotty thank you very much for the instructions. They helped me out a bunch. It was my first time flashing and only my second time rooting an android device. The first time all I had to do was download and run superoneclick so this was much more involved.
 
:confused:
 

Attachments

  • mmm.jpeg.jpg
    mmm.jpeg.jpg
    9.2 KB · Views: 86
billw129 said:
raxznazar use the htc site to unlock the bootloader and install custom recovery and superuser. After that go to step 6 of the tuturial. I ended up getting it working last night but it took till 4AM. one thing to remember is that if you have root access and you type adb shell and get the $ sign then you are not actually using root access. so you type su from the $ prompt and it changes to # showing that you now have root access. you would then have to type exit then hit enter when you are done and it will go to $ then type exit again to get out of the shell. Hope this helps. I should have done a video but I would have sounded like crap and woke everyone in the house up. I am now on at&t network with everything working. My phone is a verizon model.
Click to expand...

Thank you but HTC site? how? i m already S-off and to install custom recovery i have to go to the main recovery. but my main recovery is crushed or sumthing i donno but im getting that sign(pic posted) everytime.
 
did you try to unplug the usb cord and restart? I am very new to this to. I got that sign one time and it scared the crap out of me. I think that I unplugged the cable and restarted. also try to hold the vol down and power button and see if you can restart. after you got the s-off what ruu did you try to load?
 
billw129 said:
Hey scotty thank you very much for the instructions. They helped me out a bunch. It was my first time flashing and only my second time rooting an android device. The first time all I had to do was download and run superoneclick so this was much more involved.
Click to expand...

Glad they were helpful. Are you still having the prollems above,or are you sorted?
 
eritronix said:
I already did. and did nothing. the command was:

-su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p13
Click to expand...

well,you have written a recovery to something impiortant,wich has put the processor into a "do not boot" mode. it prolly is fixable via jtag,you might contact josh at MobileTechVideos.COM

im not sure what you overwrote,unfortunately,but recovery for s2 processors in phones like the merge,desire hd,etc. is p21,not p13

unfortunately,this is a very good example of why you should be sure what youre doing and why,and not just blindly try things when s off.

s off offers no security checks or write protections,and will let you brick your drevice :(
 
You must log in or register to reply here.
Back
Top Bottom