Here is what I did:
Months ago trying to install ICS (VM leak) went to s-off on my Sprint EVO 3D y changed my CID to super CID (111111) then thinking that the original CID of the phone was HTC__001 (following an EVO 3D GSM tutorial) changed it and went back to S-ON and stock but with the wrong CID (HTC__001) then when y tried to use my phone and update it to Sprint ICS but the phone won't even load the OS, it shows the screen where I can see my HBOOT by the way is 1.5 and go to fastboot but it says security warning etc... I do can install CWM and 4ext that means I can lock and relock fastboot oem then I tried to install several roms stock inculded but still doesn't boot to the OS even I tried to install stock RUU zip and EXE but since I'm with wrong CID the phone displays Wrong CID I don't know if installing a RUU for the CID HTC__001 makes sense but anyway when I try to install it says signature fail and since installing the RUU for Bricking or corrupting the HBOOT is imposible, I can't get in to QHSUSB_DLOAD to try any method like HTC Unbricking Project, Ultimate Recovery Tool 2.3 RC1, HBOOT Downgrade Toolkit Live CD or Juopunutbear S-OFF......
So achieving S-OFF it's imposible for my or I'm missing any other method for S-OFF and go back to the SPCS_001 CID? or there is another way to change the CID on S-ON considering that fastboot oem writecid fails on S-ON I even tried modifying the mmcblk0p4 file with an hex editor and it failed
Another way would be using a RUU with the android-info file changed to accept my HTC__001 CID even my hardware is CDMA (shooter) but signed for S-ON
Or another way is somehow corrupting the HBOOT without installing a RUU
So being S-ON with the wrong CID (HTC__001) with warning security and HBOOT 1.5 and no ROM can boot I think my phone is really death
Is there something missing I can do to make it work again or I have a really expensive brick??
anyone help??? please
Deleted
Wikd said:
Deleted
Click to expand...
Click to collapse
didn't worked for me, I don't have the exact error that shows, I'm not at home now trying to post you the error later....
any other ideas?? another method for s-off or maybe change the CID
i s-off`ed my evo 3d gsm useing JuopunutBear and i dident install the custem hboot but i did downgrade from 1.53.0007 to 1.49.0007
and i whant to get superCID but every time i triy to do it it sys my cid is 0202 and thats dont what i had before its saposted to be 11111111
PLEASE HELP THAX:crying:
(sorry for my bad spelling)
surferdude900 said:
i s-off`ed my evo 3d gsm useing JuopunutBear and i dident install the custem hboot but i did downgrade from 1.53.0007 to 1.49.0007
and i whant to get superCID but every time i triy to do it it sys my cid is 0202 and thats dont what i had before its saposted to be 11111111
PLEASE HELP THAX:crying:
(sorry for my bad spelling)
Click to expand...
Click to collapse
Fastboot oem writecid HTC__001
It should get you what you need
dessolator666 said:
Fastboot oem writecid HTC__001
It should get you what you need
Click to expand...
Click to collapse
it still doesent work it still sys my cid is 0202 is even rebooted the booyloader after rewriteing the cid
my phone is a rogers evo 3d if thats whats stoping or something like that
PLEASES HELP THAX
I bricked my Desire X, I think I tried to unroot by, pushing "recovery_signed.img" & "Relocking" the Bootloader and then I opened RUU & it says 'ERRROR{155}. Now when I "Turn ON" the device it directly goes into bootloader & no response at all. What should i do now to get device loaded with Stock ROM??
Since you're from Dubai you won't be able to use available ruus cause they are made for Eastern Europe.
Just unlock bootloader, flash custom recovery and flash Hasoon's on Infernal's stock rom.
s:
sorry to hear that i got bricked and i cant even go in recovery
devilcummer said:
sorry to hear that i got bricked and i cant even go in recovery
Click to expand...
Click to collapse
You're not bricked, use fastboot...
Sent from my HTC Desire X using Tapatalk 2
I had done it once earlier succesfully!
nlooooo said:
Since you're from Dubai you won't be able to use available ruus cause they are made for Eastern Europe.
Just unlock bootloader, flash custom recovery and flash Hasoon's on Infernal's stock rom.
Click to expand...
Click to collapse
I had once unbricked succesfully through an RUU which got deleted accidently. Then I downloaded a new RUU which have this error. Can u help me?
What is written on top of your phone's bootloader, unlocked or relocked?
reply to nlooooo
nlooooo said:
What is written on top of your phone's bootloader, unlocked or relocked?
Click to expand...
Click to collapse
RELOCKED
*Security Warning*
May I extract the 'rom.zip' fom the current RUU and flash or whatever it is...
Just go to fastboot and run RUU, if that doesn't work try do download RUU again. And which RUU did you use earlier?
Go to fastboot, connect phone to PC, and run command
fastboot getvar cid
from command prompt, I assume you have adb installed.
reply to nlooooo
nlooooo said:
Just go to fastboot and run RUU, if that doesn't work try do download RUU again. And which RUU did you use earlier?
Go to fastboot, connect phone to PC, and run command
fastboot getvar cid
from command prompt, I assume you have adb installed.
Click to expand...
Click to collapse
Should I run the command from adb installed directory? May i know the use of that command?
Never mind, just run RUU from fastboot
Forget about using a RUU when you're from Dubai or another place that doesn't correspond to one of the CID's listed in the RUU thread.
Only option you have is to do what nloooo said in the first place (unlock bootloader, flash CWM and, once in CWM, adb push a 1.14 or 1.18 stock rom to sdcard so you can flash that in CWM) or by restoring a nandroid backup you made earlier.
First check the boot you have (says somewhere on the same screen where it says it's relocked) then either adb push the 1.14 or the 1.18 from the deodexed stock rom thread.
He said that he used ruu previously so he might have a compatible device. Or he had some other ruu but I don't know where he got it.
So, we need him to adb getvar cid so we can know what to tell him... Can he get USB mounted to push PM66IMG.zip?
Sent from my HTC Desire X using Tapatalk 2
I got CID!
Stereo8 said:
So, we need him to adb getvar cid so we can know what to tell him... Can he get USB mounted to push PM66IMG.zip?
Click to expand...
Click to collapse
it showed HTC__J15 .. What to do now?? Stereo8 can u check whether the zip file name 'PM66IMG.zip' correct? I got a vertical progress bar on the right of screen when I renamed it to 'PM66DIAG.zip'? Is it OK??
Did you try to download RUU again and to run it?
You said you got error 155 that's not CID mismatch, this is from RUU readme file:
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Click to expand...
Click to collapse
Are you sure you downloaded Desire X RUU?
EDIT:
The RUU that we have should be compatible with your phone, this is from android-info.txt frextracted from RUU:
modelid: PM6610000
cidnum: HTC__001
cidnum: HTC__E11
cidnum: HTC__203
cidnum: HTC__102
cidnum: HTC__405
cidnum: HTC__Y13
cidnum: HTC__M27
cidnum: HTC__J15
cidnum: HTC__032
cidnum: HTC__A07
cidnum: HTC__304
cidnum: HTC__016
mainver: 1.18.401.1
btype:1
aareport:1
hbootpreupdate:13
DelFat:1
DelCache:1
reply to nlooooo
nlooooo said:
Did you try to download RUU again and to run it?
Click to expand...
Click to collapse
I ran it again & still same stage! What about post no:14 nlooooo??
I told you that you have compatible device and forget about PM***.img.
Post me the version of RUU that you have.
@Sarun said:
I ran it again & still same stage! What about post no:14 nlooooo??
Click to expand...
Click to collapse
Clear cache, using fastboot flasher,
Reflash recovery usibg same app.
Then flash rom. It will work
Sent from my HTC Desire X using xda app-developers app
current condition
vipinlahoti said:
Clear cache, using fastboot flasher,
Reflash recovery usibg same app.
Then flash rom. It will work
Click to expand...
Click to collapse
The phone is boooting to android with 'UNLOCKED" status. But in the first bootscreen it shows something like this in red color "This build is for....." also I cant turn on the WiFi it's struck in 'Turning On.."
Guys what should i do further?
help me
nlooooo said:
I told you that you have compatible device and forget about PM***.img.
Click to expand...
Click to collapse
The phone is boooting to android with 'UNLOCKED" status. But in the first bootscreen it shows something like this in red color "This build is for....." also I cant turn on the WiFi it's struck in 'Turning On.."
Guys what should i do further?
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
s-on is required for unlocking bootloader, s-off will go to disclaimer screen but wont respond if yes is selected, it will only say ***unlock*** (which it must, but it wont be truly unlocked, your phone needs to respond when selecting yes and MUST restart, if you need to remove battery, it wont be unlocked.
***Problem***: now I had s-off and ***LOCKED*** so I ran fastboot oem writesecureflag 3 to get s-on, unlocked through htcdev and heres the big problem:
Now:
***UNLOCKED***
HBOOT 1.49.0007 S-ON (RH - i think)
Cant change CID, flash recovery, doesnt read PG86IMG files, cant flash anything through fastboot, cant run RUU because of error 132 (signature error).
After trying to change CID with:
fastboot oem writecid HTC__621
Result =
gave a few errors
cidnum = 0202 ...???
Have hboot 1.49.0007, can unlock relock bootloader, have functioning ICS rom
fastboot getvar all
< waiting for device >
INFOversion: 0.5
INFOversion-bootloader: 1.49.0007
INFOversion-baseband: N/A
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 1.20.401.2
INFOserialno: HT23NV200556
INFOimei: 352647050653635
INFOproduct: shooter_u
INFOplatform: HBOOT-8260
INFOmodelid: PG863****
INFOcidnum: HTC__621
INFObattery-status: good
INFObattery-voltage: 5785mV
INFOpartition-layout: Generic
INFOsecurity: on
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: edba812f
INFOhbootpreupdate: 11
INFOgencheckpt: 0
all: Done!
finished. total time: 0.510s
so please help... any1...
cybergurken said:
Hi, i think this problem may deserve a new thread, please forgive me if this has been solved somewhere else but nowhere have I found a problem like mine
On my journey ttrying to root and s-off and unlock, this is what i discovered:
fastboot oem writesecureflag 3 restores s-on
Click to expand...
Click to collapse
You should not have done that.
Also, if you are S-Off that is really all that matters. There is not really any reason to unlock the Bootloader. If you were S-Off and wanted to have an unlocked bootloader you should have just found a hboot like the revolutionary one or engineering and flashed PG86IMG.zip and that would have given you Unlocked and S-Off.
For the most part, you never want to do the fastboot oem writesecureflag 3.
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Thnx 4 responding
mnomaanw said:
When it does not respond to yes while unlocking and you have to pull the battery, it gets unlocked like it would when it responds to yes. Don't think what you assume is right, like you did. You should test it before making any assumption.
No offense, but friend from all your posts I think you are totally confused about all the stuff with hboots, unlocking, recovery, s-off/on.
EDIT : I see you edited it yourself.
Click to expand...
Click to collapse
Hi, no offence taken...
However, Im still a newbie @ all of this, however, I might be wrong but 3 q's
1. Why would it hang on the "yes" option
2. If I pull out baattery, it says ***unlocked*** but I have no access to recovery, even after custom recovery flash in fastboot, it cant/wont/doesnt boot into recvoery @ all, ref. "my other posts", why would that happen
3. What is the real difference between unlocking bootloader, and s-oof, I have read many posts and I figured getting both would be on the safe side...
and lastly, xd, why would a bootloader not read/detect a PG86IMG file, that is also another problem,
Once again, tnks very much
After turning S-OFF and gettin bootloader unlocked, everythings works perfectly. But know I have problem with cid. I can't change it when i type
Quote:
fastboot oem writecid HTC__001
nothing happens, and I still have cid: 0202. I can't install any firmware and RUU doesn't work. How to fix it, and make cid: HTC__001 again?