Ok guys, I've flashed a lots of device in the past, now I'm selling my Samsung S4 and buy this HTC ONE S from a friend. I like the phone a lot, I did s off with moonshine (gave error but in the end its finish).
I flash CM11, everything good, but, the camera is so slow to take picture. My friend told me that before that, it was ok (in stock roms). So, I decided to try a sense rom, I choose liberty rom, The rom flashed ok, but, Never boots, stucks on HTClogo, and restart.
I was with philz_touch_6.19.3-ville, so I decide to flash openrecovery-twrp-2.7.0.0-ville. But still the same problem.
Then I try those recovery: openrecovery-twrp-2.6.3.0-ville and openrecovery-twrp-2.6.1.0-ville. It doesnt even boot, only restart.
If I flash CM11 again, it will boot, but the camera is slow and i want a sense rom. In Hboot show this
Moonshine S-OFF
VLE PVT SHIP S-OFF RL
CID-T-MOB010
HBOOT-2.15.4444
RADIO-1.35a.32.45.27
OpenDSP-v31.1.0.45.08.15
eMMC-boot
Dec 14 2012, 17:10:57:-1
I was thinking if upgrade to Hboot 2.16 was good, but not sure. Any advice?
PD: The g-Sensor and camera flash light dont work but is hardware, just said it if that helps in something
PD2: Ok, the slow camera was because I had the flash on, and is damage, so thats make the camera slow, I deactivate and now takes picture fast. But still, want a sense rom
PD3: I try this recovery twrp-2.7.0.8-ville.img but nothing I flash the rom, but again bootloops. I get that recovery from here http://mdmower.cmphys.com/twrp-ville/
What about running last ruu ? You're on hboot 2.15 so no need to downgrade.
Before running flash stock recovery with fastboot
benJX said:
What about running last ruu ? You're on hboot 2.15 so no need to downgrade.
Before running flash stock recovery with fastboot
Click to expand...
Click to collapse
Yes, but what about 2.16? I have this RUU RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
that is what I need? What about s-off? Or the unlocked bootloader? I will lose it?
Hboot 2.16 is needed only if you want to run MaximusHD (this rom is NOT compatible with any other hboots).
Viper rom and Liberty are compatible with both 2.15 & 2.16.
I would add that CM11 is not officialy made for 2.15 hboot. If you want CM11 on 2.16 there are unofficial build made for this. Just in case you would came back to CM11 if you uprgrade to 2.16. Most of the AOSP based roms released here are made for 2.15.
So to resume, if you want a Sense 4+ rom, just run the ruu you told me and it should be fine (flash stock recovery before). If you want to switch to AOSP, no problem. If you want some Sense 5 or Sense 5+ try Viper or retry Liberty.
But if you want MaximusHD you will have to upgrade (all is explained in the rom thread). This is, in my opinion, the best rom so far released for our phone. Stock feeling but tweakable with Sense 5 Toolbox (xposed module). I advise you to try it at least and if you don't like it, just downgrade you hboot, no problem for doing this.
About recoveries, for 2.16 you need a modded 2.6.1.0 TWRP recovery (the only one for this hboot I think, everything is explained in MaximusHD OP). With this hboot and recovery you cannot mount your sdcard from recovery.
In 2.15 I used to use 2.3.3.0 TWRP, no issues in sdcard mounting. Whan I was on 2.15 I had some issues with newer versions. Since I'm on 2.16 I didn't try 2.6.X.X and 2.7.X.X with this hboot.
Good luck to make your choice, it's hard lol
benJX said:
Hboot 2.16 is needed only if you want to run MaximusHD (this rom is NOT compatible with any other hboots).
Viper rom and Liberty are compatible with both 2.15 & 2.16.
I would add that CM11 is not officialy made for 2.15 hboot. If you want CM11 on 2.16 there are unofficial build made for this. Just in case you would came back to CM11 if you uprgrade to 2.16. Most of the AOSP based roms released here are made for 2.15.
So to resume, if you want a Sense 4+ rom, just run the ruu you told me and it should be fine (flash stock recovery before). If you want to switch to AOSP, no problem. If you want some Sense 5 or Sense 5+ try Viper or retry Liberty.
But if you want MaximusHD you will have to upgrade (all is explained in the rom thread). This is, in my opinion, the best rom so far released for our phone. Stock feeling but tweakable with Sense 5 Toolbox (xposed module). I advise you to try it at least and if you don't like it, just downgrade you hboot, no problem for doing this.
About recoveries, for 2.16 you need a modded TWRP recovery (the only one for this hboot I think, find it in MaximusHD thread). With this hboot and recovery you cannot mount your sdcard from recovery.
In 2.15 I used to use 2.6.3.0, I had problems with newer versions.
Good luck to make your choice, it's hard lol
Click to expand...
Click to collapse
Ok, I will try that rom, But I will not my S-off? And is easy to change between hboot? and yes, a lot recommended 2.6.3.0 as far I was reading, but that recovery never boots for me, and when I install it, it corrupts my sd and need to recover with 2.7.0.0.
I will run the RUU, I always have a little fear when messing with hboot hehe (Trauma from a bricked G1 a long time ago )
Ahh I will ad taht actually I try viper too and no boot. Only AOSP roms boot
lorddavid said:
Ok, I will try that rom, But I will not my S-off? And is easy to change between hboot? and yes, a lot recommended 2.6.3.0 as far I was reading, but that recovery never boots for me, and when I install it, it corrupts my sd and need to recover with 2.7.0.0.
I will run the RUU, I always have a little fear when messing with hboot hehe (Trauma from a bricked G1 a long time ago )
Click to expand...
Click to collapse
Running RUU wil not mess up your S-OFF. It will only return your phone back to stock firmware/radio/rom.
Switching between hboots (2.15 <--> 2.16) is always pretty the same.
What is annoying is that uprading or downgrading your hboot will format your sdcard, aswell as running any ruu.
To uprade to 2.16, follow the MaximusHD OP.
To downgrade to 2.15, follow this link until step 2.2 then flash the stock recovery and flash the firmware.zip the same way you flash 2.16. Then run ruu.
Some people advised me to use this tool to switch between hboots, but I preffer do it by myself. Have a look maybe you'll find it helpful.
I agree there is always a part of risk by doing this but you will not regret it when you'll find the perfect rom you want
Anyway your problem with Sense roms is kindda strange
Did you try to manually flash boot.img after flashing rom ?
benJX said:
Running RUU wil not mess up your S-OFF. It will only return your phone back to stock firmware/radio/rom.
Switching between hboots (2.15 <--> 2.16) is always pretty the same.
What is annoying is that uprading or downgrading your hboot will format your sdcard, aswell as running any ruu.
To uprade to 2.16, follow the MaximusHD OP.
To downgrade to 2.15, follow this link until step 2.2 then flash the stock recovery and flash the firmware.zip the same way you flash 2.16. Then run ruu.
Some people advised me to use this tool to switch between, but I use do it by myself. Have a look maybe you'll find it helpful.
I agree there is always a part of risk by doing this but you will not regret it when you'll find the perfect rom you want
Anyway your problem with Sense roms is kindda strange
Click to expand...
Click to collapse
Yes, Is strange, I know that the phone has hardware damage, but, only g sensor and flashlight, and everything works with AOSP, right know I'm charging the phone a little more, I've downloaded already viper rom, liberty, maximumHD, cm11 and Beanstalk.
Beanstalk has a lot of force close to me, cm11 just in the start, with a cm account, and when switching from the camera to videocamera.
Maybe there are error with the partition? I will try what you said and report back (will take a while because I read 3 times every step just to be sure)
lorddavid said:
Yes, Is strange, I know that the phone has hardware damage, but, only g sensor and flashlight, and everything works with AOSP, right know I'm charging the phone a little more, I've downloaded already viper rom, liberty, maximumHD, cm11 and Beanstalk.
Beanstalk has a lot of force close to me, cm11 just in the start, with a cm account, and when switching from the camera to videocamera.
Maybe there are error with the partition? I will try what you said and report back (will take a while because I read 3 times every step just to be sure)
Click to expand...
Click to collapse
Yes I thought about partitions, that's why if I was you I would run a ruu to make all clean and begin a clean fresh install.
I didn't test Beanstalk. CM11 works pretty well on both hboot, some FC however.
My favourite AOSP on 2.15 stills vanir aosp
But you will have time to test by yourself when everything will be repaired
I fully agree with you it's far better to take your time and read all threads carefully. Make thing in haste is the better way to do it wrong and have issues So take your time
benJX said:
Yes I thought about partitions, that's why if I was you I would run a ruu to make all clean and begin a clean fresh install.
I didn't test Beanstalk. CM11 works pretty well on both hboot, some FC however.
My favourite AOSP on 2.15 stills vanir aosp
But you will have time to test by yourself when everything will be repaired
I fully agree with you it's far better to take your time and read all threads carefully. Make thing in haste is the better way to do it wrong and have issues So take your time
Click to expand...
Click to collapse
I was trying to install maximushd first, but get an error here: fastboot flash recovery TWRP2.6.1.0.img and the green bar of the last command is still there, is normal?
the error is error: cannot load 'TWRP2.6.1.0.img': Unknown error
IT BOOTS!!!!!! Without recovery but boots!!!!!!!!!!!! I try that directly because a fas as i know the hboot manage the partitions, so install a hboot reinstall partitions right? But boots Sense again!!! I really misse it from my HTC ONE
I cant flash recovery, any advice? the error is
sending 'recovery' (8900 KB)...
OKAY [ 1.053s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.087s
I have still the recovery 2.7.0.8 but i need this version for hboot 2.16 (want to try other sense roms hehe) TWRP_2.6.1.0_ville_4.2.2.zip
Ok guys, sorry, my error, the bootloader got locked again. I did that and inmediatly I flash the recovery, Its seems everything is ok. it also clear internal storage but I wil see how is everything (hope to try sense 5.5, but as far as I read is not too much stable is that true?)
lorddavid said:
I was trying to install maximushd first, but get an error here: fastboot flash recovery TWRP2.6.1.0.img and the green bar of the last command is still there, is normal?
the error is error: cannot load 'TWRP2.6.1.0.img': Unknown error
IT BOOTS!!!!!! Without recovery but boots!!!!!!!!!!!! I try that directly because a fas as i know the hboot manage the partitions, so install a hboot reinstall partitions right? But boots Sense again!!! I really misse it from my HTC ONE
Click to expand...
Click to collapse
Yep you're right for the hboot & partitions.
Do not install normal TWRP on 2.16 hboot. The modded TWRP recovery from the OP which have to be used for this hboot is a .zip and have to be flashed when you're in ruu mode, just after flashing the firmware zip !
Did you follow all the install guide steps ?
Edit : you will find the recovery in this package. What afraids me is that you already should have downloaded this package to make a correct install of this rom. Your ~12gb of usable memory are correctly recognized by the phone ?
If not I suppose you did only one install of the rom. You need to flash recovery to make another install. Follow these steps :
1 - Boot in android, connect your phone and put the rom on your internal sdcard
2 - Reboot to fastboot
3 - You need to have file "TWRP_2.6.1.0_ville_4.2.2.zip" in your adb folder
4 - Type :
Code:
fastboot oem rebootRUU
fastboot flash zip TWRP_2.6.1.0_ville_4.2.2.zip
fastboot reboot recovery
7 - Flash MaximusHD (full wipe !). This should be the second time you do it.
8 - Reboot
Yeah. the problem is that for some reason its locked again, the bootloader, but in unlocked, and flash the TWPR of the package, and my pc see 11.9gb so its ok I think. (My mistake was copy al my data haha when i unlocked again the bootloader, its clear the storage again)
I just want to see sense 5.5, but if what I read is truth, i will use maximumhd as daily, hope that sense 5.5 gets better in a future
And just another question. Maximumhd and all sense roms are rooted? I dont see superuser. And can i enable beats with the speakers?
lorddavid said:
Yeah. the problem is that for some reason its locked again, the bootloader, but in unlocked, and flash the TWPR of the package, and my pc see 11.9gb so its ok I think. (My mistake was copy al my data haha when i unlocked again the bootloader, its clear the storage again)
I just want to see sense 5.5, but if what I read is truth, i will use maximumhd as daily, hope that sense 5.5 gets better in a future
Click to expand...
Click to collapse
So I edited my last post for nothing lol
You mean your bootloader was relocked ? It doesn't matter, being S-OFF is what is important here. Don't care about bootloader locked or unlocked.
Yes it is rooted, but it uses SuperSU not superuser. All roms released here are rooted, except if it is stated in the thread Beats cannot be enabled with speakers, only with headphones
benJX said:
So I edited my last post for nothing lol
You mean your bootloader was relocked ? It doesn't matter, being S-OFF is what is important here. Don't care about bootloader locked or unlocked.
Click to expand...
Click to collapse
Edited: you answered editign your post haha sorry. Maybe was because I still need the second flash
lorddavid said:
Edited: you answered editign your post haha sorry. Maybe was because I still need the second flash
Click to expand...
Click to collapse
You're welcome, glad it works
Liberty rom is quite smooth and usable but it stills in alpha for now. MaximusHD is rock stable It's based on the official release we should all have had.
benJX said:
You're welcome, glad it works
Liberty rom is quite smooth and usable but it stills in alpha for now. MaximusHD is rock stable It's based on the official release we should all have had.
Click to expand...
Click to collapse
Thanks, I try Liberty and boots Everything is working now, thankyou so much. So, it will better to wait a little more to use Liberty, thank you
(I will use MaximumHD for a while)
Related
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Ayahuascaa said:
Feel like a noob posting this, but I've been trying to fix this problem for the past 24hrs with no luck.
This is the first HTC device I've rooted in nearly a year, and I have to say even though it's pretty, I'm really disliking the evita.
I rooted it using Hasoon's toolkit, and other than being unable to install twrp (or cwm), or getting s-off, it all went well. I just pushed twrp 2.5 to my phone and left s-on until the toolkit gets updated. (not sure how to do this using adb, it's been awhile. ) I have a working hboot, fastboot, and twrp install, and even usb mass storage is working from twrp.
Now, the horror begins. I downloaded team vipers jb rom, and it seemed that the flash went perfectly. But it went into a loop and it seemed to have really messed up the internal sd. Couln't mount it, twrp couldn't find it during my attempts to install other roms or even a factory ruu. I found nocturnals sd fix and that worked like magic, but now twrp will not install any other roms, and everytime I try to push a factory ruu I get a parsing error? On my first attempt at restoring a factory ruu, I forgot that my cid was "1111111" and the bootloader was unlocked so it would fail immediatly. But, even with s-on I managed to get my cid to CWS__001 (ATT's cid) and relocked the bootloader temporarily. But this still didn't change things. Don't know if it matters, but I used hasoons toolkit to push the ruu to my phone and it's during this I get parsing errors. Attempting to install a rom through twrp (CM10, a stock rooted rom, etc.) will immediatly fail also. It says "error executing updater binary in zip and something else that I'll post after trying a CM nightly install.
Update: CM Nightly hangs at the HTC splash screen :crying:
Sorry it's alot to read, but I'm feeling lost at this point...
Click to expand...
Click to collapse
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
watameron said:
I think that if you don't have S-OFF, you need to manually flash boot.img as well when installing a ROM. Also, I had issues flashing ROMs with TWRP 2.5. Try 2.3.3.1.
Click to expand...
Click to collapse
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Ayahuascaa said:
Hmm... That could explain alot.
I'll try it and let you know what happens.
I have tried the 2.3.3.1 build of twrp, but for some reason the touchscreen doesn't work.
Click to expand...
Click to collapse
What HBOOT version do you have?
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
redpoint73 said:
Did you install Viper or ViperXL? ViperXL is what you want for the EVITA.
Click to expand...
Click to collapse
ViperXL JB
and my hboot is 2.14
Ayahuascaa said:
ViperXL JB
and my hboot is 2.14
Click to expand...
Click to collapse
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
exad said:
TWRP 2.3.3.1 should have a working touchscreen with hboot 2.14 are you sure you didn't try 2.3.3.0? that one requires you to downgrade touchscreen firmware first.
You need to fastboot flash boot boot.img where boot.img is extracted from the rom you're flashing if you're s-on and hboot >= 1.14.
If you have SuperCID, do not RUU without S-OFF or you really will have a paperweight.
Click to expand...
Click to collapse
Hmm.. I could have. I did it last night after two hours of frustration.
And I just did that to a new install of Nocturnal's rom, but with no luck. It still just hangs at the HTC dev warning screen. I'm going to try re downloading the ViperXL rom and hope I just had a bad copy..
heh. I did that without thinking last night and spent an hour trying to reverse the damage I did. Not only did I have s-on, but my cid was still "1111111".
./
Androidfilehost is only giving me ~50Kbps, so viper's rom has 3 hours left,
but Cleanrom is almost done.
Is there anyway to s-off the evita without booting into an os?
If not, can someone point me to a thread explaining how to manually s-off?
It seems that it's the cause for all this trouble I'm having and I've never had to do manually.
Thank you everyone for your help,
my phone still doesn't have a working os but I do feel like I'm getting somewhere.
Edit: How many of you have had problems installing roms with twrp 2.5.5.0? I'm thinking about trying 2.3.3.1. I thought this was what I flashed last night, but my touchscreen didn't work and according to exad's post I probably had the wrong one.
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
exad said:
Use twrp 2.3.3.1 all versions above 2.4 have one issue or another.
You need a Rom installed and usb debugging turned on to s-off.
Here's the link: http://forum.xda-developers.com/showthread.php?t=2155071
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Ayahuascaa said:
Thanks,
It seems that now 2.5.5.0 just skips the install and tells me that it was successful...
If so that would explain the hangups on the dev screen.
Edit: Can you point me to a link for twrp 2.3.3.1? The only thread on xda for that build doesn't have working download links
Click to expand...
Click to collapse
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
exad said:
http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.1-evita.img
Md5: d903047e6e871acb8f99834c30eb8307
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
CleanRom boots!
Thanks again to everyone who helped and exad for the 2.3.3.1 link,
Hi, i had a S4 which got a broken screen and costs too much to fix a the moment so i brought a Telstra HTC ONE XL off a friend for $100.
I do like the phone but was over the 4.2.1 software as used to the 4.3 on the S4 which i rooted and put on CM10.
I tried with this phone to put on the nightly cm 10.3 but i hit a problem ,when install the nightlies it boot loops and when i try install the stable 10.1 it fails with an error which i do belive is to do with my V2 hboot.
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial
I have unlocked through htcdev and rooted it ok.
Im stuck now though as i pressed backup current original rom which turns out its not.
The phone details are
CID TELST001
Model: HTC ONE XL TELSTRA
If someone can tell where to either find the newest telstra rru for my phone or how to update my hboot so i can use cm10?
My phone is pretty useless at the moment
stueee said:
I downloaded the RRU which is supposted to update the hboot to v3 then i can install cm10.3 (aparently) but when i run the rru it fails saying not for my phone.
Click to expand...
Click to collapse
Where are you getting CM from (link it) and what is the file named? CM will typically have the phone's code name (EVITA) in the file name. If the code name ENDEAVORU is in the file name, it is in fact for the wrong device, as the ENDEAVORU is for the quad core Tegra3 (non-LTE) version, which is completely different hardware.
Also, I don't know if 10.3 is even released yet for our device, or for the ENDEAVORU for that matter. I think you might be confused about what you are flashing. So again, link what you are trying to install.
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have. Getting s-off disables the security check which would let you run any Evita RUU but you need to get a ROM to boot first before you try that. You also need SuperCID.
Your best bet is probably to flash an older Sense ROM (4.0 or 4.1), then you can at least boot, and get SuperCID and s-off so you can run the 3.18 RUU to meet the requirements for the latest cm ROMs.
Sent from my Evita
timmaaa said:
The reason you couldn't run that RUU is because the CID check wouldn't allow it, it's looking for an at&t CID which you don't have.
Click to expand...
Click to collapse
For some reason, I got confused and thought the OP was saying that the ROM install was failing. But it clearly says the RUU (or "rru" anyway) failed.
But yes, you can only run an RUU for your carrier version. So you will need s-off to run the AT&T RUU (the RUU referenced in the OP).
But still confused about the mention of CM10.3. From what I can see, it doesn't exist for either our EVITA, or the ENDEAVORU.
Maybe he meant cm10.2 and it was a typo?
Sent from my Evita
timmaaa said:
Maybe he meant cm10.2 and it was a typo?
Click to expand...
Click to collapse
Could be. Although if so, its a type that appears twice.
It seems fairly common for folks to try to install the wrong CM (wrong device). So I want to make sure the OP isn't doing that.
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
stueee said:
redpoint73 - the CM i downloaded and installed was from http://get.cm/?device=evita and i tried
cm-10.2-20131030-NIGHTLY-evita.zip which installed but bootloops
and then i tried the stable - cm-10.1.3-evita.zip which gave me the failed error.
Click to expand...
Click to collapse
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Hi Red,
Sorry i typed out that post at almost 1am after pulling my hair out over a few hours and got a little confused.
My hboot is 2.15 and twrp is 2.6.3.0 which I believe is the latest.
What sense rom would work on mine as i really need this working now as i cant find a rom to suit anywhere with my lesser expertees.
I tried changing the cid using the super cid Telstra bat file but it won't recognize the phone as its not loaded, i tried in off state, bootloader, fastboot and twrp but is just keeps saying cant find phone.
I also tried the hex editor method but it didnt seem to update the CID after i completed it without errors.
thanks for you help.
redpoint73 said:
Okay, neither of those are CM10.3, as stated in your first post. Please post accurate information to prevent form confusing those that are trying to help.
What hboot are you currently on? Its listed on the bootloader screen.
What version of TWRP?
You should be able to mount SD in TWRP, put a Sense ROM on the phone, and get back up and running.
Click to expand...
Click to collapse
With 2.15 hboot, you cannot modify the files required for supercid.
You can try the ever so risky jet tool. But this tool deliberately bricks to downgrade your hboot.
Sent from my HTC One XL using xda app-developers app
Any recent Sense ROM will suit your current setup, have a look here and you'll find a whole bunch. Unfortunately for you the 2.15 hboot has write protection enabled so there's no way you can get SuperCID (abd therefore can't get s-off), at least not until an exploit is released.
When you tried to flash CM did you also flash the boot.img via fastboot afterwards? You're s-on so that's necessary to get it to boot. Phones on a higher hboot like yours are unable to flash the boot.img through recovery so it must be done manually.
All you do is retrieve the boot.img from the root of the ROM zip, put it in your fastboot folder on your PC, and after you've flashed the ROM in recovery you reboot to bootloader, connect the phone to the PC, open a command prompt from within your fastboot folder (shift + right click anywhere in the folder then select open command prompt here), then give the following command:
fastboot flash boot boot.img
Once that's done you can reboot the phone and it should boot into the ROM.
Sent from my Evita
stueee said:
My hboot is 2.15
Click to expand...
Click to collapse
That's pretty important. This is the reason why the older CM10.1 failed to install. CM was having issues with older hboots, so a script was added to require hboot 2.14.
Once hboot 2.15 came along, folks found that CM failed to install since the install script explicitly requires 2.14. Later versions include hboot 2.15 in the install script.
As exad and timmaaa mention, SuperCID (and therefore s-off) are not possible on hboot 2.15. So you are stuck with s-on (assuming that is what you are on now). It also means you can't currently run any RUU. Reason being, with s-on you can't run older RUUs, RUUs from another carrier, and there are no RUUs based on hboot 2.15. No "current" RUU exists (for your hboot), you can't run "previous" RUUs with the S-on restriction. So therefore you can't currently run any RUU.
But hboot 2.15 will work with newer versions of CM (and other AOSP ROMs which have been recently updated) as well as any Sense ROMs. But with s-on, you need to extract boot.img and flash manually with fastboot every time you install a ROM (as timmaaa points out). If you did not do this, this is why flashing the recent CM10.2 nightly resulted in a bootloop. Failure to falsh boot.img is the most common reason for bootloop after flashing a ROM.
stuck in bootloop
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
martin-m7 said:
ive recently have been flashing different roms onto my htc one with no problem..then i decided to try the google play edition and realised i had to be s-off...now i have super cid 11111111 and s-off and was running skydagon 14.1 with no prob...today i did a nand backup and thought i would try the liquid rom then half way through the fresh install (i wiped cache and dalvik first)my phone shut down and boots up into a loop..if i go to recovery (twrp 2.6.3.3) it only stays in recovery a few seconds then goes back to the start of bootloop...i have tried cwmr also...i have otg cable and have used adb a few times however im not highly skilled so any help would be appreciated...apologies on the excessive post..
Click to expand...
Click to collapse
You're in the wrong forum, buddy. This is the HTC One XL forum.
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
MAsterokki said:
I decided to update my Dev unlocked Sensation to ICS, but had forgotten it was probably still on a Gingerbread radio. Now I have no working rom, and for some reason I am unable to flash the original rom (RUU) via the SD card method (PG58IMG).
My CID is HTC__E11 and therefor european roms from RUU should work, but I get the following error message when trying the sd card flash: wrong zipped image. In other cases it wont go further than parsing.
When i try to flash the RUU in ruu mode on the phone I get the following error: 99 unknown fail.
Unfortunately I cannot go back to the rom I was on before, since I dont have it anymore.
So the only thing I have now is TWRP recovery 2.6.3 and unlocked HBOOT 1.27.
Furthermore I am unable to see what my current radio firmware is. I want to flash a jellybean rom.
Does anyone know what to do?
Click to expand...
Click to collapse
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
heavy_metal_man said:
ok would i be correct in thinking that you are s-on? how exactly did you upgrade from gingerbread to ics and have you tried formatting all partitions from twrp?
Click to expand...
Click to collapse
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
MAsterokki said:
Yes I am S-ON. I did try formatting all partitions from twrp, that didnt help. I also tried cwm, but that didnt help either.
My radio was finally displayed by HBOOT, it is: 11.29A.3504.18_M. I believe this is a ICS radio, so there should be no problem here. Unfortunately i cannot find the RUU that corresponds to that radio and trying to flash another ruu wont work.
To go to ICS I just installed the latest CM11 from Sultan, which works on my other sensation (which is S-OFF). I have also tried other roms, but they all wont boot for some weird reason. For every rom I do a full wipe.
Click to expand...
Click to collapse
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
heavy_metal_man said:
If your s-on you need to flash the boot.IMG of your rom from fastboot straight after flashing your rom from recovery pal. But I recommend installing 4ext recovery and enabling its "smart flash" feature and this will do it for you try this and check back pal.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
MAsterokki said:
Lol I have been doing this for so long with a S-OFF device that I totally forgot about that! Thank you so much, sorry for my stupidity haha. Still weird that I cannot flash RUU though...
Click to expand...
Click to collapse
Its cool pal it is, but then again ruus won't flash unless your bootloader is relocked
Sent from my Nexus 7 using Tapatalk
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
the_ziom said:
Hello I have supercid, s-off and previously flashed MAXIMUSHD ROM and that's on hboot 2.16 so I got board and sick of sense 5 and I want to try out one of the kitkat ROMs but I need hboot 2.15 for that and yes I know that there are hboot 2.16 kitkat roms but they are unstable so can someone tell me step by step how to downgrade hboot 2.16 to 2.15 because I'm quite of a dumb person
Click to expand...
Click to collapse
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
benJX said:
This is how I proceed :
1) Downgrade to 2.15 hboot by flashing the old firmware (extract firmware.zip and flash as you did for MaximusHD)
2) Run the latest RUU to get everything clean (I flashed this one)
3) Flash custom recovery with fastboot (TWRP 2.3.X.X)
4) You're done !
Click to expand...
Click to collapse
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
the_ziom said:
thank you but i have super cid and from what i have read i have to install the ruu according to my cid
tell me if im right
Click to expand...
Click to collapse
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
dr3amsINdigital said:
Yeah I heard about that method, but I thought it would be safer to just run the RUU even though it's more work. I think the bricks were from flashing the zips in recovery, not the new ones you flash in fastboot. Either way, I didn't feel like risking it.
Thanks! I'll try the RUU.
Click to expand...
Click to collapse
Wise choice, yeah you are right, the bricks were when they were flashing the zips in recovery. Its actually pretty safe in RUU mode but what's the point of risking it.
benJX said:
In fact, the CID matters if you have one from an operator (have a look here, but not the last one, it's the superCID), in this case, you have to choose a RUU according to your operator.
But being superCID, you can run any RUU, so run the last generic one (see my link) and everything will be ok to start from official clean install. Of course you'll stay S-OFF after running the RUU.
The only thing requested is to be on 2.15 hboot, that's why you have to downgrade to older firmware in order to run this.
Hope it will help.
Click to expand...
Click to collapse
dr3amsINdigital said:
I have kind of a similar question. After moonshine S-OFF, I'm on modified moonshine HBOOT 2.15.4444. Now I want to go back to the stock HBOOT 2.15.0000. Do I just need to run the RUU to go back? I'm bootloader unlocked, CID T-MOB010, TWRP recovery, and I flashed radio 1.20. Do I need to flash radio back to match the RUU before I run it?
Thanks
Click to expand...
Click to collapse
rosswhite said:
Running an RUU is the safest option, although its a bit hit and miss getting the RUU to run correctly. Flashalot recently made a guide (http://forum.xda-developers.com/showthread.php?t=2678700) if you run into any problems. I would try it without changing the radio, if it doesn't work then flash the matching one and go from there.
Now I cannot recommend this, as I have only tried it once myself and the consequences if it went wrong could mean a dead phone, but this post (http://forum.xda-developers.com/showpost.php?p=39216236&postcount=274) details how you can manually flash a hboot version in RUU mode since you are S-OFF. It comes from this thread: http://forum.xda-developers.com/showthread.php?t=1777223. Use it at your own risk, there have been two incidents of bricks but it depends how lucky you are feeling!
Click to expand...
Click to collapse
HELP my device does not see any memory and i cant flash any rom hellpp
the_ziom said:
HELP my device does not see any memory and i cant flash any rom hellpp
Click to expand...
Click to collapse
What hboot are you on now? Did you run an RUU to downgrade?
rosswhite said:
What hboot are you on now? Did you run an RUU to downgrade?
Click to expand...
Click to collapse
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Which recovery did you flash? Try TWRP 2.7.0.0.
the_ziom said:
Hboot 2.15 after running the |RUU.exe|
dont have the memory (does not see device when trying to side load , recovery cant mount sdcard)
help i need my phone
Click to expand...
Click to collapse
Can you boot on stock android rom installed by the ruu ?
rosswhite said:
Which recovery did you flash? Try TWRP 2.7.0.0.
Click to expand...
Click to collapse
i already have twrp 2.7 and i flashed phillz and still nothing
benJX said:
Can you boot on stock android rom installed by the ruu ?
Click to expand...
Click to collapse
yes but i formated my memory to instal a pac man rom
the_ziom said:
yes but i formated my memory to instal a pac man rom
Click to expand...
Click to collapse
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
####
benJX said:
So actually you can confirm you are on HBOOT 2.15, Pihllz recovery and no rom installed ?
If yes reboot to bootloader, select clear storage, flash this recovery. Your sdcard should be mountable and let you install your rom.
Click to expand...
Click to collapse
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
So many developers and only 2 can help me
Please I'm begging for help
the_ziom said:
Another Problem
when ever i try to flash any rom it fails! and i dont know what to do HElp
Click to expand...
Click to collapse
Flash stock recovery : http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Then Clear Storage from bootloader and flash TWRP recovery
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
MICH_** said:
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
Click to expand...
Click to collapse
1: I run CM11 which is 4.4.
2: Don't know but not sure if there is a 4.4 ROM with Sense 5.
3: The boot.img is in the ROM zip - just unzip it and the boot.img is there. When you are S-OFF the boot.img is flashed with the zip. Otherwise you have to do it manually if you are not S-OFF.
I am no expert but one thing I know - life got a lot easier being S-OFF with the HTC ONE S.
808phone said:
1: I run CM11 which is 4.4.
2: Don't know but not sure if there is a 4.4 ROM with Sense 5.
3: The boot.img is in the ROM zip - just unzip it and the boot.img is there. When you are S-OFF the boot.img is flashed with the zip. Otherwise you have to do it manually if you are not S-OFF.
I am no expert but one thing I know - life got a lot easier being S-OFF with the HTC ONE S.
Click to expand...
Click to collapse
Are you on hboot 2.15 too? Did you update your firmware?
No but there are sense 5.5 roms with android 4.3....
How did you get S-OFF? And which tutorial did you use to unlock etc?
MICH_** said:
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
Click to expand...
Click to collapse
Let's take one by one...
1. Yes. Currently only AOSP ROMs are with Android 4.4.2, there's no Sense based one (but it's been working on it)
2. Well, that's a tricky question...You don't need S-Off for sense 5.x BUT...only ROM with sense 5.5 is Liberty (by bilal_liberty). If you're not S-Off you can't flash radios. If you can't flash radios, you will not have HSPA/HSPA+ mobile data connection with that ROM (and probably with sense 6 and 4.4.2 ROM also). You will get maximum 3G (UMTS) mobile data with your current radio. On the other hand, if you decide to try an AOSP ROM, you won't have that problem there. You can be S-On and have everything working
3. You have to flash boot.img only if you're S-On. Maybe it's better if you read what S-On/S-Off means. On short, if you're S-On, some partitions are read only and you cannot write to them in recovery...most important the radio partition and the kernel/boot partition. So if you're S-On you can't flash the radio and you can't flash the kernel. Kernel has several components (I try to make a simple explanation not entering in the details): modules, ramdisk and the kernel itself. I'll take them one by one:
- modules: most are incorporated in the ROM and have the extension .so. These files are flashed on the device in the /system partition along with the ROM, in recovery. You don't need to be S-Off to have those installed
- ramdisk & kernel: they're both packed in that boot.img and they're generically referred to as "kernel". These are written in a special partition that is read-only for S-On devices while in recovery. Kernel partition is in write-mode only in fastboot. Therefore you must be S-Off to be able to write kernel from recovery OR, you have to write it from fastboot if you're S-On
So, when you flash a ROM ZIP, the install script writes the modules along with the rest of the ROM since those resides on the /system partition then tries to write also the boot.img. But in case you're S-On, it can't. So the only way to do it is from fastboot where you separately flash the boot.img
Now as I give you some info, take some time and read it (TWICE). Then take some time and look for the tutorials here. First thing you should do is to unlock your bootloader via HTC Dev site. Then you can install a recovery and make S-Off (I personally used for that Rumrunner but it's your call)
Before doing anything, install Android SDK and make sure it's properly installed and the drivers are working. You should have a functional ADB/fastboot for any of the above.
Rapier said:
Let's take one by one...
1. Yes. Currently only AOSP ROMs are with Android 4.4.2, there's no Sense based one (but it's been working on it)
2. Well, that's a tricky question...You don't need S-Off for sense 5.x BUT...only ROM with sense 5.5 is Liberty (by bilal_liberty). If you're not S-Off you can't flash radios. If you can't flash radios, you will not have HSPA/HSPA+ mobile data connection with that ROM (and probably with sense 6 and 4.4.2 ROM also). You will get maximum 3G (UMTS) mobile data with your current radio. On the other hand, if you decide to try an AOSP ROM, you won't have that problem there. You can be S-On and have everything working
3. You have to flash boot.img only if you're S-On. Maybe it's better if you read what S-On/S-Off means. On short, if you're S-On, some partitions are read only and you cannot write to them in recovery...most important the radio partition and the kernel/boot partition. So if you're S-On you can't flash the radio and you can't flash the kernel. Kernel has several components (I try to make a simple explanation not entering in the details): modules, ramdisk and the kernel itself. I'll take them one by one:
- modules: most are incorporated in the ROM and have the extension .so. These files are flashed on the device in the /system partition along with the ROM, in recovery. You don't need to be S-Off to have those installed
- ramdisk & kernel: they're both packed in that boot.img and they're generically referred to as "kernel". These are written in a special partition that is read-only for S-On devices while in recovery. Kernel partition is in write-mode only in fastboot. Therefore you must be S-Off to be able to write kernel from recovery OR, you have to write it from fastboot if you're S-On
So, when you flash a ROM ZIP, the install script writes the modules along with the rest of the ROM since those resides on the /system partition then tries to write also the boot.img. But in case you're S-On, it can't. So the only way to do it is from fastboot where you separately flash the boot.img
Now as I give you some info, take some time and read it (TWICE). Then take some time and look for the tutorials here. First thing you should do is to unlock your bootloader via HTC Dev site. Then you can install a recovery and make S-Off (I personally used for that Rumrunner but it's your call)
Before doing anything, install Android SDK and make sure it's properly installed and the drivers are working. You should have a functional ADB/fastboot for any of the above.
Click to expand...
Click to collapse
2. So i have to update my firmware, right?
3. okay, i understood everything.. thank you
Why do i need the complete SDK? Doesn´t it work just with the adb and fastboot drivers?
MICH_** said:
2. So i have to update my firmware, right?
3. okay, i understood everything.. thank you
Why do i need the complete SDK? Doesn´t it work just with the adb and fastboot drivers?
Click to expand...
Click to collapse
You don't have to upgrade the firmware since you're on the latest official one. 2.16 is an unofficial leaked firmware and you only need it if you want to flash MaximusHD or MagioRom
You don't need entire SDK but I thought it's easier since is an install package for that. Of course, if you don't build for Android, you don't need the libraries, just the tools
Sent from nowhere over the air...
Rapier said:
You don't have to upgrade the firmware since you're on the latest official one. 2.16 is an unofficial leaked firmware and you only need it if you want to flash MaximusHD or MagioRom
You don't need entire SDK but I thought it's easier since is an install package for that. Of course, if you don't build for Android, you don't need the libraries, just the tools
Sent from nowhere over the air...
Click to expand...
Click to collapse
could you give me a good tutorial for unlocking the bootloader, s-off, flash this leaked firmware and super-CID please?
Okay, i unlocked the bootloader, installed TWRP, flashed a custom rom and now i am trying to get s-off...
MICH_** said:
could you give me a good tutorial for unlocking the bootloader, s-off, flash this leaked firmware and super-CID please?
Okay, i unlocked the bootloader, installed TWRP, flashed a custom rom and now i am trying to get s-off...
Click to expand...
Click to collapse
For firmware ZIPs you can flash in recovery AFTER you make S-Off, check HERE. For S-Off I used Rumrunner cause it seems to me much easier and without so many steps...it's something like a one-click operation
Rapier said:
For firmware ZIPs you can flash in recovery AFTER you make S-Off, check HERE. For S-Off I used Rumrunner cause it seems to me much easier and without so many steps...it's something like a one-click operation
Click to expand...
Click to collapse
Rumrunner is running now
I will update my firmware tomorrow i think..
If i update the firmware with this tutorial from Maxiums 10.0 rom. Do i have hboot 2.16? Am i still able to run roms for 2.15 hboot?
MICH_** said:
Rumrunner is running now
I will update my firmware tomorrow i think..
If i update the firmware with this tutorial from Maxiums 10.0 rom. Do i have hboot 2.16? Am i still able to run roms for 2.15 hboot?
Click to expand...
Click to collapse
I didn't checked the MaximusHD tutorial but I strongly suggest you to just flash the firmware zip if you want to do an upgrade/downgrade of the firmware. Most tutorials assume you're initial S-Off and include also some steps for how to acquire this or going through RUUs.
OK..I've read the MaximusHD tutorial, it's pretty much identical with the one made by Flashalot...so the answer is YES, you can use it and after that you would have hboot 2.16. Please also note that a different recovery must be used with 2.16 ROMs. But you'll have that in the MaximusHD instructions as well
NO, you can't run or flash ROMs made for 2.15 firmware after doing this. You should downgrade the firmware to 2.15 first, by using the instructions and the firmware ZIP from the thread I've linked
Rapier said:
I didn't checked the MaximusHD tutorial but I strongly suggest you to just flash the firmware zip if you want to do an upgrade/downgrade of the firmware. Most tutorials assume you're initial S-Off and include also some steps for how to acquire this or going through RUUs.
OK..I've read the MaximusHD tutorial, it's pretty much identical with the one made by Flashalot...so the answer is YES, you can use it and after that you would have hboot 2.16. Please also note that a different recovery must be used with 2.16 ROMs. But you'll have that in the MaximusHD instructions as well
NO, you can't run or flash ROMs made for 2.15 firmware after doing this. You should downgrade the firmware to 2.15 first, by using the instructions and the firmware ZIP from the thread I've linked
Click to expand...
Click to collapse
could you please give me a link to a recovery that is compatible with 2.16? TWRP would be perfect
After installing the new hboot i have still a rom for 2.15 running on my phone. does this work? Does updating the firmware wipe internal storage?
Why do some sense 5 roms work with hboot 2.15 and others not?
MICH_** said:
could you please give me a link to a recovery that is compatible with 2.16? TWRP would be perfect
After installing the new hboot i have still a rom for 2.15 running on my phone. does this work? Does updating the firmware wipe internal storage?
Why do some sense 5 roms work with hboot 2.15 and others not?
Click to expand...
Click to collapse
Oh...you like to ask soo many questions don't you? All these questions are already answered in the threads, why don't you check them?
The main difference between 2.15 and 2.16 hboot/firmware is the partition map. On 2.16 there is no separation between the sdcard and data and you get a single big space for both. This makes more space available to data and sdcard looks bigger (12 GB instead of 10 GB). That's a brief description not entering in details. ROMs made for 2.15 will work on 2.16 and the other way around BUT with issues. Mainly it is about the sdcard size that is not available at all or has an incorect size (48 MB instead of 12/10 GB). So even if your 2.15 ROM is working...try to check if the sdcard is mounted and what space you have on it
So all these being said, your understanding of the word "works" is different from the one of the devs. For them (or for anyone else), a "working" ROM does not mean only it boots, but it's also have all the parts available including sdcard mountable and available on it's entire space, not truncated to 48 MB or not mountable at all.
Now about why some sense 5 ROMs work with 2.15 and some don't. Because some ROMs are based on the leaked 2.16 firmware and those ROMs need the new partition map to properly work. The ones that are working on 2.15 are usually ports or builds made for the standard official HTC firmware.
Link for recoveries compatible with 2.16 hboot you can find in the OP of each 2.16 ROM
Rapier said:
Oh...you like to ask soo many questions don't you? All these questions are already answered in the threads, why don't you check them?
The main difference between 2.15 and 2.16 hboot/firmware is the partition map. On 2.16 there is no separation between the sdcard and data and you get a single big space for both. This makes more space available to data and sdcard looks bigger (12 GB instead of 10 GB). That's a brief description not entering in details. ROMs made for 2.15 will work on 2.16 and the other way around BUT with issues. Mainly it is about the sdcard size that is not available at all or has an incorect size (48 MB instead of 12/10 GB). So even if your 2.15 ROM is working...try to check if the sdcard is mounted and what space you have on it
So all these being said, your understanding of the word "works" is different from the one of the devs. For them (or for anyone else), a "working" ROM does not mean only it boots, but it's also have all the parts available including sdcard mountable and available on it's entire space, not truncated to 48 MB or not mountable at all.
Now about why some sense 5 ROMs work with 2.15 and some don't. Because some ROMs are based on the leaked 2.16 firmware and those ROMs need the new partition map to properly work. The ones that are working on 2.15 are usually ports or builds made for the standard official HTC firmware.
Link for recoveries compatible with 2.16 hboot you can find in the OP of each 2.16 ROM
Click to expand...
Click to collapse
now i have everything i wanted to know tanks
I think i will stay on 2.15 and install ViperOne S 3.1.3 now. This will work on my current setup, right?
I will update the radio. Should i just flash the one attached in the ViperOne S thread in recovery?
MICH_** said:
now i have everything i wanted to know tanks
I think i will stay on 2.15 and install ViperOne S 3.1.3 now. This will work on my current setup, right?
I will update the radio. Should i just flash the one attached in the ViperOne S thread in recovery?
Click to expand...
Click to collapse
Good choice, Viper is a fine ROM and close to the original since it's sense based...also has extra customization that the original ROM doesn't have.
For the radio, well I've answered to you in the Viper thread. I would advice not to flash another radio just now. Flash the ROM, play with it for a few days then decide. If you have no issues with signal reception, wifi and so on, you don't have real reasons to change it.
I had initially (when I bought the device) radio 1.06es (I think)...since then alot of newer versions came out including the 1.20 from the leaked 2.16 firmware and the newest 1.35a from the One XL. To be honest, after several days with each, I've switched back to 1.15 that was the best radio for me.
The only ROM for which you MUST flash a different radio will be Liberty by bilal_liberty. That is based on Android 4.3 and Sense 5.5 and the newest 1.35a radio is needed in order to get H/H+ (HSPA) mobile data connection. If you don't use that radio you'll get maximum 3G (UMTS) connection. The rest will work tho
I still don't understand why I had so many problems with Viper. Dropped calls, random reboots etc...
Once I got CM11 running - never looked back in terms of reliability.