wow that is wierd ive never used it on the merge without s-off,nor have i used it with anything other than amon recovery(wich i wouldnt think would matter,but maybe it does?) so ive never experienced that.
might try switching to amon and see if that issue still persists
there are some "quirks" with the eris htcdev hboot as well,they released alot of bootloaders for alot of devices in a relatively short time,so unfortunately its not surprising to find some quirks in some.
__________________
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
I finally have success and am now making a nandroid backup Steps I took
1. unlock bootloader again
2. reboot into bootloader via fastboot
3. bot into CWM recovery via fastboot
3. INstalled fiizion rom etc...
4. Reboot and BINGO kernel changed and wifi working
5. Bootloader is locked again but can relock now that I am a pro at it
The Following User Says Thank You to stevgunt For This Useful Post:
Now If I could just get the 2fast OC Kernel to flash right I would have something but no luck so far, each time I try and flash it using any recovery it just locks the bootloader back and does not flash and all I have is the .zip of the kernel not the actual boot.img of the kernel. Any Ideas?
Now If I could just get the 2fast OC Kernel to flash right I would have something but no luck so far, each time I try and flash it using any recovery it just locks the bootloader back and does not flash and all I have is the .zip of the kernel not the actual boot.img of the kernel. Any Ideas?
welcoms to htcdev
my best idea would be s-off
failing that,you can just flash it in fastboot as i described above. rumage thru your 2 fast kernel zip file and find the boot.img put it into your adb/fastboot folder,put your phone in fastboot mode,and:
fastboot flash boot <bootimagename>.img
before you do it,id prolly hook your phone to your PC,and move a stock nandroid from phone to PC,so you can rumage thru it,and find a stock boot image(kernel) to flash just in case your phone doesnt care for the new kernel.
might want to set up folders for various roms and backups,and their associated kernels,and possibly rename the boot.img to something a little more specific(boot-stock.img,boot-2fast.img,etc)
while i can manipulate it to flash roms,backups,etc., i hate htcdev on my rezound. id give my left you-know-what for a true s-off exploit
K for anyone with mms issues after flashing, here is what worked for me. Flash a copy of the stock ruu, go under messages, settings, look at the connection information, as long as your mms works with the stock image, you know these settings are correct. Download an apn back up app. Back up your apn info to sd. Now flash the image you wish to use, download the apn backup app again, tell it to delete the settings, THEN restore the settings from your sd. If you try to restore before deleting, it will not overwrite for whatever reason. Hope this is understandable and helpful for others!
The Following User Says Thank You to korrdite For This Useful Post:
Yea NP Scotty thanks for you help to begin with. When i was at the store they ran the stock GB RUU.exe file as I watched them do it. It flashed everything back to stock supposedly but the 3g still did not work. I do however have a flashable .zip file i used on my Hero and Desire that changed all the carrier settings and I think APN stuff too I never did try that but anyways....I will try the super tool, All I want is root so I can use free Tether
for what its worth,i just flashed your upgrade nTelos RUU on my new-to-me vzw merge,and data is working fine,cell south radios and all.
this is a nice rom,for those that want GB. we now have a couple choices with this and usc
hmm what else was i gonna check into when i got a working phone?
hmm what else was i gonna check into when i got a working phone?
getting the rom to look like a VZW phone instead of USCC Phone? i kid i kid, i'm actually running the fuzion ruu, posted by 2fast, runs great, seems battery life is slightly improved versus this one at least for me. i need to learn some development techniques so i can start contributing though.
Last edited by korrdite; April 3rd, 2012 at 07:03 PM.
Naw, fuzion doesn't use the USC boot animation so I didn't bother, I however would prefer for the phone to be recognized as a proper VZW device. But it's not a huge concern
HI. Could you possibly re-upload the leaked VZW ruu? The only two links I've been able to find to it anywhere have been to megaupload(and we know what happened there) and WUploads, which won't let anyone that doesn't have the uploader's username and password get anything. Thanks in advance.Thanks so much for posting this guide. I've been trying to find a decent guide that is "beginner friendly".
Thank you so much
I've been able to get everything else you listed in the tutorial on the first page, it was just the vzw leaked ruu that I was unable to acquire. But just to be sure I have it right, the zip file containing the factory ruu (for a Us Cellular HTC Merge running 2.3.4) is UsCellular 3.10.573.1.zip, right?
hi Scotty. i have sat here basically for 8 hours with this us cellular htc merge. ive tried flashing the vzw leaked exploit ruu after renaming it to the name specified. i followed all the steps. when it came down to flashing the exploit it keeps telling me.. CID Incorrect flash failed. is there any way to fix this? please help
so how do i make it effectively... for some odd reason, if i do the adb way of doing it the commends dont work but if i do the gold card helper it does work. so im thinking somehow im doing it wrong? is it possible you can hit me up on gtalk? night.fury.wolf@gmail.com
so how do i make it effectively... for some odd reason, if i do the adb way of doing it the commends dont work but if i do the gold card helper it does work. so im thinking somehow im doing it wrong? is it possible you can hit me up on gtalk? night.fury.wolf@gmail.com
sorry for the delayed reply.did you get your gold card working?
Ihad to use the below method because the other way would not give me temp root. Guess my version is to high. I get through all of this with temp root # as you described. I then finish as you described to pick up on the page 1 topic. I have tried 4 sdcards making four different gold cards and I still get the wrong cid or whatever it is. I am at a loss on what to do. I even tried the HTC Unlock method but it says I do not have the right firmware or updated enough but it is... Please tell me what to do. If you can contact me i will be more than happy to hook up on teamviewer so you can watch or try it yourself. Please help I need to unlock it so I can use it with T-Mobile or I am out of some money ....
Thanks,
Viper
Quote:
Originally Posted by scotty85
unofrtunately,that means that the exploits have been patched,and zergRush is unable to obtain temporary root. im assuming that youre on usc GB,and that there has been some sort of OTA to it.
there are a couple different possibilities:
1)check your build number. you may be able to roll back to the latest official version if what youre on was a minor OTA,despite an s-on hboot. 3.10.573.1 was the first usc GB update,and i believe there was one after it that zergrush still worked on. not sure how many more could been between that and what youre on.
check Shipped ROMs and general google searching to try and track down an RUU if you want to try this route
2) use fre3vo for temp root
3) unlock using htcdev tools and gain permanent root to do the downgrade. i *think* that would work,but you would be on uncharted territory,and there is good possiblity youd be stuck for all eternity with htcdev unlocked/s-on with no chance to downgrade,so that would be my personal last choice.
4)maybe jcase's taco root
fre3vo worked on the latest thunderbolt update,so id say theres a good change it would here too,and this would be my first choice.
heres what you do:
-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.
Ihad to use the below method because the other way would not give me temp root. Guess my version is to high. I get through all of this with temp root # as you described. I then finish as you described to pick up on the page 1 topic. I have tried 4 sdcards making four different gold cards and I still get the wrong cid or whatever it is. I am at a loss on what to do. I even tried the HTC Unlock method but it says I do not have the right firmware or updated enough but it is... Please tell me what to do. If you can contact me i will be more than happy to hook up on teamviewer so you can watch or try it yourself. Please help I need to unlock it so I can use it with T-Mobile or I am out of some money ....
Thanks,
Viper
for what its worth,your almost there you dont need htcdev unlock,not so you need any other temp root methods. all you need to do is perfect your goldcard,as thats the only way around the CID error,unless you start with a vzw merge in the first place
once you get a working gold card,you just need to redo what youve allready done: run fre3vo,run the adb commands to downgrade. once youre on the old vzw firmware,gfree will s-off,supercid,and simunlock.
here are the goldcard directions:
Next we need to create a goldcard by doing the following:
Copy all of the data on your microSD card to a backup location on your PC
Format the microSD to FAT32 format
Open a command prompt one again and type the following:
cd [then press Enter]
cd AndroidSDKtools [then press Enter]
adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid [then press Enter]
You should get a long number something along the lines of 532600bd227d9c0347329407514d5420
Goto this page and copy the number in the above step into the box and hit Submit, you’ll then be given another long number
Go to this page and enter this new number into the SD Card Serial (CID) field
Enter the other details and hit Generate Goldcard
Check your email and save the attached goldcard image file to your pc, I usually save it to the desktop as you’ll be needing it shortly
Download HxD Hex Editor from here and install
Open HxD Hex Editor. If you are using Windows Vista or Windows 7, you must run the application as administrator
Go to the Extra menu and select Open Disk. Under physical disk, select Removable Disk (your microSD card), uncheck Open as Read-only and click OK. Note that you should select physical disk NOT the logical disk
Go to the Extra menu again and select Open Disk Image. Open the goldcard image that you received by email and saved above
You should now have two tabs; one is your removable disk and the other is your goldcard image. Press OK when prompted for Sector Size (selecting 512 (Hard disks/Floppy disks)) and click OK
Click on the goldcard image tab. Go to the Edit menu, choose Select All then select the Edit menu again and select Copy
Click on the Removable Disk tab. Highlight offset (line) 00000000 to offset (line) 00000170 (including the 00000170 line), then click on the Edit menu and select Paste Write
Click on the File menu and select Save, accepting the warning
You now have a goldcard
just do each step carefully,using the number from the gold card helper app. make sure you use the app to read mmc2. do not try and make the gold card while its in the phone,youll need to put it into a card reader. open the reccomended hex editor,and carefully fillow the steps to copy the gold card image to the sd card.
i successfully made a gold card and used to to downgrade an alltel merge,but havent needed it since,so im far from an expert on making them
if you are really fustrated,you are welcome to mail me an sd card and ill make one and send it back.heck,you can send me the whole phone if you want to
Thanks finally got it, had to use 5 different gold cards before one would work.....
Anyways I have a few more questions....
1. I am wanting to use this phone with a sim card, do you know which RUU will allow that? I think I need the Verizon Radio? Does anyone have a link? 2fastRoms is down so cannot get it from there.....
2. If I update RUU now, I want lose root, or will I?
3. Or if I wanted to use this on Page Plus, would it be better to use a verizon RUU?
Thanks for your help.....
Mark
Last edited by Viper32; May 31st, 2012 at 04:59 PM.
Thanks finally got it, had to use 5 different gold cards before one would work.....
Anyways I have a few more questions....
1. I am wanting to use this phone with a sim card, do you know which RUU will allow that? I think I need the Verizon Radio? Does anyone have a link? 2fastRoms is down so cannot get it from there.....
i do not know for sure. if you go back a few pages in this thread,i believe someone left a link to a specific vzw radio that you need to use. i actually didnt have much luck when i played around with it.the only rom i got to work with voice,text,and edge data was one of the asian test roms,but im not sure id reccomend that one. ill try and play with it some tomoro or over the weekend
2. If I update RUU now, I want lose root, or will I?
if you run a full ruu it will overwrite your custom recovery,and replace your rooted /system with one that isnt. its not a big deal,as if youve completed the process and are s-off,you can easily re-install a custom recovery and flash superuser to get root back. the important thing is to be s-off.
3. Or if I wanted to use this on Page Plus, would it be better to use a verizon RUU?
i honestly have no idea. i believe the vzw ruus are more likely to prevent the gsm part of the phone from working. i would prolly go with one of the GB ruus(ussc or nTelos)
Name: T-Mobile Data (or T-Mobile US) APN: epc.tmobile.com Proxy: <Not set> Port: <Not set> Username: None
Note: For the Username, enter "None" with the keypad. Do not leave it not set. Password: <Not set> Server: <Not set> MMSC:http://mms.msg.eng.t-mobile.com/mms/wapenc MMS proxy: <Not set> MMS port: <Not set> MMS protocol: WAP 2.0 MCC: 310 MNC: 260 Authentication type: <Not set> APN type: default,supl,admin,dun,mms
Press the Menu key.
Touch Save.
saved it,exited back to the home screen,lo and behold,edge data mms appears to be working as well.
enter the new APN info at: menu softkey/settings/wireless & networks/mobile networks/GSM/UMTS options/acess point names
its had to remember exactly what id tried when messing with this before,but i know for sure its working with nTelos 3.08.557.1 and the above APN. if i have a chance ill try and verify it on some other ruus as well. hope it helps
Last edited by scotty85; May 31st, 2012 at 10:05 PM.
Name: T-Mobile Data (or T-Mobile US) APN: epc.tmobile.com Proxy: <Not set> Port: <Not set> Username: None
Note: For the Username, enter "None" with the keypad. Do not leave it not set. Password: <Not set> Server: <Not set> MMSC:http://mms.msg.eng.t-mobile.com/mms/wapenc MMS proxy: <Not set> MMS port: <Not set> MMS protocol: WAP 2.0 MCC: 310 MNC: 260 Authentication type: <Not set> APN type: default,supl,admin,dun,mms
Press the Menu key.
Touch Save.
saved it,exited back to the home screen,lo and behold,edge data mms appears to be working as well.
enter the new APN info at: menu softkey/settings/wireless & networks/mobile networks/GSM/UMTS options/acess point names
its had to remember exactly what id tried when messing with this before,but i know for sure its working with nTelos 3.08.557.1 and the above APN. if i have a chance ill try and verify it on some other ruus as well. hope it helps
I am trying to download it but download link seems to be broken...........
I am trying to download it but download link seems to be broken...........
Viper
working fine for me. some folks have had to use different browsers with android file host,for some reason... not sure if its a firewall or anti-virus issue
working fine for me. some folks have had to use different browsers with android file host,for some reason... not sure if its a firewall or anti-virus issue
I tried the one you referred to but still not go No signal......... Does not work on mine... I tried a T-Mobile sim and a Family Mobile one...... Any other suggestions?
did you change to gsm? guess i did leave that step out
dial *#*#4636#*#* and you should get a programming menu. choose phone info and then change the prefered network type to GSM auto(PRL). i usually refresh the smsc,but idk if thats needed. back out to your home screen and at that point you shuld get some singnal bars,and working voice/sms. then enter the APN info and you should have working edge and mms
is this the rom youve tried the sim cards on? did you try the nTelos one as well? from this info,youre on a different baseband,and your main version number matches tht of the usc upgrade ruu.
if you havent tried the above on the nTelos ruu yet,flash that one and see if it works
i will try and flash the usc one and see if i have any different luck.
when it booted,it switched to gsm mode. i put it in gsm auto(prl) and a minute or so later i had signal bars. i flashed superuser,and when it rebooted,i had edge,without doing anything
same deal,upon boot,it detected a sim card,switched to global mode. went to programming menu,changed to gsm auto(prl) and voila,signal bars and working voice. installed superuser and rebooted to working edge data.
a couple other things you can check:
settings/security
-check "set up sim card lock" and make sure theres no checkmark
-check "disable simlock" and you get a message "SIM lock is disabled"
also maybe kind of long shot,but are you sure your sim is inserted correctly/ and fully?
i havent done anything special to mine,the only difference that i can think of is that it started life as a vzw merge,not usc or alltel.
Last edited by scotty85; June 1st, 2012 at 07:26 PM.
when it booted,it switched to gsm mode. i put it in gsm auto(prl) and a minute or so later i had signal bars. i flashed superuser,and when it rebooted,i had edge,without doing anything
same deal,upon boot,it detected a sim card,switched to global mode. went to programming menu,changed to gsm auto(prl) and voila,signal bars and working voice. installed superuser and rebooted to working edge data.
a couple other things you can check:
settings/security
-check "set up sim card lock" and make sure theres no checkmark
-check "disable simlock" and you get a message "SIM lock is disabled"
also maybe kind of long shot,but are you sure your sim is inserted correctly/ and fully?
i havent done anything special to mine,the only difference that i can think of is that it started life as a vzw merge,not usc or alltel.
Yeah sim is in right, I am flashing NTelos RUU again now, I had been trying all of them,lol..... I do not know maybe because this is USC one something is different......
Viper
I will post update here in few minutes, just got power back on............
hmm. i am at a loss. i dont know why your lock screen isnt changing. maybe you could try running the vzw current firmware .exe and then try the ntelos rom again.
download,run as administrator if your version of windows permits that,then follow the onscreen directions.
after it flashes,maybe check and see if you have gsm signal,and if not try the ntelos rom again.
failing that,you could try this one:
*link removed*
but be careful with it,i was messing with it when i bricked my last merge(prolly a coincidence? ) so dont try and root it,or modify it in anyway,just play with it for a bit and then flash back to something else. if your sim doesnt work with this rom,then i dont think its going to my last merge this is the only one i could get to work.
heck,maybe running that one,then a different one will make it work like its sposed to
Last edited by scotty85; June 4th, 2012 at 05:37 AM.
Thanks, I am downloading the Verizon one now..... I will try it first.....
May I ask why such the warnings on the other one? Is it a custom RUU or something? Whats its Origin......
Also sorry to mention 2fastRoms stuff after doing allot of searching I see you and him do not see eye to eye from what I can tell from some other forums......
That's his loss you have been a great help.... Not that I am new to flashing and all that stuff as I have been doing so since the G1 but the adb commands stuff I need to work on......
I mean my own personal phones are a HTC Rezound and a Thunderbolt (Both S-Off,rooted and custom modded)
Thanks, I am downloading the Verizon one now..... I will try it first.....
May I ask why such the warnings on the other one? Is it a custom RUU or something? Whats its Origin......
its just some sort of asian test rom. as long as you leave it intact,it should be perfectly safe, ive flashed it and messed with it a few times. you cant really run it,since it doesnt have the google play store. last time i messed with it,i was trying to root it so i could try and add the play store,since it was the only thing that my previous merge would have working voice and data on with my t mobile sim(it was also a vzw model,curiously),and after some unsuccessfult attemts at flashing recovery as a PD42IMG type file,i tried to flash an allrady unlocked htcdev hboot,wich i had flashed before with no issues. installed fine,and when i hit enter after typing adb reboot-bootloader it made a short buzz,and then turned off,and hasnt come on again since
i cant say for sure that the radio had some sort of issued with the htcdev unlocked hboot,or if the file had become corrupt,or if it was some sort of wierd,remarkable coincidence of hardware failure. so the reason for the warnings,id hate to see something similar happen if you tried to install a recovery and flash root files.
it is neat to play with it and see how it looks, so dont be to afraid of flashing it,just leave it intact,dont try and flash any different radios,hboots or recoveries sorry if i sounded wierd or mysterious about it,lol.
Quote:
Originally Posted by Viper32
Also sorry to mention 2fastRoms stuff after doing allot of searching I see you and him do not see eye to eye from what I can tell from some other forums......
thats putting it nicely,lol... we had finally started being civil on xda,but yes we do have a "history" it takes alot to rub me the wrong way,but hes good at it. i was actually going to recomend his gold card guide when you were having trouble,but when i went to get the link,i noticed as well the site was gone.
maybe i should delete the other thread since all the links are broken. i move all that to a seperate thread after he showed up with it on this thread,after some words were exchanged on rootz.
Quote:
Originally Posted by Viper32
I mean my own personal phones are a HTC Rezound and a Thunderbolt (Both S-Off,rooted and custom modded)
ive had the thunderbolt since release day,and currently use a rezound daily. im kind of itching to fire the bolt up for a bit,but im pretty fixated on ICS at the moment,so i keep using the rezound or a sensation. i wish the poor old TB would get some leaks,or working AOSP RIL soon. ive got a fair amount of stuff in both forums here,and some on xda.
Last edited by scotty85; June 2nd, 2012 at 04:07 PM.
The Following User Says Thank You to scotty85 For This Useful Post:
Thanks for all your help.... You have been great......
This phone just will not work with Sim Card... I have tried everything you have suggested and many other things but just not going to happen.....
Anyways I am going to step away from it for a few days, then maybe revisit.
In the meantime I picked up a flawless INC1 phone for my son for $5.00... Yes there is a catch..... It is stuck on white boot screen.....
You got any suggestions on what i could do for it, heck I am only out $5.00 if it is hosed.....
I know this is the wrong section for the Inc1 but you have been a true champ at helping me with the Merge.....
If I need to post somewhere else let me know and maybe we can continue the help with it there without cluttering this one....
Send me PM if you want to chat one on one about it.... I have teamviewer which is a great software if you want to hook up so you can see whats happening during testing.....
I finally tried the chinese RUU, the sim card works with it. Not sure where to go from here though. I do not think this is the complete answer as it has some strange stuff on it and no Market, lol....
I finally tried the chinese RUU, the sim card works with it. Not sure where to go from here though. I do not think this is the complete answer as it has some strange stuff on it and no Market, lol....
Got any other ideas?
Viper
awsome! i figured it would work with that one we could try and figure out a way to install the market,but before doing that,i think you should try and install apn backup and restore,and backup the APNs. then restore one of the other ruus,put it in gsm auto(prl) and delete the apns,then restore the apns. if things dont start working in a few minutes,try a reboot.
also answered your inc thread... unfortuantely i think its toast