Hi
begining statues of my phone:
my phone is one xl(evita) and relock , s-on then read more!
i did change cid of HTC__J15 to CW___001 and then s-on and relock the bootloader but now i can't unlock retry...!!
the old carrier was GCC but then relock is at&t !
please help me...
tnx
Why did you change it to the at&t CID? The at&t CID is blocked by htcdev. You need to go through the hassle of getting SuperCID so you can unlock your bootloader now. Plus, there's no advantage to having the at&t CID because you can't install any firmware from the standard Evita onto your middle eastern variant. This is a great example of why you shouldn't do anything when you don't know what you're doing. All of the information I've just given you is readily available in our forum hag you done some research. Anyway, what are your bootloader details?
Sent from my Evita
timmaaa said:
Why did you change it to the at&t CID? The at&t CID is blocked by htcdev. You need to go through the hassle of getting SuperCID so you can unlock your bootloader now. Plus, there's no advantage to having the at&t CID because you can't install any firmware from the standard Evita onto your middle eastern variant. This is a great example of why you shouldn't do anything when you don't know what you're doing. All of the information I've just given you is readily available in our forum hag you done some research. Anyway, what are your bootloader details?
Sent from my Evita
Click to expand...
Click to collapse
(bootloader) version-baseband: 3.12.38.00.24
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.01.401.03
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT2CTW303033
(bootloader) imei: 35437005019****
(bootloader) product: evita_utl
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8350000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3964mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b27b8968
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
my firmware version is 3.12 and i can't super cid with XPwn xploit and then unlock !!
What can I do to get My phone unlocking?
tnx
You can't do anything. You've gotten the phone to a point where it's impossible for you to unlock it now. You can't change the CID again because you're s-on. You can't use the usual way to get SuperCID because you don't have the 3.18 version installed. Why in the world did you do what you did?
Sent from my Evita
timmaaa said:
You can't do anything. You've gotten the phone to a point where it's impossible for you to unlock it now. You can't change the CID again because you're s-on. You can't use the usual way to get SuperCID because you don't have the 3.18 version installed. Why in the world did you do what you did?
Sent from my Evita
Click to expand...
Click to collapse
Would having his device j tagged help him. I think its pretty cheap to get done now , idk about in the middle east tho lol
Senseless Power Unlocked
timmaaa said:
You can't do anything. You've gotten the phone to a point where it's impossible for you to unlock it now. You can't change the CID again because you're s-on. You can't use the usual way to get SuperCID because you don't have the 3.18 version installed. Why in the world did you do what you did?
Sent from my Evita
Click to expand...
Click to collapse
yes , i know...
if i do super cid with XPwn xploit , My phone is bricked?
DESERT.TECH said:
Would having his device j tagged help him. I think its pretty cheap to get done now , idk about in the middle east tho lol
Senseless Power Unlocked
Click to expand...
Click to collapse
The problem is I doubt they have the correct stuff for the middle eastern variant.
Master King said:
yes , i know...
if i do super cid with XPwn xploit , My phone is bricked?
Click to expand...
Click to collapse
Maybe. But I think it just won't work. You can take the risk and try but if it was me I wouldn't.
Sent from my Evita
timmaaa said:
The problem is I doubt they have the correct stuff for the middle eastern variant.
Maybe. But I think it just won't work. You can take the risk and try but if it was me I wouldn't.
Sent from my Evita
Click to expand...
Click to collapse
ok
now can i install RUU from at&t brand for upgrade frimware & then super cid?
As an example:
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe
I don't know if it's safe. I've seen at least one person brick their phone by installing firmware from the standard Evita onto the middle eastern variant.
Sent from my Evita
What should I do now?
I want to unlock...
please help me
Well first I'd edit out the imei from the post about your bootloader settings..
Like timmaaa said, you're at a point where you have very little options. You could try XPwn or RUU but it's a huge risk. See, this is why you read...so you don't do things like this...
Sent from my One X using Tapatalk
You can't, that's what I've been trying to tell you. The things you've done to your phone have made it impossible.
Sent from my Evita
Related
I've bought a phone which has S-OFF, ***LOCKED***, which I'm trying to root. I've seen many guides, read them but they are all from the point you have S-ON. I've tried manual ADB install of CWM but that fails, permission denied.
Any advice before I brick it ? The phone seems to be in a quasi state...not sure how I progress.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3963mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
are you sure you are S-OFF? If so, you can try a pre-rooted rom.(Flash a recovery first)
http://forum.xda-developers.com/showthread.php?t=1183684
Have the same problem. It says ***Locked*** S-OFF. Don't know what to do. Before made RUU I have rooted my phone succesfully (one click root), but now can't do that in the same way. ;/
I wasn't sure if S-OFF was really off but everything I tried was failing. This was from a Win7 64 bit, I switch to Win7 32bit PC and SuperOneClick worked then!
I've got root, CWM recovery installed and all sorted so thank. Not sure why 64bit Windows 7 was causing a problem, nothing indicated it was but a 32 bit pc everything worked perfectly.
How you switch to windows 32bit?
Generally, when S-OFF, the only thing needed to be able to do just about anything - is to use a special PG88IMG.ZIP that includes latest reengineered bootloader and custom recovery.
I'm not sure if there is one in this forum, but it's easy to create.
Jack_R1 said:
Generally, when S-OFF, the only thing needed to be able to do just about anything - is to use a special PG88IMG.ZIP that includes latest reengineered bootloader and custom recovery.
I'm not sure if there is one in this forum, but it's easy to create.
Click to expand...
Click to collapse
Where could I get this? Or how it is called? Because I have no clue what I need to enter in google.
To begin with, search for PG88IMG.ZIP to understand, what it is and what it does.
You need to unlock the bootloader, the ***locked*** indicates its still locked. Use HTCDev or some other tool to unlock your bootloader. Not sure how S-off works for this phone, it might have just been re-locked, so try "fastboot oem unlock" i think is the command and it should unlock
Then you can flash a recovery image and then flash a zip file containing the su binary and app via recovery
Sent from my HTC One X using Tapatalk 2
Just flash a ROM from the INDEX
Do you have a custom recovery?
Swyped from my DesireS
stumpyz9 said:
You need to unlock the bootloader, the ***locked*** indicates its still locked. Use HTCDev or some other tool to unlock your bootloader. Not sure how S-off works for this phone, it might have just been re-locked, so try "fastboot oem unlock" i think is the command and it should unlock
Then you can flash a recovery image and then flash a zip file containing the su binary and app via recovery
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Please, do not give suggestions when you don't know how things work - see the bold part of your own post. You wouldn't want someone that doesn't know exactly how motor works to fix your car, would you?
If he has S-OFF, there is no need to unlock bootloader and void warranty. Moreover, having S-OFF is better and more powerful than having unlocked bootloader. All the info is in the stickies, and you should go read them too.
Jack_R1 said:
Please, do not give suggestions when you don't know how things work - see the bold part of your own post. You wouldn't want someone that doesn't know exactly how motor works to fix your car, would you?
If he has S-OFF, there is no need to unlock bootloader and void warranty. Moreover, having S-OFF is better and more powerful than having unlocked bootloader. All the info is in the stickies, and you should go read them too.
Click to expand...
Click to collapse
Dont talk to me like i dont know what im talking about. Ive rooted and messed with plenty of phones. I based my advice off of my experience. Just because i dont know all of the specifics of a particular device doesnt really matter, all of HTCs devices operate basically the same. So maybe you shouldnt be worried about me and more worried about helping this guy like everyone else is. Its not up to you to decide if he wants to take my advice or not, thats for him to decide.
Sent from my HTC One X using Tapatalk 2
stumpyz9 said:
Dont talk to me like i dont know what im talking about. Ive rooted and messed with plenty of phones. I based my advice off of my experience. Just because i dont know all of the specifics of a particular device doesnt really matter, all of HTCs devices operate basically the same. So maybe you shouldnt be worried about me and more worried about helping this guy like everyone else is. Its not up to you to decide if he wants to take my advice or not, thats for him to decide.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You basically wrote that you don't know what you're talking about, and by suggesting to unlock bootloader on S-OFF phone you made it obvious beyond any doubt. Indeed, all of HTC devices operate the same, all of HTC devices have bootloader security, all of them more or less since eMMC introduction block write access to /system in bootloader, all of them can be unblocked by turning S-OFF or unlocking the bootloader.
Unlocking the bootloader voids the warranty and prevents /boot from being flashed from recovery, subjecting the user to constant kernel flashing through FASTBOOT for any ROM he wants to flash, while S-OFF allows full and undisturbed recovery functionality. Thus, bootloader unlock is inferior solution that should be avoided if possible, and suggesting it for a phone that already has S-OFF is BAD/not smart/pick whatever negative adjective you want.
Of course, all that is written in stickies, as I said, but I guess that you can't be bothered reading before writing, and when suggested to do so, prefer going all defensive. Yes, you don't know what you're talking about. I'm glad you rooted zillion devices, if you think it makes you know everything - read the info above again.
I already did my part to help the guy, and I don't have enough time for people that want everything laid out for them. If he's willing to use some Google and read - he'll get to his solution using my pointer, or somebody will point him to the relevant guide (and there is one in INDEX thread, AFAIK). The old debate of giving someone a fish vs teaching him fishing. I picked my side a long time ago.
Guys, don't be angry at each other
Thank you, you both helped me a lot. Big thanks )
Rooted my phone. If it's interesting I can tell how
NX3 said:
I've bought a phone which has S-OFF, ***LOCKED***, which I'm trying to root. I've seen many guides, read them but they are all from the point you have S-ON. I've tried manual ADB install of CWM but that fails, permission denied.
Any advice before I brick it ? The phone seems to be in a quasi state...not sure how I progress.
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.401.8
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3963mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Lucky!
Looks like you're S-OFF'd and have SuperCID, which means you should be able to install any rom you like.
If I'm guessing correctly you have ENG hboot 2.00?
Just ignore the ***Locked***, as you're S-OFF'd you should do anything. How did you try to flash cwm?
Fastboot flash recovery?
(bootloader) version-bootloader: 2.00.0002
(bootloader) cidnum: 11111111
(bootloader) security: off
Click to expand...
Click to collapse
It looks like a xtcclip s-off so you've got a permanent s-off regardless which hboot you use.
Hi guys, i have the same problem. I'm *****Locked***** but s-off, so i made this: http://forum.xda-developers.com/showthread.php?t=1525100 but as i'm s-offed i don't need the 2nd pass (i think).. so in 3rd pass when i make this, the cmd tells me that im not allowed to install the recovery. What's wrong?
Read the answer in your original thread
i have a sensation 4g that I had rooted , super cid, and s-off using revolutionary method ,i'm thinking i have a wrong s-on / soft brick maybe that returned my phone to s- on but still rooted and super cid , I have tried the junopbear s-off method , various ruu , and everything else I could find after doing much research with no luck , in the process i lost super cid and now have T-MOB010 cid with htc unlock and rooted .
the problem I think I have had trying to run a ruu to just put back to stock is that I have hboot 1.29 with version 1.50.531.1 and cid T-MOB010 and cannot find a ruu that will match those or update without an error
version: 0.5
(bootloader) version-bootloader: 1.29.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.50.531.1
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3868mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 705f86f6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
any ideas or help on how to either s-off or return to stock and start from scratch would be appreciated
(I have tried kgs , all in one toolkit, control bear windows and linux in a virtual box, various ruu 3.33,1.50,3.32, all error , control bear says cowardly refusing to s off error code B2 B6 41 C9 have flashed stock rooted ics with stock recovery and with 4ext touch with smart flash )
try this ruu
http://hotfile.com/dl/147174878/5c8...0.14.9035.01_M_release_223976_signed.exe.html
or this one
http://shipped-roms.com/download.ph...0U_11.23.3504.07_M2_release_256085_signed.exe
also what error do you have when using ruu.exe?
rzr86 said:
try this ruu
http://hotfile.com/dl/147174878/5c8...0.14.9035.01_M_release_223976_signed.exe.html
or this one
http://shipped-roms.com/download.ph...0U_11.23.3504.07_M2_release_256085_signed.exe
also what error do you have when using ruu.exe?
Click to expand...
Click to collapse
yeah I have tried both of those and I get error 155
also have run as admin and tried PG58IMG.zip method
also I had unlocked the phone so it is a t-mobile but has a strait talk (t-mobile) sim , before I lost s-off i had flashed a PG58IMG that had hboot 1.29.000 , firm 3.33.401.106 , radio 11.76c.3504.00p_11.29A.3504.18_M_PG58IMG so not sure why version changed to 1.50.531.1
was fine till I was messing around with partitioning my sd a couple days later had to pull the battery and when I turned it on it went to bootloader with locked bootloader and s on
watters33 said:
yeah I have tried both of those and I get error 155
also have run as admin and tried PG58IMG.zip method
also I had unlocked the phone so it is a t-mobile but has a strait talk (t-mobile) sim , before I lost s-off i had flashed a PG58IMG that had hboot 1.29.000 , firm 3.33.401.106 , radio 11.76c.3504.00p_11.29A.3504.18_M_PG58IMG so not sure why version changed to 1.50.531.1
was fine till I was messing around with partitioning my sd a couple days later had to pull the battery and when I turned it on it went to bootloader with locked bootloader and s on
Click to expand...
Click to collapse
error 155 AFAIK is a connection issue
when you connect the device to pc from bootloader before using the ruu.exe in the hboot screen must say fastboot usb
did you check that?
Yes always made sure it said fastboot usb
Sent from my HTC Sensation 4G using xda app-developers app
watters33 said:
Yes always made sure it said fastboot usb
Sent from my HTC Sensation 4G using xda app-developers app
Click to expand...
Click to collapse
Hmm,
Then see if your bootloader says locked or relocked
If it is unlocked you must relock it
Sent from my HTC Sensation Z710e using xda premium
rzr86 said:
Hmm,
Then see if your bootloader says locked or relocked
If it is unlocked you must relock it
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
yes I relocked it to run the ruu tried unlocked and relocked with 4ext recovery and stock recovery
watters33 said:
yes I relocked it to run the ruu tried unlocked and relocked with 4ext recovery and stock recovery
Click to expand...
Click to collapse
give a try with these drivers
http://forum.xda-developers.com/showthread.php?p=36523572
http://d-h.st/v0p
http://forum.xda-developers.com/showthread.php?t=1668276&highlight=tool (second post->old info(click to show content and you will see somewhere a link for htc drivers)
try each one and see if you have success with ruu installation
Hi all,
I successfully unlockes, rooted and S-off my Sensation XE and I think I also SIM-unlocked the phone.
To be able to do this, I had to downgrade my bootloader from 1.29.0000 to 1.17.000 to be able to S-Off it.
I also restored the original backup from the SD card. I never had any errors.
The poblem now is that the phones gets into endless cycles of rebooting and I'm not able to switch it on. I can still asily get into the bootloader. I think the problem lies in the Bootloader version and I tried to find my phone's up-to-date hboot version (I guess it has to be 1.29.1111 now). Any help would be highly appreciated. Links and easy explanation as I'm still a noob please.
Many thanks.
Output of my fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.17.1111
(bootloader) version-baseband: 10.14.9035.01_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.45.531.1
(bootloader) serialno: ********************
(bootloader) imei: *******************
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG58*****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3800mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 92e53710
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
wmgamd said:
Hi all,
I successfully unlockes, rooted and S-off my Sensation XE and I think I also SIM-unlocked the phone.
To be able to do this, I had to downgrade my bootloader from 1.29.0000 to 1.17.000 to be able to S-Off it.
I also restored the original backup from the SD card. I never had any errors.
The poblem now is that the phones gets into endless cycles of rebooting and I'm not able to switch it on. I can still asily get into the bootloader. I think the problem lies in the Bootloader version and I tried to find my phone's up-to-date hboot version (I guess it has to be 1.29.1111 now). Any help would be highly appreciated. Links and easy explanation as I'm still a noob please.
Many thanks.
Click to expand...
Click to collapse
Hi,
If you can get into bootloader,can you please post what it says there?
malybru said:
Hi,
If you can get into bootloader,can you please post what it says there?
Click to expand...
Click to collapse
Thanks for the quick reply. It says:
-Firmware-1.17-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011,22:31:39
wmgamd said:
Thanks for the quick reply. It says:
-Firmware-1.17-
Pyramid PVT SHIP S-OFF RL
HBOOT-1.17.1111
RADIO-10.14.9035.01_M
eMMC-boot
Jun 2 2011,22:31:39
Click to expand...
Click to collapse
Hi,
You are on GB.
Follow THIS THREAD in order to update your firmware and recovery.
Then, flash a new ROM.
malybru said:
Hi,
Follow THIS THREAD in order to update your firmware and recovery.
Then, flash a new ROM.
Click to expand...
Click to collapse
Thanks. Will do and keep you posted with the results.
Success. :good:
All I needed was the firmware update. My old ROM is back and working.
Thanks a million. you're a star.
wmgamd said:
Success. :good:
All I needed was the firmware update. My old ROM is back and working.
Thanks a million. you're a star.
Click to expand...
Click to collapse
how did you downgrade from hboot 1.29 to 1.17?
boyriot said:
how did you downgrade from hboot 1.29 to 1.17?
Click to expand...
Click to collapse
you can downgrade when you are on S-OFF
boyriot said:
how did you downgrade from hboot 1.29 to 1.17?
Click to expand...
Click to collapse
Hi, I used the same link in the begining of this post, added by malybru and downloaded the firmware 1.17 initially and flashed it. I then followed this link:
http://forum.xda-developers.com/showthread.php?t=1864053 (only the S-off section though as I've rooted and unlocked my phone earlier via HTCDev.com). Then I restored the backup.
when it didn't work as decribed in the begining of my post, I downloaded the newest firmware, but my mistake was that I left the old file (1.17) in the download folder on my pc which led to automatic addition of ''(1)'' to the end of the newest firmware file name. this led to the phone not seeing it as a firmware file and hence not using it.
When Malybru posted the same link, I had more confidence in the file and retried the file 1 more time and this time, I noted the change to the firmware name and corrected it. It all work like a charm.
Good luck.
rzr86 said:
you can downgrade when you are on S-OFF
Click to expand...
Click to collapse
but the OP said, he had to downgrade first before to be able to S-Off it.
so that mean, he was S-ON when downgrading right?
boyriot said:
but the OP said, he had to downgrade first before to be able to S-Off it.
so that mean, he was S-ON when downgrading right?
Click to expand...
Click to collapse
i just read again the OP
you are right
OP how did you downgrade while on S-ON?
rzr86 said:
i just read again the OP
you are right
OP how did you downgrade while on S-ON?
Click to expand...
Click to collapse
Sorry for the confusion. On careful recounting the steps I took, I did indeed S-off it first, using the link in my last post before being able to downgrade. The reason I downgraded was because when using the file PG58DIAG.nbh, I used to get an error msg about S-OFF, so I S-offed it but I kept getting the same error msg; so when researched online, I noticed that another cause for this error could be the wrong firmware so then I had to downgrade...
So I guess you're right rzr86.
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
IIRC the RUU for your device reverts all of that. Not 100% sure about the S-ON though.
I've read somewhere in another guild that it's necessary to first Relock your bootloader (using the oem lock command) and afterwards use the right RUU for your device...
I thought this could be helpful
Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader first will cause this to not be the case?
DRUMROT said:
Thanks for the tips.
Since I'm super cid, I can flash any RUU at this point. Any idea if locking my bootloader it first will cause this to not be the case?
Click to expand...
Click to collapse
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself
FantasyGamer said:
I think to get S-OFF you have to use for example the All-in-one toolkit, I don't think relocking your bootloader will cause a S-on... But I think others may have more info about that. Planning on running an RUU for the first time myself
Click to expand...
Click to collapse
Yeah, I'm assuming I'd have to do some more then just run the RUU.
I'd gladly give it a go but like I posted earlier, I'd like to know if there is a certain order to do this in. If I run the RUU before removing s-off, will that make things easier? Harder? No different?
Anyone?
Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.
FantasyGamer said:
Personally, I think it's easier to first run the RUU and then go back to S-ON, because while you're S-OFF you won't have problems with the RUU for your CID, and the All-in-one kit says that you need to run stock Rom and stock recovery before you can S-OFF. So actually, I don't think it's recommended first going S-ON and then running an RUU.
Click to expand...
Click to collapse
Hmmm, all right. I've never used the all-in-one kit but I've noticed it has a "back to s-on" function so I'll give it a try. I'm on Linux so I need to run it in Wine (Windows emulator) so hopefully there's no hiccups.
DRUMROT said:
My phone has been having audio issues and I've ruled out everything on the software side.
Going to send it to HTC but I need to get back to stock obviously. Is there a specific order I should do these in? How does one get back to s-on? I assume removing super cid would be just like getting it only change the cid to HTC_001 or whatever, right?
How do I unroot?
And then of course I need to relock the bootloader, which if I'm not mistaken is as simple as running fastboot oem lock, right?
I basically need a step by step guide. I've searched around but haven't found everything exactly as I need it. Perhaps this could become a useful thread for others, with everything in one place.
Any help would be great, thanks in advance.
Click to expand...
Click to collapse
1)If you have put on a modified HBoot (such as to remove tampered or red warning) return to stock.
(only added this because if you S-on with modified HBoot it will brick your phone)
2)Run RUU.exe
3)Reset lock status flag
http://forum.xda-developers.com/showthread.php?t=2155955
4)S-ON your phone
http://androidforums.com/one-s-all-...-get-back-stock-moonshine-facepalm-s-off.html
---------- Post added at 01:15 PM ---------- Previous post was at 01:05 PM ----------
Edited that, If anyone notices a problem please post.
So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)
FantasyGamer said:
So, little question for myself.
Do I need to first Relock my bootloader?
Or can I just go and run an RUU? (I'm S-OFF)
Click to expand...
Click to collapse
No, it doesn't need to be locked when S-OFF.
The most important is running the RUU that matches your CID. (since you are s-off it is easy to change the CID to whatever you want, and thus run whatever RUU you want)
i have bought a used htc one s and it had sense 5.5 based JB4.2.2 rom but i want to downgrade to stock firmware. kindly tell me which RUU i should use and how should i procede.
HBOOT shows tampered, unlocked and S-ON
and here is other details
Code:
sudo fastboot getvar all
[sudo] password for hasan:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.11.50.05.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH267W
(bootloader) imei: 35990
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: VODAP304
(bootloader) battery-status: good
(bootloader) battery-voltage: 4111mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-64bedd38
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
I tried RUU RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4 on windows 8.1 64bit but it is not detecting the phone at all
currently I am on linux so i hope you guys can suggest something relevant
thanks a lot
Hi, I got the SIM unlock code from my carrier for my HTC One S but it doesn't appear to work. It's also a lot shorter than the code I used on my Xperia Z1 (same carrier) but they say that it's supposed to be valid.
My HTC One S has the bootloader unlocked and CyanogenMod 10.2 installed on it. Could not having a locked bootloader and stock ROM be the reason the unlock code doesn't work?
Thanks!
polybius said:
Hi, I got the SIM unlock code from my carrier for my HTC One S but it doesn't appear to work. It's also a lot shorter than the code I used on my Xperia Z1 (same carrier) but they say that it's supposed to be valid.
My HTC One S has the bootloader unlocked and CyanogenMod 10.2 installed on it. Could not having a locked bootloader and stock ROM be the reason the unlock code doesn't work?
Thanks!
Click to expand...
Click to collapse
You probably need the non modified stock firmware installed.
BTW you can also unlock it for FREE
Well, I did get the code for free
Yeah, I've been trying to restore everything to stock to find out but I'm having problems with that also. Perhaps I'll try the link you posted to verify the code. Maybe it's slightly different. Thanks!
Well, the code is the same, guess it just won't unlock without being stock ROM or something and I can't get it back to stock
polybius said:
Well, the code is the same, guess it just won't unlock without being stock ROM or something and I can't get it back to stock
Click to expand...
Click to collapse
Why can't you get it back to stock?
Any of the guides I follow don't seem to work. I relock the bootloader but then I can't seem to apply the matching RUU for the phone. What looks like the matching one (hboot and radio) is a ZIP file (OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip) and I'm not sure how to apply it. The exe RUU versions don't work either because, I'm assuming, they don't match my hboot and radio. I feel like a pretty competent guy when it comes to rooting and imaging Android devices but this just isn't working for me Thanks for your help.
polybius said:
Any of the guides I follow don't seem to work. I relock the bootloader but then I can't seem to apply the matching RUU for the phone. What looks like the matching one (hboot and radio) is a ZIP file (OTA_Ville_U_JB_45_S_TELUS_WWE_3.16.661.4_1.13.50.05.31_10.30.50.08L_release_307532nohrvy5j6i2o2i8i.zip) and I'm not sure how to apply it. The exe RUU versions don't work either because, I'm assuming, they don't match my hboot and radio. I feel like a pretty competent guy when it comes to rooting and imaging Android devices but this just isn't working for me Thanks for your help.
Click to expand...
Click to collapse
May you type in commandline:
fastboot getvar all
and post all values except your imei here?
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT26EW403840
imei: xxxxxxxxxxxxxxxxxx
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: TELUS001
battery-status: good
battery-voltage: 4146mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.068s
polybius said:
version: 0.5
version-bootloader: 2.15.0000
version-baseband: 1.13.50.05.31
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT26EW403840
imei: xxxxxxxxxxxxxxxxxx
product: vle
platform: HBOOT-8960
modelid: PJ4011000
cidnum: TELUS001
battery-status: good
battery-voltage: 4146mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-64bedd38
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.068s
Click to expand...
Click to collapse
Flash Viper 2.2 as sense base stock rom.
Use rumrunner to gain S-OFF
Flash any RUU you like
Thanks! I'll give that a try. I read you need SuperCID for S-OFF, does rumrunner do that for you?
polybius said:
Thanks! I'll give that a try. I read you need SuperCID for S-OFF, does rumrunner do that for you?
Click to expand...
Click to collapse
Rumrunner will get you S-OFF. Then you can change the CID.
Perhaps you know, I'm getting this when I try to image that Viper ROM.
assert failed: getprop("ro.product.device") == "ville"
Click to expand...
Click to collapse
polybius said:
Perhaps you know, I'm getting this when I try to image that Viper ROM.
Click to expand...
Click to collapse
Try to first flash the included boot.img before flashing Viper 2.1.0
or try try Viper 3
You need any sense based rom to get S-OFF
Ok, so, I guess I missed the part of installing Viper where it says to have TWRP and not ClockworkMod recovery >_<
Got TWRP on there, was able to flash Viper 2.1 EASILY. And it unlocked like a charm. THANKS!! Didn't have to get S-OFF for the unlock. What ROM is the best for the One S in your humble opinion? Should I still get S-OFF?
polybius said:
Ok, so, I guess I missed the part of installing Viper where it says to have TWRP and not ClockworkMod recovery >_<
Got TWRP on there, was able to flash Viper 2.1 EASILY. And it unlocked like a charm. THANKS!! Didn't have to get S-OFF for the unlock. What ROM is the best for the One S in your humble opinion? Should I still get S-OFF?
Click to expand...
Click to collapse
S-OFF means you can flash any stock RUU e.g unbranded and flash any radio version e.g. 1.20 and the kernel (boot.img) get flashed with the rom via recovery and has not to be flashed by fastboot command.
I actually use Candy 5 v1.5.0 but I can't say what fits your needs best
Does Candy have decent battery life? What is your general experience with it? I really want to put Lollipop on this phone
Also, do you have a good tutorial to remove the red Dev warning on boot?
polybius said:
Also, do you have a good tutorial to remove the red Dev warning on boot?
Click to expand...
Click to collapse
Battery performance is very good for me with Candy 5. I use my phone mainy for messaging and making calls (Its a phone lol). I can't say how long last the battery when you play games or surf the web heavily. For me the battery easy lasts two days.
For getting rid of the red warning you can flash a modded HBoot which can be found HERE. Make sure you use the same version number that is actually installed on your phone but "modded"
LS.xD said:
Battery performance is very good for me with Candy 5. I use my phone mainy for messaging and making calls (Its a phone lol). I can't say how long last the battery when you play games or surf the web heavily. For me the battery easy lasts two days.
For getting rid of the red warning you can flash a modded HBoot which can be found HERE. Make sure you use the same version number that is actually installed on your phone but "modded"
Click to expand...
Click to collapse
Hmmm. I have 2.15 but I seem to be getting an error during the flash: FAILED (remote: 41 model id check fail)
Is that the variance in model that you mentioned earlier?
polybius said:
Hmmm. I have 2.15 but I seem to be getting an error during the flash: FAILED (remote: 41 model id check fail)
Is that the variance in model that you mentioned earlier?
Click to expand...
Click to collapse
Seems so And I don't know how to solve it for PJ4011000. May be you can ask or look in the thread if somebody has successfully done it for your model. You probably can edit the flashable file, but I you should NOT try it, if you not exactly know how.