Related
I am in China and I bought an HTC s510e last week, that was made in Taiwan.
When I look at the boot menu screen, is says my phone is locked, although when I put a SIM card from another country in there it doesn't ask me for an unlock code. Perhaps the phone is locked to China?
Now my main problem is that there is constantly all kinds of Chinese software being installed on my phone without my knowing, and there seems to be no way of uninstalling most of it, and what I can uninstall, gets installed again soon after.
I am thinking the solution might be debranding the phone, or rooting the phone.
However, I can't figure out which ROM to put on there that won't brick the phone and that will still allow me to read and write Chinese (using pinyin). The menus should be in English of course.
Some information on the phone:
HTC s510e
Android version 2.3.5
HTC Sense version 3.0
Software number 2.10.401.5
Kernel version 2.6.35.10-g9ac6c7a
[email protected]#1
Wed Sep 21 13:48:03 CST 2011
Baseband version 20.4801.30.0822U_3822.10.08.04_M
Build number 2.10.401.5CL156318 release-keys
Browser version WebKit/533.1
More info on my boot screen
SAGA PVT SHIP S-OFF RL
HBOOT-2.00.002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
I kind of know next to nothing about the subject, would be very grateful if anyone can point me in the right direction.
Thanks
i hope any one help you
correction
This is a correction to my previous post
On my boot screen, where is says HBOOT-2.00.002 I should have written HBOOT-2.00.0002, don't know if this makes any difference.
I have tried rooting my phone using SuperOneClick. The phone is rooted, or so it says, but SuperUser can't get any superuser privileges. Unrooting doesn't work, the program freezes.
No BusyBox on the phone yet, tried installing it, but can't because SuperUser doesn't have the necessary privileges.
Installed ROM Manager, flashed a ROM recovery image with it, but that's about all I can do with the RM, doesn't want to back up my ROM, doesn't boot into recovery.
I can boot into recovery manually after shutting down the phone, but once in recovery....I get a red triangle and have to take my battery out and reinsert it to get the phone working again.
I tried unlocking the bootloader through the htcDev center, but I first have to update something on my phone, I chose a couple of possibilities in their list provided but nothing worked, couldn't update. (By the way, I can't update the ROM on my phone either, for some reason I get an error message. Perhaps because my phone is not set to receive OTA updates?)
As you guys can see....I don't know where to start or what to do, nothing seems to have any effect. Already happy nothing of what I did bricked the thing.
Would really appreciate it if someone could help me out here. How to unlock the bootloader? How to root properly?
Thanks in advance.
Okay, here is how I did it.
I ran SuperOneClick a few more times, it got rid of the useless Superuser application, but still said my phone was rooted.
I unlocked my bootloader through the HTCDev website. It asked me to first update my bootloader, I skipped the step since that didn't work. Now my bootloader is unlocked no problem.
In stead of trying to root my phone any further (it said it was rooted but didn't seem to be properly rooted), I downloaded the AndroidSDK, got into my phone with adb shell command.
Tricky part:
-the thing wouldn't let me remove any file, giving me read-only error
-also wouldn't let me change file permissions, same error
-solution: first give a adb root command, which will give you root privileges, then you give a adb remount command which makes all files read and write.
Next you can use adb shell, and from there follow the normal steps to remove files. At the end I left the shell and gave a adb reboot command, rebooting the phone.
I got rid of the most annoying junk on my phone. Wouldn't mind to find a way to have the thing properly rooted, but for now I'm happy with what I got.
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.
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!!
I have been faffing about with S-OFF and the like in an attempt to de-brand my phone to stock HTC with root (the handset was an Orange UK CID). I've been at this for a couple of days now and have seemingly got myself stuck in a corner with the 2.0 hboot, which seems to be what's causing the problem for me - I was previously able to run the stock ICS RUU, but can't any longer.
Handset: HTC One SV LTE (model ID PL8010000)
*** UNLOCKED ***
K2_UL PVT SHIP S-OFF RL
CID: HTC__001 (have also been in SuperCID 11111111 numerous times)
HBOOT: 2.00.0000
RADIO: 1.15.40a.00.04
OpenDSP: v9.2.0268.1214
eMMC-boot
Mar 14 2013, 22:10:43-1
OS at the moment is Viper, because that's all I can get to install. None of the OTAs work (various errors relating to parsing android-info.txt and remote access issues in fastboot). The trouble with Viper is that the radio is apparently knackered, because I can't get a signal at all, and I was on stock JB and on ICS.
If anyone can provide me with a stock ICS 1.00.0000 HBOOT, I can try the RUU again at least. OTAs don't work from there, but it'd be a start. Any other ideas would also be greatly appreciated!
EDIT: Sorry, I forgot I'd already found a stock HBOOT and used it earlier, so have done that again now. Have now run RUU and am on stock HTC__001 version of ICS (K2_UL_ICS_40_HTC_Europe_1.17.401.5_R_Radio_0.12.40.00.14_2_10.49.40.11L_release_301902_signed). However, I still need help getting updated through the OTAs, of which I have 3 in .zip form:
OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.2-1.17.401.5_R_release_308698hqk34kifwjk0g071
OTA_K2_UL_JB_45_S_HTC_Europe_2.14.401.6-2.14.401.2_release_311966gsyc11xrfb40ox3c
OTA_K2_UL_JB422_SENSE50_MR_HTC_Europe_3.11.401.1-2.14.401.6_release_338297mseg08soslxcubit
METHOD 1:
When I try to run any of the above via fastboot oem rebootRUU, it fails and says it can't parse android-info.txt. I've checked the android-info in all three files, and the CID I have on the handset is listed in there, and the model ID is correct. I have verified with fastboot getvar cid that the CID is indeed HTC__001, so I don't understand what the problem is.
METHOD 2:
I've tried re-locking the bootloader and running again, but that still fails as above.
METHOD 3:
I've also tried just flashing the firmware.zip alone, but that spits out errors relating to the checks at two early stages in the updater script:
assert(check_cid(getprop("ro.cid") - I'm not sure why that fails given that the CID is correct for the OTAs, but it works if I just delete this check
assert(getprop("ro.product.device") == "k2ul" || - again, this is the correct device I'm trying to apply the OTA to, so I don't understand the issue
Sorry about the confusion in the initial post; any help would be greatly appreciated!
Your task should basicly be the easiest today, lol.
Get back to SuperCID, flash the RUU again (if needed, the 1.0 hboot before), and then, when phone is booted into android, let it search for updates.
Download and installing should go fine, because you are stock from the RUU and have SuperCID. Do this until no updates left and you are on 4.2.2.
You can also orientate on this guide.
old.splatterhand said:
Your task should basicly be the easiest today, lol.
Get back to SuperCID, flash the RUU again (if needed, the 1.0 hboot before), and then, when phone is booted into android, let it search for updates.
Download and installing should go fine, because you are stock from the RUU and have SuperCID. Do this until no updates left and you are on 4.2.2.
You can also orientate on this guide.
Click to expand...
Click to collapse
Man, I am so sorry. Not only did I fix this myself, I found out what I'd done to cause the ballsup. You know how I said I was getting 0 signal on the network? When changing the CID, I had accidentally overwritten the first 4 digits of the IMEI, so it wasn't recognised as valid any more. Just re-edited mmcblk0p4 to reinsert the original IMEI and it's now getting a signal. Prior to that, I managed to flash HBOOT 1.0 and run RUU then flash the OTAs manually. Have also reflashed TWRP 2.7 and backed up so I can hopefully recover faster from any more mess I make for myself...
Having said that, when I was trying to get the OTAs actually over-the-air, it kept reporting no updates available. Do you think that's just a result of the IMEI issue or do I need to be fully S-ON and locked (as in HTCL) to get OTAs? Do I also need the stock recovery?
Thanks very much for the reply, mate. I wouldn't have been able to do this stuff without your guides and replies on this forum, as well, so I'm grateful for your help.
Well, hard to say with your OTAs, because i never had a non-working CID.
But to run the official OTAs you need for sure a stock recovery!
old.splatterhand said:
Well, hard to say with your OTAs, because i never had a non-working CID.
But to run the official OTAs you need for sure a stock recovery!
Click to expand...
Click to collapse
The CID's fine, it's just the fact I overwrote it onto part of the IMEI... at one point I had manually edited HTC__001 into mmcblk0p4 then later rewritten it via the set cid command, which resulted in that line of the file being set to "HTC__001_001" because I'd keyed it in with the _001 overwriting the first 4 digits of my IMEI. Because I am an idiot, it would seem. Nonetheless, when I was requesting the updates OTA the CID was working fine. However, I only had stock recovery *some* of those times I tried to get OTAs, and I can't say whether the IMEI ballsup was there right from the start or not because I have no idea when I did that. I'll possibly reflash from the RUU again at some point and attempt an OTA on stock recovery with the correct IMEI, but for the time being I'm playing around with Viper because half the reason I started faffing about in the first place was that I thought some of the stock bloatware on the Orange firmware was possibly slowing down the handset (which it evidently was, since it remained slow post-fstrim) and Viper lets me strip the HTC crap out as well.
Anyway, sorry about the dimwittedness, and thanks very much for your help! :good:
Hi,
im currently stuck on the step of changing the CID on a smartphone of a friend. the Current CID is T-MOB101 with an unlocked bootloader ( HBOOT 2.15) S-On and an old CM running)
Id like to update to HBOOT 2.16 but im failing at step one, chaning the CID to the SCID.
Ive tried many times to flash mmcblk0p4 with the modified data (yes, ive done that) but it doesnt stick. No matter what i do i always get
fastboot oem readcid
...
(bootloader) cid: T-MOB101
Ive even verified the uploaded file, its fine.
https://i.imgur.com/nGBDEul.png
Take a look at moonshine or rumrunner.
If I remember correctly, facepalm isn't usable, anymore, with the t-mobile version of the One S if the latest official firmware got installed.
Sent from my HTC One M9 using XDA Labs
Well, both dont seem to work with the CM installed.
I guess i have to roll back to an official FW and try again
Also ive just noticed, im unable to mount /sdcard, in both recovery and rom.
Kinda strange
Facepalm and moonshine definitely don't work with CM. They're both meant to be used with a sense rom.
Rumrunner, on the other hand, should be usable with CM11.
The storage issue should be solvable by flashing a RUU.
Sent from my HTC One M9 using XDA Labs
Well, RR seems to not like my device. All i get is this
==================== rumrunner S-OFF 0.5.0 ==============================
rumrunner S-OFF comes with NO WARRANTY (express or implied)
and NO GUARANTEE OF FITNESS for any particular task.
We have made every effort we can to make this a safe process for users
however the authors disclaim any liability for damage to your phone
or other materials or devices used during this process.
The entire risk of running rumrunner S-OFF lies with you, the user.
By using this software you acknowledge and accept that the authors
are not liable for any loss, material or otherwise howsoever caused.
Do you understand the implications of this warning?
(Yes/No)
Yes
Dear User: We will expect that YOU:
(1) Know how to use ADB and FASTBOOT binaries
---- [Yes, use these tools to test USB connection BEFORE running rumrunner] ----
(2) Realize that rumrunner S-OFF cannot support every CUSTOM rom in this world
(3) Understand that irc support IS NOT A GENERAL HELPDESK
(4) Are able to identify and download the CORRECT package for YOUR device
(5) Know how to enable USB-debugging on YOUR device (Yes, do that now)
(6) Understand that you may NOT repack or redistribute rumrunner S-OFF
Ok?
(Yes/No)
Yes
!! Do NOT for any reason taunt, unplug, drop, eat or pet your device !!
Please wait....
..........
Checking for updates......
Test 1: Rebooting into bootloader
Waiting for fastboot (7/120)
Waiting
Test 2: Booting device
Waiting for ADB (23/120)
must ferment longer...
must sanitize, skunky rum is nasty
hold please..............................................
[------------------------------------------------------------]
Rebooting into bootloader (again)
Waiting for fastboot (7/120)
FATAL: Download updated package at www.rumrunner.us
Press ENTER to exit
The RRU ive found for my device ( TMO_DE ) doenst like it either, propably because its severy behind the actual FW on the device (2.38.111.10 is the latest RUU ive found, but the current version on the phone is detected as 3.16.111.11)
With S-ON you can only use RUUs that have the same or a higher firmware version than your phone. Downgrading is only possible with S-OFF.
The latest RUU for T-Mobile Germany that I could find euqals version 3.16.111.7. I know that the One M9 accepts older RUUs as long as only the digits behind the last dot mismatch. I'm not sure whether the same applies to the One S, though, since I set my One S S-OFF before I used RUUs for the first time.
Alternatively, you could contact Llabtoofer's RUU service. Be aware that it's not for free.
Rumrunner (like all methods for older devices like the One S) isn't perfect. It might happen that you need to try them up to twenty times before they actually work as intended. Double check whether you followed the prerequisites & instructions on the official website. The HTC Sync Manager still being installed and the usage of an USB 3.0 port instead of an 2.0 port are only two of the possibles reasons why Rumrunner might fail.
Thanks for the RUU
and for trying an USB 2.0 port: My devices dont have them anymore :/
Anyways, im very grateful for your help