Related
read this: the purpose of this post is to let folks know that if you htcdev unlock with s-off,your device will go back to reading unlocked until you relock it,at wich time it will read relocked,just like before you s-offed.
what does this mean?! if you dont care about getting back to a locked state for warranty purposes,then it doesnt mean anything. if one of the big reasons that you s-offed in the first place was to get back to locked,then,as the title says,dont unlock with htcdev after s-off. you can install recoveries and hboots via hboot in a PH98IMG files,or you can install available patched hboots to enable engineering commands.
i hope this helps clarify it for those who were confused by the title. my intention was not to cause panic,simply to educate folks in what id found,as i know the subject of locked/relocked is very important to some.
_______________________________________________________________________________________
ok,i have been posting in several threads that the unlocking after s-off is no big deal. i still maintain that.
however...
on my other s-off,htcdev devices,reflashing the hboot/running an RUU makes the device locked again. after more discussion with con,i decided i better test if i was gonna keep saying it.
i stand corrected!
i started by flashing back the 2.11.000 hboot and unlocking it. i flashed it again. still unlocked.. hmmm. so i flashed jp patched hboot,now juopunutbear flashed 2.11 back. still unlocked. hmmm.
so i relocked. reflashed 2.11. still relocked. uh oh. flashed the eng hboot. now relocked eng 2.11.20005,lol... relocked engineering hboot. flashed the 2.05.0000 ship hboot. still relocked.
at this point i ran the entire RUU for 2.01.605.11. still relocked
i plan to try flashing the leak ruu,then 2.01.605.11 again,but for now,im tired. 6am comes very shortly.
i should have known this phone would somehow be different
moral of the story is that if you are one of the folks whom care about your hboot saying locked,dont unlock it
sorry for any misconceptions based on my experiences with other devices
scotty1223 said:
ok,i have been seen posting in several threads that the unlocking after s-off is no big deal. i still maintain that.
however...
on my other s-off,htcdev devices,reflashing the hboot/running an RUU makes the device locked again. after more discussion with con,i decided i better test if i was gonna keep saying it.
i stand corrected!
i started by flashing back the 2.11.000 hboot and unlocking it. i flashed it again. still unlocked.. hmmm. so i flashed jp patched hboot,now juopunutbear flashed 2.11 back. still unlocked. hmmm.
so i relocked. reflashed 2.11. still relocked. uh oh. flashed the eng hboot. now unlocked eng 2.11.20005,lol... unlocked engineering hboot. flashed the 2.05.0000 ship hboot. still relocked.
at this point i ran the entire RUU for 2.01.605.11. still relocked
i plan to try flashing the leak ruu,then 2.01.605.11 again,but for now,im tired. 6am comes very shortly.
i should have known this phone would somehow be different
moral of the story is that if you are one of the folks whom care about your hboot saying locked,dont unlock it
sorry for any misconceptions based on my experiences with other devices
Click to expand...
Click to collapse
I am betting you can s-on the phone then re s-off and have it say locked. Or someone could edit an hboot to just say locked.
Sent from my ADR6425LVW using XDA
nosympathy said:
I am betting you can s-on the phone then re s-off and have it say locked. Or someone could edit an hboot to just say locked.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
im sure it can be edited,im sure thats how we became locked again after s-off. and yeah im certain re-s-off-ing would do it too
i dont personally care,my device has no mfg warranty and its kinda neat to me that it appears to stay unlocked thru up/downgrades,and if i want to run the eng or patched hboots,i still can.
i just wanted to prevent others who do care from becoming entrapped back in the situation because of other advice i may have given. should have tested first,spoke later
When I did my S-OFF I was on 2.11 hboot and the ICS firmware. I flashed the juonoptioeefianwefo hboot and then the ENG hboot and old firmware patch. My end result was it saying "locked" in hboot.
I was rather pissed off since I the reason I flashed the ENG hboot was so that it would say "unlocked" instead of juonoptionaofewhf.
My warranty is voided several times over in other ways* so it doesn't matter much to me and after the huge amount of time getting the darn wire trick to work I was rather proud to have my phone say S-OFF and "unlocked".
*apparently living in a high humidity area is enough to trigger the wetness seals.
jefffeely said:
When I did my S-OFF I was on 2.11 hboot and the ICS firmware. I flashed the juonoptioeefianwefo hboot and then the ENG hboot and old firmware patch. My end result was it saying "locked" in hboot.
I was rather pissed off since I the reason I flashed the ENG hboot was so that it would say "unlocked" instead of juonoptionaofewhf.
My warranty is voided several times over in other ways* so it doesn't matter much to me and after the huge amount of time getting the darn wire trick to work I was rather proud to have my phone say S-OFF and "unlocked".
*apparently living in a high humidity area is enough to trigger the wetness seals.
Click to expand...
Click to collapse
Yeah high humidity trips em lol. I had an iPhone 3G back in the day trip both the headphone Jack and charging port water markers on a 70% humidity day.
Sent from my ADR6425LVW using XDA
The number of things that can happen to invalidate your warranty really is annoying. My cousin has a completely stock Inspire that is stuck on hboot but AT&T won't touch it because it has a small ding in the case from when she dropped it.
After S-OFF (GB stock, amon ra, rooted system), I erroneously thought I needed to unlock. Then I locked the bootloader for any future OTA update and it showed Relocked.
I reinstalled the ENG hboot, but it still shows Relocked.
I asked in the sbear chat room, and the answer was
there is no simple way to get the ENG hboot to change from displaying Relocked to display just plain Locked.
But...It is just cosmetic and doesn't really matter.
Howard
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
I don't know what any of this means...
I just think this makes it more confusing for people..
Mine said 'Locked' after S-Off so I just unlocked it and everything seemed better..
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
That is because you kept the stock hboot which doesn't allow for fastboot commands without being unlocked. By choosing one of Jp's hboot's or the eng hboot you could have installed recovery without unlocking. I did the same thing. So I went back to s-on and redid the s-off procedure and installed jb's hboot. Now I am s-off and locked again. Whew!
Sent from my ADR6425LVW using Tapatalk 2
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
I second this. I had to unlock before I could flash recovery. I don't care that my phone says unlocked, just wanted to point out that for one reason or another some have had to unlock again.
Good usage of Smileys.
I agree with scotty, my hboot says locked and I have s-off so far I have flashed everything except for ruu's. Even recoveries worked.
Sent from my ADR6425LVW using xda premium
I was on the latest firmware and RezROM ICS. Performed S-OFF and never seen an option to install JB-Hboot so I didnt. At that time mine said UNLOCKED/TAMPERED.
Then after a couple of days of reading and trying to decide what to do next I decided to RUU down to the latest official and as soon as that was finished I went back to boot loader and it said LOCKED / S-OFF. I flashed the ENG Hboot with no issues and Now it says LOCKED / VIGOR PVT ENG S-OFF RL.
I also made a backup of RezROM before all this. Restored my backup, flashed the firmware patch, flashed PH that came with RezROM and rebooted and have had no issues at all.
I am not in a 4G area so I might actually have the issue others were having with 4G dropping out. Will have to wait and see.
zone23 said:
I don't know what any of this means...
I just think this makes it more confusing for people..
Mine said 'Locked' after S-Off so I just unlocked it and everything seemed better..
Click to expand...
Click to collapse
Ditto
I was/am on the stock GB firmware, completed S-OFF, phone said locked (still on stock GB HBOOT), I unlocked it ... no problems since.
HowardZ said:
After S-OFF (GB stock, amon ra, rooted system), I erroneously thought I needed to unlock. Then I locked the bootloader for any future OTA update and it showed Relocked.
I reinstalled the ENG hboot, but it still shows Relocked.
I asked in the sbear chat room, and the answer was
there is no simple way to get the ENG hboot to change from displaying Relocked to display just plain Locked.
But...It is just cosmetic and doesn't really matter.
Howard
Click to expand...
Click to collapse
I saw you sign on. Did they ever answer my question about running the tool multiple times?
Sent from my ADR6425LVW using XDA
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
No,I won't change the title. To some folks its important to stay locked. I will try and clarify the op later today.
You don't need to unlock to install a recovery. It's easily permanently flashed via a PH98IMG,or fastboot booted via the jpbear patched hboots.
Sent from my ADR6425LVW using XDA
dmoses1969 said:
I was on the latest firmware and RezROM ICS. Performed S-OFF and never seen an option to install JB-Hboot so I didnt. At that time mine said UNLOCKED/TAMPERED.
Then after a couple of days of reading and trying to decide what to do next I decided to RUU down to the latest official and as soon as that was finished I went back to boot loader and it said LOCKED / S-OFF. I flashed the ENG Hboot with no issues and Now it says LOCKED / VIGOR PVT ENG S-OFF RL.
I also made a backup of RezROM before all this. Restored my backup, flashed the firmware patch, flashed PH that came with RezROM and rebooted and have had no issues at all.
I am not in a 4G area so I might actually have the issue others were having with 4G dropping out. Will have to wait and see.
Click to expand...
Click to collapse
I'm in the same situation. There's a thread here on how to fix it but I guarantee your 4G is whacked. I flashed back to a GB stock ROM then flashed an ICS ROM. Seemed to work okay when in my 3G only area but I visited a 4G area yesterday and it was just messed up. I flashed the latest GB RUU and did a reset from the stock hboot, flashed JuopunutBear hboot for GB, then AmonRa 3.15 and CleanROM DE. I'm going back to a 4G area tomorrow so if it doesn't work I'll post in that thread. Could just be me but everything about the phone seems better/cooler/faster after the RUU.
TheEnzyteGuy said:
I agree with scotty, my hboot says locked and I have s-off so far I have flashed everything except for ruu's. Even recoveries worked.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I've flashed JuopunutBear hboot (GB and ICS), eng hboot, stock hboot, AmonRa, a nandroid, and a few roms after locked/s-off and have had no problem. Just flash eng or juopunutbear hboot before flashing recovery and you're good to go.
Edit: I was on the appropriate firmware when flashing the GB and ICS hboots.
Recovery can still be flashed as a PH file on the regular HBOOT.
D
HTC having last laugh?
Sent from my ADR6425LVW using xda premium
Hi,
i unlocked my Evo 3d the HTCdev.com way, al working fine and in tried to flash a new rom through CWM recovery (LeeDrOiD_3D_V5.3.0)
Now my unit is staying in a bootloop, the white HTC screens pops up for a few seconds and boots throught to the LeeDrOid bootscreen, you hear the sound for a second and it reboots again.
I Already tried to flash the boot.img extracted from the LeeDrOid manually, but it stays the same.
Did i overlooked something? Did i brick my unit? I dont know...
The following numbers pop up when i boot in the bootloader:
***Unlocked****
SHOOTER-U PVT SHIP S-ON RL
HBOOT-1.53.0007
eMMC-boot
Radio: 11.25.3504.06
What to do? Or do i have a fancy paperweight now?
I think its because you are trying to flash a gingerbread rom. AFAIK its not possible to boot GB on 1.53 hboot. I would suggest trying an ICS rom
So i installed Yoda's ICS v5.1 and now the unit only boots till the white HTC screen and reboots on and on...
maybe if you list the things you tried i could help you more.
factory reset and wipe cache+delvik cache before installing rom?
manually flashed boot.img?
i would suggest getting s-off to save yourself all the hassle
How do i install S-OFF when i cannot fully boot the unit?
Yes, i tried to install Boot.img manually through ABD, but issue still persists.
S-off isnt something to install. I'd recommend you run an RUU and get beck to stock. After that look in the gsm development section you will find a thread for s-offing your phone. It involves the wire trick.
Sent from my HTC EVO 3D X515m
Which RUU should i download, which one do you recommend? And i can do this while connected with Fastboot, isnt it?
http://www.filefactory.com/file/c0a...00_10.13.9020.08_2M_release_203403_signed.exe
Sent from my HTC EVO 3D X515m
I had the very same issue, see my post here for some help http://forum.xda-developers.com/showthread.php?t=1897719
I think your hboot is the key; if your unlocked through HTC while on a GB rom then you are limited to GB roms, if you want ICS, you need to re lock, ruu the stock ICS rom, then unlock, then install the custom ICS rom.
I'm no expert but that seemed to fix my issue, i did take the extra step and get S-off, so i truly get full control of my phone.
His hboot is 1.53 which means he did update to ics. Relocking his bootloader and running an RUU should get him to boot into stock rom. Then maybe he can s-off.
There are so many people with 1.53 hboot having problems with every single rom. I didnt take the ota for this exact reason. Revolutionary hboot hasnt given me trouble with any rom.
Sent from my HTC EVO 3D X515m
EM|NEM said:
His hboot is 1.53 which means he did update to ics. Relocking his bootloader and running an RUU should get him to boot into stock rom. Then maybe he can s-off.
There are so many people with 1.53 hboot having problems with every single rom. I didnt take the ota for this exact reason. Revolutionary hboot hasnt given me trouble with any rom.
Click to expand...
Click to collapse
I just checked the unlimited.io (JBear) website and their modified bootloader for the Evo 3D GSM on ICS is 1.53.5353 so it seems like they support the wire trick with the ICS update, but I agree that it would be better to start by flashing the ICS RUU.exe then HTC unlock and root before doing JuopunutBear.
ramjet73
Phone boot loops
guys please i need your help.
my phone always restarts after booting. its HTC EVO 3D GSM WITH HBOOT 1.53.0007
i have already rooted the phone but its on S-ON.
USB DEBUGGING is not turned on and i don't have recovery installed.
am completely lost cos am new on this. My phone has been out of service for almost 5 months now please someone should
help me cos am going crazy here.
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
Remove/replace the battery and restart the bootloader and try flashing the RUU again. If that doesn't work you can try flashing the RUU.exe from Windows with the bootloader in "fastboot USB" mode.
ramjet73
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
one thing i have learned is when flashing roms, make sure you have the correct firmware package, and hboot.. because some Roms use the VM Firmware from the leak a few months back, while others use the Sprint Firmware, also depending on the base of the rom you may need to flash a newer or older hboot
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
wloftus said:
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
Click to expand...
Click to collapse
I agree about being s-off, but the ruu.exe will error out if the bootloader is unlocked. You must relock the bootloader first.
coal686 said:
I agree about being s-off, but the ruu.exe will error out if the bootloader is unlocked. You must relock the bootloader first.
Click to expand...
Click to collapse
i use linux so i dont do the EXE's... i take the RUU and rename it to PG86IMG.zip and it still works unlocked or not... just different approaches depending on the OS you use i guess
wloftus said:
i use linux so i dont do the EXE's... i take the RUU and rename it to PG86IMG.zip and it still works unlocked or not... just different approaches depending on the OS you use i guess
Click to expand...
Click to collapse
That should be the same thing as long as the RUU.zip is extracted from the RUU.exe and properly signed.
But coal is right about needing the bootloader locked/relocked to flash the RUU if you are S-ON (which the OP said he is), regardless of whether you use the RUU.exe or RUU.zip.
ramjet73
ramjet73 said:
That should be the same thing as long as the RUU.zip is extracted from the RUU.exe and properly signed.
But coal is right about needing the bootloader locked/relocked to flash the RUU if you are S-ON (which the OP said he is), regardless of whether you use the RUU.exe or RUU.zip.
ramjet73
Click to expand...
Click to collapse
no he is not...ive reloaded GB and ICS manually while being unlocked you cant tell me what i have and have not done considering IM the one thats done it
wloftus said:
no he is not...ive reloaded GB and ICS manually while being unlocked you cant tell me what i have and have not done considering IM the one thats done it
Click to expand...
Click to collapse
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
Click to expand...
Click to collapse
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
ramjet73 said:
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
Click to expand...
Click to collapse
make up your mind you first said its the locked relocked status... now you say its the s-on , s-off status....if iive still done flashes with the s-on status and while still unlocked so i dont know what problems you all are running into
wloftus said:
make up your mind you first said its the locked relocked status... now you say its the s-on , s-off status....if iive still done flashes with the s-on status and while still unlocked so i dont know what problems you all are running into
Click to expand...
Click to collapse
I don't think so.
You really should try flashing an RUU (.exe or .zip) with radio S-ON and an unlocked bootloader before you advise other users to try that. If you can do that successfully I will admit I am wrong in this thread. Otherwise, please stop insisting that it will work.
You have been ignoring the fact that the OP is S-ON throughout this thread and that really isn't going to help him at all.
ramjet73
ramjet73 said:
I don't think so.
You really should try flashing an RUU (.exe or .zip) with radio S-ON and an unlocked bootloader before you advise other users to try that. If you can do that successfully I will admit I am wrong in this thread. Otherwise, please stop insisting that it will work.
You have been ignoring the fact that the OP is S-ON throughout this thread and that really isn't going to help him at all.
ramjet73
Click to expand...
Click to collapse
i have... i infact did it earlier with the upgrade to ICS while flashing the firmware.zip file after renameing it to PG86IMG.zip and WOW it worked... im done arguing ... this is my last post... post again if you feel you need the last word....
wloftus said:
im done arguing ... this is my last post... post again if you feel you need the last word....
Click to expand...
Click to collapse
Thank you. I will make one last post just so people are clear on the requirements for flashing an RUU with S-ON.
Here's a quote from mpgrimm2's My Running stock RUU Reference info post:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
That guide has been around for a long time on XDA and another website and it has been used by a lot of people, including myself. If that information was wrong, I'm sure mpgrimm2 would have corrected it by now.
If you want to flash an RUU with S-ON and an unlocked bootloader, make sure that you relock it before flashing or you will get an error.
ramjet73
wloftus, I'm not saying you're lying since as you said, you were the one who did it and you say it worked for you. But, if one is s-on and unlocked, the ruu will error out with error 155. I google searched ruu lock bootloader error and found many sites that say the bootloader must be locked if s-on (see below). But, if one wants to try while leaving the bootloader unlocked, then be my guest. If it works, great; if not, then relock the bootloader.
Sources:
Should I relock my bootloader
[HOW TO] Flash RUU / OTA when getting ERROR 155 although phone is back to stock
And one specific to the Evo3d: http://forums.androidcentral.com/htc-evo-3d/198402-ruu-2-89-651-2-hboot-1-58-a.html#post2084625
wloftus said:
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
Click to expand...
Click to collapse
Hey thanks for your comment, yes it says relocked but also Security Warning... do you know how can I remove this? so I can leave it locked again and try to reinstall the stock RUU?
ramjet73 said:
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
Click to expand...
Click to collapse
I agree with you... the probllem is that I cannot relock the cell phone... when I try I get the message relocked but also the message security warning!!
how can I remove it??
anonimoyque said:
I agree with you... the probllem is that I cannot relock the cell phone... when I try I get the message relocked but also the message security warning!!
how can I remove it??
Click to expand...
Click to collapse
There's a thread here that discusses, but people seem to have used various methods to solve it from restarting the bootloader to reflashing their unlock token. That's why I recommended in my first post of this thread that you remove/replace the battery and restart the bootoader.
ramjet73
I have my EVO HBOOt 1.53 (JopunutBear) S-off stock 4.0 rom. Now when i flash jb or ics custom roms i get a bootlop.
What can i do?
So have i to downgrade to hboot 1.49? If yes how to do this.
Yes i tried severyl things like http://forum.xda-developers.com/showthread.php?t=1906172&page=10 [ bootloader doesnt find pg86img.zip]
and other s-off guides but nothing really works
Thanks for help
Are you putting the pg file in the root of your sdcard or in a separate file folder?
( Don't ask me for help as I couldn't care if your phone explodes, eh! )
yes i put it in root. how big is the rigt pg file. i have one with about 324kb and one with about 300mb
luisniklas said:
yes i put it in root. how big is the rigt pg file. i have one with about 324kb and one with about 300mb
Click to expand...
Click to collapse
That one with about 384 kB. Then, turn off your phone, turn it on in bootloader (volume down + power on). Wait a little and it will ask you to update. Press volume up, and wait. After that you have to delete that PG file from sd card. (that pg 300 MB has a rom on it..thats why it is so big)
Sent from my EVO 3D GSM, using XDA Premium
If the bootloader doesn't find the zip, make sure it's named PG86IMG.zip (capitalization as is) and make sure there is no double zip extension.
Here my BL. It Doesnt find the small PG file.
Does it something has to do with my JoupunutBear HBOOT 1.52.7777
Are there other ways to downgrade hboot with s-off?
Can i flash JoupunutBear HBOOT 1.49 from unlimited.io?
Sent from my Nexus 7 using XDA Premium HD app
If you can boot into your ROM then just check whether your phone is recognizing data on your sdcard. Sometimes after the wire trick sdcards tend to flip out. Your pc might be detecting it fine but the phone might not. Just humor me and try playing a song or something from the card just to rule out this possibility
Sent from my Evo 3D GSM
i will try this. is hboot downgarde the only way to get custom roms working?
EDIT:SD works
What about cid for pg file? i have htc_102. i tried fastboot oem writecid 1111111 and htc_01 but nothing changed.
Cid shouldn't be a problem with the zip from that thread. Try running an RUU and then downgrading hboot
EM|NEM said:
Cid shouldn't be a problem with the zip from that thread. Try running an RUU and then downgrading hboot
Click to expand...
Click to collapse
A ics ruu? How too downgrade then?
Sent from my Nexus 7 using XDA Premium HD app
Solved it. Only flahed JB hb0ot 1.49 Form unlimited.io
@mods plus Close
Sent from my Nexus 7 using XDA Premium HD app
I have the same problem as you and I had. I need help, step by step. Do you just use HBOOT 1:49 and below = Gingerbread or you first installed the GB ruu, etc..
MeisterRoerich said:
I have my EVO HBOOt 1.53 (JopunutBear) S-off stock 4.0 rom. Now when i flash jb or ics custom roms i get a bootlop.
What can i do?
So have i to downgrade to hboot 1.49? If yes how to do this.
Yes i tried severyl things like http://forum.xda-developers.com/showthread.php?t=1906172&page=10 [ bootloader doesnt find pg86img.zip]
and other s-off guides but nothing really works
Thanks for help
Click to expand...
Click to collapse
If you are still having issues let me know. I have recently had the same problem as yourself.
With hboot 1.53 you can only run ICS ROMs but if you are not able to run ICS either I would use a 4EXT recovery then enable smart flash (I know this should only matter when s-on is worth a go) Also use fastboot to flash the boot.img from what ever ROM you have chosen just incase it's an issue with that.
PG86img.zip files are CID specific and need to be for your location and carrier (from my understanding) unless you have a super CID which is 11111111 (denoting a factory unlocked device, but don't quote me)
I too have a 1.53.0007 hboot and also am having trouble finding a solution to hboot changes once you are s-off with that hboot. How I got that hboot after gaining s-off is beyond me but it seems I am not alone and if that hboot can be put in it HAS to be able to change it. The easiest way that I can think of is to gain s-on (I haven't looked hard enough for that yet though) then to s-off again and make the hboot update that way.
by the way (now I can't find it's exact meaning and am choked) I was really surprised that the beer reference had more than just a catchy ring to it. Engineering something or other, I shoulda wrote it down
http://forum.xda-developers.com/showthread.php?t=1906172
the PG86IMG in this thread is compatible with all CIDs. as long as you are s-off you can change your hboot easily using this thread
EM|NEM said:
http://forum.xda-developers.com/showthread.php?t=1906172
the PG86IMG in this thread is compatible with all CIDs. as long as you are s-off you can change your hboot easily using this thread
Click to expand...
Click to collapse
Thank you so much. And now I'm able to flash jellybean ROMs I think I'll stick with the ICS one I am using (King Cobra, I think could be Cool though) as it is great on batteries and everything works great. And I get to freak people out with the creepy 3d camera. lol.
machv5 said:
If you are still having issues let me know. I have recently had the same problem as yourself.
With hboot 1.53 you can only run ICS ROMs but if you are not able to run ICS either I would use a 4EXT recovery then enable smart flash (I know this should only matter when s-on is worth a go) Also use fastboot to flash the boot.img from what ever ROM you have chosen just incase it's an issue with that.
PG86img.zip files are CID specific and need to be for your location and carrier (from my understanding) unless you have a super CID which is 11111111 (denoting a factory unlocked device, but don't quote me)
I too have a 1.53.0007 hboot and also am having trouble finding a solution to hboot changes once you are s-off with that hboot. How I got that hboot after gaining s-off is beyond me but it seems I am not alone and if that hboot can be put in it HAS to be able to change it. The easiest way that I can think of is to gain s-on (I haven't looked hard enough for that yet though) then to s-off again and make the hboot update that way.
by the way (now I can't find it's exact meaning and am choked) I was really surprised that the beer reference had more than just a catchy ring to it. Engineering something or other, I shoulda wrote it down
Click to expand...
Click to collapse
I just flashed hboot from joupnut bear
MeisterRoerich said:
I just flashed hboot from joupnut bear
Click to expand...
Click to collapse
I am assuming that your phone wasn't S-OFF at the time? I accidentally tried to S-OFF one of my EVO 3Ds (GSM) that was already S-OFF at the time and I got a "WOW!!! What are you doing. Your phone appears to be S-OFF already. Doing so again could result in impotence, and death" or words to that effect. Basically a gaudy do you want your phone to die type of a message. If your device was S-OFF to begin with I was not aware that you could use Juopunutupbear to change the HBOOT version without going through the whole S-OFF process. Can you give some more details as to your phones state (i.e., HBOOT version, S-ON or S-OFF, etc...) before you used juopunutupbear to change the HBOOT. Thanks
machv5 said:
I am assuming that your phone wasn't S-OFF at the time? I accidentally tried to S-OFF one of my EVO 3Ds (GSM) that was already S-OFF at the time and I got a "WOW!!! What are you doing. Your phone appears to be S-OFF already. Doing so again could result in impotence, and death" or words to that effect. Basically a gaudy do you want your phone to die type of a message. If your device was S-OFF to begin with I was not aware that you could use Juopunutupbear to change the HBOOT version without going through the whole S-OFF process. Can you give some more details as to your phones state (i.e., HBOOT version, S-ON or S-OFF, etc...) before you used juopunutupbear to change the HBOOT. Thanks
Click to expand...
Click to collapse
I s-OFFed my phone (Hboot 1.53 or sth.) with jouponut bear and then i flashed hboot 1,49.999 fro here: http://unlimited.io/jbhboots.htm
There is a thread about how exacly you can downgrade your hboot, maybe could be better explained but study the forum a bit more... I also had that problem and after two days searching and downloading all kinds of files I did it...
Sent from my Evo 3D GSM using xda app-developers app
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