Hi guys,
I have One XL Arabic version, Model number is "HTC EVA_UTL", CID is HTC__J15.
I'm on the latest official firmware 4.1.1, software number "1.01.401.03", build number "1.01.401.03 CL141628 release-keys".
HBoot is "2.10.0000".
Here is a picture of my HBoot
{
"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"
}
I was searching the development section here, but I didn't find any thing related to my HBoot.
Can I use the Asian or the U.S. variants ROMs for this one?
Thanks,
Halim2k said:
Hi guys,
I have One XL Arabic version, Model number is "HTC EVA_UTL", CID is HTC__J15.
I'm on the latest official firmware 4.1.1, software number "1.01.401.03", build number "1.01.401.03 CL141628 release-keys".
HBoot is "2.10.0000".
I was searching the development section here, but I didn't find any thing related to my HBoot.
Can I use the Asian or the U.S. variants ROMs for this one?
Thanks,
Click to expand...
Click to collapse
That's tough to answer without testing. It "SHOULD" be safe but without testing there's no way to know for sure.. the drivers that come with your hboot may or may not mesh well with the roms since they are typically based off aT&T or Telus Roms.
Strange... Two posts about this phone within 24 hours. As exad said, it SHOULD work, but nothing is guaranteed. If you would be our guinea pig, then it would help out numerous other people. If you don't feel comfortable doing that, then it's totally understandable.
Yrah and that makes it three posts within a week. I wonder if it's just been released recently.
Sent from my Evita
---------- Post added at 02:55 AM ---------- Previous post was at 02:51 AM ----------
Here's that other thread I was talking about before, this guy says he was able to flash our ROMs onto his Evita UTL.
http://forum.xda-developers.com/showthread.php?p=43237946
Sent from my Evita
It's OK to make it as guinea pig for others, but my only concern is that I can't find any RUU for it, as a last defense line
I'll try to search again.
Halim2k said:
It's OK to make it as guinea pig for others, but my only concern is that I can't find any RUU for it, as a last defense line
I'll try to search again.
Click to expand...
Click to collapse
For the 3.18 software on our phones, it bricks if you RUU while S-ON with 11111111 or 22222222 as the CID so just be mindful of this as i imagine the latest RUU for your device, if you find one, will probably behave similarly.
Just out of interest, I had a look around. On the RUU collection thread there is a HTC GCC (Gulf Cooperation Council) RUU section which seems to fit your device with a CID of HTC__J15.
Please listen to Exad and be careful, because running an RUU with the wrong setup on your phone can definitely brick it.
EDIT: it looks like the RUU listed for your phone on the link above is lower than your current firmware configuration. Interestingly enough though, it seems to share the 1.14 hboot that our device had, which is positive.
Sent from my Evita
Thanks all for the advice.
I'll unlock the bootloader, install a recovery, nand backup, then I'll try revone S-Off.
I have an old ICS RUU, but sure it's useless without S-Off.
Halim2k said:
Thanks all for the advice.
I'll unlock the bootloader, install a recovery, nand backup, then I'll try revone S-Off.
I have an old ICS RUU, but sure it's useless without S-Off.
Click to expand...
Click to collapse
Correct! Once you're S-OFF you shouldn't have any problems RUUing at all. If you don't mind, I'd love if you update this post regarding stability of our Roms on your phone after you've had a chance to try one for a couple days.
Sure, I'll update the post tomorrow.
What's revone s-off? There's only one working s-off method for the XL and it's called Facepalm, it can be found here.
Sent from my Evita
Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Now I unlocked using HTCdev, installed Viper XL, as expected got a bootloop.
Then extracted boot.img from ROM zip and "fastboot flash boot boot.img".
Now every thing is working fine, I didn't check LTE connectivity yet, as my SIM is only 3G, I'll check it soon.
Every thing else is working fine.
There is no way to get S-OFF or to change CID as I tried every single method for One XL with no success.
Also I could not find any new RUU for the phone.
Thanks for the help guys, any questions are welcomed.
Halim2k said:
Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Now I unlocked using HTCdev, installed Viper XL, as expected got a bootloop.
Then extracted boot.img from ROM zip and "fastboot flash boot boot.img".
Now every thing is working fine, I didn't check LTE connectivity yet, as my SIM is only 3G, I'll check it soon.
Every thing else is working fine.
There is no way to get S-OFF or to change CID as I tried every single method for One XL with no success.
Also I could not find any new RUU for the phone.
Thanks for the help guys, any questions are welcomed.
Click to expand...
Click to collapse
Have you tried the JET tool?.... It would be risky but SHOULD work.
That's how I did mine as AT&T superCID methods don't work for my phone.
Halim2k said:
Revolutionary method of getting S-OFF "revone" which is for HTC One, but I gave it a try anyway and failed.
Click to expand...
Click to collapse
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita
timmaaa said:
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita
Click to expand...
Click to collapse
So true! I suppose I didn't stress this enough. Especially since JET tool does purposefully brick the phone in order to write an older Hboot. Though, theoretically even if it did brick, it should not be so far as the unbrick evita thread wouldn't be able to restore it. This of course does not make it any less dangerous. Just saying.
OP does seem to be knowledgeable, which is the only reason I am pointing out these more advanced methods that may work.
I think the the codes after the codename go like this:
U - WCDMA/GSM
L - FDD-LTE
T - TD-LTE and/or TD-SCDMA
A - FDD-LTE-Advanced
W - CDMA2000
G - GSM
D - Dualsim
H - ??
All the Evita's up to now were UL's ( WCDMA/GSM + FDD-LTE ).
This Saudi Arabia Evita being a UTL should be capable of WCDMA/GSM + TD-LTE and/or TD-SCDMA + FDD-LTE.
The difference might be all software driven, but it is unlikely. Different amps, filters etc are likely in use if not more.
It is clearly running a different hboot, radio, dsp than any EVITA_UL has had.
The HTC software versioning seems to make this device not software pegged to the Evita_UL.
The Arabic RUU is not for this device, it is for a Evita_UL like all the other devices we had seen. maybe ROM's will work but great care should be taken as the radio, hboot and dsp etc are all very likely incompatible, or will break the support of the TD technologies.
The Arabic device was from the x.xx.415.x branch not x.xx.401.x.
It seems the Arabic Evita_UL has been abondoned, it never received an update to Jelly Bean. It is possible the device was never released and was reworked to add TD-LTE and later became this Evita_UTL device.
This phone should at best be regarded as a relative of the Evita_UL but not the same device.
There is no publicly available RUU that will work with this device.
Before replacing anything backups should be taken, eg of all the partitions.
No risky actions should be taken without great care.
Assume you know nothing about this device and anything you do could brick it.
exad said:
Have you tried the JET tool?.... It would be risky but SHOULD work.
That's how I did mine as AT&T superCID methods don't work for my phone.
Click to expand...
Click to collapse
I red JET tool thread, and for sure it will hard brick my phone.
timmaaa said:
Please just be careful about trying exploits which are not designed for our phone, you could seriously screw up your phone.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, I tried revone as I was almost 99% sure it's safe, as it's not envolving any HBoot flashing.
twistedddx said:
I think the the codes after the codename go like this:
U - WCDMA/GSM
L - FDD-LTE
T - TD-LTE and/or TD-SCDMA
A - FDD-LTE-Advanced
W - CDMA2000
G - GSM
D - Dualsim
H - ??
All the Evita's up to now were UL's ( WCDMA/GSM + FDD-LTE ).
This Saudi Arabia Evita being a UTL should be capable of WCDMA/GSM + TD-LTE and/or TD-SCDMA + FDD-LTE.
The difference might be all software driven, but it is unlikely. Different amps, filters etc are likely in use if not more.
It is clearly running a different hboot, radio, dsp than any EVITA_UL has had.
The HTC software versioning seems to make this device not software pegged to the Evita_UL.
The Arabic RUU is not for this device, it is for a Evita_UL like all the other devices we had seen. maybe ROM's will work but great care should be taken as the radio, hboot and dsp etc are all very likely incompatible, or will break the support of the TD technologies.
The Arabic device was from the x.xx.415.x branch not x.xx.401.x.
It seems the Arabic Evita_UL has been abondoned, it never received an update to Jelly Bean. It is possible the device was never released and was reworked to add TD-LTE and later became this Evita_UTL device.
This phone should at best be regarded as a relative of the Evita_UL but not the same device.
There is no publicly available RUU that will work with this device.
Before replacing anything backups should be taken, eg of all the partitions.
No risky actions should be taken without great care.
Assume you know nothing about this device and anything you do could brick it.
Click to expand...
Click to collapse
Thanks for the info.
I spent the last 2 days searching and reading about this variant, and you are right.
This one has TD-LTE support, and it is different than any other variant, and of course we can't cross flashing boot image.
That is why I think 4G LTE will not work with cooked ROMs.
Also without a proper backup, there no way to go back to stock firmware, as this firmware version which is "1.01.401.03" is the initial release.
Now my most important concern is to find stock RUU or OTA for this variant, which I really appreciate any help about it.
I would ask tour carrier about it. They should have an ruu or ota. If you can extract the radio you should be able to run our roms
Sent from my One X using xda app-developers app
Just some more random info. The source for this device and software version was released in March by HTC. HTC dont have a habit of releasing source prior to the release of the device.
When it first got released it caught my eye because of the software version not matching the existing pattern and the T in the model.
Maybe you can find someone with a bit of spare time to compare what can be found in the kernel for differences to the evita_ul.
http://dl4.htc.com/RomCode/Source_and_Binaries/evitautl-jb-crc-3.4.10-cl141628-1.zip
Also seems like a prerelease 1.00.401.01 existed.
mid is reported in other forums as PJ8350000
@guys
Need ur help in restoring my bricked phone! HTC EVA_UTL, i did was s-off and then tried to flash the "RUU_Evita_UL_Vodafone_DE_1.82.162.4_Radio_0.17a.32.09.04_T_10.85.32.16L_release_260067_signed" thru SDCARD method and when it asked me to confirm to update by pressing the volume up button, i did! and it just satrted flashing the first part and then went dead!
so i would like to know if there's a way to fix it by copying it from other same model phone or any thing?
pls inform?
WBR
ReyTech.
Related
Unlock Boatloader is officially launched
This is not S-OFF
The strange thing here is that you can get root with this unlock even tho your device will remain S-ON
{
"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"
}
http://www.htcdev.com/bootloader/unlock-instructions
Seems very pointless in the DEV section for me... We already have unlocked bootloader´s and S-Off here....
and this is not for the DEV section We dont like theire method here! We have revolutionary
and this has nothing to do in this section
xtcislove said:
Seems very pointless in the DEV section for me... We already have unlocked bootloader´s and S-Off here....
and this is not for the DEV section We dont like theire method here! We have revolutionary
and this has nothing to do in this section
Click to expand...
Click to collapse
Going to disagree. It's another method to unlock, although not really s-off. Cwm and roms can still benefit.
Sent from my HTC Sensation 4G
GideonX said:
Going to disagree. It's another method to unlock, although not really s-off. Cwm and roms can still benefit.
Sent from my HTC Sensation 4G
Click to expand...
Click to collapse
not trying to start a war, but i really am confused: HOW will this help those of us here in the dev section? is there any benefit to using their official tool, which is guaranteed to void any and all warranties for us if we DO use them? given that rather large caveat to use, why would anyone voluntarily use this? what could we gain that Im not seeing? I'd honestly like to know, i saw their anouncement yesterday, and looked into it, but didnt know what to make of it myself. I hope someone more knowledgeable than myself can answer this for all of us.
jmwils3 said:
not trying to start a war, but i really am confused: HOW will this help those of us here in the dev section? is there any benefit to using their official tool, which is guaranteed to void any and all warranties for us if we DO use them? given that rather large caveat to use, why would anyone voluntarily use this? what could we gain that Im not seeing? I'd honestly like to know, i saw their anouncement yesterday, and looked into it, but didnt know what to make of it myself. I hope someone more knowledgeable than myself can answer this for all of us.
Click to expand...
Click to collapse
Warranty paranoia again.
Unlocking via htc does not void your warranty completely. No one is going to deny your warranty if what caused it was not related to the unlocking.
For example, if your digitizer fails, no one will deny you warranty on it because you unlocked via htc as that was not the cause. If you decided to drop it and went looking for a warranty exchange, that's another story. Make sense?
As stable as revolutionary dev release is, some people just want an htc official method. Wasn't that what thousands of users petitioned for?
Either way, I think it has a place here.
Sent from my HTC Sensation 4G
I have followed the HTC instructions and got HBOOT UNLOCK and still S-OFF thanks to revolutionary.
But HTC only unlock the Boatloader (not the S-ON)
Wasnt this released mid-august?
Sent from my HTC Sensation Z710e using XDA App
Steve0007 said:
I have followed the HTC instructions and got HBOOT UNLOCK and still S-OFF thanks to revolutionary.
But HTC only unlock the Boatloader (not the S-ON)
Click to expand...
Click to collapse
some guys are searching for an unlocked hboot 1.18.
since you got it with the official htc method, could you dump it for us?
http://forum.xda-developers.com/showthread.php?t=1231998&page=2
I think the whole point is this is the _development_ section. Here we discuss and help each other _making_ methods. Since this method is completely done (HTC official) it has no place in the development section, but rather in the standard (q&a?) section.
this method requires no development, it is done. Read the 'iron fist' post by the mods to see what should go in development and not.
dipje said:
I think the whole point is this is the _development_ section. Here we discuss and help each other _making_ methods. Since this method is completely done (HTC official) it has no place in the development section, but rather in the standard (q&a?) section.
this method requires no development, it is done. Read the 'iron fist' post by the mods to see what should go in development and not.
Click to expand...
Click to collapse
While we're fisting, we may as well get the Evo 3D thread in the right place too.
http://forum.xda-developers.com/showthread.php?t=1243847
Strange, they don't care as much as us Sensation users on whether or not it belongs in dev. They do however share the same warranty paranoia, crazy!
GideonX said:
Warranty paranoia again.
Unlocking via htc does not void your warranty completely. No one is going to deny your warranty if what caused it was not related to the unlocking.
For example, if your digitizer fails, no one will deny you warranty on it because you unlocked via htc as that was not the cause. If you decided to drop it and went looking for a warranty exchange, that's another story. Make sense?
As stable as revolutionary dev release is, some people just want an htc official method. Wasn't that what thousands of users petitioned for?
Either way, I think it has a place here.
Sent from my HTC Sensation 4G
Click to expand...
Click to collapse
+1 to this from a prior Nexus One user. On the Nexus One, we never had S-OFF. We ALWAYS had S-ON and the unlocked bootloader with the unlocked icon one would see when first booting up. The Nexus One had root. We had a ton of developers back in the day putting out all sorts of ROMs and not just Sense versions. Yes, I know that once CM7 gets past Alpha, we should see MIUI as well as CM7 variants along with Sense. But ONLY having an unlocked bootloader did not stop development with S-ON. BUT....more important...MY Nexus had bad Nand memory issues causing over 85MB of bad memory in the /Data partition, and some more bad Nand in /Cache as well as /System. I submitted my unlocked Nexus ONE to HTC. The warranty with regards to the bad Nand was covered. Unlocking the bootloader did NOT affect my warranty since it did NOT cause the bad Nand. Too much hysteria regarding methods of unlocking and I am proof positive this is hysteria is exactly that. Will HTC state this policy in public. Nope. But they did honor the warranty and they full well knew my Nexus One was unlocked.
Last question for all....what can the Sensation do right now with our Revolutionary S-Off that a Sensation with a fully rooted but S-ON unlocked bootloader cannot do. I ask only because this exact issue about S-ON vs S-OFF and unlocked bootloaders was asked by me long before the Revolutionary means was finally posted. I was inundated with the fact that the Sensation was locked down more by hardware and higher Security and just unlocking the bootloader would not really gain anything.
Waiting to be bombarded with opinions. Would rather see facts presented please.
Does an unlocked bootloader, but with S-ON enable us to utilize commands such as "fastboot flash ....." ?
eyegor said:
Does an unlocked bootloader, but with S-ON enable us to utilize commands such as "fastboot flash ....." ?
Click to expand...
Click to collapse
Well, I'll tell you what I have done, my Sensation was S-OFF-ed using Revolutionary method but since I like more official things than actual hacks I wanted to go htc way so I flashed latest 2.3.4 RUU (I've Super CID my phone, just in case) than I unlocked it using htc unlocker so now I have UNLOCKED and S-OFF on my bootloader screen, flash recoveries as well as ROM's works without any problems. I didn't tested flash radio yet 'cause there's nothing newer than this one I already have.
Just some interesting note regarding this htc unlocking procedure, on last screen on a phone, when it actually finally asks you to unlock by pressing POWER button actually nothing happens, to exit and reboot this screen you have to choose second option, like what you will choose if you change your mind and decided to not unlock. This is a problem with a POWER button many people have after updating on 2.3.4. Your phone will be unlocked anyway.
I see. This could be due to the fact that you did not set the security flag back to three after flashing the RUU.
Does the website ask you for the serial number/imei or anything like that?
eyegor said:
Does an unlocked bootloader, but with S-ON enable us to utilize commands such as "fastboot flash ....." ?
Click to expand...
Click to collapse
It should. But I base that on my Nexus One which only has the unlocked bootloader.
banesi said:
Well, I'll tell you what I have done, my Sensation was S-OFF-ed using Revolutionary method but since I like more official things than actual hacks I wanted to go htc way so I flashed latest 2.3.4 RUU (I've Super CID my phone, just in case) than I unlocked it using htc unlocker so now I have UNLOCKED and S-OFF on my bootloader screen, flash recoveries as well as ROM's works without any problems. I didn't tested flash radio yet 'cause there's nothing newer than this one I already have.
Just some interesting note regarding this htc unlocking procedure, on last screen on a phone, when it actually finally asks you to unlock by pressing POWER button actually nothing happens, to exit and reboot this screen you have to choose second option, like what you will choose if you change your mind and decided to not unlock. This is a problem with a POWER button many people have after updating on 2.3.4. Your phone will be unlocked anyway.
Click to expand...
Click to collapse
I confirm, pressing the Power to yes does not react but i aslso confirm that it works as i have now HB 1.18 UNLOCK and i am also S-OFF (using previously revolutionary S-OFF instructions)
has anyone here use the htc unlock ?
Steve0007 said:
I confirm, pressing the Power to yes does not react but i aslso confirm that it works as i have now HB 1.18 UNLOCK and i am also S-OFF (using previously revolutionary S-OFF instructions)
Click to expand...
Click to collapse
can you post here the hboot 1.18.0000 unlocked ?
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
vladnosferatu said:
can you post here the hboot 1.18.0000 unlocked ?
Code:
adb shell
dd if=/dev/block/mmcblk0p12 of=/sdcard/hboot.img
Click to expand...
Click to collapse
1.18 hboot 1.18 UNLOCK posted HERE
Other ways:
a) extract the firware from Official 1.45.XXX.XX Rom and flash the necessary firware components (this is what I did)
b) flash official 1.45.XXX.XX Rom, S-OFF it with revolutionary solution and then follow official HTC Unlock Boatloader instructions...
Steve0007 said:
1.18 hboot 1.18 UNLOCK posted HERE
Other ways:
a) extract the firware from Official 1.45.XXX.XX Rom and flash the necessary firware components (this is what I did)
b) flash official 1.45.XXX.XX Rom, S-OFF it with revolutionary solution and then follow official HTC Unlock Boatloader instructions...
Click to expand...
Click to collapse
thanks a lot
hey everyone, i had my telstra one xl on JB for awhile then i wanted to do the newest update from them so upon reading up on it i need to have supercid and s-off, so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111, sweet now to do s-off which failed to flash the RUU, i needed to relock the bootloader, so i relocked it.
problem is now its stuck in a bootloop to fastboot and wont show up in ADB devices, i also cant get into twrp in recovery now.
is there any way to fix this or throw the phone out?
It's a bit difficult to make out what you're saying in parts of that post.
Was s-off successful?
Was the RUU successful?
Which RUU did you use?
What are your current bootloader details?
Sent from my Evita
sirus17 said:
so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111,
Click to expand...
Click to collapse
Did you actually verify that you had SuperCID? I don't think there is a one-click for the Telstra version. The one-click app for SuperCID I'm aware of is intended for AT&T, and will fail with any other CID.
Which may actually be a good thing (if SuperCID failed). Since if a Jellybean RUU is flashed with SuperCID and s-on (its not clear whether you were successful with s-off) it will pretty much a guaranteed brick.
sirus17 said:
is there any way to fix this or throw the phone out?
Click to expand...
Click to collapse
If the screen comes on, its probably possible to recover. But we need more info as timmaaa indicated above.
There is actually a one-click tool for the Telstra version, I stumbled across it very soon after getting my phone mid last year. I found it on an Australian Android site, I think it was Ausdroid.
I'm not sure whether the tool is specifically for the Telstra version alone, but it definitely works on Telstra Evitas as I used it on my fiance's Evita (and mine which is a Hong Kong model).
Sent from my Evita
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
twistedddx said:
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
Click to expand...
Click to collapse
Really not sure, now that I look into it more. If its the old one by DesignGears, it does work with Rogers, but doesn't seem to mention Telstra (at least if I just search the thread for "Telstra"): http://forum.xda-developers.com/showthread.php?t=1672284
And x-factor also fails for any CID except AT&T, if I understand correctly. So it seems these scripts all look for certain CIDs, so if its not explicitly included, they will fail. Of course, if there is one made specifically for Telstra (as timmaaa mentioned) it apparently wasn't posted on XDA.
But really my main point is that the OP needs to verify and be clear on this, as well as several other factors.
hi there..
i'm new on this section..cause i just bought the device.. anyway..
i read almost most important topics about s-off and super cid and custom recovery.. but i can not be 100% sure that i can do this alone
HTC HD2 is my first android device and i almost aware of how the things work to have a stock rom on y device..
but because of my device has not any warranty so i need to be careful not to brick my phone..
so i want to ask you guys help me step by step to do this right..
i think first i need to s-off my phone / read about this on some persian forums / to do this i have to get the unlock code from HTCDev ..right?
i know the steps..
next i need to install custom recovery which TWRP 2.6.3.0 is better than other version..right?
then i move the downloaded rom to my phone and from the recovery i install it.. right?
that was the final step.. ok?
so what about super cid.. how can i do this? is it necessary or what?
how can i back to stock rom/?
and what is the best rom for battery saveing which has sence 5?
thanks..
If you have the HD2 you're in the wrong forum, this is the One XL forum. You need to find the correct forum and ask there as each device has different methods to unlocking and rooting.
Sent from my Evita
timmaaa said:
If you have the HD2 you're in the wrong forum, this is the One XL forum. You need to find the correct forum and ask there as each device has different methods to unlocking and rooting.
Sent from my Evita
Click to expand...
Click to collapse
thanks for noticing ,,, BUT ...
{
"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"
}
Firstable...wrong forum but since u new...is ok.....u need to start somewhere first.... Basically installing custom rom is always same process but different phone different method.....like timmaaa said on previous post.
1. U need to get root....to get superuser
2. Install recovery
3. U need to unlock your bootloader from Htc.Dev and choose your device
4. SuperCID .....
5. S-OFF
6.Download Custom ROM of your choice
7.Flash ROM from recovery....
8.Enjoy your custom ROM
But remember different device .....different method to root...etc
Swyped From BlueICESense_JBE
first of all thanks for help..
guys.. i bought HTC One XL.. belongs to no carrier.. i'm in middle east.. i do not understand what are saying about different device..
you mean every one xl with different carrier has its own method to root or s-off or etc.. interesting..
so now you know about my phone..
by the way i know the steps.. how can i do them/
i mean first i should unlock my bootloader to root my phone or install recovery..right?
but the order of the steps ted77usa said is different and i am totally confused.. you know what i mean?
what is the difference between s-off and unlock the bootloader?
is superCID necessary and if yes how do i do this?
these are my problems...
jabi_james said:
first of all thanks for help..
guys.. i bought HTC One XL.. belongs to no carrier.. i'm in middle east.. i do not understand what are saying about different device..
you mean every one xl with different carrier has its own method to root or s-off or etc.. interesting..
so now you know about my phone..
by the way i know the steps.. how can i do them/
i mean first i should unlock my bootloader to root my phone or install recovery..right?
but the order of the steps ted77usa said is different and i am totally confused.. you know what i mean?
what is the difference between s-off and unlock the bootloader?
is superCID necessary and if yes how do i do this?
these are my problems...
Click to expand...
Click to collapse
Well at first u said ur phone/device are HTC HD 2 ....now u said Htc one Xl.....htc one xl mean from att ...if u do have htc one xl .....u are on the right forum and right device......all the step are connected.....u need to root ur device first so u can install recovery Twrp is recommended for our device.....coz to install recovery required superuser permission......U know what.... first thing first......power off your phone and then hold power+volume down combo button.....this would bring u to your bootloader and tell us what kinda hboot that u have? Either s-off or s-on.....locked or unlocked.....and what version of your Hboot so we can go from there......because diferent hboot is diferent method and steps......If u have adb/fastboot.exe u can plug your device to Pc ...and enter command from where u save adb/fastboot file......code are : adb reboot bootloader this would reboot your phone and bring you to your bootloader......And knowledge for adb/fastboot is required in order for u to mod your device......if your bootloader unlockEd.....most likely u have supercid....coz during process of unlocking bootloader u chance your device ID for example At&t is CWS__001 and u change it to 11111111 ( supercid ) but diferent carier is diferent thats what i mean and YES supercid is required for S-OFF......And u said u bought Htc one X with no carrier ....u might have international htc one X......not htc one xl that's different device
Swyped From BlueICESense_JBE
jabi_james said:
first of all thanks for help..
guys.. i bought HTC One XL.. belongs to no carrier.. i'm in middle east.. i do not understand what are saying about different device..
you mean every one xl with different carrier has its own method to root or s-off or etc.. interesting..
so now you know about my phone..
by the way i know the steps.. how can i do them/
i mean first i should unlock my bootloader to root my phone or install recovery..right?
but the order of the steps ted77usa said is different and i am totally confused.. you know what i mean?
what is the difference between s-off and unlock the bootloader?
is superCID necessary and if yes how do i do this?
these are my problems...
Click to expand...
Click to collapse
The problem was that in the first post you only mentioned the HD2, hence the confusion. To help you properly I'm gonna need to see your bootloader details please. If you have the middle eastern model this might be tricky.
Sent from my Evita
---------- Post added at 11:02 AM ---------- Previous post was at 11:00 AM ----------
ted77usa said:
Well at first u said ur phone/device are HTC HD 2 ....now u said Htc one Xl.....htc one xl mean from att ...if u do have htc one xl .....u are on the right forum and right device......all the step are connected.....u need to root ur device first so u can install recovery Twrp is recommended for our device.....coz to install recovery required superuser permission......U know what.... first thing first......power off your phone and then hold power+volume down combo button.....this would bring u to your bootloader and tell us what kinda hboot that u have? Either s-off or s-on.....locked or unlocked.....and what version of your Hboot so we can go from there......because diferent hboot is diferent method and steps......If u have adb/fastboot.exe u can plug your device to Pc ...and enter command from where u save adb/fastboot file......code are : adb reboot bootloader this would reboot your phone and bring you to your bootloader......And knowledge for adb/fastboot is required in order for u to mod your device......if your bootloader unlockEd.....most likely u have supercid....coz during process of unlocking bootloader u chance your device ID for example At&t is CWS__001 and u change it to 11111111 ( supercid ) but diferent carier is diferent thats what i mean and YES supercid is required for S-OFF......And u said u bought Htc one X with no carrier ....u might have international htc one X......not htc one xl that's different device
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Hang on, that's not exactly right. Not all Evitas are from at&t, they are available in several countries, from several carriers, branded and unbranded, and there is also a middle eastern model which is a bit different. We need to establish which model he has first.
Sent from my Evita
ted77usa said:
Well at first u said ur phone/device are HTC HD 2 ....now u said Htc one Xl.....htc one xl mean from att ...if u do have htc one xl .....u are on the right forum and right device......all the step are connected.....u need to root ur device first so u can install recovery Twrp is recommended for our device.....coz to install recovery required superuser permission......U know what.... first thing first......power off your phone and then hold power+volume down combo button.....this would bring u to your bootloader and tell us what kinda hboot that u have? Either s-off or s-on.....locked or unlocked.....and what version of your Hboot so we can go from there......because diferent hboot is diferent method and steps......If u have adb/fastboot.exe u can plug your device to Pc ...and enter command from where u save adb/fastboot file......code are : adb reboot bootloader this would reboot your phone and bring you to your bootloader......And knowledge for adb/fastboot is required in order for u to mod your device......if your bootloader unlockEd.....most likely u have supercid....coz during process of unlocking bootloader u chance your device ID for example At&t is CWS__001 and u change it to 11111111 ( supercid ) but diferent carier is diferent thats what i mean and YES supercid is required for S-OFF......And u said u bought Htc one X with no carrier ....u might have international htc one X......not htc one xl that's different device
Swyped From BlueICESense_JBE
Click to expand...
Click to collapse
Hey Ted, sorry to say but there are multiple things wrong with this post. Maybe just hold back on giving advice until you're well versed with this device. Giving wrong advice can lead to someone bricking their phone and nobody wants to be responsible for that.
u need to root ur device first so u can install recovery Twrp is recommended for our device.....coz to install recovery required superuser permission
Click to expand...
Click to collapse
There is no superuser permission required to install a custom recovery, it's actually the other way around: custom recovery is required to install superuser. What is required for a custom recovery though is an unlocked bootloader.
There is quite a bit of confusion over what rooting actually is, all it does is give you access to the root directory on the device, like having administrative privileges on Windows. It actually has nothing to do with the ability to flash custom ROMs, you need the unlocked bootloader and custom recovery to flash custom ROMs. A user can actually use a custom ROM perfectly well without ever needing to have root.
if your bootloader unlockEd.....most likely u have supercid....coz during process of unlocking bootloader u chance your device ID for example At&t is CWS__001 and u change it to 11111111
Click to expand...
Click to collapse
It isn't necessarily likely that a user has SuperCID if they have an unlocked bootloader, this is only true for at&t phones. All other Evitas are able to unlock the bootloader at htcdev without SuperCID. At&t phones need SuperCID first because the at&t CID is blocked at htcdev. Quite often these non-at&t phones (of which there are many) get SuperCID after unlocking the bootloader and attaining root.
And u said u bought Htc one X with no carrier ....u might have international htc one X......not htc one xl that's different device
Click to expand...
Click to collapse
Like I said in a previous post, this isn't true. At&t only makes up a percentage of all Evitas in the world. There are Evitas available in pretty much every country, and on various carriers (and unbranded) like Rogers, Telus, O2, T-Mobile, Telstra to name just a few. You can buy the One XL outright online from many websites, and these are usually the Hong Kong model, this is how I bought mine. So, to assume that a non-at&t One XL is the international One X isn't correct.
Now, while all of these Evitas are the same (apart from the availability of a 32gb model in Australia and Europe, the only difference being the storage capacity), there is a middle eastern variant of the Evita which is not like all the others. It has different hboot versions and very little is known about it, like whether all of our software is compatible or not. It's possible that it is but I've only seen three of four users with this device and I'm not comfortable advising anyone that it is. The few users that I've seen with this phone haven't reported back as to whether they've tried the software, and if so whether it worked or not.
Anyway, I just wanted to clear those things up for you, as I said it's very dangerous to give advice unless you're absolutely certain of what you're taking about. I hope this has helped somewhat.
Sent from my Evita
Well explained......:thumbup::thumbup: and sorry for what I posted.....and hope this would clear the confusion I made....... learned something new everyday.....:thumbup:
Swyped From BlueICESense_JBE
It's all part of the learning process.
Sent from my Evita
hey guys.. appreciate you for being patient..
here is my phone's HBoot information.. hope i can figure it out with your help..
what else do you need?
Ok, thanks for posting that. Please read this entire post before doing anything, it's extremely important. Your first step is to unlock your bootloader at htcdev (this isn't s-off as you previously posted though, s-off is something different). Your next step is to install TWRP recovery (I've seen people having problems with 2.6.3, so maybe stick to 2.6), but this is where it gets a little tricky, I'll tell you why.
You have the middle eastern variant of the HTC One XL, I'm able to identify that by the 2.10 hboot, and by the codename which is EVITA_UTL, all other One XL's codename is just EVITA.
The problem with this is that we know very little about your variant, I've only seen a couple, so we're not absolutely sure if the software is compatible. The only way you're going to know for sure whether the software (TWRP recovery, ROMs, radios, kernels) is compatible or not is to try to flash it. If it works, that's great and we'll all know that it's safe to use the software, and you can enjoy some custom ROMs. But, if it doesn't work, there's a high chance you could brick your phone.
So, as you can tell this is a very risky situation for you. It's entirely up to you whether you try flashing the software or not, but I thought you should be fully aware of the risk involved. Either way, please do let us know what you decide to do. If you decide to go ahead it'll provide excellent information for other guys like you with this variant of our device.
Sent from my Evita
hey there...
so these are my whole phone information
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main: 1.01.401.03
version-misc: PVT SHIP S-ON
serialno: HT2CTW305376
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 4024mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
i unlocked my bootloader few minutes ago.. but on thing.. where can i find the stock recovery image and stock RUU rom ? if anythings go wrong i would be able to go back to stock..
That's the problem, I don't know of an available RUU for your device, so I don't know if there's a stock recovery available. Maybe your carrier can provide you with that though.
I do have some good news for you though, I vaguely remembered another guy who has your device flashing one of our ROMs so I did some looking around. I found this thread. If you have a read you'll see he successfully flashed one of our ROMs and it worked fine. Please read this post in particular though, it states that you should not use hboot or radio from our device on yours, and also you will not have LTE support.
Sent from my Evita
---------- Post added at 11:33 PM ---------- Previous post was at 11:22 PM ----------
PS. You really should remove your IMEI number from that post above, never post your IMEI publicly.
Sent from my Evita
Ok, I think I've worked out how to backup your stock recovery. What you want to do is download TWRP 2.6 and put it in your fastboot folder. Now you connect your phone and issue this command:
Code:
fastboot boot recovery "recovery filename.img"
(The exact recovery filename, minus the talking marks)
This will boot your phone into TWRP recovery while it's still stored on your pc without having to overwrite the stock recovery on your phone. Basically it's running an emulated recovery, and the next time to reboot it'll be gone and your stock recovery will remain on your phone.
Now, while you're in TWRP you can either install superuser binaries or a custom pre-rooted ROM. This will give you root, once you've booted into the rooted ROM you can use an app called Flashify to backup your stock recovery.
Once you've confirmed that your recovery backup has worked (using a file explorer) you're free to permanently flash TWRP recovery onto your device.
Sent from my Evita
thanks man..
you mean i can flash for example viper Xl with emulated TWRP when stock recovery still installed on my phone.. wow...
and i didn't get the last part.. how can i confirmed with file explorer that my stock recovery which has been backed up works fine ?
and one thing..
while i'm restoring the original rom my recovery would be TWRP.. well ,,so if there's an original update exist my recovery must be stock to get the update.
it's possible to flash the stock recovery after restoring the original rom without damaging to it? you know what i mean?
jabi_james said:
thanks man..
you mean i can flash for example viper Xl with emulated TWRP when stock recovery still installed on my phone.. wow...
and i didn't get the last part.. how can i confirmed with file explorer that my stock recovery which has been backed up works fine ?
Click to expand...
Click to collapse
Yeah that's exactly what I mean, it's pretty cool actually. Before flashing Viper you should use the backup tool in TWRP to backup system, data, and boot and then you'll have a backup of your stock ROM.
What I meant in the last part was you should install something like ES File Explorer from the Play Store. That way after you've backed up your stock recovery you can confirm that it worked by navigating to /flashify-backup/recovery using the file explorer to make sure the recovery image is there.
I'm about to attach a couple of screenshots for your reference, I'll have them uploaded in a couple of minutes.
Sent from my Evita
problem..
my recovery name is (openrecovery-twrp-2.6.3.0-evita)
so i write in cmd (fastboot boot recovery openrecovery-twrp-2.6.3.0-evita.img)
but it says (can not load recovery)
oh.. i think i destroy my phone .. a message appears at the top of the bootloader and says : (Tampered)
i write this command in cmd [fastboot boot "recovery filename.img"]
what did i do...
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).
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.