Hello ,
I just bought a used DNA. when i'm entered to the bootloader i see the following info :
TAMPEERED (in Gray)
UNLOCKED
SHIP S-ON
HBOOT - 1.33.0001
RADIO 1.00.00.1023_3
My ROM is Supercharged hatka
Build Number : 2.04.605.2
i have root access and my CID is VZW_001 (I used CID getter)
Does it's means that i cant S-OFF my device right now \ Change my CID ?
and one more question - can i change rom ? (if he is on the same Build number)
incident said:
Hello ,
I just bought a used DNA. when i'm entered to the bootloader i see the following info :
TAMPEERED (in Gray)
UNLOCKED
SHIP S-ON
HBOOT - 1.33.0001
RADIO 1.00.00.1023_3
My ROM is Supercharged hatka
Build Number : 2.04.605.2
i have root access and my CID is VZW_001 (I used CID getter)
Does it's means that i cant S-OFF my device right now \ Change my CID ?
and one more question - can i change rom ? (if he is on the same Build number)
Click to expand...
Click to collapse
I believe you need to do this first: http://forum.xda-developers.com/showthread.php?t=2149417
Then, change the CID and then you can S-off your device and change ROM
Someone confirm?:highfive:
Edit: Also, check to see what Kernel you're using
And get GooManager and update your twrp recovery [my suggestion]
UrGuardian999 said:
I believe you need to do this first: http://forum.xda-developers.com/showthread.php?t=2149417
Then, change the CID and then you can S-off your device and change ROM
Someone confirm?:highfive:
Edit: Also, check to see what Kernel you're using
And get GooManager and update your twrp recovery [my suggestion]
Click to expand...
Click to collapse
Hi Mate,
Thanks for the quick response. are you sure that i can S-OFF my device ? (even if i already with 2.04 build ?):fingers-crossed::fingers-crossed::fingers-crossed:
btw . my Kernel is 3.4.10-ga02d2c6 [email protected] #1 SMP PREEMPT
incident said:
Hi Mate,
Thanks for the quick response. are you sure that i can S-OFF my device ? (even if i already with 2.04 build ?):fingers-crossed::fingers-crossed::fingers-crossed:
btw . my Kernel is 3.4.10-ga02d2c6 [email protected] #1 SMP PREEMPT
Click to expand...
Click to collapse
You need to use that first link and remove the OTA [2.04 build] and revert back. Then you can go down the road of s-off'ing your device. As always, follow the directions of each link I posted. I'm sure you can S-off, but you're a few steps away.
I suggest you flash DSB's 3.1.3 Kernel. It's been very stable for me.
Wait for someone else to respond too, but I'm pretty sure this is all that you need to do
I deleted all the relevant APk's of the OTA
I installed the CID-2.APK but it's still shows me VZW_001 :<
can i S-OFF my device without the changing my CID ? (probebly it's will not benefit me a lot..)
btw
Can i change rom or i'm stuck with "hataka" ?
incident said:
I deleted all the relevant APk's of the OTA
I installed the CID-2.APK but it's still shows me VZW_001 :<
can i S-OFF my device without the changing my CID ? (probebly it's will not benefit me a lot..)
btw
Can i change rom or i'm stuck with "hataka" ?
Click to expand...
Click to collapse
I think you need to flash this file to remove it, not just delete related APK's.
As for CID
For this to work [S-off], you must be HTCdev unlocked and have superCID
Click to expand...
Click to collapse
Your CID can't be VZW_001
And of course you can flash another ROM other than Hatka, that's just one of the options
UrGuardian999 said:
I think you need to flash this file to remove it, not just delete related APK's.
As for CID
Your CID can't be VZW_001
And of course you can flash another ROM other than Hatka, that's just one of the options
Click to expand...
Click to collapse
When i said that i deleted those apk h i mean that they removed with this script, sorry about the missunderstanding.
Here is my cid via cid getter .. maybe the cid getter mistake and i need to check with the fastboot command?
Sent from my HTC6435LVW using xda app-developers app
If you see something else (e.g. VZW__001) then reboot normally and try the process again.
Click to expand...
Click to collapse
If it didn't change, I guess try a couple more times and use the fastboot command
Go on your computer and do the command to read the cid. Cid getter is buggy and shows the vzw one no matter what.
Sent from my HTC6435LVW using xda app-developers app
BOOOM !!!
got to my laptop at home, did fast boot getvar cid :
CID : 222222222
should i now do the S-OFF guide without any problems ??:fingers-crossed::fingers-crossed:
Bigandrewgold said:
Go on your computer and do the command to read the cid. Cid getter is buggy and shows the vzw one no matter what.
Sent from my HTC6435LVW using xda app-developers app
Click to expand...
Click to collapse
Now that you mentioned it in the other thread, it won't matter anyways because he also has the OTA.
@Incident, you're going to have to wait till they fix the OTA issue before you can press on.
Correction:
For this to work, you must be HTCdev unlocked and have superCID (custom recovery/root is optional), see the thread below for help and information regarding obtaining superCID, unlock, etc. If you have taken the OTA for the DNA (sw version 2.xx) without FIRST obtaining superCID, there is no superCID nor s-off method for you currently. Note this thread is provided for convenience only
Looks like you can do S-off, but do it at your own risk.
UrGuardian999 said:
Now that you mentioned it in the other thread, it won't matter anyways because he also has the OTA.
@Incident, you're going to have to wait till they fix the OTA issue before you can press on.
Correction:
For this to work, you must be HTCdev unlocked and have superCID (custom recovery/root is optional), see the thread below for help and information regarding obtaining superCID, unlock, etc. If you have taken the OTA for the DNA (sw version 2.xx) without FIRST obtaining superCID, there is no superCID nor s-off method for you currently. Note this thread is provided for convenience only
Looks like you can do S-off, but do it at your own risk.
Click to expand...
Click to collapse
I think that CID-GETTER app is buggy , look my result in the cmd :
c:\ADB + Fastboot + Drivers>fastboot getvar cid
cid: 22222222
finished. total time: 0.000s
so i can do the S-OFF "without" worries ?
incident said:
I think that CID-GETTER app is buggy , look my result in the cmd :
c:\ADB + Fastboot + Drivers>fastboot getvar cid
cid: 22222222
finished. total time: 0.000s
so i can do the S-OFF "without" worries ?
Click to expand...
Click to collapse
Yes, you can s off without any problems.
Sent from my HTC6435LVW using xda app-developers app
incident said:
I think that CID-GETTER app is buggy , look my result in the cmd :
c:\ADB + Fastboot + Drivers>fastboot getvar cid
cid: 22222222
finished. total time: 0.000s
so i can do the S-OFF "without" worries ?
Click to expand...
Click to collapse
Agree, it says in the S-off thead that as long as you're unlocked and have CID you should be good to go
Related
Forgive if not the place...
I have a problem. I can not unlock bootloader.
When I type "fastboot flash unlocktoken Unlock_code.bin" It answers "sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...FAILED (remote: unlock token check failed) finished. total time: 0.150s" I have tried reinstalling the drivers and doing it in different pc get the same result.
I configured it correctly repeatedly...
Help please. Thank you, very much.
raa_ said:
Forgive if not the place...
I have a problem. I can not unlock bootloader.
When I type "fastboot flash unlocktoken Unlock_code.bin" It answers "sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...FAILED (remote: unlock token check failed) finished. total time: 0.150s" I have tried reinstalling the drivers and doing it in different pc get the same result.
I configured it correctly repeatedly...
Help please. Thank you, very much.
Click to expand...
Click to collapse
Check your unlock_code.bin file, its reporting 0kb and that's a null file.
I would also recheck if the phone is being properly id'ed by the OS and there are no further communications issues.
Code, in theory gives correctly...
The conexion is correct (apparently)...
The file Unlock_code.bin is 2 kb.
raa_ said:
Code, in theory gives correctly...
The conexion is correct (apparently)...
The file Unlock_code.bin is 2 kb.
Click to expand...
Click to collapse
Try removing the battery off the phone then booting in fastboot and try again.
I did as usual... It answers "FAILED (remote: unlock token check failed) finished. total time: 0.150s"
I repeated the process many times
raa_ said:
I did as usual... It answers "FAILED (remote: unlock token check failed) finished. total time: 0.150s"
I repeated the process many times
Click to expand...
Click to collapse
What hboot are you ? I would do a ruu exe and redo that lockcode part to see if it fixes ya.
Sent from my PG86100 using xda premium
EVO 3D data are:
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0018
eMMc-boot
Oct 3 2011,15:03:01
How do a ruu exe? Help me please.
raa_ said:
EVO 3D data are:
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0018
eMMc-boot
Oct 3 2011,15:03:01
How do a ruu exe? Help me please.
Click to expand...
Click to collapse
So I'm guessing your cdma ? Sorry man been a long long day been running on 3 hrs of sleep lol I think you can root the revolutionary way since your not 1.5 hboot .
Sent from my PG86100 using xda premium
reaper24 said:
So I'm guessing your cdma ? Sorry man been a long long day been running on 3 hrs of sleep lol I think you can root the revolutionary way since your not 1.5 hboot .
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
In the stickies in the dev section football's post has links for the cdma ruu exe's
Make sure you know if your cdma or gsm?
Anyways download the one for hboot 1.49 . Don't snag the latest 2.17 or you will be hboot 1.5 .
When you have the program downloaded your AntiVirus may say something about it cause it is a exe don't worry file is safe.
Hook your phone up to your computer run the program while in hboot..
Sent from my PG86100 using xda premium
My model is European, I guess then that is GSM
Think you do have bad structure of Hboot?
Then you can not do? I can do?
Thanks
They're Gsm phone. There are stickies in the GSM Development Section for this, but here's where to go:
[Tutorial] [UNLOCK/ROOT] EVO 3D GSM Hboot 1.49.0011> + S-On [HTC Unlock method] http://forum.xda-developers.com/showthread.php?t=1248231
Unlock via HTC's site. If u get stuck at step13, you may have to reflash the original GSM Ruu (zip or exe) and try again.
[Tutorial - How to revert back to Original ROM for backup or warranty purposes] http://forum.xda-developers.com/showthread.php?t=1262457
(You can likely skip the "goldcard" setup if you can get the correct RUU for your phone/carrier from Football's GSM Ruu thread)
Once unlocked u use fastboot command prompt to flash (& enter) the correct Cwm Recovery (ShooterU ). Make a backup from recovery. Then flash the Su zip like it says in the op. Then your rooted.
Make a new rooted backup from recovery if you like.
Originally Posted by dr wasim said:
how to create backup from cwm? and do we have to flash kernal for installing any custom rom?
Click to expand...
Click to collapse
To make a CWM Backup, see guide/flashing notes in my signature, go to post 4 (cwm recovery notes) and u can get an idea of how to make w backup. Keep in mind the file links in the thread are for Sprint Cdma phones, so don't use the links. The step-by-step is correct.
The kernel is usually included with the ROM u just need to enter recovery by fastboot command prompt and make sure the ROM & kernel are compatible with your phone/baseband.
Sent from my PG86100 using Tapatalk
I have seen that I can´t go recovery, is normal?
raa_ said:
My model is European, I guess then that is GSM
Think you do have bad structure of Hboot?
Then you can not do? I can do?
Thanks
Click to expand...
Click to collapse
Ya ur gsm .. sorry man .. I know more about cdma .
Not much about gsm .
Sent from my PG86100 using xda premium
Thank you reaper24
I hope someone can help me
Did u go to the thread I mentioned? U won't have a recovery until u HTC unlock & flash one via fastboot command prompt.
Sent from my PG86100 using Tapatalk
Ok, thanks.
I follow the link http://forum.xda-developers.com/showthread.php?t=1256208, I hope to get lucky
Solved!!!
I installed "RUU_Shooter_U_HTC_Europe_1.20.401.2_Radio_10.53.9 020.00_10.13.9020.08_2M_release_203403_signed" and it put me Hboot 1.49.007 then I installed Revolutionary Recover S-OFF & Recovery Tool 0.4pre4
Thank you for all!!
These steps will get you completely back to stock.
I want to first say thanks to the unlimited.io team for making S-OFF possible.
Secondly, by following these instructions you are acknowledging that should something go wrong and you brick your device, I am not at fault nor are the developers of the S-OFF method for the HTC RUBY. Follow these instructions at your own risk! I am NOT a dev, just stupid enough to be the first one (I think) To try this. I am not going to give instructions on how to use fastboot, if you are S-Off, then you should already know.
Third, you WILL be able to re-unlock your bootloader and regain S-OFF after you have followed these instructions. If you want to do so, there are other threads on how to do that.
And 4th, I have only tried this on a tmobile branded device. I have no idea if this works on any other device. I think it should, but I don't know for sure. If anybody wants to give it a try and let me know, then i will update the OP.
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
That's it!
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
kaabob said:
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
Click to expand...
Click to collapse
I should have clarified, the steps are if you want to go completely stock, will update the OP.
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
bjcolema said:
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
That's good to know. Thanks.
Sent from my HTC_Amaze_4G using XDA
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
Thanks for replying.
This is correct, my phone said locked, not relocked.
I would like to stress that YOU NEED A FULL RUU, not a stock nandroid backup. Otherwise, you are going to need that link on my sig
Sent from my HTC Sensation using XDA
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
electronicrice said:
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
Click to expand...
Click to collapse
If you are S-Off, then following this guide will put you back to stock gingerbread.
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
I dont know a way for going back to stock without being s=off. You could possibly flash the newest official release (ics, one that hasnt been modified) then relock your bootloader, but i think that it will show relocked rather than locked. Worth a try though.
Okay thanks for the input guys. It isn't a huge deal, I just didn't think there was enough "goodies" rom-wise for ICS, but there are some hardworking devs on here. Looking forward to the Sense 4.0 rom.
dcmtnbkr said:
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Click to expand...
Click to collapse
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
frodoboy said:
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
Click to expand...
Click to collapse
When s-on, you can't go back to s-off by writing the security flag again . You have to do again the juopunutbear procedure including the wire trick
Sent from my HTC Sensation Z710e
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
3oudreaux said:
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
Click to expand...
Click to collapse
This one would be best: RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
I spent 3 hrs trying to solve the relocked and locked issue until finally I got it resolved. with the manual option to lock with hasoon tool, places *** RELOCKED *** in hboot, which clearly and obvious for any technician to see you tampered with the hboot files from stock. my reason for doing this to get my warranty back.
how did i fixed "RELOCKED" to show as *** LOCKED *** ? after the hasoon tool 3.2 relocked the bootloader i was challenged, but decided the first step would be switching the security off and on (s-off/ s-on)
first return to stock RUU through boot loader, then adb command fastboot oem writesecureflag 3 to enable s-on. *toggled it on
i reinstalled juopunutbear s-off again carefully following the instructions. with a paperclip grounding the phone and selecting for juopunutbear's modified files "y" enter.
then your *** RELOCKED *** shows as *** juopunutbear *** in hboot. (at first i thought I dig myself a bigger hole)
I used Hasoon tool 3.2 again to RELOCK bootloader, with the intention of reinstall the stock RUU again. however it still showed as *** juopunutbear *** with the message its already locked.
Now I installed the the Stock RUU again from bootloader. once complete back to the hboot, to show *** LOCKED *** and s-off Progress!!!
repeat enable s-on instructions by writing adb: fastboot oem writesecureflag 3,
now shows
*** LOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
OpenADSP-02.6.0.2226.00.0202
eMMC-boot
a step closer for the warranty being back to the device, without a dispute with the warehouse/ carrier
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
aoakes said:
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
Click to expand...
Click to collapse
No need to get rid of that. New phone from T-Mobile with HBOOT 1.93 and it had that line it . It looks like 1.90 is the one that doesn't have that line. Because my wife's phone is on 1.90 and she doesn't have it.
I'm going to be following the method in a few days. Can you guys confirm this all works as it should?
Hi
I am stuck on the bootloader, because:
- I unlocked via htcdev online
- installed CWM recovery
- I tried to install custom roms update-ics-yetki-1.0.zip LeeDrOiD-Flyer-V2.2.0.zip (unfortunately with s-on)
result: black screen on system boot, unable to go further than bootloader or recovery.
after relocking I tried to run :
RUU_Flyer_TMO_DE_2.27.111.1_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204120_signed.exe
some errors on installing like 140, bootloader error
so I am not sure if this is the good RUU
before bricking my Flyer definitely I would like to know how can I know which is right RUU for my device to install?
The only information about my device I can get are those:
Flyer pvt ship S-ON RL
HBOOT 1.11.0011
MICROP - 0950
RADIO-3822.11.08.07M2
eMMC-boot
Oct 25 2011, 16:55:07
the device has (had) a T-Mobile (Germany) branding
cid: T-MOB101
version-main: 3.55.111.1
anyone a clue?
Thank you
You MUST relock bootloader first in order to flash RUU!!!
Go to fastboot and enter: fastboot oem lock. Then try to install RUU. Nice unbricking!
sgarza said:
I wrote
after relocking I tried to run :
RUU_Flyer_TMO_DE_2.27.111.1_Radio_20.3504.30.089BU_3809.07.04.06_M_release_204120_signed.exe
some errors on installing like 140, bootloader error
so I am not sure if this is the good RUU
Click to expand...
Click to collapse
Keioboy said:
You MUST relock bootloader first in order to flash RUU!!!
Go to fastboot and enter: fastboot oem lock. Then try to install RUU. Nice unbricking!
Click to expand...
Click to collapse
Thanks for reply
of course... I relocked it but update utility gives me error 140....
somebody thinks it's because of incompatibility of flashing an older version on a newer one,
I don't know if that has something to do with kernel, radio, baseband or whatsoever....
sgarza said:
Thanks for reply
of course... I relocked it but update utility gives me error 140....
somebody thinks it's because of incompatibility of flashing an older version on a newer one,
I don't know if that has something to do with kernel, radio, baseband or whatsoever....
Click to expand...
Click to collapse
Ok, the only way I found to solve was flashing a
rom.zip retrieved from temporary files after launching the HTC update utility, (RUU.exe)
from RUU_Flyer_HC_S_HTC_TUR_3.62.468.1
I renamed the rom .zip to PG41IMG.zip,
then copied it on a goldcard, prepared before...launched bootloader and so on...
that was the only one without errors that finally worked...
now trying to flash a custom rom, I need phone functions....which rom?...
Hello, I need urgent help with my HTC AMAZE, several weeks ago was making an S-OFF my smartphone and I did but when installing CM10 while booting the smartphone is turned off and did not respond in a way that not even loaded but with instructions XDA, I could give unbrick. After that install the ICS RUU STOCK quitting but when booting just restarts when you try to enter or make RECOVERY FACTORY RESET, and saw that it was still S-OFF try to unlock the bootloader but although the screen presents options unlock not unlocked, you also install the HBOOT 1.90.0004 (PH85IMG method) but will not let me install the GB ROM and now I can not install the RUU ICS because it tells me that the CID is incorrect, i tried to change it but nothing.
Model: S-OFF HTC Amaze
Modelid: PH8511000
CID: 0202 (do not know why)
HBOOT: 1.90.0004
ROM: ICS Stock ROM
Thanks in advance
Andy1886 said:
Hello, I need urgent help with my HTC AMAZE, several weeks ago was making an S-OFF my smartphone and I did but when installing CM10 while booting the smartphone is turned off and did not respond in a way that not even loaded but with instructions XDA, I could give unbrick. After that install the ICS RUU STOCK quitting but when booting just restarts when you try to enter or make RECOVERY FACTORY RESET, and saw that it was still S-OFF try to unlock the bootloader but although the screen presents options unlock not unlocked, you also install the HBOOT 1.90.0004 (PH85IMG method) but will not let me install the GB ROM and now I can not install the RUU ICS because it tells me that the CID is incorrect, i tried to change it but nothing.
Model: S-OFF HTC Amaze
Modelid: PH8511000
CID: 0202 (do not know why)
HBOOT: 1.90.0004
ROM: ICS Stock ROM
Thanks in advance
Click to expand...
Click to collapse
did you try to supercid since you are s-off...here is the link,read it and follow the instructions...
http://forum.xda-developers.com/showthread.php?t=1612475
and flash the latest jbear hboot ...here http://unlimited.io/jbhboots.htm
read the instructions carefully....
and please read more and more before doing anything to your device
HTC Soft Bricked
ok i read the that if i should use the hboot PH85IMG_SHP_1.93.0002 to get superCID or modify it. i clould flash this hboot renaming PH85IMG copy the file to the root of my sd card and apply the update?
HTC Soft Bricked
hatim_rajput said:
did you try to supercid since you are s-off...here is the link,read it and follow the instructions...
http://forum.xda-developers.com/showthread.php?t=1612475
and flash the latest jbear hboot ...here http://unlimited.io/jbhboots.htm
read the instructions carefully....
and please read more and more before doing anything to your device
Click to expand...
Click to collapse
ok i read the that if i should use the hboot PH85IMG_SHP_1.93.0002 to get superCID or modify it. i clould flash this hboot renaming PH85IMG copy the file to the root of my sd card and apply the update?
Andy1886 said:
ok i read the that if i should use the hboot PH85IMG_SHP_1.93.0002 to get superCID or modify it. i clould flash this hboot renaming PH85IMG copy the file to the root of my sd card and apply the update?
Click to expand...
Click to collapse
1st of all before doing anything else what is your current bootloader version shows in your bootloader? :/
HTC Bricked
ravike14 said:
1st of all before doing anything else what is your current bootloader version shows in your bootloader? :/
Click to expand...
Click to collapse
Hboot-1.90.0004
S-OFF
Bootloader-locked
Andy1886 said:
Hboot-1.90.0004
S-OFF
Bootloader-locked
Click to expand...
Click to collapse
well your in gb :S anyhow since your s off and somehow it shows your unlock try to flash the 4ext recovery from hasoon's aio kit??
HTC Soft Bricked
ravike14 said:
well your in gb :S anyhow since your s off and somehow it shows your unlock try to flash the 4ext recovery from hasoon's aio kit??
Click to expand...
Click to collapse
yes i tried but i shows this error FAILED (remote: not allowed), i think that my problem is the rare CID: 0202 i cant flash anything because it shows ''Incorrect CID'' even when i change it on the ''android-info.txt'' ; or am i doing it wrong?
Andy1886 said:
yes i tried but i shows this error FAILED (remote: not allowed), i think that my problem is the rare CID: 0202 i cant flash anything because it shows ''Incorrect CID'' even when i change it on the ''android-info.txt'' ; or am i doing it wrong?
Click to expand...
Click to collapse
well relock your bootloader and try flashing a GB ruu :/
HTC Soft Bricked
ravike14 said:
well relock your bootloader and try flashing a GB ruu :/
Click to expand...
Click to collapse
i tried but it shows ''Incorrect CID'' again. My cid is 0202 and i don't know how to revert it because i can't set the debugging mode due to a boot loop.
Andy1886 said:
i tried but it shows ''Incorrect CID'' again. My cid is 0202 and i don't know how to revert it because i can't set the debugging mode due to a boot loop.
Click to expand...
Click to collapse
well i did some digging i think you need to flash the original GB HBOOT you can find a img file called HBOOT.img flash it from hasoon's S OFF kit and then flash the gb ruu if it doesnt work flash the jbear GB HBOOT if it doesnt try the ICS HBOOT (since you told your s off and tried the ics stock ruu) from unlimited.io and flash it from hasoon's s off kit and try flashing 4ext and flash a gb rom and get a working device..or else once you flash the hboot run a ruu which has 1.93.0002 hboot so you can supercid then flash the new radio>>jbearhboot>>4ext>>any rom you like if you want
(i'm not responsible if something happen's to your phone do it at your own risk)
have a look:
http://forum.xda-developers.com/showthread.php?t=1655182
http://forum.xda-developers.com/showthread.php?t=1612475&page=13
HTC Soft Bricked
ravike14 said:
well i did some digging i think you need to flash the original GB HBOOT you can find a img file called HBOOT.img flash it from hasoon's S OFF kit and then flash the gb ruu if it doesnt work flash the jbear GB HBOOT if it doesnt try the ICS HBOOT (since you told your s off and tried the ics stock ruu) from unlimited.io and flash it from hasoon's s off kit and try flashing 4ext and flash a gb rom and get a working device..or else once you flash the hboot run a ruu which has 1.93.0002 hboot so you can supercid then flash the new radio>>jbearhboot>>4ext>>any rom you like if you want
(i'm not responsible if something happen's to your phone do it at your own risk)
have a look:
http://forum.xda-developers.com/showthread.php?t=1655182
http://forum.xda-developers.com/showthread.php?t=1612475&page=13
Click to expand...
Click to collapse
Hi again man, i did it as you said but the command promp shows the following error : FAILED <error 42: remote not allowed>.
Andy1886 said:
Hi again man, i did it as you said but the command promp shows the following error : FAILED <error 42: remote not allowed>.
Click to expand...
Click to collapse
Be more specific what did you do?
Sent from my HTC_Amaze_4G using xda premium
HTC Soft Bricked
ravike14 said:
Be more specific what did you do?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I tried to flash the GB HTBOOT, ICS HBOOT and the JB_HBOOT and the result was the same error. writing 'hboot'... FAILED (remote: not allowed)
Andy1886 said:
I tried to flash the GB HTBOOT, ICS HBOOT and the JB_HBOOT and the result was the same error. writing 'hboot'... FAILED (remote: not allowed)
Click to expand...
Click to collapse
You end up in this trouble after the s off??
Sent from my HTC_Amaze_4G using xda premium
HTC Bricked
ravike14 said:
You end up in this trouble after the s off??
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
Yeah, my cell was even hard bricked and when i restored i tried to flash the GB RUU due a bootloop; then the RUU only flashed the HBOOT and shows an error after that the CID was changed and has been a nightmare.
Andy1886 said:
Yeah, my cell was even hard bricked and when i restored i tried to flash the GB RUU due a bootloop; then the RUU only flashed the HBOOT and shows an error after that the CID was changed and has been a nightmare.
Click to expand...
Click to collapse
Well the thing is your s off is gone wrong like 1% cuz if it went right you should be in jbear ics hboot like us (reason devs took it down for windows and you took the risk) moving on the only hope is to try to flash the ics jbear hboot or the 1.93.0002 then your golden you can supercid, you can flash it from hasoons s off kit or as PH85IMG.zip ...relock n unlock the bootloader again if you can, and follow the same procedure if it doesn't go right...it's not necessary but it won't hurt to give it a try aswell good luck mate :good:
Sent from my HTC_Amaze_4G using xda premium
HTC Soft Bricked
ravike14 said:
Well the thing is your s off is gone wrong like 1% cuz if it went right you should be in jbear ics hboot like us (reason devs took it down for windows and you took the risk) moving on the only hope is to try to flash the ics jbear hboot or the 1.93.0002 then your golden you can supercid, you can flash it from hasoons s off kit or as PH85IMG.zip ...relock n unlock the bootloader again if you can, and follow the same procedure if it doesn't go right...it's not necessary but it won't hurt to give it a try aswell good luck mate :good:
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I did it :laugh:, i flashed the HBOOT 1.93.0002 i just used the JB FW Easy Flasher & Fastboot Toolkit modifying the
CID in the android-info.txt and copying some files to the toolkit folder. I flashed the ICS RUU (last) but i still in a bootloop that is the only thing that i need to fix now.
Andy1886 said:
I did it :laugh:, i flashed the HBOOT 1.93.0002 i just used the JB FW Easy Flasher & Fastboot Toolkit modifying the
CID in the android-info.txt and copying some files to the toolkit folder. I flashed the ICS RUU (last) but i still in a bootloop that is the only thing that i need to fix now.
Click to expand...
Click to collapse
That's really good news :good: good job mate now it'll be easy I guess hmm what's your current state?? The info hboot cid bootloader??
HTC Soft Bricked
ravike14 said:
That's really good news :good: good job mate now it'll be easy I guess hmm what's your current state?? The info hboot cid bootloader??
Click to expand...
Click to collapse
Here we go.
current state: S-OFF
HBOOT: 1.93.0002
Modelid: PH8511000
CID: T-MOB010
Bootloader: LOCKED
just got a replacement phone. And i want root back.
I already did the bootloader unlock crap. i have my token key. i unlocked bootlaoder via cmd.
I still have s-on though. which s-of program should i use?
hboot: v2.09.0000
radio: 1.12.11.1210
is there no new root for the recently updated phone's?
I've tried regawmod, but it just took me to htcdev. to unlock my bootloader again and failed to do that. (i got stuck in some log on/off loop)
redm1st said:
just got a replacement phone. And i want root back.
I already did the bootloader unlock crap. i have my token key. i unlocked bootlaoder via cmd.
I still have s-on though. which s-of program should i use?
hboot: v2.09.0000
radio: 1.12.11.1210
is there no new root for the recently updated phone's?
I've tried regawmod, but it just took me to htcdev. to unlock my bootloader again and failed to do that. (i got stuck in some log on/off loop)
Click to expand...
Click to collapse
First off, root & S-off are not the same. Second, all you need to do now is install a custom recovery, like TWRP, and flash a custom ROM. Then you'll be rooted.
You can gain S-off via Dirty Racun/Baby Racun.
Regaw's root method does not currently work. He has that posted in the OP of his thread, unless something has changed within the last few days.
Sent from my EVO using xda premium
redm1st said:
just got a replacement phone. And i want root back.
I already did the bootloader unlock crap. i have my token key. i unlocked bootlaoder via cmd.
I still have s-on though. which s-of program should i use?
hboot: v2.09.0000
radio: 1.12.11.1210
is there no new root for the recently updated phone's?
I've tried regawmod, but it just took me to htcdev. to unlock my bootloader again and failed to do that. (i got stuck in some log on/off loop)
Click to expand...
Click to collapse
Click the link in my sig
BTW Questions belong in Q&A
Joy! First victim AND in the wrong forum. I like it
http://forum.xda-developers.com/showthread.php?t=2198636
Delakit said:
Joy! First victim AND in the wrong forum. I like it
http://forum.xda-developers.com/showthread.php?t=2198636
Click to expand...
Click to collapse
Lol
:beer:
Sent from my EVO using xda premium