Related
Hi guys, i received a DESIRE S, but this phone has been with other guy that sells me that phone.
Now i think its rooted because i downloaded the "ROOT CHECKER" on the market and it says "yes" that im rooted. Then i did de power button and volume down, and i got this:
SAGA PVT ENG S-OFF
HBOOT-0.98.2000 (PG8810000)
RADIO-38.03.00.03_M
eMMC-boot
I dont know what method to root was used
I think im with the sock rom because when i turn on my phone, it just show htc logo then starts normally (pin code, etc)
Ill give more information about my phone:
software number 1.12.0.0
Is that a way to unroot my phone? PLEASE
I have read some threads of other guys trying this but theyr hboot's are differents of mine, so im scared of brick my phone
Can any1 tell me step by step to unroot my phone? i have no experience with root's and this things
EDIT: Sorry for my bad english. Im Portuguese.
It looks like he unlocked the phone with the ENG HBOOT of HTC. This version of HBOOT is for the service personnel and was then released by HTC.
AFAIK you can simply flash a RUU ROM which will unroot the phone. But it won't change that it is S-OFFed. Root and S-OFF are different things. But normally it won't matter in all-day use if your phone is S-OFFed.
It was S-OFFed by Revolutionary then an ENG bootloader was flashed on it. Returning to Stock is pretty easy in your situation.
First you need to find your real software version:
1) follow the guide about adb and fastboot in my signature (make sure that you have USB Debugging ON in your Settings -> Applications -> Development)
2) connect the device to PC, open command prompt and type:
Code:
adb devices
{your serial number should appear}
adb reboot bootloader
{the phone will reboot}
fastboot devices
{your serial number should appear}
fastboot getvar version-main
the number obtained from the last command is the real one. You can leave your phone connected and go to the "Shipped Desire S ROM collection" thread (it is sticky in the Android Development subforum here). Find a RUU with the same number as yours, download it, start the exe on your PC and follow the instructions. Keep in mind that this will DELETE all you personal data and applications!. After completion you will have completely Stock device and you can check for updates, I believe you will get the latest Sense 3.0 Good luck, if any questions post here.
OMG, you are my GOD!
I'll read everything in your signature, then i will start the process.
One question: Doing all this, im unrooted and s-on? Because all i want are the official updates and with s-off i think i can't update, or can i?
eheh, i'm really appy with your answer
When i type the last command:
"fastboot getvar version-main", it says: < waiting for device >
something wrong?
i can do the commands "adb", "adb devices", but the "fastboot devices" dont appear, why?
what im doing wrong?
Forget my post over there /\
i got the number 1.21.0.0
ill search a ruu with this number, thanks !! :d
Desire S said:
Forget my post over there /\
i got the number 1.21.0.0
ill search a ruu with this number, thanks !! :d
Click to expand...
Click to collapse
hmmm. there is no such as far as I know
Do you have an update notification?
---------- Post added at 09:30 PM ---------- Previous post was at 09:23 PM ----------
Tell me the output of this command:
Code:
fastboot getvar cidnum
No updates
I got the number in cidnum: 11111111 :s
I can't find any RUU, my software number is strange
Desire S said:
No updates
I got the number in cidnum: 11111111 :s
I can't find any RUU, my software number is strange
Click to expand...
Click to collapse
I think that you can use whatever RUU you like
this cidnum is called super cid - you can flash anything on it
the version number (that is also checked by the Rom Update Utility, or so called RUU) is the lowest possible - so again you can flash anything on it
So you just have to choose one of the RUU provided that suits you best and use it - if you are from the Europe I suggest to flash directly 2.10.401.8 - you will have the latest version. If from other region - choose accordingly.
{just a reminder: if you just want Sense 3.0 there is no need to remove root - you can flash a the latest prerooted stock ROM and have all benefits of the Stock system, BUT will keep the option to change to the forthcoming ICS or Sense 3.5 ROM which most probably will never arrive officialy for our devices. Think about it }
When i run this RUU, whas specifics will have my phone?
Now i got this:
SAGA PVT ENG S-OFF
HBOOT-0.98.2000 (PG8810000)
RADIO-38.03.00.03_M
eMMC-boot
When i run the ruu, what i ill get? s-on?
All i want are thhe official updates :s (2.3.5 and sense 3.0)
And can you paste there the ruu that you think is the best for my software number?
oh, and thanks for everithing, is there a way to give a "positive reputation"??
and what you think about my english? its "ok" right?
EDIT: I'M from portugal
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
so maybe this can help you choosing the best RUU for me
thanks again
EDIT2: I bought this phone at 1 guy, so i don't know the right localization of the phone :S
1) the RUU will get you S-ON (in fact complete Stock like you just got it from the shop)
2) you will get latest 2.3.5, Sense 3.0 update when flashing this RUU - it has Spanish locale
3) there is a THANKS button at the bottom of my posts
4) your English is fine, I can understand you perfectly, I hope my English is the same for you
One more question :
When people root their desire s, they should have the app of "super user" right?
Mine dont have this app. This means that mine is not rooted and just are s-offed?
Don't ask me why but when I received my phone it had s-off!
Desire S said:
One more question :
When people root their desire s, they should have the app of "super user" right?
Mine dont have this app. This means that mine is not rooted and just are s-offed?
Click to expand...
Click to collapse
You can always use SuperOneclick to push Superuser to your phone. Or try to install it from the Market
Hey amida, i was thinking, and i think i want to go to reaper v.1.1 rom. So i downloaded the rom manager in market then flash but i got a error: something like "privilege commands" this meand that im just s-off and not rooted?
So i want to root my phone, can you tell-me the best guide for my hboot? PLEASEEE
I have installed the superuser on the market but when i open i got no apps in there. When i click "flash clockworkmod revoery" i got the error "privileged commands". When i do the power button and volume down, i'm sure that im s-off and got this:
SAGA PVT ENG S-OFF
HBOOT-0.98.2000 (PG8810000)
RADIO-38.03.00.03_M
eMMC-boot
I cant understand if im rooted or not
Follow this thread
[INFO] After Revolutionary (S-OFF) Install Clockworkmod, root & more
from my Desire S using XDA Premium
Hi i'm going to get chevronwp7 when the tokens come out again as the unlocking problems here don't work on my phone and i'm wondering can I use homebrew? apps if I use chevronwp7?
I'm new to this stuff
You can use a lot of homebrew - anything that doesn't say it requires "interop unlock" or "full unlock" should work - but definitley not all of it.
What phone do you have? Some phones can easily be more completely unlocked.
GoodDayToDie said:
You can use a lot of homebrew - anything that doesn't say it requires "interop unlock" or "full unlock" should work - but definitley not all of it.
What phone do you have? Some phones can easily be more completely unlocked.
Click to expand...
Click to collapse
Ok thanks and HTC HD7
The HD7 actually can be interop-unlocked, but you probably need to downgrade its firmware (if you look under Settings -> About -> More info, check the Firmware version number. If the third cluster of digits is greater than 50000, you'll need to downgrade). HTC "fixed" the driver we were using to make registry modifications, including interop-unlock, some months back.
The HD7 can also run (many!) custom ROMs, if you decide to go that route. You'll probably need to downgrade the bootloader, also called the SPL (look for the bootloader version, if it's greater than 3.1.x you'll need to downgrade, if it's greater than 5.0 you'll need a couple cheap pieces of equipment to do it). Custom ROMs are typically "fully unlocked" and can run anything, even including some software ported from WinMo 6.5.
GoodDayToDie said:
The HD7 actually can be interop-unlocked, but you probably need to downgrade its firmware (if you look under Settings -> About -> More info, check the Firmware version number. If the third cluster of digits is greater than 50000, you'll need to downgrade). HTC "fixed" the driver we were using to make registry modifications, including interop-unlock, some months back.
The HD7 can also run (many!) custom ROMs, if you decide to go that route. You'll probably need to downgrade the bootloader, also called the SPL (look for the bootloader version, if it's greater than 3.1.x you'll need to downgrade, if it's greater than 5.0 you'll need a couple cheap pieces of equipment to do it). Custom ROMs are typically "fully unlocked" and can run anything, even including some software ported from WinMo 6.5.
Click to expand...
Click to collapse
?? How do you down grade firmware ??
Either roll back to an old backup, or re-flash the phone with an older ROM. The first option loses any data changed or added since the backup was made, though, and the second option wipes it all (hard reset).
In theory it should be possible to downgrade just the firmware (not the entire ROM) without wiping the phone, but if anybody has found a way to do so, I don't know of it. That doesn't mean much though; I'm not terribly knowledgeable around flashing the phone.
sinister1 said:
?? How do you down grade firmware ??
Click to expand...
Click to collapse
Did you ever find a Mango Verizon Spark stock rom and try reloading?
LiFePo4 said:
Did you ever find a Mango Verizon Spark stock rom and try reloading?
Click to expand...
Click to collapse
No I have not.
sinister1 said:
No I have not.
Click to expand...
Click to collapse
I was digging around XDA to find one to have on hand "just in case". I came across this thread;
http://forum.xda-developers.com/showthread.php?t=1254384
Went to this link;
http://www.filefactory.com/f/0dacfac3a33cc378/
And from reading the thread this is the one people used early on to upgrade VZW Trophys to Mango;
RUU_Spark_W_S_VERIZON_WWE_2.01.605.04_2K_new_partition_...
What confuses me is the other ones; are they NoDo original (the 1.xx ones)? And the second one could be the Mango one that also pushed the HTC Gen 1 drivers (which are fine) since it is slightly larger file size and has Radio in the file name...
GDTD - ideas?
You could try but I don't know.
EDIT: Read this post! The one file above is the one. It looks like from the date in this thread the one with Radio in it is the Gen2 drivers (don't want that). This thread also explains the other ones (1.xx).
http://forum.xda-developers.com/showthread.php?t=1427904
You can use a lot of homebrew - anything that doesn't say it requires "interop unlock" or "full unlock" should work - but definitley not all of it.
What phone do you have? Some phones can easily be more completely unlocked.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Andy8888 said:
You can use a lot of homebrew - anything that doesn't say it requires "interop unlock" or "full unlock" should work - but definitley not all of it.
What phone do you have? Some phones can easily be more completely unlocked.
Click to expand...
Click to collapse
Sinister1 and I are both on VZW Trophy (CDMA) phones and AKAIK no one has done a homebrew or custom ROM, so we are sort of screwed. We have Stock ROMs; that's all that's out there. DFT at one point said they were working on custom CDMA ROMs for the Sprint HTC Arrive and VZW HTC Trophy but they really have no way to test or use it so why would they.
---------- Post added at 09:08 PM ---------- Previous post was at 08:45 PM ----------
I edited post 9 so make sure to read it again if you haven't. The stock NoDo and Mango ROMs are there and I explained how to look for them.
im kind of confused. i want to roll back to the stock rom of my hd7 and these ospl, hspl is confusing (probably because im noob to this).anyway, i do have the stock rom by anzar and i want to flash my hd7 the stock rom, but the confusion worries me. the reason why i want to downgrade is my phone is kinda laggy now and always hard resets by itself.done all the ts provided to me by the htc tech rep and none of them fixed the problem. im thinking of flashing the stock rom and upgrade to mango from there (leaving out internet sharing since i dont need it and the device's mac address changes which i dont want my phone to do)
can i flash my hd7 (tmous) with the rom from anzr without downgading bootloader, spl's etc?
OS Version: 7.10.7720.68
firmware revision number: 2250.21.51004.531
hardware revision number: 0002
radio software version: 5.70.09.02a_22.51.50.21u
radio hardware version: a.12.0.d4
bootloader version: 5.10.2250.0(132968)
chip soc version: 2.2.5.0
thanks in advance for any reply or comment regarding this post
I want to send back my phone to htc because my earpiece is not working correclty. I rooted my phone with AlpharevX method. I wanted to go back to S-ON and stock rom so i dont void my warranty. I flashed 0.98 bootloader and the i run RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30.0822U_3822.10.08.04_M_release_234765_signed but it stoped updating the phone and gave me ERROR 131. It changed bootloader and radio but my phone has no rom inside. What should i do now?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wooow there is a big mess here!
First your phone is branded. You have to use the proper RUU. European won't do. Not true
Second you have used a leaked RUU firmware, posted by mdeejay so you should have used misc_version.
Third now you stuck without root so you have to use htcdev.com
Sent from my HTC Desire S
I thought my phone was not branded.... I should have checked that beforehand. I called HTC and they have the ruu for my phone but they wont give it to me... I'll try to find it elsewhere... not even htc has it on their site. If i get the old RUU will it flash the old bootloader and old radio? or im stuck on the new ones?
Sorry
I have checked and your CID is included in the European RUU. But still you have used the wrong RUU because 2.10.401.9 contains only the CID for Russia. The last GB RUU for the rest of the European region is 2.10.401.8
Anyway now even if you can get back the old 0.98 hboot you cannot use Revolutionary, because you need USB Debugging and an booted OS for it. With the Stock recovery you cannot use the misc_version. I am afraid the only way is htcdev.com flash a custom recovery, use the misc_version, relock the bootloader then go back to stock with a proper RUU. I hope they will acknowledge that your problem is hardware related and has nothing to do with the unlocked bootloader. But you can avoid that if you use older RUU (1.28 or 1.47) there is no Locked/Relocked line there
I run RUU_SAGA_ICS_35_S_HTC_EU_14.01.401.2_20.76.30.0835_3831.19.00.110_275068 everything went ok, phone booted. Ready to ship to HTC for repair! Thanks amidabuddha
ignited said:
i checked the EU ICS update and has my cid in there.... i flashed it and it updated ok... now it is booting....
Click to expand...
Click to collapse
You was fast
This is an option too.
There was a way with an OTA but now it is too late for that. The ICS RUU should keep the warranty on the hardware and I hope they will acnowledge it.
amidabuddha said:
You was fast
This is an option too.
There was a way with an OTA but now it is too late for that. The ICS RUU should keep the warranty on the hardware and I hope they will acnowledge it.
Click to expand...
Click to collapse
The ICS RUU is not official either?
ignited said:
The ICS RUU is not official either?
Click to expand...
Click to collapse
Well it is semi-official, so to say But should keep the warranty on the hardware.
Also the OTA way that I was thinking about has a 50 % chance to work, because it includes a modification of a signed by HTC zip.
So in any case the ICS RUU is the better option compared to htcdev.com unlock in terms of warranty. And the easier as well.
Good luck with the repair and sorry if I confused you somehow with my posts.
HTC INCREDIBLE S 710e
I follow the instructions to downgrade and s off my htc incredible s710e from this page.
http://forum.xda-developers.com/showthread.php?t=2118187
everything going quite right but during RUU installing i got an error message which says that this RUU is not suitable for you please select suitable RUU for your handset.
Igot RUU from this page.
http://d-h.st/vgw
now i want a Suitable RUU for my HTC.
HTC INCREDIBLE S 710e
HBOOT-2.02.002
RADIO-3831.18.00.11_M
eMMC_boot
May 22 2012
Android 4.0.4 (Ice Cream Sandwich)
Full HTC Sense 3.6 Interface
Multi-language (WWE)
softwre # 4.10.707.1
serial # ht23xtd11136
IMEI # 359836048384758
Wrong forum.This is Desire S.And delete serial and IMEI
SuperCID 11111111 for HTC One SV (k2u, k2ul)
As some people were asking and because of the completeness i'll post here the guide, to change your cid to supercid. This is the first step to get S-Off and it's mostly the same as at One S.
Credits and thanks to jmztaylor for guiding me through this painful session!
Notice:
You must know, that you can brick your device when you are doing something wrong! Only do this, if you know and understand what to do and how to do. Otherwise, let it be.
Ansonsten besser Finger weg!
I am not responsible if your device is bricked or damaged in any way!
Think about this twice!!!
I have tested this on k2_u, others reported success on k2_ul too.
For the other devices of One SV i don't know and don't give any guarantee that it will work.
Requirements:
You should have a working adb/fastboot environment and HTC drivers installed on PC. And you should know, how to handle adb/fastboot/dd commands.
USB-Debugging should be activated on the device.
The smartphone must be unlocked (over HTCdev.com) and must be rooted.
This will only work, if you are on ICS. With Jelly Bean hboot this will not work.
You need a Hex-Editor, i recommend HxD.
You can get your actuall cid with this fastboot cmd:
Code:
fastboot oem readcid
Result for me: HTC__102
How to:
Open cmd window where your adb is located.
There you make the following commands one after the other:
Code:
adb shell
Code:
su
Code:
dd if=/dev/block/mmcblk0p4 of=/sdcard/mmcblk0p4.img
Code:
exit
Code:
exit
Code:
adb pull /sdcard/mmcblk0p4.img
Now your bootloader is extracted to SD card, then into your adb folder.
Look at the file size of mmcblk0p4.img, it MUST be the same size after changing the cid! Don't flash it back, if it isn't the same size.
Now open the mmcblk0p4.img with Hex-Editor and look, where your cid is located (on my picture it is HTC__102). Afterwards it is followed by your IMEI number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now you have to overwrite your cid, Not copy and paste!
That means, put the cursor before H of HTC__102 and then you have to add 8 times the number 1 so it then looks like in the next picture.
If you are doing something wrong, HxD will complain. If not, it should be ok.
Now save.
Don't forget to check the filesize!
Back to command line you have to make the following commands one after the other:
Code:
adb push mmcblk0p4.img /sdcard/mmcblk0p4MOD.img
Code:
adb shell
Code:
su
Code:
dd if=/sdcard/mmcblk0p4MOD.img of=/dev/block/mmcblk0p4
Code:
exit
Code:
exit
Code:
adb reboot bootloader
Now you can check your new supercid with the fastboot command:
Code:
fastboot oem readcid
The result should be 11111111
Now you can go on, making your device S-Off.
Have fun!
Any chance to get super CID for all those who has JB alredy installed?? because i guess that i can´t go back to ICS , can i??
thanks
titin83 said:
Any chance to get super CID for all those who has JB alredy installed?? because i guess that i can´t go back to ICS , can i??
thanks
Click to expand...
Click to collapse
I'd also love to know the answer :good:
CID didn't changed
Hello and thanks for your time creating this guide.
I done everything exactly as you said but my CID didn't change...
My SV is K2_UL with HBOOT - 2.00
Any help?
Stallion34 said:
Hello and thanks for your time creating this guide.
I done everything exactly as you said but me cid didn't change...
My SV is K2_UL with HBOOT - 2.00
Any help?
Click to expand...
Click to collapse
Its because your on hboot 2.00. You need to S-Off your device with Moonshine and then you can change CID, if you still want.
And please, remove the quote of the first post, we have to scroll so long.
Thx for the answer...
I followed your suggestion but moonshine gives me an adb failure during the proccess...
I want to S-off my device and then try your custom JB rom...
Stallion34 said:
Thx for the answer...
I followed your suggestion but moonshine gives me an adb failure during the proccess...
I want to S-off my device and then try your custom JB rom...
Click to expand...
Click to collapse
You are already on JB, so there is no real profit for you, cause mine is not modded.
Let's talk in the Moonshine thread.
I can't post on development forums yet because I have < 10 posts
Anyway, I managed to S-OFF my device.
I disabled Root Call Blocker from running on Device boot and everything worked fine...
After S-OFF I changed successfully my CID (in case of needing it in future)
Thx again for your time.
Two last questions for you.
Is there any info from HTC about ONE SV and 4.2.2 android?
Do you know if CM or MIUI will develop firmware for ONE SV?
Thx in advance...
Stallion34 said:
I can't post on development forums yet because I have < 10 posts
Click to expand...
Click to collapse
Oh sorry, iforgot.
Anyway, I managed to S-OFF my device.
I disabled Root Call Blocker from running on Device boot and everything worked fine...
After S-OFF I changed successfully my CID (in case of needing it in future)
Click to expand...
Click to collapse
Fine.
Is there any info from HTC about ONE SV and 4.2.2 android?
Do you know if CM or MIUI develop firmware foer ONE SV?
Click to expand...
Click to collapse
CM i think yes, MIUI i don't think atm.
All info about 4.2.2 you'll find here.
Once we are S-OFF, why could be useful change our CID to 1111111?i got S-OFF whit moonshine but my hboot is still in 2.0.
Should I change it?
Thanks
titin83 said:
Once we are S-OFF, why could be useful change our CID to 1111111?i got S-OFF whit moonshine but my hboot is still in 2.0.
Should I change it?
Thanks
Click to expand...
Click to collapse
Updates! (if we will get some, lol)
A german "test" HTC One of a big internet website got the Android 4.2.2 update and they made a news article, the update is rolling out in germany. But others didn't get it.
In the end the phone had SuperCid and that was, why the phone got an update earlier than others.
Isn't that funny
FYI boost mobile keeps their CID in the same block. BUT it bricked my phone, I REPEAT, I BRICKED MY BOOST MOBILE k2_cl ONE SV, by trying to change to superCID.
I also got lucky and the nice people at radioshack gave me another @ no cost.
Just be more careful and beware Bricks can and will happen if you aren't prepared ( i.e. I was too lazy to actually use the method in this guide and used a terminal emulator on my phone) and gave myself a beautiful brick.
russellvone said:
FYI boost mobile keeps their CID in the same block. BUT it bricked my phone, I REPEAT, I BRICKED MY BOOST MOBILE ONE SV, by trying this superCID.
I also got lucky and the nice people at radioshack gave me another @ no cost.
Just be more careful and beware Bricks can and will happen if you aren't prepared ( i.e. I was too lazy to actually use the method in this guide and used a terminal emulator on my phone) and have myself a beautiful brick.
Click to expand...
Click to collapse
perhaps, you are not lucky
I had success with this way, and i'm very happy
I was just informing and sharing that I tried to change my CID with a different method than the one posted in the guide. And I failed to profit from it.
Yup, thats why i stated that this is very risky and for k2u/k2ul! The first one who tried the guide in german board also bricked his device by using a different hex-editor. He got a new one for free too.
But it is damn risky, everybody should know it, when trying.
I followed the guide exactly and got 2 One SV set to SuperCID.
You warned me... Lol should have listened :thumbup:
Lets say, its good, when you can return it for warranty.
There is no need to say, that you've bricked it yourself. You can say it doesn't start from one minute to the next...
Hello ! I did the precedure but there was img size and i didnt change it ... Can i lock bootloader and to expect the update if i relock my bootloader ? Thanks for some answear ! Btw i got custom recovery installed if this is importent
You can always relock your bootloader with cmd:
Code:
fastboot oem lock
But with custom recovery the OTA update will for sure fail!
ah my luck ... :/ I already done the steps from here andonce i was with success now i got error : device not found ... cant found where is my mistake :/ S-OFF and all , is like some circle :/ Can anybody help me ?
I have a question about making a demo htc one a9 into a working normal phone.
I found this
http://forum.xda-developers.com/one-...etail-t3269515
and many other guides about how to do that.
The general problem for me is that I simply cannot access the developer options
(or to be more exact, turn them on from the right corner of the dev options menu...everything but "running services" is gray and can't be clicked).
Is there a way to turn them on so I can turn OEM uncloking on to unlock bootloader via HTC support
as it seems that it's the only option to access fastboot to install twrp and root this device etc.??
Thanks in advance.
I'm not exactly sure, but I believe the demo HTC One A9 is running a different software altogether. I think you have to run an RUU to bring it to a non demo phone, although like I said,I'm not sure, I've never done it before
I now tried installing a new RUU to the phone, but the problem is that no version seems to suit it!
I always get the fail message when trying the SD card method.
"10 RU_MODELID_FAIL modelid in android-info mismatched" (x3 times)
What does this mean? do I still have the wrong RUU? I tried many from here:
http://forum.xda-developers.com/one-a9/general/wip-ruu-htc-one-a9-t3240344, including all the european versions I could find.
(Including the one where CID HTC__002 is shown).
EDIT:
As I can't use fastboot I tried finding out CID and MID using adb shell resulting:
CID = HTC__002
MID = just no answer here...
In the phones identity it says the Model number is same as the phones name (HTC One A9).
Phone number is unknown, IMSI is unavailable, bluetooth adress is unavailable...
Kernel version 3.10.73-perf-gb10289f
Baseband version [email protected]_29.05_F
Build number 1.10.401.7 CL635503 release-keys
Software number 1.10.401.7
Android 6.0, HTC Sense 7.0_g
Maybe a stupid question, but did you try typing 10 times on the build nr in the info and software section to get the developer option running?
Sent from my HTC One A9 using XDA-Developers mobile app
---------- Post added at 02:15 PM ---------- Previous post was at 02:11 PM ----------
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Just there where build nummer is written.
Sent from my HTC One A9 using XDA-Developers mobile app
Yes I have clicked the build number to open the developer settings tab.
As I mentioned in my first post ("to be more exact...") the problem is that I can't "turn them on".
By this I mean that when you open the developer settings tab it shows all the options there (OEM-unlock, USB-debugging etc.) grayed.
I can't click them from off to on. There is also a "switch" in the top right corner of the developers settings tab which makes you able to choose if the
settings are used or ignored (off). That is the "release" switch for all the real settings in the tab, and I can't turn it on!
Also, as I mentioned in my second post, I tried installing different RUU:s to the phone unsuccesfully
(they don't need the OEM unlock and could return the phone to a more normal state so I could access the dev. settings).
I also tried the windows.exe method instead of SD-card method, but somehow the phone got stuck in the update window
and that's where the situation is at the moment.
I'll probably wait for the battery to drain to zero and reboot the machine a couple times before charging it and hopefully I'll get out of that loading screen...
If anyone has an idea on how to get rid of the loading screen stuck, or an idea on how to make the dev. settings work/have a correct RUU for this device
based on the information provided in my second post, please post a reply!
Again, thanks for all the answers.
chargoal said:
Yes I have clicked the build number to open the developer settings tab.
As I mentioned in my first post ("to be more exact...") the problem is that I can't "turn them on".
By this I mean that when you open the developer settings tab it shows all the options there (OEM-unlock, USB-debugging etc.) grayed.
I can't click them from off to on. There is also a "switch" in the top right corner of the developers settings tab which makes you able to choose if the
settings are used or ignored (off). That is the "release" switch for all the real settings in the tab, and I can't turn it on!
Also, as I mentioned in my second post, I tried installing different RUU:s to the phone unsuccesfully
(they don't need the OEM unlock and could return the phone to a more normal state so I could access the dev. settings).
I also tried the windows.exe method instead of SD-card method, but somehow the phone got stuck in the update window
and that's where the situation is at the moment.
I'll probably wait for the battery to drain to zero and reboot the machine a couple times before charging it and hopefully I'll get out of that loading screen...
If anyone has an idea on how to get rid of the loading screen stuck, or an idea on how to make the dev. settings work/have a correct RUU for this device
based on the information provided in my second post, please post a reply!
Again, thanks for all the answers.
Click to expand...
Click to collapse
VolUp+Power will force power off.
The 1.10.401.7 RUU and above SHOULD flash. I'm not certain that this will solve your problem though, since your CID will still be the same (I'm pretty sure HTC__002 is for Euro demo devices only). I suggest using Sunshine to s-off and convert to BS_US001 (US unlocked) or HTC__001.
CSnowRules said:
VolUp+Power will force power off.
The 1.10.401.7 RUU and above SHOULD flash. I'm not certain that this will solve your problem though, since your CID will still be the same (I'm pretty sure HTC__002 is for Euro demo devices only). I suggest using Sunshine to s-off and convert to BS_US001 (US unlocked) or HTC__001.
Click to expand...
Click to collapse
Yeh I figured that forced shut down already, but thanks anyways.
Umm, do I need the chargeable/paid version of Sunshine to S-off?
I tried the free android version earlier and it didn't work on the phone (just said I should contact XDA help or something...).
I'm not familiar with this program (or with s-offing/RUU's/CID's etc. to be honest), so this is a bit of a learning process to me.
So if the CID is wrong (HTC_002, which you thought to be some kind of demo CID) how does this matter when it comes to the normal
use of the phone? Won't it be getting normal OTA updates or something?
Do I have to change it in order to make the phone work normally?
So you think that the only way to solve this mess is to purchase Sunshine in order to s-off without unlocking the bootloader
(going around the original problem with the dev. settings been locked) and to change the CID (and MID? does this matter?)?
Could the phone be turned into a "fresh" normal HTC without using any custom ROMs like cyanogenmod after this progress?
Is the Sunshine 100% reliable when it comes to s-offing this kind of phone? Wouldn't want to pay 25$ for nothing...
Sorry for the amount of questions.
Thanks for you help, it is much appreciated.
chargoal said:
Yeh I figured that forced shut down already, but thanks anyways.
Umm, do I need the chargeable/paid version of Sunshine to S-off?
I tried the free android version earlier and it didn't work on the phone (just said I should contact XDA help or something...).
I'm not familiar with this program (or with s-offing/RUU's/CID's etc. to be honest), so this is a bit of a learning process to me.
So if the CID is wrong (HTC_002, which you thought to be some kind of demo CID) how does this matter when it comes to the normal
use of the phone? Won't it be getting normal OTA updates or something?
Do I have to change it in order to make the phone work normally?
So you think that the only way to solve this mess is to purchase Sunshine in order to s-off without unlocking the bootloader
(going around the original problem with the dev. settings been locked) and to change the CID (and MID? does this matter?)?
Could the phone be turned into a "fresh" normal HTC without using any custom ROMs like cyanogenmod after this progress?
Is the Sunshine 100% reliable when it comes to s-offing this kind of phone? Wouldn't want to pay 25$ for nothing...
Sorry for the amount of questions.
Thanks for you help, it is much appreciated.
Click to expand...
Click to collapse
As far as I know, the only way to make the phone as if it were a stock retail device is by going s-off to change the CID. I haven't heard of Sunshine failing. It does checks to make sure it will work and doesn't charge you unless it will.
You can s-off, change CID, flash appropriate RUU, then s-on and have a completely stock, retail-converted device.
I wouldn't go back s-on if the phone is for your personal use.
Refer to the convert to unlocked thread.