I got it working just fine just restarted fastboot, but I haves new problem with ROM I downloadedb for gingerbread usc Google play won't auto update from market.
I got it working just fine just restarted fastboot, but I haves new problem with ROM I downloadedb for gingerbread usc Google play won't auto update from market.
i uploaded the play store .apk from my rezound. you can try deleting the normal vending.apk and installing it in system/app: Phonesky.apk
assuming you completed the process,youll stay s-off,and all youll have to do following running the ruu is re-install recovery,re-flash root files.
__________________
The Delivery Guy
If someone has helped you,please click the THANKS button on that post.
Please post questions so others can benefit from the answers. donate to my device fund
Last edited by scotty85; September 24th, 2012 at 05:32 PM.
The Following User Says Thank You to scotty85 For This Useful Post:
What did work. Downloaded and re-installed the Stock ROM,
wait for play to update. Do a carrier update just to make sure for usc it *228
Finally re-flash the custom recovery and then install the zip for superuser
Last edited by tmaleshafske; September 24th, 2012 at 09:41 PM.
Reason: Problem resolution
im not sure what you mean you "cant push anything into it"
you are are apparently on a new enuff gingerbread build that zergrush is failing because the exploit has been patched(hellions with blue flames means zergrush didnt get temp root). what errors are you recieving with fre3vo?
you could try taco root for temp root,it will prolly work,but as exploits go,its slightly more of a PITA.
you could also htcdev unlock to get root access to downgrade.
-open the DHDDowngrade.zip file,then the folder contained inside of it. transfer "Fre3vo" into the miniadb_merge folder with adb/fastboot.(ignore the rest of the files in DHDDongrade,fre3vo is the only one you need)
-in your command window: change to the miniadb_merge directory by typing: cd c:\miniadb_merge (your promt should change to c:\miniadb_merge>)
*note that in the next few steps,anything in bold type is an adb command. you can directly copy from this window,and paste into your command window to eliminate typos.
-enable usb debugging,plug in your phone via usb. select "charge only" mode.
-make sure adb is seeing your phone: adb devices (should return your serial number)
- enter the commands from your link,one at a time,hit enter after each:
-make sure it worked. when you see "exploiting device" then your command prompt again: adb shell (if your prompt changes to a # youre good to go)
heres what the above will look like in your cmd window:
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>cd c:\tbolt2
c:\tbolt2>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxx device
c:\tbolt2>adb push fre3vo /data/local/tmp
956 KB/s (9796 bytes in 0.010s)
c:\tbolt2>adb shell chmod 777 /data/local/tmp/fre3vo
c:\tbolt2>adb shell /data/local/tmp/fre3vo -debug -start F0000000 -end FFFFFFFF
fre3vo by #teamwin
Please wait...
Attempting to modify ro.secure property...
fb_fix_screeninfo:
id: msmfb
smem_start: 802160640
smem_len: 3145728
type: 0
type_aux: 0
visual: 2
xpanstep: 0
ypanstep: 1
line_length: 1920
mmio_start: 0
accel: 0
fb_var_screeninfo:
xres: 480
yres: 800
xres_virtual: 480
yres_virtual: 1600
xoffset: 0
yoffset: 0
bits_per_pixel: 32
activate: 16
height: 94
width: 56
rotate: 0
grayscale: 0
nonstd: 0
accel_flags: 0
pixclock: 0
left_margin: 0
right_margin: 0
upper_margin: 0
lower_margin: 0
hsync_len: 0
vsync_len: 0
sync: 0
vmode: 0
Buffer offset: 00000000
Buffer size: 8192
Scanning region f0000000...
Scanning region f00f0000...
Scanning region f01e0000...
Scanning region f02d0000...
Scanning region f03c0000...
Scanning region f04b0000...
Scanning region f05a0000...
Scanning region f0690000...
Scanning region f0780000...
Scanning region f0870000...
Scanning region f0960000...
Scanning region f0a50000...
Scanning region f0b40000...
Scanning region f0c30000...
Scanning region f0d20000...
Scanning region f0e10000...
Scanning region f0f00000...
Scanning region f0ff0000...
Scanning region f10e0000...
Scanning region f11d0000...
Scanning region f12c0000...
Scanning region f13b0000...
Scanning region f14a0000...
Scanning region f1590000...
Scanning region f1680000...
Scanning region f1770000...
Scanning region f1860000...
Scanning region f1950000...
Scanning region f1a40000...
Scanning region f1b30000...
Scanning region f1c20000...
Scanning region f1d10000...
Scanning region f1e00000...
Scanning region f1ef0000...
Scanning region f1fe0000...
Scanning region f20d0000...
Scanning region f21c0000...
Scanning region f22b0000...
Scanning region f23a0000...
Scanning region f2490000...
Scanning region f2580000...
Scanning region f2670000...
Scanning region f2760000...
Scanning region f2850000...
Scanning region f2940000...
Scanning region f2a30000...
Scanning region f2b20000...
Scanning region f2c10000...
Scanning region f2d00000...
Scanning region f2df0000...
Scanning region f2ee0000...
Scanning region f2fd0000...
Scanning region f30c0000...
Scanning region f31b0000...
Scanning region f32a0000...
Scanning region f3390000...
Scanning region f3480000...
Scanning region f3570000...
Scanning region f3660000...
Scanning region f3750000...
Scanning region f3840000...
Scanning region f3930000...
Scanning region f3a20000...
Scanning region f3b10000...
Scanning region f3c00000...
Scanning region f3cf0000...
Scanning region f3de0000...
Scanning region f3ed0000...
Scanning region f3fc0000...
Scanning region f40b0000...
Scanning region f41a0000...
Scanning region f4290000...
Scanning region f4380000...
Scanning region f4470000...
Scanning region f4560000...
Scanning region f4650000...
Scanning region f4740000...
Scanning region f4830000...
Scanning region f4920000...
Scanning region f4a10000...
Scanning region f4b00000...
Scanning region f4bf0000...
Scanning region f4ce0000...
Scanning region f4dd0000...
Scanning region f4ec0000...
Scanning region f4fb0000...
Scanning region f50a0000...
Scanning region f5190000...
Scanning region f5280000...
Scanning region f5370000...
Scanning region f5460000...
Scanning region f5550000...
Scanning region f5640000...
Scanning region f5730000...
Scanning region f5820000...
Scanning region f5910000...
Scanning region f5a00000...
Scanning region f5af0000...
Scanning region f5be0000...
Scanning region f5cd0000...
Scanning region f5dc0000...
Scanning region f5eb0000...
Scanning region f5fa0000...
Scanning region f6090000...
Scanning region f6180000...
Scanning region f6270000...
Scanning region f6360000...
Scanning region f6450000...
Scanning region f6540000...
Scanning region f6630000...
Scanning region f6720000...
Scanning region f6810000...
Scanning region f6900000...
Scanning region f69f0000...
Scanning region f6ae0000...
Scanning region f6bd0000...
Scanning region f6cc0000...
Scanning region f6db0000...
Scanning region f6ea0000...
Scanning region f6f90000...
Scanning region f7080000...
Scanning region f7170000...
Scanning region f7260000...
Scanning region f7350000...
Scanning region f7440000...
Scanning region f7530000...
Scanning region f7620000...
Scanning region f7710000...
Scanning region f7800000...
Scanning region f78f0000...
Scanning region f79e0000...
Scanning region f7ad0000...
Scanning region f7bc0000...
Scanning region f7cb0000...
Scanning region f7da0000...
Scanning region f7e90000...
Scanning region f7f80000...
Scanning region f8070000...
Scanning region f8160000...
Scanning region f8250000...
Scanning region f8340000...
Scanning region f8430000...
Scanning region f8520000...
Scanning region f8610000...
Scanning region f8700000...
Scanning region f87f0000...
Scanning region f88e0000...
Scanning region f89d0000...
Scanning region f8ac0000...
Scanning region f8bb0000...
Scanning region f8ca0000...
Scanning region f8d90000...
Scanning region f8e80000...
Scanning region f8f70000...
Scanning region f9060000...
Scanning region f9150000...
Scanning region f9240000...
Scanning region f9330000...
Scanning region f9420000...
Scanning region f9510000...
Scanning region f9600000...
Scanning region f96f0000...
Scanning region f97e0000...
Scanning region f98d0000...
Scanning region f99c0000...
Scanning region f9ab0000...
Scanning region f9ba0000...
Scanning region f9c90000...
Scanning region f9d80000...
Scanning region f9e70000...
Scanning region f9f60000...
Potential exploit area found at address f9fd6200:e00.
Exploiting device...
c:\tbolt2>adb shell
# <-indicates that you have temp root access
(ignore tbolt2,these are actually my thunderbolt directions )
if you get your "#" prompt,indicating temp root,type exit to get back to your miniadb_merge> prompt,and pickup the directions in the first post at: adb push busybox /data/local
basically,youre just eliminating those first few lines that pertain to zergrush. once youve successfully downgraded,you can follow the directions exactly,as youre on older firmware where the exploits will work for sure.
I would like to join the droves of those thanking you Mr. Scotty. Your most excellent guide has gotten me introduced to the world of phone modding. I'm just getting started, i have a merge I'm attempting to get to work on my AT&T account. It was a USC branded phone, but with your help, i just got the downgrade up and should have s-off, root, superCID, and simunlock soon. Thank you again.
Scotty, your one helpful dude. Thank you so much for all the help you've given in this thread. I wouldn't have gotten as far as I have with my merge if it had not been for your help here.
I think I'm pretty much there except that my t-mobile sim is not being recognized. My sim card works in my g1 just fine but my merge does not recognize it at all. I get "sim card not found, please insert sim" when I go into the GSM options. I guess my questions is: Is this what it will say if the phone is not sim unlocked or is it a problem with the sim/hardware? This sim works fine in my g1 so I'm a bit confused.
This was a usc phone when I started. Now it has the usc 2.04.573.2 on it. I followed your steps exactly and didn't encounter any issues but now I'm stuck on getting the sim to work. I flashed the radio to 1.06.00.0910 which, from my understanding is needed to allow a US sim card to work. Any suggestions on where to go from here?
Again, thank you so much for the huge drop of knowledge on this thread :-)
The Following User Says Thank You to phishinphree For This Useful Post:
Scotty, your one helpful dude. Thank you so much for all the help you've given in this thread. I wouldn't have gotten as far as I have with my merge if it had not been for your help here.
I think I'm pretty much there except that my t-mobile sim is not being recognized. My sim card works in my g1 just fine but my merge does not recognize it at all. I get "sim card not found, please insert sim" when I go into the GSM options. I guess my questions is: Is this what it will say if the phone is not sim unlocked or is it a problem with the sim/hardware? This sim works fine in my g1 so I'm a bit confused.
This was a usc phone when I started. Now it has the usc 2.04.573.2 on it. I followed your steps exactly and didn't encounter any issues but now I'm stuck on getting the sim to work. I flashed the radio to 1.06.00.0910 which, from my understanding is needed to allow a US sim card to work. Any suggestions on where to go from here?
Again, thank you so much for the huge drop of knowledge on this thread :-)
thanks for your nice words. unfortunately,i do not have any idea how you should procede. i had a usc merge that i could not get to work with a sim,either. another user on the thread had a vzw merge and had the same issues. in both cases,the sim card was recognized with the chinese test rom,but it bricked his device,so i wont recomend trying that.
my current merge takes a t mobile sim with no prollem,no matter what rom or radio its on. if you rread back a few pages youll see all the stuff we tried... we never did figure out exactly why it wasnt working.
out of curiosity,what is the top line of your hboot information? should be lexikion xx ship s-off what is xx on your phone?
I was worried that would be the case. Here's all the hboot info. I flashed it back to stock, not sure if that changed the XB part as I paid more attention to the version numbers. From what I've read here and elsewhere, its the radio that stops the sim from working. Some said a verizon radio would allow the sim to work but most of the links on another thread I found were dead so I couldn't get far.
I was worried that would be the case. Here's all the hboot info. I flashed it back to stock, not sure if that changed the XB part as I paid more attention to the version numbers. From what I've read here and elsewhere, its the radio that stops the sim from working. Some said a verizon radio would allow the sim to work but most of the links on another thread I found were dead so I couldn't get far.
when i had the same issue,i tried every available radio and ruu. the test rom worked just fine,but as i mentioned the last user that tried that was left with a dead device,so there is obviuosly some thigns we do not understand about it.
it may be something do do with xb vs xc. mine with the working sim is an xc. we will have to do some more research on that.
Right on. It was free to me so I'm not too worried about bricking it. Its been since I rooted my g1 since I've been back into this stuff so forgive me if its a stupid question but can flash to xc or is that something that cannot be changed?
Also assuming I get the test rom on this device without bricking it, is it a viable rom to stick with or is it just a test that wouldn't connect to towers or whatever?
Right on. It was free to me so I'm not too worried about bricking it. Its been since I rooted my g1 since I've been back into this stuff so forgive me if its a stupid question but can flash to xc or is that something that cannot be changed?
Also assuming I get the test rom on this device without bricking it, is it a viable rom to stick with or is it just a test that wouldn't connect to towers or whatever?
im not really sure what the xb/xc refer to it is indicative of some type of hardware,it does not change no matter what hboot you run.
the test rom is not something youd want to run for any length of time. it is chinese,and has assorted china-specific apps and such,and no market. it also has a huge "htc confidential" watermark that you cant get rid of.
i flashed it,then flashed a different ruu with no issue. the other user flashed it,flashed an ruu,and then when the phone went to reboot,it just turned off and wouldnt power back on. i believe i followed it with anotehr signed ruu,an actual .exe file,so maybe this was a factor. the other user flashed one of my unsigned "custom ruus".
i had cautioned him about it,after having bricked a second merge that i had. i wsa trying to install a recovery,so i could install superuser,so i could try and install the market. recovery for some reason would not take,so i tried to flash a different hboot. i typed "fastboot reboot-bootloader aFTER THE flash,and it made a short buzz,and turned off.
so i would strongly recomend agains messing with the chinese test rom,as there are too many unknown factors to predict wether it would end badly or not. if you choose to give it a shot,i would recomend following it with a signed .exe file,but that may not be enuff.
scotty85, I got given a USC Merge that had software issues. Turns out the board was bad. Bought Merge cheap off ebay with clean ESN, cracked screen, owner claimed it was USC branded. Took the board out of that one, put it in the one with the bad board, voila! Everything worked. Until I tried to activate it. Turns out, it has Sprint OS installed and Sprint RUU's.
If I follow these steps, do you think after goldcard/downgrade/push USC ruu that I can change this phone from Sprint to USC? Not sure what steps to follow, tried to make a goldcard once but didn't seem to work. The carriers here are CDMA and do not use removable sim cards.
Last edited by jasonofx; November 5th, 2012 at 06:35 PM.
well,you are not on a sprint OS. your build number is from nTelos,bluegrass wireless,or possibly some other small carrier using sprint or vzw towers. your hboot screen displays the merge codename "lexikon" and the correct merge hboot version.
to answer your original question,rooting the phone via this guide or any method will not let you use it on a cdma network that it was not intended to. while the sim slot will be unlocked,there have been issues even using the merge on different gsm networks.
cdma carriers tend to be picky about the devices they allow on their network,so your question can really only be answered by USC. cdma flashing and cloning is potentially illegal and/or fradulent,and not something we are permited to discuss here.
using the guide will turn off the radio secure flag,unlock the sim slot,and give the phone superCID wich will allow you to flash other carriers RUUs,install a custom recovery,and give you the ability to modify system files that you normally will not have access to. if you wish to root,we will be happy to help you
Oh, ok. Thanks for the info. I think I'll just look for another phone, I have to use US cellular because that's what my job provides, and this phone is worthless to me right now.
Oh, ok. Thanks for the info. I think I'll just look for another phone, I have to use US cellular because that's what my job provides, and this phone is worthless to me right now.
have you spoken to us cellular? if not it would be worth a 5 minute phone call to find a definate answer.
if you cannot use it,at least you have made yourself a working,useable,sellable phone hopefully you can sell it quickly and pick up one you can use.
i had the same prollem with vzw,and ended up doing the same thing(selling the all tell merge and picking up a vzw model)
have you spoken to us cellular? if not it would be worth a 5 minute phone call to find a definate answer.
if you cannot use it,at least you have made yourself a working,useable,sellable phone hopefully you can sell it quickly and pick up one you can use.
i had the same prollem with vzw,and ended up doing the same thing(selling the all tell merge and picking up a vzw model)
Yes, actually, I took it in to try to activate it, and their techs are the ones who discovered that it could not be activated on their network because it was from another provider. I just googled the prl and thought because of that it was a Sprint phone. I got this phone for $40, so I really want to find another one, US Cellular, on the cheap with a clean ESN and just swap the board. But also, I am eligible for an upgrade, and the rep at the store told me that the GS3 is $199, and will probably drop to $149 over the holidays, so I'm keeping that in mind, too. The Electrify 2 may drop to $99.
The Following User Says Thank You to jasonofx For This Useful Post:
well,you are not on a sprint OS. your build number is from nTelos,bluegrass wireless,or possibly some other small carrier using sprint or vzw towers. your hboot screen displays the merge codename "lexikon" and the correct merge hboot version.
to answer your original question,rooting the phone via this guide or any method will not let you use it on a cdma network that it was not intended to. while the sim slot will be unlocked,there have been issues even using the merge on different gsm networks.
cdma carriers tend to be picky about the devices they allow on their network,so your question can really only be answered by USC. cdma flashing and cloning is potentially illegal and/or fradulent,and not something we are permited to discuss here.
using the guide will turn off the radio secure flag,unlock the sim slot,and give the phone superCID wich will allow you to flash other carriers RUUs,install a custom recovery,and give you the ability to modify system files that you normally will not have access to. if you wish to root,we will be happy to help you
Anyway I can find out exactly which carrier it is so I can sell it? I don't wanna go through any hub-bub on eBay with it, so I want to confidently advertise it correctly to avoid that.
On another note, I was able to pick up the Motorola Electrify M on the day it came out for only $99!!!!!!!! Pimp-ass phone, everbody check it out. I like that it has a large screen and smaller form factor than the GS3.
other than making some phone calls to various carriers and asking if the MEID/ESN are activatable,im not real sure.if the phone has not been modified yet,you could find the CID,wich would give a pretty strong clue.
-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.
again,for those reading this,dont flash it! we dont know why its killed a couple of phones.
jianC,feel free to pm me if you find anything interesting in this rom,or have any theories. also if you have trouble downloading the ruu,i do have it saved so i can upload it somewhere if you need it
Please help me. I've bought HTC merge that had some chinese firmware installed. It was unlocked for all cdma & gsm. I wanted to S-off & root it. Hence I downloaded above files & followed ur instructions.
Initially I placed renamed & placed "PD42IMG-vzw-leak.zip" but got stuck at :
# dd if=/dev/block/mmcblk0p17 of=/sdcard/misc-stock.img bs=4096
I got error : Access Denied.
Then I replaced the zip file with "PD42IMG_customGBupgrade" & renamed it as "PD42IMG.zip", rebooted & updated.
This time I proceeded much further. But now I got stuck at:
$ /data/local/psneuter
Failed to set prot mask (Inappropriate ioctl for device)
Please help me to S-Off, root, & unlock it. I've downloaded all necessary files (I guess)
Thanks
Last edited by krishna009; March 23rd, 2013 at 03:06 PM.
Reason: Changing Code tags
I would pretty strongly recomend that you do not mess with the Chinese firmware. I know of a couple phones that have been bricked trying to change from it,back to US firmware. We just do not know enuff about it to do it safely. If you flash the downgrade vzw firmware,it may leave you with an unusable(i.e. hard bricked and unrecoverable) phone.
Having said that,your first error may have been lack of an sd card(not present or mounted to the pc.as a disk drive).
Your second error is because you are not on the downgrade vzw firmware,so the psneuter exploit does not work. Neither of these errors have anything to do with the particular PD42IMG file you have on your sd card.
Where did you get this phone running Chinese firmware,and what is the info on its hboot screen?
I would pretty strongly recomend that you do not mess with the Chinese firmware. I know of a couple phones that have been bricked trying to change from it,back to US firmware. We just do not know enuff about it to do it safely. If you flash the downgrade vzw firmware,it may leave you with an unusable(i.e. hard bricked and unrecoverable) phone.
Having said that,your first error may have been lack of an sd card(not present or mounted to the pc.as a disk drive).
Your second error is because you are not on the downgrade vzw firmware,so the psneuter exploit does not work. Neither of these errors have anything to do with the particular PD42IMG file you have on your sd card.
Where did you get this phone running Chinese firmware,and what is the info on its hboot screen?
In fact, I've already messed with it. When I booted using "PD42IMG-vzw-leak.zip" my phone showed "Verizon" splash. In that mode I checked & was able to get calls but I couldn't call (I am in India).
Then When I booted using "PD42IMG_customGBupgrade.zip" my phone showed "US Cellular" splash. Now its working fine (donno how) I get calls, I can make calls. Everything is perfect! All cards (carriers) cdma & gsm networks work fine.
I bought it on ebay, initially when I bought it did not show any particular splash screen except htc. But in menu there were many chinese apps installed.
I guess now the chinese firmware has gone off from my mobile & now it has become US Cellular specific, since I already mentioned that splash shows 'US Cellular' & (God knows how) it is working perfect fine on all n/w. I successfully tested it on GSM Virgin & currently using successfully on Tata-cdma.
I know this is a lot of info, but I just wanted to make it clear.
Now can you please guide me to S-off, root, & unlock it (I guess its already unlocked as I can use any sim)
Now can you please guide me to S-off, root, & unlock it (I guess its already unlocked as I can use any sim)
Thanks!
someone has beat you to the punch(or you got a rare one that came that way):
Quote:
Originally Posted by krishna009
My hboot screen shows this:
LEXIKON XB SHIP S-OFF <--you are s off
HBOOT-0.88.0000
RADIO-1.08.00.0804
eMMC-boot
Dec 2 2010, 16:07:41
you are allready are s off. you are likely allready superCIDed as well,as you wouldnt have been able to install the vzw leak and custom BG upgrade otherwise. in short- you have no use for this guide
Quote:
Originally Posted by krishna009
In fact, I've already messed with it. When I booted using "PD42IMG-vzw-leak.zip" my phone showed "Verizon" splash. In that mode I checked & was able to get calls but I couldn't call (I am in India).
Then When I booted using "PD42IMG_customGBupgrade.zip" my phone showed "US Cellular" splash. Now its working fine (donno how) I get calls, I can make calls. Everything is perfect! All cards (carriers) cdma & gsm networks work fine.
im glad this had a good outcome for you. likely it worked since you used the full,signed vzw leak. if you had used the custom upgrade first,it may not have worked this way. i personally have flashed the "confidential" chinese firmware,and then run a .exe ruu to get back. i personally killed that same merge flashing an unsigned hboot trying to get a recovery installed. there haVE been other cases where folks tried to flash a custom(unsigned) ruu and ended up with a dead phone. as i said,we just dont know much about what hooks the firmware has.
to further compicate things there are XB,XC,and i believe CT merges:
and we have no idea how that changes things,either. this is a neat little phone,but unfortunately they were never real popular in the root comunity.
so lets review:
-you are allready s-off.
-you can flash any ruu that you wish,so you likely are superCID as well.
-you are allready sim unlocked.
-if you are allready on a custom upgrade ruu you should have a custom recovery,you just need to flash root files if thats not a pre-rooted ruu.
if youre not on the software you want to run,you just need to run the ruu that you choose,if its a factory ruu you can install amon recovery as a PD42IMG,then flash root files.
alternately,you can try flashing some custom roms(if you can find some)
one last bit of advice,you are no longer on the chinese test rom,and id recomend not going back to it
what were your goals for becoming s off? you can achieve them now
Its good to here that my cell is already S-off & unlocked, however; I don't think its rooted. I think one of the best way to check if the mobile is root is to type 'su' & check the response. Well when I tried this I got "Access denied" error
I also tried to check with one of the app "check root" The result was same, even that app said that busybox has not been installed.
What does this mean? I guess still my mobile is not rooted?
no,you are still not rooted. as i said above,you can install amon recovery as a PD42IMG file if you havent run a custom upgrade ruu(if you have,then you have a recovery allready)
once you have recovery,its a simple matter if flashing root files. you can flash the eng merge toolkit linked in the first page,but some folks have had prollems with it on GB.
you must flash the zipfile from recovery. you cant simply install it from the market,wich is a common error after reading that post. the download link you want is about halfway down the page and labled UPDATE-SuperSU-v1.25.zip
i dont want to put up a direct link,as when he updates it the link breaks,leaving folks looking for it in the future out of luck.
so to recap:
-check if you have amon recovery installed. if not download and install it as a PD42IMG file in hboot
-download supersu
-flash supersu in amon recovery
I got HTC Merge about a year or more ago (US Cellular). I'm using it in Europe (GSM). After changing couple of SIM cards from different carriers the phone started to restart while SIM card is inserted. It operates normally when there is no SIM card present. I was a bit disappointed and went on and bought another phone since HTC service in Europe refused to take in into the shop it since it's US model.
Alternately missing the hardware keyboard and all i order a replacement SIM/SD Card reader part from ebay (thinking it's a parts fault). Unfortunate it wasn't. The same thing happens with the new part. Could this be a software issue?
are you still using the us cellular rom? have you checked the mobile networks settigns and made sure youre on a gsm or global setting?
if there is not a menu setting,you can try getting to phone info from the dialer by dialing *#*#4636#*#* try switching to wcdma,or gsm only depending on what your carrier uses
The Following User Says Thank You to scotty85 For This Useful Post:
are you still using the us cellular rom? have you checked the mobile networks settigns and made sure youre on a gsm or global setting?
if there is not a menu setting,you can try getting to phone info from the dialer by dialing *#*#4636#*#* try switching to wcdma,or gsm only depending on what your carrier uses
I'm still on US Cellular stock ROM 3.20 / Android 2.3.4.
*#*#4636#*#* to GSM only does the trick. The phone doesn't restart but new issue emerges. Mobile internet stuck in EDGE mode. No UMTS or HSDPA/HSUPA (which is available)
*#*#4636#*#* to any other option and the random restarting (within minutes from power on) is back again
This is a huge improvement but EDGE is annoying as hell. Any thoughts?
Can anyone try switching to GSM only to check out is this a case or it's just my phone?
Thanks!
Last edited by Nicholas091; April 5th, 2013 at 04:36 PM.
Reason: Better explanation
The Following User Says Thank You to Nicholas091 For This Useful Post:
sorry,i just realized you had edited your post above and it was different than the last time id seen it glad switching to gsm only did the trick,but as for data im not really sure what we may need to do there. do you know what bands your carrier is using?
if your carrier is sending out 3g/hspa+ on those bands,it may need some changes in the rom somehow,since its designed to be used on a cdma network and only "roam" overseas while a us cellular customer is on vacation... i honestly have no idea where me may need to look or make changes.
i can try swapping my settings around later and see if anything casues reboots. i use it on us t mobile,so all i get on it is edge data,no matter what,unfortunately.
Are you s off /supercid? You might try one of the other ruus.possibly even just rerun the USC ruu.
If its a software issue that's changed after you recieved the phone,a combination of ruu and factory reset with the stock recovery still in place may do the trick
The Following User Says Thank You to scotty85 For This Useful Post:
C:\miniadb_merge>adb push misc-downgrade.img /sdcard/
1638 KB/s (0 bytes in 262144.000s)
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
512+0 records in
512+0 records out
262144 bytes transferred in 0.096 secs (2730666 bytes/sec)
# sync
sync
# exit
exit
C:\miniadb_merge>adb reboot bootloader
C:\miniadb_merge>
then ithis shows up
PHP Code:
HBOOT
[1] parsing ... [SD ZIP] ok
[2] boot ok
[3] recovery ok
[4] system ok
[5] splash1 ok
[6] partition ok
[7] user data ok
[8] tp ok
[9] tp ok
after this i just keep on going to the next step I was intrigued
Quote:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\adalidh>cd c:\miniadb_merge
C:\miniadb_merge>adb push psneuter /data/local/
adb server is out of date. killing...
* daemon started successfully *
1743 KB/s (0 bytes in 585731.000s)
C:\miniadb_merge>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT17VM800243 device
C:\miniadb_merge>adb push psneuter /data/local/
1926 KB/s (0 bytes in 585731.000s)
C:\miniadb_merge>adb push busybox /data/local/
1581 KB/s (0 bytes in 1062992.000s)
C:\miniadb_merge>adb push wpthis /data/local/
1846 KB/s (0 bytes in 679475.000s)
C:\miniadb_merge>adb push gfree /data/local/
1947 KB/s (0 bytes in 716548.000s)
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
$ adb shell
adb shell
adb: permission denied
$ /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... Failed.
Module returned an unknown code (Operation not permitted).
$ /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... Failed.
Module returned an unknown code (Operation not permitted).
$ exit
exit
then i follow the instructions step by step
and thanks to you guys now im soff supercid and all tah
i must say that is not easy but is possible to do it at one shot
9Likes
.apks are simply transfered and installed with a root file manager like root explorer.
)
