CID Bricked Shooter (CDMA) - HTC EVO 3D

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

Related

[Q] Wrong CID and S-OFF

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

[Q] Big problem is there anything I can do???

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:crying:

big problem

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???
really sorry to hear about your problem.
i think you might get some quicker replies tho if you were to post this in the Q&A section so people will know your asking for help.
best of luck in fixing your phone!

[Q] Evo 3D that hates me!!! ROOT s-OFF and unlock bootloader cant select yes

[Q] Evo 3D that hates me!!! ROOT s-OFF and unlock bootloader cant select yes
Hi all, im a newbie to android rooting etc, so please be patient if I dont understand... XD
I will try to give a backround with a very detailed discription for those who might have the same problem, a similar problem or for those trying to help...
so I bought this beast in Feb with stock software on: this was my 1st root, s-off attempt :
http://forum.xda-developers.com/showthread.php?t=2130585
1st attempt quote from post
Hi there,
Developers, gonna be developers and android noobs
I got a small issue with mu EVO 3d GSM...
Firstly Id like to apologize if this has been asked...
Problem: I need to get past BOOTLOADER BLOCK !!!
Before you carry on reading -
Bought this phone online, from China, Original HTC!!! but with 1 or 2 chinese apps installed, Android 2.3.4...
This was standard when I first entered bootloader (out of the box)
***LOCKED***
SHOOTER_U PVT SHIP S-OFF RH
HBOOT-1.49.0012
RADIO-10.13.9020.08_2M
eMMC-boot
What is suprising is it needed to say Locked and s-on...
So I wanted to root and s-off...
Tried Revolutionary... Everything ran well, after 2nd reboot into bootloader, error - Communications between phone and PC has been interrupted
After that I retried and it said - 'Your device is already s-off' then it wanted to download and install CWM Recovery 4.0.142 Revolutionary...
HTCDEV - Step 13 didnt happen, it just stayed on the normal bootloader screen (in Fastboot USB)
Flashed a earlier version of HBOOT (1.49.007) before Revolutionary ROOT method(revolutionary didnt support HBOOT 1.49.0012), i noticed everytime i 'completed' revolutionary method with error, my HBOOT changed to 1.49.1107 for some reason, IDK
Now my bootloader setup is:
***Revolutionary***
SHOOTER_U PVT SHIP S-OFF RH
HBOOT-1.49.1107
RADIO-10.13.9020.08_2M
eMMC-boot
In CWM Recovery - I flashed SU.zip, it removed /bin and /xbin, and wanted to start copying or rooting file and then showed an error msg 'installation aborted', booted into ROM and SU app requested SU access???
BTW... downloaded and tried 3 RUU's all 3 for 3d of course and all 3 gave the same error - MODEL ID ERROR (i need the correct model) and in fastboot...
Use same Rev code : fastboot flash unlocktoken Unlcok_code.bin
Half the time it is done successfully but with no disclaimer screen (stays on fastboot) and changes hboot to 1107
OR
Gives error (Remote : Partition no avaiblable) or (Remote : not allowed)
Try fastboot oem lock, Doesnt lock and same result as mentioned above and every now and then it says loading custom splash sceen failed, htc disclaimer screen???
If anyone has had this problem or similar, please help, I would really appreciate it
Thnks in advance!!!
END
Now, Ive got a similar problem,
HBoot
1.58.5858 Jpbear
Unlocked
So I flashed the RUU_Shooter_U_TWM_TW_1.23.921.5_Radio_10.55.9020.00_10.13.9020.29_M_release_207920_signed.exe, it was the closest I could find with HBoot 1.49.0012 and gb 2.3.4...
Okay, np it flashed it with no problems... but little did I know, I lost root, bootloader relocked with disclaimer screen and lost s-off... Im buggered
So after messing around including almost bricking my phone, flashing new hboots, trying htcdev unlock with rogers, EMEA and sprint, no luck...
The only result is it showing the disclaimer screen (as mentioned in 1st boot attempt) that i cant select yes...
I tried flashing recovery, however when I flash recovery, it either hangs with HTC screen for a min or two then reboots or just hangs there forever...
Somewhere along the line I tried booting into Android and it jut boot in fastboot, for some unknown reason it also didnt pickup the PG86IMG.zip file I had on, it actually didnt pickup and PG86IMG files???
I also came across writesecureflag 3 in fastboot, gave it a try and it gave me a ***security warning***...
After that, I coud flash a PG86IMG but when I tried the htcdev unlock, I select ye, no response, removed battery and it said ***unlocked***, but when I flash a recovery, it flashes recovery in cmd but cant boot into it or it just doesnt flash onto the phone???
Somehow in between all of this I could get past the "yes" in unlock bootloader which was pure luck of the joy of the moment made me forget what I did before, I also tried flashing these RUU's
RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed
RUU_SHOOTER_U_ICS_35_S_Rogers_WWE_3.28.631.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262715_signed(1)
RUU_SHOOTER_U_ICS_35_S_hTC_Asia_WWE_3.28.707.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_264110_signed
When booted in TWN-TW RUU, I could install Rom manager and flash CWM through that but through fastboot, it didnt boot through it
fastboot flash recovery recovery.img
fastboot boot recovery.img
RESULT: hangs on htc screen for a min or 2 then reboot into OS
Now im currrently on Asia ICS, hboot jbear 1.58.5858, htc recovery...
And in want of root, s-off, and most important able to Unlock Bootloader by selecting yes with a response,
please ANY help would be of use
thnx in advance
Its not much but will have a small paypal reward for those who helped (btw it will prob help others aswel)
[TAGS] : root issue, s-off problem, unlock bootloader cant select yes, evo 3d hboot not detecting PG86IMG, evo 3d bootloop
wow, you got a used or refurbished 3d which was already s-off. if you had posted before doing anything ,all you needed to do was flash a recovery and flash su zip. When you have s-off with custom hboot, like you had, you cannot unlock through htcdev and you don't have to. S-off with custom hboot means you can already flash any hboot ,recovery,Rom ,kernel or any mods.
You never needed HTC dev unlock.
you said.you are s-on with jbear.hboot? I.don't think.that's possible ,.check again if it's s-off or s-on . If it's s-on then it cannot be jbear.
You never lost s-off when you ran the RUU, you lost s-off by running the write secureflag command . It was your luck you were on stock.hboot , if you were on custom one,your evo 3d was dead for sure. Now flash the RUU that is made for your phone. then follow instructions from unlimited.io or ramjet73's thread , flash recovery then su zip. If you want another Rom you can directly flash that Rom without su.
Again, you never needed the htcdev. But now you will need it for the wire trick.
Thnx for responding, u made my day xD
mnomaanw said:
wow, you got a used or refurbished 3d which was already s-off. if you had posted before doing anything ,all you needed to do was flash a recovery and flash su zip. When you have s-off with custom hboot, like you had, you cannot unlock through htcdev and you don't have to. S-off with custom hboot means you can already flash any hboot ,recovery,Rom ,kernel or any mods.
You never needed HTC dev unlock.
you said.you are s-on with jbear.hboot? I.don't think.that's possible ,.check again if it's s-off or s-on . If it's s-on then it cannot be jbear.
You never lost s-off when you ran the RUU, you lost s-off by running the write secureflag command . It was your luck you were on stock.hboot , if you were on custom one,your evo 3d was dead for sure. Now flash the RUU that is made for your phone. then follow instructions from unlimited.io or ramjet73's thread , flash recovery then su zip. If you want another Rom you can directly flash that Rom without su.
Again, you never needed the htcdev. But now you will need it for the wire trick.
Click to expand...
Click to collapse
So, okay, I messed around abit more, not as if I could do any further damage besides bricking LOL
So this is my position and will leave it till next response...
***Relocked*** (can unlock, relock np because of s-on, if s-off, I cant, it just hangs after selecting yes, no response)
HBoot 1.49.0012
I have fastboot and OS access,
cant flash recovery or zip, etc, can change cid
Hboot doesnt read PG86IMG.zip files at all,
Goes through PG86... list, hangs 2 sec on PG86IMG.zip, says checking or parsing PG86IMG.zip for less than a sec then 'cancels', goes to hboot screen
Rev tool does not work
1st attempt - (1st line)Zerging root...
result- Cannot aquire root
for 2nd consecutive to 3,4,5,etc attempt
- goes to 2nd line in rev tool,
result gives error Communications with phone stopped,
When flashing recovery, it flashes perfectly, when fastboot boot recovery.img or hboot>recovery, hangs for a while then reboots
So flashing files through fastboot is a no go (generally gives error > remote:not allowed)
Thus conclusion, im considering the downgrade/unbrick method but It doesnt pickup and PG86IMG files (check exact speeling p.s. have done this alot)
I did a day ago aquire root, 4ext recovery but wanted unlock boot loader, so s-on, the only way to unlock, then got myself to this delema, stupid I know :silly:
So if you have any tricks up your sleeve, let me know please and thnx

[Q] Error 131 on RUU Flash after HBOOT Downgrade

I recently bought my new Evo 3D from eBay. As far as I can tell, it is in perfect shape. I was hoping to flash it to Page Plus and was dismayed when I realized how impossible the rooting process looked. I began with downgrading my 1.58 HBOOT to 1.40. Now I am attempting to flash the 1.13 RUU so I can finally move on in this process, but every time I attempt to flash it (or any other RUU), I get the error, "Error [131]: CUSTOMER ID ERROR." Now most fastboot commands do not work, and my phone bootloops with the stock ROM. Any idea how to fix it?
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Brian706 said:
I used the juopunut bear wire trick for s-off so excuse me if I'm a little ignorant here with the downgrade method. Once you are down to hboot 1.40 (which sounds like you were successful with) can't you use the revolutionary s-off tool?
Once s-off you can easily run any ruu but I guess I don't understand why you need to downgrade even further to s-off, when revolutionary (I thought) works with hboot 1.40 and 1.30
Click to expand...
Click to collapse
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Macadamia Daze said:
As I understand I can't use Revolutionary without booting into Android (since it needs ADB), which is currently impossible because of the bootloop.
Click to expand...
Click to collapse
Oh, I see now!
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Brian706 said:
Oh, I see now!
So far, in every case I've seen, running the latest RUU has solved the bootloader unlock issue for people. I would run the 1.58 RUU and see if you can unlock the bootloader. Then go from there.
Or as I saw mentioned in the other thread, use the PG86IMG version of the RUU or extract it yourself from the exe. Flashing through the bootloader does not perform a cid check.
Click to expand...
Click to collapse
So far, I have yet to have any success despite flashing many RUUs. I took a break for quite a while, but decided I may try again. I am downloading now the 2.08 RUU, which one thread suggested.
Macadamia Daze said:
I should also point out that HTCDev unlock fails for me. On hboot 1.58 the fastboot commands are successful, but I am never presented with the unlock dialog on the phone. On hboot 1.4 most fastboot commands fail. Also, I can easily restore to stock by flashing a PG86IMG which includes hboot 1.58.
Click to expand...
Click to collapse
If I remember correctly, the HTCDev unlock doesnt work for the earlier bootloaders. It says so on the very first page when its walking you through the steps. I could be wrong but you may wanna keep that in mind

Categories

Resources