Related
So I bought a One S from craigslist about 2 weeks ago. The guy said it was a dev phone. At the top on the case is a tag of numbers and letters printed on the phone. When I first boot the phone it has a HTC splash screen along with the text
"This build is for development purposes only. Do not distribute outside of HTC without HTC's permission. Failure to comply may lead to legal action."
Booting into the bootloader I get this:
*** LOCKED ***
VLE XC SHIP S-OFF RH
CID-11111111
HBOOT-0.90.0000
RADIO-0.14.31.22_2
OpenDSP-v10.1.0.31.0221
eMMC-boot
Feb 21 2012,14:27:31
HBOOT
<VOL UP> to previous item
<VOL DOWN> to next item
<POWER> to select item
FASTBOOT
RECOVERY
FACTORY RESET
CLEAR STORAGE
SIMLOCK
IMAGE CRC
SHOW BARCODE
Also it came with CWM 5.8.1.5 already installed. I tried to use Hasoon's tool to install a more recent CWM but it wouldn't work.
I tried to unlock the bootloader using the htcdev site and token and that didn't work.
I was able to flash it with the UTB ROM using the existing CWM and it works but I cannot gain root access even though supersu is installed and I add apps to its list.
Any ideas on how to get root access?
Looking at your HBOOT version it seems like the device is on early software. You're already S-OFF, so you can try flashing the official TMO release ROM and follow the guides on XDA to root.
hammondnav said:
Looking at your HBOOT version it seems like the device is on early software. You're already S-OFF, so you can try flashing the official TMO release ROM and follow the guides on XDA to root.
Click to expand...
Click to collapse
I don't see the official release. There is a thread here that says T-Mobile USA Complete Rom but there's no link to the actual ROM.
I thought reselling of these phones can land u into trouble ?
I mean the development phones
what about busybox? there's an app to install that if you don't have it
Sent from my Kindle Fire using xda premium
dude thats awesome
post us some pictures of the phone and the HBOOT menu
If you are S-OFF and supercid, the possibilities are endless... flash an ruu, that should bring you upto date with the latest firmware and software..
azzledazzle said:
dude thats awesome
post us some pictures of the phone and the HBOOT menu
If you are S-OFF and supercid, the possibilities are endless... flash an ruu, that should bring you upto date with the latest firmware and software..
Click to expand...
Click to collapse
it wont let me post my photo album because i am still new so i am pm'ing you the link. what are some things i can do with this phone? i'm still a noob but a quick learner. so far i've only flashed a couple of roms. currently using black dragon's. still haven't gotten root access though.
dannyy2200 said:
it wont let me post my photo album because i am still new so i am pm'ing you the link. what are some things i can do with this phone? i'm still a noob but a quick learner. so far i've only flashed a couple of roms. currently using black dragon's. still haven't gotten root access though.
Click to expand...
Click to collapse
You could talk to the devs in the development section (as soon as you have your 10 posts) und help them to get s-off with providing informations maybe.
yeah man that would be a great idea, PM some and see if you can help them as for getting the bootloader unlocked, Unless HTCdev isnt working, there isnt much else yet.
why does it not work ? what errors does it give ?
hmm seems that I'm lacking some knowledge ^^
Is there any necessesity for unlocking the bootlaoder if the device already has s-off? Thouht that s-off would mean no security and full system access.
S-OFF means the NAND partition is writeable, When its S-ON this partition is locked (Security ON ), so with S-OFF we can customise even further, Flashing Radio.IMGs and lots more,
With unlocked bootloader we can do things like install a recovery and flash Root.
the perfect scenario would to have S-OFF AND Unlocked Bootloader.
azzledazzle said:
S-OFF means the NAND partition is writeable, When its S-ON this partition is locked (Security ON ), so with S-OFF we can customise even further, Flashing Radio.IMGs and lots more,
With unlocked bootloader we can do things like install a recovery and flash Root.
the perfect scenario would to have S-OFF AND Unlocked Bootloader.
Click to expand...
Click to collapse
Ah alright, I thought S-OFF would already allow to flash root.
nope usually when using an S-OFF tool, such as revolutionary, It will unlock bootloader at the same time..
surely theres someone out there can can do something really awesome with this developer phone !!
azzledazzle said:
yeah man that would be a great idea, PM some and see if you can help them as for getting the bootloader unlocked, Unless HTCdev isnt working, there isnt much else yet.
why does it not work ? what errors does it give ?
Click to expand...
Click to collapse
well it doesn't give me any errors, and says unlock successful, and just acts as if it went ahead and unlocked, but when i boot into the loader it still says locked. weird.
hmmmm..
maybe theres a command you can use in adb ? Im not sure..
I know the command to relock is ''fastboot oem lock'' maybe ''fastboot oem unlock'' might do something lol.
i have no idea as with most things in my life
Hello everyone.
I am new to this part of the forum for i just received a somewhat non working AT&T HTC ONE XL from a friend.
I presume he did not read much into his issue at the time and messed up this phone one way or the other.
Basically the phone works, just not as a phone.
So i will take my time to explain the whole situation with as much detail as possible.
I am personally familiar with rooting, setting up recovery and installing custom roms on android phones (just not on this model yet).
The phone details in its current state are:
- android version 4.0.4
- htc sense version 4.0
- software number cleanrom 4.5 beta2
- htc extension version htcextension_403_1_ga_20
- kernel 3.0.8-01564-gdc95f45
- baseband 0.16.32.09.01_3_10.79.32.08L
As soon as i received the phone, i contacted at&t to ask for an unlocking code, they gladly oblige.
I insert the new SIM card (non AT&T) and the phone asks me to insert the code. After correctly inserting it, the phone accepts the code and proceeds to reboot. After the reboot i get the phone locked screen again and asks me for the code one more time.
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
So at this point i am open for ideas.
I'm positive the issue is not very hard to solve but i also know that i am missing the original recovery. I can only guess no official updates were installed so the phone was running the original 4.0.4 version.
Meanwhile i will be scouting this forum on how this phone exactly works for i understood that there were two forms of recoveries for it (one full and one partial).
I still don't know the recovery version, if it's good, how to access it (different combinations of volume and power pressing didn't work for me).
Finally your opinion on how to make the phone unlocking code work, as in would i need to go back to official, or would a custom different rom work as a solution.
Wish you guys a good day and awaiting your feedback.
Cheers.
Need more info. Boot into bootloader by holding down both the volume down rocker and the power button. After the power button is held for a few seconds, you should see the capacitive buttons flash a few times, and the phone will reboot. Let go of the power button, but DO NOT let go of the volume down rocker until the while hboot screen comes up. When you see the hboot screen, tell us what it says.
In particular, we need to know if it says s-off or s-on, if it says CID 11111111, and hboot version. Also, if it says LOCKED, UNLOCKED, or RELOCKED.
Official RUU will not run if the bootloader is UNLOCKED (needs to be RELOCKED or LOCKED). But be aware, if the phone is superCID and s-on, running a Jellybean RUU or OTA will brick the phone. Which is one of the reasons we need the bootloader info.
RUU does not need to have stock recovery to run, only OTA does. My guess is your bootloader is unlocked, or its the wrong RUU. Any error message when the RUU fails (if so, what does it say)?
Hi, thank you for your quick reply.
I'm going to write down all that is written in the recovery for i still don't understand what locked or unlocked means, s-on or s-off.
anyway, here goes:
tampered
unlocked
evita pvt ship s-on rl
hboot-1.09.0000
radio-0.16.32.09.01_3
opendsp-v25.1.0.32.0405
emmc-boot
i can't find anything related to cid and i'm still not used to this recovery just yet. wouldn't want to press anything just yet.
i hope i gave enough info and i guess it doesn't look too good just yet.
thank you again for your help.
you should remind me to reduce the use of "just yet".
i'm doing some more reading about superCID and S-on or S-off.
I understand there's a utility from this thread that could determine the supercid status.
http://forum.xda-developers.com/showthread.php?t=1672284
again i'd like to point out i have no clue what has been done to this phone so i am trying to handle it with as much care as possible in order not to brick it.
in case superCID is 1111111 and naturally i don't have the original CID, where would that leave me?
As i am understanding slowly how this phone works, if the previous user managed to install a custom rom and a custom recovery on it, would only make sense to assume the superCID has been modified? (i'll be running the tool shortly unless someone jumps and says NOOOOOOOOO don't do it!!!)
I also noticed the teamwin recovery installed is 2.1.8.1
next is understanding what s-on and s-off are all about.
i have a feeling my chances of reverting to stock firmware are slimming. this is quite a complicated phone, nice challenge.
i'm going to point out again what my main problem is: i can't unlock the sim using the code provided by at&t since as soon as the phone reboots it asks me again. so i don't mind whichever route to take, whether custom or stock, as long as i can unlock the sim the simple way.
cheers.
srasiroslayer said:
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
Click to expand...
Click to collapse
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
srasiroslayer said:
i have a feeling my chances of reverting to stock firmware are slimming.
Click to expand...
Click to collapse
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
redpoint73 said:
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
Click to expand...
Click to collapse
Wunderbar,
Thank you again for clarifying things up.
I've been taking this time to read more about this phone on this thread:
- http://forum.xda-developers.com/showthread.php?t=1671237
So i am starting to understand how it works.
i have to admit that i should consider myself lucky for if the phone had a locked bootloader, it would've been bricked.
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Cheers
srasiroslayer said:
Wunderbar,
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
Click to expand...
Click to collapse
You don't need a Linux environment to get fastboot/adb working. And you will need them if you want to get s-off or change the CID (which would be the solutions to your problem of running the RUU).
To get fastboot/adb going, I'd suggest you start here: http://forum.xda-developers.com/showthread.php?t=1754018
There are some apps what will read the phone's state including CID. Others here have mentioned the name of one (or more) such app, but I can't recall, and I don't use it. I'm used to using fastboot.
srasiroslayer said:
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Click to expand...
Click to collapse
Not sure. Going back to stock might help. Its all I can think of. But don't be disappointed if it still doesn't work.
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
My question is, shouldn't i have the original CID number?
and another off topic point, i have no clue what s-on or s-off are.
i'll get into that reading mode again in a bit.
Thank you again, i feel i'm on the right track now and confident.
Cheers
P.S.: do you need me to post the "fastboot getvar all" results? or only thing missing to be sure of was the CID?
Hang on, you're s-on and SuperCID, don't run the RUU or you'll brick your phone. You need to do some reading and research all this before you try these things.
Sent from my Evita
Guys I am Vivek Rajput, from India. I have AT&T HTC oneX. Anything related to internet is not working except whatsapp. Every app is showing network error msg. Showing some data here which i got after reading here. Assume me complete novice about software/cellphones.
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.320911_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
Have you checked your APNs?
Sent from my Evita
srasiroslayer said:
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
Click to expand...
Click to collapse
If you are going to s-off, you DO NOT want to change the CID. SuperCID (11111111) is needed to s-off.
As mentioned, make sure you s-off before RUU, or you will brick.
Once you are s-off, it shouldn't matter whether you lock the bootloader or not. S-off means all security checks are bypassed, including the check for bootloader lock.
srasiroslayer said:
and another off topic point, i have no clue what s-on or s-off are.
Click to expand...
Click to collapse
s-off, as mentioned above means all security checks are off. There are good and bad points to this.
The good, is that you will be safe of the SuperCID + RUU brick condition. Custom ROMs will also be easier to flash, if you are interested in doing that (do not need to flash boot.img separately).
The bad of s-off, is that because all security checks are off, there are no safety checks to prevent you from flashing the wrong things. You have to be very careful you don't flash something that is not intended for the device, as it may brick the phone.
Are you are okay with that, then proceed with s-off. If not, the alternate solution is to change the CID back to the proper AT&T CID (cws__001). This will also prevent the SuperCID + RUU brick condition. But may make the phone harder to s-off in the future, if you later choose that route.
It looks like then that the s-off route is the one to take, since i will definitely in the future be interested in flashing custom roms.
And it looks relatively easy as per:
http://forum.xda-developers.com/showthread.php?t=2155071
After doing some reading, it also looks safe to achieve s-off on custom roms such as my case.
I'm still reading if s-off will work on my bootloader version or if there are any specific versions to run it at. (so far no mention so good)
I'm guessing i will run s-off today and if everything works out as it should will post my results here.
Only then will i proceed to run the RUU which i downloaded from htc for the at&t model specifically (no chance i could go wrong with that).
Thank you for all the help, i honestly don't think i would've found my way around easily without guidance.
Cheers
Yes, the s-off method is easy, and it should work on any hboot version.
Good luck.
Could just having S-off fix my sim locked issue?
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
srasiroslayer said:
Could just having S-off fix my sim locked issue?
Click to expand...
Click to collapse
I doubt it. SIM lock and s-off are not related, to my knowledge.
srasiroslayer said:
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
Click to expand...
Click to collapse
Once you are s-off, all security and safety checks are off by definition. As long as you are running an RUU meant for EVITA, you will be safe, and it should run properly.
Looks like i got the 99 error thing.
at first i had the error 92 and all was working good but after the final reboot didn't get s-off
the second try i'm getting error 99.
I'm going to read more into it.
I'm still s-on so.......
So here are the current updates.
As i mentioned in the previous post, running it the first time resulted in error 92 which is normal, followed instructions and didn't get s-off.
second time i had error 99. still no s-off.
I turn off the device and power it back on, run the script all over again with a real good attention and precision (i usually don't f*ck things up).
This time i get the error 92 again and still no success at the end. (did this over 4 times now and no s-off).
would i be logical for me to assume that once the rom is booted it's messed up somewhere? hence the last part of the script not working and also hence sim unlock not working?
what's a good custom rom that would i could install using recovery and not brick my phone?
maybe just installing one would solve all my issues.
Cheers
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
timmaaa said:
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm trying it on CleanROM 4.5 beta2.
And by best rom in my case was asking one that would be compatible with my situation, as in hboot 1.0.9, teamwin 2.1.8.1 recovery, supercid, unlocked, s-on.
Cheers.
Hi
Before starting I want you to know that I have been through 5-10 threads regarding the subject problem and still not know what to do. I am basically a layman to Flashing. The most adventurous thing I have done is downgrading a Sony Xperia Arc S from ICS to Gingerbread using a simple sofware sort of thing called "flashtool" and downloading ......... (i am leaving it blank cuz at the moment I am quite confused. Lets call it its original firmware)
And before I can explain the problem I am confused between the following terms: RECOVERY, ROM, KERNEL and RUU. Kernel i know is a software layer between H/w and OS. But then why we need to flash it seperately???? it should be a part of OS: which i think is called a ROM. RUU is the update to a recovery. but what exactly is the difference between ROM and RECOVERY. both seem to be like some sort of an image file that contains complete OS. Then there are bloody BOOTs that you have to unlock and keep lock at some times. God knows why
Now coming to the problem:
My HTC One X (bought here in Pakistan and should be containing the international firmware, i dont know for sure)
One fine morning a few days ago my phone showed up the update HTC released recently which changes the appearance of the GUI. I was quite happy to see it and immediately selected the option to install the update. The update ran and installed successfully. I used the new GUI for 2 days or so and then suddenly my phone got stoned (or brick or stuck). It turned off when i tried to use it and then started showing
*** LOCKED ***
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MI CROP-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH : OFF
Jun 21 2013, 18:24:41
Battery level is too low to flash
FASTBOOT USB
HBOOT
REBOOT
REBOOT BOOTLOADER
POWERDOWN
So I am screwed really badly. The USB debugging mode that i know is essential to install a firmware is not enabled. and my device is not rooted. The device is not charging up properly.
I have downloaded Hansoon all in one toolkit (which seems to be of no use since debugging mode is not enabled). I have android SKD downloaded in my pc. so is HTC Sync. But dont have any idea where to begin.
AND MOST IMPORTANTLY I WANT TO SAVE THE DATA INSIDE THE PHONE THAT I CANT ACCESS.
..... i am trying to root the device using hansoon. but for that i need to generate some sort of a code. Now my device is showing up one option named barcode where i can see MB SN and IMEI of the device. is it possible to generate that code using these three???
I think I have posted it in the wrong forum. mods please delete it. I am starting a new thread in the right forum
Your phone is HTC one X Endeavour ......this forum for HTC one X Evita.....please check HTC one X forum ....we can't really help u that much ... BTW u go to www.htcdev.com to generate unlock_code.bin and follow instruction from there coz right now your bootloader show ****security warning****
Swyped From BlueICESense_JBE
Hey Folks,
This is my first post in the Sensation forums, i've been reading topics for a few days, but I didn't find any solution to my problem and i'm starting to get annoyed by it.
I've obtained a HTC Sensation a few days ago, and as with my previous devices (Galaxy Gio, Optimus Black) I wanted to flash a custom rom on it. I happened to unlock the bootloader of my friends Sensation few weeks earlier, so i thought this was going to be a piece of cake.
Well it wasn't, I couldn't unlock the bootloader using HTCdev method because the phone is vodafone branded. I tried numerous things, i wasn't able to perform the juopeanutbro (?) trick, tried flashing a custom hboot through fastboot (JB_hboot.zip) in linux (gave me an error 42 "Remote: Custom id check failed" or something like that). And after a few days of trying and trying i'm getting tired of it.
So my question is, is there any option i missed to achieve S-OFF or unlock bootloader? I'd love to flash a custom rom on it because I don't like the 4.0.3 Firmware which the phone is running now.
Phone Details:
Android version: 4.0.3 (vodafone)
HBOOT:1.27.0000
Radio: 11.29A.3504.18_M
CID:VODAPE17
Did you select the Vodafone model there in list of HTC dev...
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA Premium 4 mobile app
Ihttp://forum.xda-developers.com/showthread.php?t=1668276
If htc Dev method doesn't work for your phone, use the non htc Dev method. Follow everything on the screen, do not run out of battery power (that will probably brick your phone)
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Redjack77 said:
Yes I did select the vodafone model, and I end up with the "failed" error when flashing unlock_code.bin. I don't understand why the HTCdev method doesn't work in the first place. And the method described by stillsober requires the almost impossible wire-trick.. Well i'm afraid there is no other method..
Click to expand...
Click to collapse
has your motherboard been replaced?
what error did you have?
It's not that impossible, I did it in like 10 tries, there are YouTube videos timed exactly so you know when to connect and disconnect the wire. plus you can try as many time as it takes so you really can't go wrong... You know both method require the insulated wire right? It's just one requires the more accurate timing
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Redjack77 said:
Well I've somehow managed to achieve S-OFF!!!!!! This is my fastboot screen:
h t t p://i43.tinypic.com/2wgubtj.jpg
I read in a guide somewhere on the forum that when having S-OFF flashing a custom recovery would be possible, and writing supercid too, well the first thing failed (again...) but I did manage to write supercid. This is my command prompt screen:
h t t p://i39.tinypic.com/2uqzkna.jpg
So what do I have to do now??
Click to expand...
Click to collapse
what does it say in the top?
juopunutbear or locked?
also i can't view the pics
can you post here in a post?
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://, because i can't include links in my posts as I have lest than 10 posts submitted.
But I actually have solved all my problems, because I knew juopeanutbear had unlocked bootloaders available on his website and in fastboot you are possible to flash these with the command "fastboot oem rebootRUU" wich put the device in RUU update mode, and then flash the unlocked HBOOT from juopeanutbear's website with the command "fastboot flash zip jb_hboot.zip.
Note (to people who might find this useful in the future): The devices sticked on showing a green loading bar in RUU update mode after entering the second command, on the command prompt it showed done, but the device didn't reboot or what. Just wait a while (to be sure) and enter command "fastboot reboot-bootloader"
Now my fastboot screen shows **Juopeanutbear** instead of ***locked*** and I've already managed to flash clockworkmod SUCCESFULLY!!!!!!!
Now I will replace CWM by 4ext and i'm good to go I guess, how I managed to get S-off will remain a secret for me, I assume I did do the wire-trick correctly after all, but didn't notice (you know,, spending a few nights behind your PC doesn't give you a clear state of mind
Redjack77 said:
Well on the picture it says ***Locked*** and you can just paste the link in your browser without the h t t p://,
Click to expand...
Click to collapse
you are right
i included also the h t t p : //
so you managed it yourself
crongats
now it is time for a custom rom
note: probably after achieving S-OFF you chose no for installing the jb hboot
Running Team Venom's Viper sense 5 rom and just like I expected I LOVE IT!!
Hi Everyone,
knowing it's all out there, just need to read (a lot), please help me finding the correct way to solve my problem. I can not change to other ROM, mostly due to lack of knowledge. Please before you judge and claim I should read and learn, i have kids who don't allow me read things properly, and there are tons of information out there, seems simplier to ask for directions this time, based on the situation of the phone.
This is the first custom rom I tried on my new S4 HTC One S (not brand new, just new to me). It was stock rom, locked. Followed instructions on different threads, I unlocked the phone, flashed TWRP recovery, installed SuperSU, copied Venom Rom zip to SD card and installed from recovery, with the aroma. Success. Before installation I did a backup in TWRP.
I very much like the rom (though have 2 issues: 1. phone reboots randomly without any notification. 2 phone loses carrier randomly, so I see no GSM connection as if SIM was removed. This happens when phone is untouched so no way SIM is loosy or something). When I try to chose carrier manually from settings, it sais no SIM card is installed...
But I would like to try other roms as well, and also wish to compare some stock roms. So I downloaded a generic HTC Europe stock RUU, hoping I can easily flash it. Relocked the phone, ran the RUU.exe with Fastboot USB mode in bootloader, but it all came up with error messages and left me at the HTC logo. All I can do is to re-install Venom 3.0.0 from recovery, that works, otherwise I end up in boot loop.
Also I can not go back to the original state using the backup from TWRP. It installs boots but it basicaly freezes before the phone setup comes. I can see the background image, the clock and the GSM antenna sign, but thats all, nothing else happens, no matter how hard I try to reboot.
Phone current boot screen shows: Tampered + Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
Radio-1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10
When I re-locked the phone it said Tampered + Relocked + Security Warning
As recovery I have TWRP 2.6.0.0 flashed. I did nothing else.
Could someone help me with instructions or at least directions how I could go back to a nice stock RUU? With the one I downloaded i had different error codes 213 (wrong ID) and 255 Unkown error.
I believe as the phone is not S-OFF and/or Super CID, it is relevant which RUU I download. The phone used to boot with a voda logo, so I believe it was one of the UK or AT voda stock roms, but neither works.
Your opinion/feedback is highly appreciated.
Cheers,
skee
skee81 said:
Hi Everyone,
knowing it's all out there, just need to read (a lot), please help me finding the correct way to solve my problem. I can not change to other ROM, mostly due to lack of knowledge. Please before you judge and claim I should read and learn, i have kids who don't allow me read things properly, and there are tons of information out there, seems simplier to ask for directions this time, based on the situation of the phone.
This is the first custom rom I tried on my new S4 HTC One S (not brand new, just new to me). It was stock rom, locked. Followed instructions on different threads, I unlocked the phone, flashed TWRP recovery, installed SuperSU, copied Venom Rom zip to SD card and installed from recovery, with the aroma. Success. Before installation I did a backup in TWRP.
I very much like the rom (though have 2 issues: 1. phone reboots randomly without any notification. 2 phone loses carrier randomly, so I see no GSM connection as if SIM was removed. This happens when phone is untouched so no way SIM is loosy or something). When I try to chose carrier manually from settings, it sais no SIM card is installed...
But I would like to try other roms as well, and also wish to compare some stock roms. So I downloaded a generic HTC Europe stock RUU, hoping I can easily flash it. Relocked the phone, ran the RUU.exe with Fastboot USB mode in bootloader, but it all came up with error messages and left me at the HTC logo. All I can do is to re-install Venom 3.0.0 from recovery, that works, otherwise I end up in boot loop.
Also I can not go back to the original state using the backup from TWRP. It installs boots but it basicaly freezes before the phone setup comes. I can see the background image, the clock and the GSM antenna sign, but thats all, nothing else happens, no matter how hard I try to reboot.
Phone current boot screen shows: Tampered + Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
Radio-1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10
When I re-locked the phone it said Tampered + Relocked + Security Warning
As recovery I have TWRP 2.6.0.0 flashed. I did nothing else.
Could someone help me with instructions or at least directions how I could go back to a nice stock RUU? With the one I downloaded i had different error codes 213 (wrong ID) and 255 Unkown error.
I believe as the phone is not S-OFF and/or Super CID, it is relevant which RUU I download. The phone used to boot with a voda logo, so I believe it was one of the UK or AT voda stock roms, but neither works.
Your opinion/feedback is highly appreciated.
Cheers,
skee
Click to expand...
Click to collapse
To go back to stock u have to flash the right RUU, depends on which CID ur phone got.
u can download it here: http://www.androidruu.com/?developer=Ville
If u downloaded the right RUU, boot ur HOS into fastboot relock the phone and start the RUU.
Let it finish and u r on stock
Hi Homeboy, thanks for the answer. Seems clear. I have only 1 question. How can I make sure which is the right RUU?
I believe I should do a getvar all command, to see the CID id? Then what shall I look at the RUU's filename?
And after the phone having been relocked, shall it be in fatboot USB in bootloader or shall the phone be up and running when I start the RUU.exe from the computer?
thanks
skee81 said:
Hi Homeboy, thanks for the answer. Seems clear. I have only 1 question. How can I make sure which is the right RUU?
I believe I should do a getvar all command, to see the CID id? Then what shall I look at the RUU's filename?
And after the phone having been relocked, shall it be in fatboot USB in bootloader or shall the phone be up and running when I start the RUU.exe from the computer?
thanks
Click to expand...
Click to collapse
hi,
i saw u live in Hungary so it should be the Europe RUU try this:
http://www.androidruu.com/getdownload.php?file=Ville/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
And yes phone should be in fastboot when u start the RUU.