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.
Related
Hi all,
I have tired to flash the new Rom yesterday and during checking the signature device reboot and installer said that it can not proceed.
After reboot phone goes directly into fastboot and gives ***Locked*** with Security Warning massage. I have tried different RUU but it is exactly the same.
Installation is failing on the checking signature.
I have tried Unrevoked3 but it is not able to find the device. Could you please let me know how to do it?
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-2822.10.0804_M
eMMC-boot
I was trying to upload RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed
http://forum.xda-developers.com/search.php?searchid=23896455
Error nr 141?
LE: hope it works now, if not search the forum, the link reffers to the search results.
You will certainly get the answer there.
Link does not work:
Sorry - no matches. Please try some different terms.
I have tried to find an answer but no luck so far, I am quite new to this. Is there anyone who can point me in the right direction?
Another solution is to try the RUU 2.10.401.8
I had some problems with the same Ruu, but not with the signature, and the previous version worked flawlesly.
What's your CID?
Sent from my HTC Desire S
I have tried few others RUU and every single of them is falling during the installation.
ok I manage to unlock the device finally
But again it is falling during the installation of a new ROM. Do I have to revert back Hboot to 0.98 before installation? if so how to do it?
So the RUU that I recommended completed successfully?
What do you want to do next?
Now you are S-ON, if you want to install custom roms you have to unlock your bootloader with the htcdev method(you will lose your warranty and need to flag manually the boot file) or to downgrade.
Sent from my Samsung Galaxy Tab
I want to downgrade the phone to orginal ROM T-mobile uk. So I could take off the simlock, I have put the unlocking code yesterday but nothing happens. I was advised to downgrade the rom and should be ok.
Could some help me out with my problem please when ever I am trying to upload new rom it is stuck on signature verification.
I will quote Enigmaamit as he said it better than me:
enigmaamit said:
SIM unlock and bootloader unlock are two completely different things.
Click to expand...
Click to collapse
The only way to SIM-unlock your phone yourself is a XTC clip... better ask your phone operator.
I know the diffrance between those two, I have ordered unlocking code. After putting this into device when ever I put into new sim card it stoped nofifing me about it. But it is not able to find a new network. Below what I have receive form operator:
"It said "Successful" but nothing has happened
Darren
posted this on Apr 11 16:22
This has happened to a handful of customers who have all had one thing in common - the phones have been "rooted".
By rooting a handset the owner has removed some of the restrictions on the phone, which allows the owner to install whichever software of the phone that they wish. Unfortunately this has caused some issues when an unlock code has been entered.
It is easily rectified by reinstalling the original operating system that the phone was supplied with, then applying the unlock code and the phone should be unlocked, truly, successfully.
You can then reinstall the software you had on the phone before attempting the unlock and continue using the phone as you wish."
So that is the reason why I am trying to revert any changes.
i for one don't believe this
So their replay is bull**** in that case?
In my opinion yes(i can't say that i am a very experienced user) but i like to think i know some stuff about this.
I can't imagine what custom rom/Ruu version/app will "block" you to sim unlock your phone.
The only restrictions may be made by the phone manufacturer.
So i will try through HTC Clip in that case. But why I can upload any new RUU?
like i said earlier, i had some problems to with the 2.10.401.9 ruu.
Try the 2.10.401.8 it should work, if your phone is branded try a gold card.
A while back I attempted to root my phone on my Macbook Pro. I sort of gave up half way through because I was unable to find a tutorial detailed enough to unlock the bootloader. Basically, what I did was change my CID to 1111111, and then I did a factory reset hoping that to OTA Jellybean update would have been sent out from AT&T. Scratch that.... When I use the CID Getter app, it says that my CID is back to the stock "CWS__001," and now I have access to a computer running Windows 7 64bit... I am using this video tutorial.
I am able to backup my phone two times, but when it tries to fetch my CID, it says that it has already been unchanged. That is as far as I am able to go... I still have the token from when I tried rooting the first time, and htcdev.com has sent me the unlock_code.bin. I tried to just go ahead and run it via command prompt, but it just says "waiting for device." I know that the drivers are installed correctly and up to date, HTC sync isnt showing up in my task manager under processes OR service, the device is in USB debugging mode, I have tried it without disable fastboot before rebooting it in bootloader mode, and I have tried it disabled as well. I am stuck here. Am I going to have to try and flash a RUU or whatever, because I am new to rooting android devices. I am pretty savvy when it comes to this sort of stuff, but I am at whits end... What should I do?
What do you mean by "factory reset"? A factor reset or running the RUU will not change the CID.
It seems you meant to link a video, but didn't, so I'm not sure what procedure or tools you are trying. I would advise trying the all-in-one toolkit to temp root and change the CID: http://forum.xda-developers.com/showthread.php?t=1952426
My other advice would be to read up on the actual guides posted here on XDA, rather than rely on video walkthoughs that just spoon feed you the steps without actually requiring you learn anything.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will). So if you've actually changed back to the AT&T CID, it was for nothing.
n/m
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
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.
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: