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

[scotty85]

is there any roms to try on
i google for them and the links i found lead me to 2fastroms.com: The Leading Fast ROM Site on the Net
and is a no go
thanks for taking the time of helping a lot

try liamf1's website, there should be link in his cm7 thread. he seems to be on top of lexikon rom developent

 

[felipeferras]

about to re-do the whole process again because is not working on T-Mobile

i just don't know where did i mess it up

 

[scotty85]

about to re-do the whole process again because is not working on T-Mobile

i just don't know where did i mess it up

You didn't do anything wrong,and re-doing the process isn't going to change it. Read back thru the thread,and you'll see others had prollems as well.

My current merge works fine on any radio,any ruu,on t mobile. My previous one did not.

We don't know why at this point,but some merges just don't seem to like gsm

 

[felipeferras]

but it was working and the other one i have too
and now none of them is working

i have a brand new HTC merge i get from ebay im gonna try that one too
ill try couple things before i mess with the new one

 

[felipeferras]

now this cmmon

 

[scotty85]

that is no big deal. that is just the htcdev compatible hboot. if you run an older ruu,it will replace it with the older .88 hboot.

locked does not mean anything as far as your sim cards

 

[felipeferras]

i start from fre3vo and forward and yes it is fix
i must say that i didn't do anything wrong the phones there juts updated by there self or something like that
now time to start beautifying my Merges

 

[lexasush]

Hi.
Please help me. I have root my merge, Then I wanted to install Cyanogenmod 7 but not set cwm retсovery, but set a rom and gapps. Now my phone will not boot, and in boot written
locked (OOW)
LEXICON PVT SHIP S-ON
HBOOT-0.89.0000
RADIO-1.08.00.0524_3
eMMC-boot

 

[felipeferras]

Hi.

if you connect it to the pc is detected ?
how come you S-ON and installed CM7?
does the Merge is stuck on the android/arrow/skateboard ?
can you power off and go to the hidden menu then try to use it as a fastboot device;
if it works load a PD42IMG on to the Micro SD and reboot

 

[scotty85]

Hi.
Please help me. I have root my merge, Then I wanted to install Cyanogenmod 7 but not set cwm retсovery, but set a rom and gapps. Now my phone will not boot, and in boot written
locked (OOW)
LEXICON PVT SHIP S-ON
HBOOT-0.89.0000
RADIO-1.08.00.0524_3
eMMC-boot

how did you flash cm7 without recovery,and with a locked bootloader?

at this point,if you know your phones build number and CID,you can try and find an ruu.

failing that, you can re-unlock the bootloader,and flash a rom or restore a backup.

be aware that the kernel will not flash from a permantly installed recovery on an s on phone. so if you did flash cm7,it likely is not booting due to a kernel incompatability

some info on "s-on" flashing:
http://androidforums.com/rezound-all-things-root/587430-s-want-flash-roms-read.html

heres how you can get some info about your phone that will help us:

first download and install these drivers: revolutionary drivers (mirror)

then,download this small file:
mini-adb.zip

-unzip it,and place the unzipped folder onto the root of your C drive(not inside a folder)

-open a cmd window(with win 7,click start bubble,type "command" or "cmd" in hte search box)

-now change to your mini-adb directory(assuming you didnt chagne the name). type in the black cmd window that opened on your PC:
cd c:\mini-adb

-pull the battery in your phone for a few seconds. hold volume down,then power. hold them both until you see the white/colored writing hboot screen

-select "fastboot" from the hboot menu with the vol rocker/power button

-in your cmd window type:
fastboot devices

it should output your phones serial number. if so youre good to go. if not,youre apparently having a driver issue. i usually recomend these drivers from Revolutionary: modified htc drivers download and install the drivers(you should just have to run that file). afterwards,unplug your phone,plug it back in. make sure its in fastboot. as soon as you get a result from "fastboot devices" your ready to procede to the next step.

-in your cmd window,type(or copy/paste,is much easier):
fastboot getvar all

-copy the info that outputs here. right click in your cmd window,click mark,highlight it all in white. hit enter. paste the info here. it will help us know which ruu for you to run.

 

[lexasush]

INFOversion: 0.5
INFOversion-bootloader: 0.89.0000
INFOversion-baseband: 1.08.00.0524_3
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main:
INFOserialno: HT18JM802664
INFOimei: 352442048423725
INFOproduct: lexikon
INFOplatform: HBOOT-7630
INFOmodelid: PD4210000
INFOcidnum: UTSI_010
INFObattery-status: good
INFObattery-voltage: 3883mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-d1a37910
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!

 

[lexasush]

1 if you connect it to the pc is detected ?
2 how come you S-ON and installed CM7?
3 does the Merge is stuck on the android/arrow/skateboard ?
4 can you power off and go to the hidden menu then try to use it as a fastboot device;
if it works load a PD42IMG on to the Micro SD and reboot

1 fastboot is detected
2 I dont know, I flash recovery, but not cwm, and install root from zip
3 Picture HTC
4 Fastboot is work, but I tried flash cwm 5 recowery - failed
now instal cwm 6 recovery

 

[scotty85]

sorry for the late reply,i am unfamiliar with your CID(UTSI_010) what carrier,and part of the workd are you in? also,is this carrier a CDMA or GSM carrier?

you have no main version,so it should be possible to flash any numbered RUU,we may just need to create a gold card if we cannot find an RUU for your cd.

your other option,would be to re-unlock the bootloader,re-install a recovery,and then try and flash a rom,or restore a backup. with htcdev unlock,you will need to pull the boot image from the rom or backup,and put it into your adb/fastboot folder,and then flash it with fastboot flash boot boot.img (assuming the boot image to be named simply "boot"

 

[Raptor_Jesus]

I'm attempting to return mine back to S-ON, and maybe I missed the fix somewhere in this thread, but the ./gfree -s on feature is failing.

Information:

LEXIKON XC SHIP S-OFF
HBOOT-0.88.0000
RADIO-1.08.00.0320
eMMC-boot

[HIGH]
C:\miniadb_merge>adb devices
List of devices attached
SERIAL NUMBER device


C:\miniadb_merge>adb shell
$ su
su
# cd /data/local/
cd /data/local/
# ./gfree -s on
./gfree -s on
--secu_flag on set
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-gda47c97
New .modinfo section size: 204
Attempting to power cycle eMMC... OK.
Write protect was successfully disabled.
Searching for mmc_blk_issue_rq symbol...
- Address: c029f4f4, type: t, name: mmc_blk_issue_rq, module: N/A
Kernel map base: 0xc029f000
Kernel memory mapped to 0x40002000
Searching for brq filter...
- Address: 0xc029f4f4 + 0x34c
- 0x2a000012 -> 0xea000012
Backing up current partition 7 and patching it...
Backing up partition /dev/block/mmcblk0p7 to /sdcard/part7backup-1370621474.bin ...
Error opening backup file.
[/HIGH]

Thanks.

 

[scotty85]

you have to be on the exploitable old vzw firmware in order for gfree to work.

if there is not an official,signed ruu to run after turning s on,the process will be more complicated.

why do you wish to turn s on? id pretty strongly recomend against it.

 

[Raptor_Jesus]

Are you aware of any other tools that can set me to S-ON.

If not, is it easier for me to just factory reset and start from step 1 of your post?

I incorrectly assumed that with permroot, S-OFF, SuperCID, etc. that I could just skip right to the end.

Thanks.

 

[scotty85]

again,the prcess is much more complicated if there is not an ruu for you to run afterwards,so we need alot more information.
-what carrier are you on
-what was your original build number and CID

there are no tools that i am aware of. in order to get back to how you were,you may need to:
-install vzw software
-install eng hboot
-have a gold card ready
-use gfree to change CID and radio secure flag
-run a custom ruu to get you back to stock system,boot,recovery,radio,etc,but not hboot
-only after everything is working correctly could you replace the eng s off hboot with a ship s on one.

why do you want to turn s on?

 

[Raptor_Jesus]

There is no carrier. It's a verizon branded phone but it is not on any service right now.

I couldn't tell you the original build and CID as it was shipped to me with superCID and its current build.

I'll start by downgrading to the software you mention and follow along.

Down the rabbit hole we go.

 

[scotty85]

There is no carrier. It's a verizon branded phone but it is not on any service right now.

I couldn't tell you the original build and CID as it was shipped to me with superCID and its current build.

I'll start by downgrading to the software you mention and follow along.

Down the rabbit hole we go.

ahh. if you wish to restore to vzw,you can:
-run the downgrade ruu
-run the steps to temp root and run gfree to restore VZW__001 CID and s on
-run newer vzw ruu

the prollem with a carrier who has no ruu is simply that you cannot flash unsigned files while s on

 

[lexasush]

sorry for the late reply,i am unfamiliar with your CID(UTSI_010) what carrier,and part of the workd are you in? also,is this carrier a CDMA or GSM carrier?

you have no main version,so it should be possible to flash any numbered RUU,we may just need to create a gold card if we cannot find an RUU for your cd.

your other option,would be to re-unlock the bootloader,re-install a recovery,and then try and flash a rom,or restore a backup. with htcdev unlock,you will need to pull the boot image from the rom or backup,and put it into your adb/fastboot folder,and then flash it with fastboot flash boot boot.img (assuming the boot image to be named simply "boot"

I'm from Ukraine, and use GSM
I already made a gold card. I also have a backup of my original firmware

 

[Raptor_Jesus]

ahh. if you wish to restore to vzw,you can:
-run the downgrade ruu
-run the steps to temp root and run gfree to restore VZW__001 CID and s on
-run newer vzw ruu

the prollem with a carrier who has no ruu is simply that you cannot flash unsigned files while s on

I have an XTC Clip if I ever need S-Off again.

Thanks for your help and this guide.

 

[scotty85]

I'm from Ukraine, and use GSM
I already made a gold card. I also have a backup of my original firmware

ok. since you have no main version,try to run this ruu:
Shipped ROMs

make sure the gold card is in the phone,then run the utility on the PC as administrator,if possible with your version of windows. when prompted to plug in the phone,power on into hboot,then select fastboot from the hboot menu,then plug in.

hopefully the utility will flash,wich will get you back to a working phone,with cell south software.

if you wish to have a rooted phone,and flash roms,then it may be advisable to go ahead and flash the vzw downgrade. if you do that,you can simply pick up the directions at step 6 to achieve superCID and s off.

do you have a nandroid of your original rom you can upload? i can turn it into an hboot flashable upgrade ruu if you like

 

[Raptor_Jesus]

Spoiler

A final question about something that isn't quite clear in your guide:

To begin with, I moved the original vzw leaked PD42IMG.zip to the formatted SD card, loaded into the bootloader, it scanned and found PD42IMG and I allowed it to update. (This put me into the vulnerable rom I assume.)

Then I backed up my mmcblk0p17 to the sdcard, pushed the misc-downgrade to the /sdcard/ and synced.

I rebooted and am in the bootloader where it found "PD42IMG.zip" and wants to know if I want to update again.

Is this the correct thing to do, or should I say No and select another option?

Edit: Nevermind. I see now that because I was already S-OFF I had no reason to go through with the steps required to otherwise allow me to flash the exploitabled PD42IMG.

 

[scotty85]

A final question about something that isn't quite clear in your guide:

To begin with, I moved the original vzw leaked PD42IMG.zip to the formatted SD card, loaded into the bootloader, it scanned and found PD42IMG and I allowed it to update. (This put me into the vulnerable rom I assume.)

Then I backed up my mmcblk0p17 to the sdcard, pushed the misc-downgrade to the /sdcard/ and synced.

I rebooted and am in the bootloader where it found "PD42IMG.zip" and wants to know if I want to update again.

Is this the correct thing to do, or should I say No and select another option?

in normal situations,yet. in your case,no

youre allready s off,so you dont need the steps to change main version. sorry ifn i wasnt quite clear on that,but all you need to do is flash then downgrade,then pick up at step 6.

excpet,instead of:
/data/local/gfree -f (wich performs all patches- that you allready have)

you can use:
/data/local/gfree -c xxxxxxxx to change the cid

and
/data/local/gfree -s on to turn s on

 

[Raptor_Jesus]

Yeah. If you notice my edit I caught onto that.

I now have S-On.

Thanks for a great guide.