Greetings all. Please help.
S4, T-mobile (TMOUS)
What i have done:
+ debranding PJ4011000->PJ4010000
+ SuperCID 11111111
+ S-OFF by facepalm, moonshine, rumrunner
I try every kind of s-off and as a result: Bootlooping phone (black desktop, and in a minute - system restart)
Checked on RUU 2.31,2.35, 3.14, ViperOneS, CM10.
If i get S-ON, RUU firmware works fine
Please help, how can i get everything works?
NewbieFound said:
Greetings all. Please help.
S4, T-mobile (TMOUS)
What i have done:
+ debranding PJ4011000->PJ4010000
+ SuperCID 11111111
+ S-OFF by facepalm, moonshine, rumrunner
I try every kind of s-off and as a result: Bootlooping phone (black desktop, and in a minute - system restart)
Checked on RUU 2.31,2.35, 3.14, ViperOneS, CM10.
Please help, how can i get everything works?
Click to expand...
Click to collapse
Are you s-off or not?
Sent from my Nexus 4 using Tapatalk
nicknc said:
Are you s-off or not?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Forget to mention one thing, while system boot, there is no sim card datection (sim insert) and no sim card logo, if sim is out)
At this moment i have:
Unlocked
S-OFF
CID-11111111
Hboot 2.15
Radio 1.11
OpenDSP-v.31-1.0
eMMC-boot
NewbieFound said:
Forget to mention one thing, while system boot, there is no sim card datection (sim insert) and no sim card logo, if sim is out)
At this moment i have:
Unlocked
S-OFF
CID-11111111
Hboot 2.15
Radio 1.11
OpenDSP-v.31-1.0
eMMC-boot
Click to expand...
Click to collapse
Lock your boot loader and RUU to RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2
I know it's a TMOUS ruu, but it is reliable and you won't be keeping it.
After that, you should still be s-off, so unlock bootloader again, fastboot TWRP 7.0.0.8, root and then press forward with whatever ROM you want to use.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Lock your boot loader and RUU to RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.5 0.05.31_10.30.50.08L_release_309489_signed_ICS_2
I know it's a TMOUS ruu, but it is reliable and you won't be keeping it.
After that, you should still be s-off, so unlock bootloader again, fastboot TWRP 7.0.0.8, root and then press forward with whatever ROM you want to use.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for help.
I've installed RUU_Ville_U_JB_45_S_TMOUS_3.14 - still black desktop and reboot after 30 seconds Should RUU work fine on S-OFF?
NewbieFound said:
Thank you for help.
I've installed RUU_Ville_U_JB_45_S_TMOUS_3.14 - still black desktop and reboot after 30 seconds Should RUU work fine on S-OFF?
Click to expand...
Click to collapse
Yes, RUU works fine on s-off
What do you mean by "black desktop"?
Sent from my Nexus 4 using Tapatalk
nicknc said:
Yes, RUU works fine on s-off
What do you mean by "black desktop"?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Photo of my phone after RUU:
http://imgur.com/PWtgmA9
Bootloader:
relocked
s-off
cid-11111111
hboot 2.15
radio 1.13
Same result i get after installing ViperOneS or CM10, or any other RUU
NewbieFound said:
Photo of my phone after RUU:
http://imgur.com/PWtgmA9
Bootloader:
relocked
s-off
cid-11111111
hboot 2.15
radio 1.13
Same result i get after installing ViperOneS or CM10, or any other RUU
Click to expand...
Click to collapse
But recovery works, right?
Sent from my Nexus 4 using Tapatalk
nicknc said:
But recovery works, right?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
What do you mean by "recovery works"?
I can install any RUU (tmous/europe) or custom (viperones) - no errors. But nothing phone doesn't work after install.
NewbieFound said:
What do you mean by "recovery works"?
I can install any RUU (tmous/europe) or custom (viperones) - no errors. But nothing phone doesn't work after install.
Click to expand...
Click to collapse
So with s-on, your phone works normally, right?
How are you achieving s-off?
NewbieFound said:
What do you mean by "recovery works"?
I can install any RUU (tmous/europe) or custom (viperones) - no errors. But nothing phone doesn't work after install.
Click to expand...
Click to collapse
Sent from my Nexus 4 using Tapatalk
nicknc said:
So with s-on, your phone works normally, right?
How are you achieving s-off?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
1. With S_ON RUU works fine, i haven't checked it on viperones or cm modes
2. In past week i try:
- moonshine
- rumrunner
- facepalm
each of them get me S-OFF, and bootloop
NewbieFound said:
1. With S_ON RUU works fine, i haven't checked it on viperones or cm modes
2. In past week i try:
- moonshine
- rumrunner
- facepalm
each of them get me S-OFF, and bootloop
Click to expand...
Click to collapse
Some phones can't seem to s-off. Maybe you're in that group.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Some phones can't seem to s-off. Maybe you're in that group.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Thank you for help!
Okay, if my phone can't be s-off, can i install viperones, then retrun S-ON, and if i don't like viper install RUU again? (in other words, can i install RUU on custom roms while S-ON?)
NewbieFound said:
Thank you for help!
Okay, if my phone can't be s-off, can i install viperones, then retrun S-ON, and if i don't like viper install RUU again? (in other words, can i install RUU on custom roms while S-ON?)
Click to expand...
Click to collapse
You're welcome, feel free to hit the thanks button.
As for flashing ruu's while s-on, the short answer is yes. However, you don't need to flash a RUU every time you want to change Roms. You can just wipe between and flash away.
Lastly, be sure to update your radio before going back to s-on. It makes it much easier.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Lastly, be sure to update your radio before going back to s-on. It makes it much easier.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Well I installed ViperOneS and go S-ON, and only then read FAQ and remembered about radio 1.20
Right now i'm s-ON on radio 1.13
Where can i found some info about 1.35 and 1.20 radio's?
NewbieFound said:
Well I installed ViperOneS and go S-ON, and only then read FAQ and remembered about radio 1.20
Right now i'm s-ON on radio 1.13
Where can i found some info about 1.35 and 1.20 radio's?
Click to expand...
Click to collapse
Start in the radio thread.
Sent from my Nexus 4 using Tapatalk
nicknc said:
Start in the radio thread.
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Could you be so kind and share a link. I found only guides/how to, but couldn''t find thread where there is comparison between 1.20 and 1.35 radio
http://forum.xda-developers.com/showthread.php?t=2709164 is the link for the 1.35 radio. This supposedly only works for non-us markets
For 1.20, which works for all, search the android development forum. I believe it is in there.
Sent from my Nexus 4 using Tapatalk
Related
I am happy to announce that I got the S=OFF on OTA 2.15. I use moonshine http://www.moonshine.io method in Linux. I try in windows, but was unable to to remove the HTC Sync. It work in Linux. I use Linux Mint in KDE 14.
Can anyone else confirm this works? I have to wait until tomorrow to test.
Sent from my Nexus 7 using xda app-developers app
Worked
darius359 said:
Can anyone else confirm this works? I have to wait until tomorrow to test.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I can confirm. I just finished it. I had a Soft Brick with error mounting SD Card. After returning to S-On I was able to return to stock with a RUU. After that was complete up and running, I used Moonshine and now S-Off again.
I just need to work on the signal issue created with the updated TMOUS Firmware.
mjsheldon4 said:
I can confirm. I just finished it. I had a Soft Brick with error mounting SD Card. After returning to S-On I was able to return to stock with a RUU. After that was complete up and running, I used Moonshine and now S-Off again.
I just need to work on the signal issue created with the updated TMOUS Firmware.
Click to expand...
Click to collapse
Hey I'm in the same boat as you. Do you still have the signal issue? How are you fixing it?
I have phone from TMO_DE with OTA 2.15 and just passed the moonshine without any problems (previously, I couldn't make S-off becouse I can't do SuperCID)
One S Multi-Tool is a timesaver and so much easier. After I was able to S-Off again with moonshine I was still having issues with custom roms and the signal on stock. With the stock the signal disconnected constantly and with custom it had errors and would not load. I returned to S-On but was able to keep my SuperCID so I could flash another RUU. I ran a lower RUU which downgraded my HBoot. Then I was able to flash a custom Rom. I am keeping the S-on for now because it kept breaking the connection to the sdcard. The signal was still choppy but with the lower HBoot I was able to flash a different radio. I had the newest but when I flashed a lower version, works perfect.
Sent from my HTC One S using xda app-developers app
mjsheldon4 said:
One S Multi-Tool is a timesaver and so much easier. After I was able to S-Off again with moonshine I was still having issues with custom roms and the signal on stock. With the stock the signal disconnected constantly and with custom it had errors and would not load. I returned to S-On but was able to keep my SuperCID so I could flash another RUU. I ran a lower RUU which downgraded my HBoot. Then I was able to flash a custom Rom. I am keeping the S-on for now because it kept breaking the connection to the sdcard. The signal was still choppy but with the lower HBoot I was able to flash a different radio. I had the newest but when I flashed a lower version, works perfect.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
can you point out which RUU and which radio you flashed? That would be a great help. Thank you!
joemanbui said:
can you point out which RUU and which radio you flashed? That would be a great help. Thank you!
Click to expand...
Click to collapse
This is the RUU. Will put you down to ICS and hboot 1.08
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
This is the radio. V6 is for S-Off Devices or those with HBoot lovver then 1.13. After your HBoot is set I flash the 0.16 radio, which is the same that is included with the RUU but it is an Aroma installer and gives the ability to adjust for T-Mobile and fix wifi partition. Works great.
V4 is for Hboots that are S-On and higher then 1.13. Resets after a ROM flash.
[S4][01.05][V6][V4]Radio Collection for Sense ROM's and AOSP ROM's + Build.prop fix
None of this is my work, just what I have done some research on and found they worked for me.
mjsheldon4 said:
This is the RUU. Will put you down to ICS and hboot 1.08
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
This is the radio. V6 is for S-Off Devices or those with HBoot lovver then 1.13. After your HBoot is set I flash the 0.16 radio, which is the same that is included with the RUU but it is an Aroma installer and gives the ability to adjust for T-Mobile and fix wifi partition. Works great.
V4 is for Hboots that are S-On and higher then 1.13. Resets after a ROM flash.
[S4][01.05][V6][V4]Radio Collection for Sense ROM's and AOSP ROM's + Build.prop fix
None of this is my work, just what I have done some research on and found they worked for me.
Click to expand...
Click to collapse
Thanks for the reply! I've been trying for so long to fix this problem and it's great to finally see someone who has had positive results. I'll give it a try tonight and hopefully I'll have the same result.
mjsheldon4 said:
This is the RUU. Will put you down to ICS and hboot 1.08
RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S.16_2_10.22.31501S.10L_release_263233_signed.exe
This is the radio. V6 is for S-Off Devices or those with HBoot lovver then 1.13. After your HBoot is set I flash the 0.16 radio, which is the same that is included with the RUU but it is an Aroma installer and gives the ability to adjust for T-Mobile and fix wifi partition. Works great.
V4 is for Hboots that are S-On and higher then 1.13. Resets after a ROM flash.
[S4][01.05][V6][V4]Radio Collection for Sense ROM's and AOSP ROM's + Build.prop fix
None of this is my work, just what I have done some research on and found they worked for me.
Click to expand...
Click to collapse
Thank you so much!! This worked perfectly for me. These fixes should be posted in a thread somewhere because a lot of people seem to be having the same problem.
Sent from my HTC VLE_U using xda app-developers app
cuiltheory said:
I am happy to announce that I got the S=OFF on OTA 2.15. I use moonshine http://www.moonshine.io method in Linux. I try in windows, but was unable to to remove the HTC Sync. It work in Linux. I use Linux Mint in KDE 14.
Click to expand...
Click to collapse
Is this the same as superCID S-OFF?
I facepalmed s-off a very long time ago, I wouldn't want a custom hboot can be a disaster sometimes lol
Doesn't soff let u do everything anyway? Why's the eng hboot needed
evrycard said:
Is this the same as superCID S-OFF?
Click to expand...
Click to collapse
No and yes. It depend on your hboot version. For OTA with 2.15, there was no way to get the s=off as we could not do the supercid. With moonshine script, you do not need the supercid. I still have tmous cid. Different way to get the s=off and works.
cuiltheory said:
With moonshine script, you do not need the supercid
Click to expand...
Click to collapse
haha I thought I had achieved something finally able to write to mmcblk0p4 to supercid after moonshining. guess not so much.
k2thec said:
haha I thought I had achieved something finally able to write to mmcblk0p4 to supercid after moonshining. guess not so much.
Click to expand...
Click to collapse
LOL. Do not beat your self. You were still ahead of most of us.
k2thec said:
haha I thought I had achieved something finally able to write to mmcblk0p4 to supercid after moonshining. guess not so much.
Click to expand...
Click to collapse
You should be able to. With S-OFF, just use fastboot oem writecid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
Moonshine is awesome. I used it to s-off over the most recent OTA, and applied SuperCID using the hex editor "1111111" method. Going to switch over to Verizon when my contract is up, and wont have to give up my ville_u :good: :laugh:
ryanshew said:
You should be able to. With S-OFF, just use fastboot oem writecid 11111111
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me
Click to expand...
Click to collapse
o yeah I totally did that, just seemingly pointless if I am s-off already, right?
So has anyone gained S-Off with Hboot 2.15 using moonshine on a windows machine?
I did install latest JB OTA. but do have Super CID.
Cheers
nozzla said:
So has anyone gained S-Off with Hboot 2.15 using moonshine on a windows machine?
I did install latest JB OTA. but do have Super CID.
Cheers
Click to expand...
Click to collapse
Yes. I did 2 phones
Sent from my HTC VLE_U using xda premium
I am looking for a Stock T-Mobile Jelly Bean image that won't brick my phone. I tried searching for one, but I couldn't find anything or I found RUUs for outdated versions of HBoot. I am trying to revert back to stock, but I am sorta scared to do so with an outdated RUU. I have HBoot version 2.15 and Radio version 1.13.50.05.31. Thanks in advance.
Would this be the RUU I have to download? http://bugsylawson.com/files/file/1...531-10305008l-release-309489-signed-ics-2exe/
I would just prefer a nandroid backup of the stock image that I can just flash with CWM.
I downloaded the RUU, I just need to know if that is the correct one for my phone before I use it. I really don't want a bricked phone. I checked the MD5sum already and it matches, that is the only thing holding me back.
Sent from my One S using xda premium
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
OccupyDemonoid said:
Okay, thank you for the reassurance. I just am pretty paranoid about bricking my phone. I have been looking up how to use RUUs for the last day or so, I just couldn't find anything on how to select the right one. Thanks again.
I just checked out your link and I am downloading now. I do not have SuperCID and I will be looking my boot loader.
Sent from my One S using xda premium
Click to expand...
Click to collapse
If you are on TMOB US then it's for you. Furthermore, you can match thr CID of your phone to that in the RUU.exe --> Firmware.zip --> android-info.txt.
You'll have to extract firmware.zip from temporary files when you run RUU without connecting phone.
Sent from my Nexus 7 using Tapatalk HD
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
I ended up using that RUU that was linked earlier in this thread and everything went fine. I just don't have the stock recovery. I guess that isn't that much of a problem though.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
The RUU installs the Stock Recovery automatically. You don't have to do anything extra.
You can find stock recovery (if you want to keep it for any purpose) inside the RUU (extraction would require you to run the RUU and then extract the recovery from Temporary Files)
OR
you can find it in the forums.
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
OccupyDemonoid said:
Hmmm, that's strange. Oh well I guess. When I tried to go into the recovery it just showed a red exclamation mark with a phone under it. I don't really need a recovery right now. Thanks for letting me know where I can find it.
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
I believe that is the stock recovery. The red exclamation mark is telling you that you don't have access to it. Perfectly normal.
tivofool said:
I have ran that RUU with the same hboot and radio as you. Why do you think it would brick your phone? you haven't supercid and have locked your bootloader right?
(didn't download from that site though)
http://forum.xda-developers.com/showthread.php?t=2094414
Click to expand...
Click to collapse
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
DroidLuvver said:
Can I also run this same RUU as quoted in this thread ?
I have the same radio but different hboot ...
SuperCID = HTC__001 <---- I got this right now, I will have to put in TMO CID before I run RUU, is that true?
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-1-13.50.05.31
I would like to go back to Stock becuase after rooting and putting custom ROM (AOKP, I lost 4g, it was working before)
Click to expand...
Click to collapse
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
tivofool said:
Yes, I think it will give you an error with that cid. Someone could correct me, but with s-off you can run whatever ruu you want.
Click to expand...
Click to collapse
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
DroidLuvver said:
I am planning on changing the CID to match what's in the firmware and then running this RUU but... what about my hboot.. it's different than what you guys have. Its 1.13
Click to expand...
Click to collapse
It will install the newer hboot to 2.15
tivofool said:
It will install the newer hboot to 2.15
Click to expand...
Click to collapse
So I should be able to run the RUU with lower boot like mine and it will upgrade the boot to 2.15 -
Is it true that with 2.15 hboot, modifying the CID is not allowed ?
Any reason why I should stay with 1.13 HBOOT and not go to 2.15 Hboot? Meaning any disadvantages of upgrading to HBOOT 2.15 ?
Well, say you updated your phone via ota & your cid is European or something. And all of the ruus for that CID are lower hboots. If u are s-on and and needed to ruu you wouldn't be able to.
But there is a guide to run a ota.zip for those people, so it isn't hopeless.
So not too many disadvantages.
In fact I just installed the newest Rom and firmware today. So my hboot is 2.16.
And the gossip is that update will be officially put out by HTC in a few weeks.
Sent from my HTC One S using Tapatalk 2
Remember this.
if you want to go stock again in future (warranty purpose)
some providers have only provided an ota (only ruu with lower hboots) when upgrading to jb. So downgrading gets hard
It's not that easy to flash an ota as is a ruu.
If your s-off downgrading is no issue.
Verstuurd van mijn HTC One S met Tapatalk
hi everyone. my sensation is getting me angry for a few week. i can't flash roms or others using fastboot commands cause my device is s-off, but i still have the bootloaader locked. from the command prompt i always obtain the same message "writing boot...failed(remote: not allowed)". first at all, i unlocked my device using HTCdev, after i flashed my first rom i found the bootloader locked. second, i tried to turn my device s-off, but controlbaer crashed, so i didn't complete it, but hovewere i'm s-off. how can it be ??? at now, can i flash roms or other .zip just by recovery (4ext) ?? or how can i unlock again the bootloader ??? hope somebody give me an answer. :good:
If you are S-Off and even that the boot loader is locked there should be no problem to install ROM - via 4ext
Sent from my HTC Sensation using xda premium
gab_ITA said:
hi everyone. my sensation is getting me angry for a few week. i can't flash roms or others using fastboot commands cause my device is s-off, but i still have the bootloaader locked. from the command prompt i always obtain the same message "writing boot...failed(remote: not allowed)". first at all, i unlocked my device using HTCdev, after i flashed my first rom i found the bootloader locked. second, i tried to turn my device s-off, but controlbaer crashed, so i didn't complete it, but hovewere i'm s-off. how can it be ??? at now, can i flash roms or other .zip just by recovery (4ext) ?? or how can i unlock again the bootloader ??? hope somebody give me an answer. :good:
Click to expand...
Click to collapse
Hi,
Look HERE
Second post.
Try flashing this:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
This should give you an unlocked bootloader.
malybru said:
Hi,
Look HERE
Second post.
Try flashing this:
HBoot 1.27.1100 Patch (Go from Hboot 1.29.0000 to 1.27.1100)
This should give you an unlocked bootloader.
Click to expand...
Click to collapse
I already have hboot 1.27. Could it work hovewere ?
Sent from my HTC Sensation using Tapatalk 4 Beta
gab_ITA said:
I already have hboot 1.27. Could it work hovewere ?
Sent from my HTC Sensation using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi,
I am not sure what to suggest.
People who flash this are normally locked and hboot 1.29
It works for them,so it should work for you
I do not think it would do any harm.
Or perhaps you could flash the 1.27 > 1.29 version first.
Then, go 1.29 > 1.27
How did your bootloader become locked?
malybru said:
Hi,
I am not sure what to suggest.
People who flash this are normally locked and hboot 1.29
It works for them,so it should work for you
I do not think it would do any harm.
Or perhaps you could flash the 1.27 > 1.29 version first.
Then, go 1.29 > 1.27
How did your bootloader become locked?
Click to expand...
Click to collapse
gab_ITA said:
I already have hboot 1.27. Could it work hovewere ?
Sent from my HTC Sensation using Tapatalk 4 Beta
Click to expand...
Click to collapse
When you say you have 1.27 do do you mean a patched one? Besides, @malybru posted a patched one.
You could try unlocking your bootloader (i am not sure, but this may cause brick).
JAM THAT THANKS BUTTON.
Happy to help.
I have 1.29 after flashing new radio and s-off and there is no problem using 4ext for flashing any zip so far
Sent from my HTC Sensation using xda premium
malybru said:
Or perhaps you could flash the 1.27 > 1.29 version first.
Then, go 1.29 > 1.27
How did your bootloader become locked?
Click to expand...
Click to collapse
Wells, it's always a way xD i unlocjed th bootloader using HTCdev, but when i flashed my first ROM(slimbean) it became again locked. I really can't explain how di it appen .... so, i'll try the patched one, let's see if it work....
Sent from my HTC Sensation using Tapatalk 4 Beta
gab_ITA said:
Wells, it's always a way xD i unlocjed th bootloader using HTCdev, but when i flashed my first ROM(slimbean) it became again locked. I really can't explain how di it appen .... so, i'll try the patched one, let's see if it work....
Sent from my HTC Sensation using Tapatalk 4 Beta
Click to expand...
Click to collapse
Flashing a rom via recovery shouldn't change bootloader status. Either you flashed a new firmware, or did an ruu.
Besides, a patched hboot should enable fastboot commands.
Far_SighT said:
Flashing a rom via recovery shouldn't change bootloader status. Either you flashed a new firmware, or did an ruu.
Besides, a patched hboot should enable fastboot commands.
Click to expand...
Click to collapse
i've just dowloaded the patched hboot. how do i install it ?
gab_ITA said:
i've just dowloaded the patched hboot. how do i install it ?
Click to expand...
Click to collapse
Hi,
It is all explained on the thread.
Hi Guys
I am trying to get SuperCID, S-Off, then --> 3.18RUU and TWRP2.6.0.0 --> CM10.1 or 10.2
I have a phone that i Unlocked bootloader on HTCDev a long time ago. Rooted, TWRP2.6.0.0 running CM10.1 but because newer kernels require newer HBOOT so i am trying to get it.
I have TELST001 as CID
the phone in bootloader shows
****TAMPERED*****
****UNLOCKED****
EVITA PVT SHIP S-On RL
HBOOT-1.09.0000
Radio 0.20os.32.09.15
OpenDSP-V251.0.32.0405
eMMC-boot
Apr 2 2012,, 21:08:24
i have tried fastboot oem writecid 11111111 comes up with failed
I have also tried the oneclick SuperSID http://forum.xda-developers.com/showthread.php?t=1952038 - didn't work
any ideas whats the best step to take to get to the elusive cm10.2?
Thank you for your help!
You can try the hex edit method, which can be found here:
http://forum.xda-developers.com/showthread.php?t=2212737
Sent from my Evita
timmaaa said:
You can try the hex edit method, which can be found here:
http://forum.xda-developers.com/showthread.php?t=2212737
Sent from my Evita
Click to expand...
Click to collapse
This should work too:
Code:
adb shell
su
echo -ne "11111111" | dd of=/dev/block/mmcblk0p5 bs=1 seek=20
Once you get Super CID, you can get S-Off using the method found here: http://forum.xda-developers.com/showthread.php?t=2155071
which worked wonderfully for me just this morning.
Then, once you've verified that you have S-Off, you can update your HBoot using this method: http://forum.xda-developers.com/showthread.php?t=2156686
I used the third zip listed, worked just fine.
If you do not have S-Off and you attempt this, the chance of bricking your phone is incredibly high.
When you get to green bar, as mentioned in the instructions, let it sit for a few seconds, and then move on to the next step without waiting for it to go away (because it won't...).
Once you're done with that, I would clear the cache using <fastboot erase cache>, flash your recovery software using <fastboot flash recovery "recovery software name here"> and then boot to that to flash your rom.
As I said, I just did this all this morning, and I'm happily running a rom that requires the updated HBoot. So best of luck!:good:
That's not entirely correct. It's not just the hboot you're meant to update. You really should run an RUU.
Sent from my Evita
Thank you all!
I have successfully superCID and S-Off then RUUed to the latest 3.18
now it says
*Unlocked*
EVITA PVT SHIP S-OFF RL
CID 11111111
HBoot 2.14.0000
Radio 0.24p.32.09.06
open DSP v34.1.0.45.1219
eMMC-Boot
Nov 26 2012 18:37:14:-1
but when i go into recovery it gives me a big exclamation mark
so presumably the TWRP is gone
So i used goomanager to install. that didn't work.
there's no root (after RUU) presumably normal
what is the best way to get TWRP on, then flash latest CM10.1
Many thanks for your help!
Download twrp and flash in fastboot.
Fastboot flash recovery recoveryfilename.img
Sent from my HTC One X using xda app-developers app
exad said:
Download twrp and flash in fastboot.
Fastboot flash recovery recoveryfilename.img
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Legendary.
Worked like a charm.
on latest CM10.1 nightly now.
Appreciate all of the above help!
Hello everyone..I would like to see if someone could help me..I have a one x with supercid, s-off, and bootloader unlocked..I want to flash a custom Rom like viper but wouldn't know where to start..would I ruu 3.18 or relock bootloader? Any help will be appreciated.
Sent from my HTC One X
xViiZe said:
Hello everyone..I would like to see if someone could help me..I have a one x with supercid, s-off, and bootloader unlocked..I want to flash a custom Rom like viper but wouldn't know where to start..would I ruu 3.18 or relock bootloader? Any help will be appreciated.
Sent from my HTC One X
Click to expand...
Click to collapse
All you need to do is flash the ROM from recovery....
Sent from my Evita
Ok so the hboot version wouldn't matter? I have ics 2.20 hboot 2.14. And viper xl is jb.
Sent from my HTC One X
No it doesn't matter.
Sent from my Evita
Alright thank you ..I appreciate it
Sent from my HTC One X
---------- Post added at 11:26 PM ---------- Previous post was at 11:08 PM ----------
ohh im sorry i was about to install the rom but then i checked my hboot version and it is 1.14 ..i read in a couple of threads that with 1.14 u need to install the boot img with the rom is this true? or would i need a hboot upgrade?
No, you're s-off so you don't need to do that.
Sent from my Evita
Ok let me try and I'll post results when I'm done
Sent from my HTC One X
So I flashed it and it did boot..thank you. So from now on if i would like to flash a different Rom, I would just got to twrp again right?
Sent from my HTC One X using xda app-developers app
xViiZe said:
So I flashed it and it did boot..thank you. So from now on if i would like to flash a different Rom, I would just got to twrp again right?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Correct
Sent from my HTC One XL using xda premium
Yeah just boot into TWRP, do a full wipe (cache/dalvik cache/system/factory reset), and flash your ROM (and gapps if it's an aosp ROM).
Sent from my Evita
Ok thank you guys..
Sent from my HTC One X using xda app-developers app
Heisenberg said:
Yeah just boot into TWRP, do a full wipe (cache/dalvik cache/system/factory reset), and flash your ROM (and gapps if it's an aosp ROM).
Click to expand...
Click to collapse
I accidentally flashed a ruu you while my phone was super CID. Now it won't boot. Is there a way that I could force my phone into fastboot? That is without having to do a j tag on it
first thing, sorry for my bad english
I have my att hox from an order version from 1.17 or something like that. i tried to upgrade my hboot by ruu but i got an error 158 image error right at the process of updating signature (relocked my bootloader). Then i tried to s-off by using the facepalm method but no luck.
I'm trying to install android revolution hd 31.0 but i got stuck at 30% or the older 22.0 at 30% as well and viperxl 3.8.0 final so im using 3.28 viperxl and cyn 10.1
I downloaded the RUU 3.18(cingular) directly from htc webside
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-v31.1.0.45.0815
eMMC-boot
cid is 11111111
any help will be greatly appreciated!!!
Flash twrp 2.6 (make sure for evita)
Wipe everything except SD card
Flash any sense rom for evita
Soff
Ruu
Sent from my One X using xda app-developers app
thanks for fast reply!!!
Im gonna try it now
You mentioned trying to install Android Revolution, don't do that, it's not for our phone. You need to stay in this device forum that you're posting in or you'll flash something that'll brick your phone.
Sent from my Evita
oh i didnt know that
Somehow i cant use adb on sense rom, only with cyn
i tried a few times already but still s-on no matter what.
What happens?
Sent from my One X using xda app-developers app
I installed the twrp 2.6.0 then tried to install cleanrom and viperxl to s-off but still s-on
I followed the steps n got the same 92 error but still s-on after bott my phone into boot loader
OK.. Paste your cmd so I can see
Sent from my One X using xda app-developers app
Im on viperxl now and i stuck at the adb device offline thing again
tried adb kill/start-server but no luck
phongduong93 said:
Im on viperxl now and i stuck at the adb device offline thing again
tried adb kill/start-server but no luck
Click to expand...
Click to collapse
press and hold power until the phone shuts off then turn it back on and try again.
exad said:
press and hold power until the phone shuts off then turn it back on and try again.
Click to expand...
Click to collapse
still the same, i also tried that with adb kill/start-server
it was working fine with cleanrom after adb kill/start-server
Is HTC sync running? If so make sure it isn't. I remember I had this issue too once.. I can't remember how I fixed it now...
I think I just changed usb ports rebooted the pic and phone etc.
Sent from my One X using xda app-developers app
thanks for the helps i really appreciated but i no longer own the device.
Wrong posts -
quentin2260 said:
Hi !
Your wifi fix (Tesco ION 3.2.0) in the first page doesn't work with my phone because it's S-ON.
How can I flash this fix with my S-ON (its difficult to flash kernel with S-ON) ?
Click to expand...
Click to collapse
Why don't you just get s-off? And what fix are you talking about? Are you posting in the right thread?
Sent from my Evita.