Related
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.
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 2.16
How can I install CM11 successfully ?
Thx :laugh:
Installing CM 11
kc6992 said:
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 1.16
How can I install CM11 successfully ?
Thx :laugh:
Click to expand...
Click to collapse
Aquire S-Off and SuperCID . This makes things ten times more easier . There are recent thread posts in Android development that show you how .
You will have to actually update your hboot to 2.15 and implement a twrp that supports SElinux.
1 ) http://forum.xda-developers.com/showthread.php?t=2322755
Use that to upgrade your hboot.
2 ) http://flemmard.net/recoveries/openrecovery-twrp-2.6.3.0-ville-selinux.img
Download and flash this recovery.
3 ) http://download.cyanogenmod.org/?device=ville
Get the latest nightly from the get.cm
... and flash away
---------- Post added at 11:11 PM ---------- Previous post was at 11:06 PM ----------
If you need specifics, Let me know.
I've been down your path and I hopefully can help you out on each step.
Happy flashing
S-Off
Thanks for the fast reply.
Is it better to do S Off before superCID ?
To make it s-off which méthode should i use? Facepalm or moonshine?
kc6992 said:
Thanks for the fast reply.
Is it better to do S Off before superCID ?
To make it s-off which méthode should i use? Facepalm or moonshine?
Click to expand...
Click to collapse
S-Off First, Cause that's what enables you to install different RUU's and update/downgrade firmware.
Try Facepalm
.. and for superCID, use one of the toolkit's. that one's a bit easier
kc6992 said:
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 1.16
How can I install CM11 successfully ?
Thx :laugh:
Click to expand...
Click to collapse
You have hboot 2.16 not 1.16. What I suggest is before downgrading, try one of CM11 builds for 2.16. They're compiled by RockR172 for 2.16 and they're based on official builds. Latest available is the one from 20/12 and you'll find it in the second post from the CM11 thread. If you find then CM11 comfortable to use, you could downgrade your hboot to 2.15 and start using the official nightlies.
Sent from nowhere over the air...
Hboot
Rapier said:
You have hboot 2.16 not 1.16. What I suggest is before downgrading, try one of CM11 builds for 2.16. They're compiled by RockR172 for 2.16 and they're based on official builds. Latest available is the one from 20/12 and you'll find it in the second post from the CM11 thread. If you find then CM11 comfortable to use, you could downgrade your hboot to 2.15 and start using the official nightlies.
Sent from nowhere over the air...
Click to expand...
Click to collapse
You right i have hboot 2.16 ...
This unofficial Rom will also work with s-off if i use "Incase you don't have S-OFF, fastboot flash boot boot.img" or won't it?
http://forum.xda-developers.com/showthread.php?t=2528113
For the next step:
How can I downgrade hboot then? must i have to lock and then unlock it again with HTCdev?
Must i be s-off and supercid?
kc6992 said:
You right i have hboot 2.16 ...
This unofficial Rom will also work with s-off if i use "Incase you don't have S-OFF, fastboot flash boot boot.img" or won't it?
http://forum.xda-developers.com/showthread.php?t=2528113
For the next step:
How can I downgrade hboot then? must i have to lock and then unlock it again with HTCdev?
Must i be s-off and supercid?
Click to expand...
Click to collapse
Yes. That was the one I told you about. In the second post, you'll find links to the 2.16 builds. The latest one is THIS. That step for flashing kernel in fastboot is mandatory for anyone that's S-On, for any ROM and for any hboot higher than 1.09. So after you flash that ROM, reboot to fastboot and flash the boot.img (that you have previously extracted from the ROM zip) using that command.
For downgrade, there a couple of threads describing the procedure in the Dev section, there's no need to repeat all this at this point. Fist flash this CM and see if you are OK with it...not to find later that you've downgraded and now you want MaximusHd back. Going from sense based ROMs to non-sense based ROMs was a challenge for many and there are alot of things that differs. That's why I said you might want to check first and only after take such decision
I just compiled a recent CM11 version (0109-nightly) for hboot 2.16. You can download it from
https://drive.google.com/file/d/0B0ajti88ZAFzYkZqNEVydkZwSzg/edit?usp=sharing
if you want. Its compiled from the official CM11 sources where additionally two cherry picks
are necessary to support the new hboot and TWRP recovery
http://review.cyanogenmod.org/#/c/53647/
http://review.cyanogenmod.org/#/c/53559/
Edit: Note that this build is ONLY for HBOOT 2.16 !!!
If you are s-on you still have to extract the kernel (boot.img) from the archive and flash it via fastboot after
flashing the zip. Alternatively you can use the FlashImageGUI app (from play store). In this case flash the boot.img BEFORE
you flash the rom zip. Worked great for me when I was still s-on and you don't need a computer to flash a
new rom.
kc6992 said:
You right i have hboot 2.16 ...
This unofficial Rom will also work with s-off if i use "Incase you don't have S-OFF, fastboot flash boot boot.img" or won't it?
http://forum.xda-developers.com/showthread.php?t=2528113
For the next step:
How can I downgrade hboot then? must i have to lock and then unlock it again with HTCdev?
Must i be s-off and supercid?
Click to expand...
Click to collapse
Hey Bro How Did U managed to install Maximus Hd on S on and without supercid...plzz tell me m tired of this Tmobile Rom.....thankx.
I believe Twistedkat ROM works on hboot 2.16. Check it out in dev forum
http://forum.xda-developers.com/showthread.php?t=2584591&page=37
Nobody?????
Hemantgits said:
Nobody?????
Click to expand...
Click to collapse
What Hboot are you on ?
kc6992 said:
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 1.16
How can I install CM11 successfully ?
Thx :laugh:
Click to expand...
Click to collapse
This thread is very confusing!
Firstly the OP must be S-Off to flash the 2.16 firmware in order to run MaximusHD with the right storage etc, no? Might be confused thinking superCID is S-Off? Also, TWRP version must be 2.6.1.0 not 2.4.1?
drkxyz said:
I just compiled a recent CM11 version (0109-nightly) for hboot 2.16. You can download it from
https://drive.google.com/file/d/0B0ajti88ZAFzYkZqNEVydkZwSzg/edit?usp=sharing
if you want. Its compiled from the official CM11 sources where additionally two cherry picks
are necessary to support the new hboot and TWRP recovery
http://review.cyanogenmod.org/#/c/53647/
http://review.cyanogenmod.org/#/c/53559/
Edit: Note that this build is ONLY for HBOOT 2.16 !!!
If you are s-on you still have to extract the kernel (boot.img) from the archive and flash it via fastboot after
flashing the zip. Alternatively you can use the FlashImageGUI app (from play store). In this case flash the boot.img BEFORE
you flash the rom zip. Worked great for me when I was still s-on and you don't need a computer to flash a
new rom.
Click to expand...
Click to collapse
Did the CM 0109-nightly for 2.16 hboot you compiled flash ok? Are you running it now? I think most of the dev's have had problems getting it to install properly. I don't think you can be S-On and on 2.16 hboot, unless I'm missing something?
fatboyslimerr said:
I believe Twistedkat ROM works on hboot 2.16. Check it out in dev forum
http://forum.xda-developers.com/showthread.php?t=2584591&page=37
Click to expand...
Click to collapse
I tried to flash the latest version of Twistedkat ROM the other night and it wouldn't flash with any recovery that I tried on 2.16 hboot.
rom
rosswhite said:
This thread is very confusing!
Firstly the OP must be S-Off to flash the 2.16 firmware in order to run MaximusHD with the right storage etc, no? Might be confused thinking superCID is S-Off? Also, TWRP version must be 2.6.1.0 not 2.4.1?
Did the CM 0109-nightly for 2.16 hboot you compiled flash ok? Are you running it now? I think most of the dev's have had problems getting it to install properly. I don't think you can be S-On and on 2.16 hboot, unless I'm missing something?
I tried to flash the latest version of Twistedkat ROM the other night and it wouldn't flash with any recovery that I tried on 2.16 hboot.
Click to expand...
Click to collapse
I wasn't confused. I really was S-On with twrp 2.4.1 and it worked well
Now i'am back on hboot 2.15 and i flashed CWM in order to flash CM11.
For maximusHD on hboot 2.16 and S-ON I just followed the tutorial : http://forum.xda-developers.com/showthread.php?t=2445392
I know it may sound confusing, but maximusHD worked for me on S-ON, and it has been my daily Rom for over 3 months.
When i installed it, I just couldnt run the firmware.zip (i had a fail) but it worked correctly without.
kc6992 said:
I wasn't confused. I really was S-On with twrp 2.4.1 and it worked well
Now i'am back on hboot 2.15 and i flashed CWM in order to flash CM11.
For maximusHD on hboot 2.16 and S-ON I just followed the tutorial : http://forum.xda-developers.com/showthread.php?t=2445392
I know it may sound confusing, but maximusHD worked for me on S-ON, and it has been my daily Rom for over 3 months.
When i installed it, I just couldnt run the firmware.zip (i had a fail) but it worked correctly without.
Click to expand...
Click to collapse
Ok, the thing is it's the firmware.zip that gives you a hboot version of 2.16. So if you didn't flash that, you were on a lower hboot, you can still flash the ROM I believe but you only have 2gb of storage available. Anyway, It doesn't matter now. Enjoy CM11.
CM nightly on 2.16 firmware works great for me. Updated to 0110 in the meanwhile and I only have the known bugs like backlight not coming
up after a phone call and very rare reboots (indeed no reboot on 0110 since now :fingers-crossed: )
There are indeed lots of people who installed MaximusHD on hboot 2.16 with s-on over in the MaximusHD thread. It's very dangerous though
and may lead to bricked devices ...
rosswhite said:
This thread is very confusing!
Firstly the OP must be S-Off to flash the 2.16 firmware in order to run MaximusHD with the right storage etc, no? Might be confused thinking superCID is S-Off? Also, TWRP version must be 2.6.1.0 not 2.4.1?
Did the CM 0109-nightly for 2.16 hboot you compiled flash ok? Are you running it now? I think most of the dev's have had problems getting it to install properly. I don't think you can be S-On and on 2.16 hboot, unless I'm missing something?
I tried to flash the latest version of Twistedkat ROM the other night and it wouldn't flash with any recovery that I tried on 2.16 hboot.
Click to expand...
Click to collapse
Here is an updated CM11 build for hboot 2.16, containing the latest patch for the backlight bug. Its been built from the
original CM11 sources.
https://drive.google.com/file/d/0B0ajti88ZAFzRmV3Mi1aM2lxY0E/edit?usp=sharing
Works great and I haven't had any backlight problems or reboots yet !!!
kc6992 said:
Hello everyone,
After a few month with the maximus rom i wanted to test out the new Cyanogenmod rom 11 on my htc one s.
But when i try flashing it with the recovery, it fails. I heard, that i have to downgrade something in order to get the new Rom installed. What must I do?
I have been reading a lot of topics without finding a concrete answer.
I am S-ON (No superCID) and I have TWRP 2.4.1 and Hboot 1.16
How can I install CM11 successfully ?
Thx :laugh:
Click to expand...
Click to collapse
Mozziliac said:
What Hboot are you on ?
Click to expand...
Click to collapse
Hboot 2.15
New CM11 built 140115 for hboot 2.16 for anyone who is interested
https://drive.google.com/file/d/0B0ajti88ZAFzMDl4TW1Oc2tVQVE/edit?usp=sharing
Can anyone post/link this into the CM11 development section?
Have fun ...
drkxyz said:
New CM11 built 140115 for hboot 2.16 for anyone who is interested
https://drive.google.com/file/d/0B0ajti88ZAFzMDl4TW1Oc2tVQVE/edit?usp=sharing
Can anyone post/link this into the CM11 development section?
Have fun ...
Click to expand...
Click to collapse
Now you can post it yourself.
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
Hi everyone. Long time lurker here. Great help and info is always found on the forums. Im a bit inconsistent in the android department, have done a few flashes on android phones from friends here and there, but its been a while since Im stuck like right now.
Anyways, i have an HTC One S (idk how to identify if its Ville_U or VilleC2) on stock(?) v.4.0.3 from Rogers, yesterday i spent all day trying to;
-Unlock bootloader (htcdev method)
-Root (v4.0.3)
-Install Custom Recovery (been using both TWRP and CWM)
-SuperCID (Succesfully changed from i believe ROGERS01 or something like that to 11111111)
-S-Off (main goal was because i need to flash a 2.15 hboot , CM 10.2 install was giving me an "assert" error about that
- Finally install CM 10.2
Anyways, i was able to successfully do all those things in an exhausting whole day, but after installing CM 10.2, i was getting an HTC logo bootloop.
Yea, i know about flashing boot.img via fastboot after finishing with the CM install, but actually, THAT boot.img was what was causing the bootloop. I tried flashing my original boot.img from my nandroid backup back just to see what happens, and it doesnt actually bootloop, it just hangs on the htc logo.
So i guess thats my /first/ problem : i cant get cyanogenmod 10.2 to boot. Can anyone help me out here? Ive got:
VLE PVT SHOP S-OFF RL
CID-11111111
HBOOT 2.16.0000 ****note on this on next paragraph
RADIO-0.17-31501S.10_2
OPENDSP-v28.1.0.32.0504
eMMc-boot
My second problem is : after this problem, today i got desperate and started doing some stuff, updated hboot from 2.15, tried out a "Bulletproof v2.1" kernel, i dont remember what else. Anyways, now internal sdcard says its 48mb.
How can i fix this? im on twrp recovery right now. I cant flash my nandroid back bcuz nandroid >> 48mb
Thanks to anyone who has the time to help me out. I posted this on the cyanogenmod boards, but havent got a reply back.
Here we go...
Sheleby121 said:
Hi everyone. Long time lurker here. Great help and info is always found on the forums. Im a bit inconsistent in the android department, have done a few flashes on android phones from friends here and there, but its been a while since Im stuck like right now.
Anyways, i have an HTC One S (idk how to identify if its Ville_U or VilleC2) on stock(?) v.4.0.3 from Rogers, yesterday i spent all day trying to;
-Unlock bootloader (htcdev method)
...
My second problem is : after this problem, today i got desperate and started doing some stuff, updated hboot from 2.15, tried out a "Bulletproof v2.1" kernel, i dont remember what else. Anyways, now internal sdcard says its 48mb.
How can i fix this? im on twrp recovery right now. I cant flash my nandroid back bcuz nandroid >> 48mb
Thanks to anyone who has the time to help me out. I posted this on the cyanogenmod boards, but havent got a reply back.
Click to expand...
Click to collapse
First we need to know Ville or ville c2 !!! Can you post a link to the hboot update u used?
No matter if ville or ville c2 --> download this toolkit pls --> http://forum.xda-developers.com/showthread.php?t=2471151
i suppose you have installed htc usb drivers?! If not --> http://forum.xda-developers.com/showthread.php?t=2217396
Boot your One S into bootloader mode (Pressing "Vol down + power") ad connect it to your pc. Open the toolkit from the upper link and perform:
-> Fastboot commands --> "Get MID"
it will show you the model id. PJ401xxxx = ville ///// PJ402xxxx = ville c2
LS.xD said:
First we need to know Ville or ville c2 !!! Can you post a link to the hboot update u used?
No matter if ville or ville c2 --> download this toolkit pls --> http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
I used the hboots from this link http://forum.xda-developers.com/showthread.php?p=39216236#post39216236
Now, i cant downgrade hboot, i get FAILED <remote. Not Allowed> error.
How can i identify what ville it is?
Sheleby121 said:
I used the hboots from this link http://forum.xda-developers.com/showthread.php?p=39216236#post39216236
Now, i cant downgrade hboot, i get FAILED <remote. Not Allowed> error.
How can i identify what ville it is?
Click to expand...
Click to collapse
i just posted it...
"No matter if ville or ville c2 --> download this toolkit pls --> http://forum.xda-developers.com/show....php?t=2471151
i suppose you have installed htc usb drivers?! If not --> http://forum.xda-developers.com/show....php?t=2217396
Boot your One S into bootloader mode (Pressing "Vol down + power") ad connect it to your pc. Open the toolkit from the upper link and perform:
-> Fastboot commands --> "Get MID"
it will show you the model id. PJ401xxxx = ville ///// PJ402xxxx = ville c2"
LS.xD said:
First we need to know Ville or ville c2 !!! Can you post a link to the hboot update u used?
No matter if ville or ville c2 --> download this toolkit pls --> http://forum.xda-developers.com/showthread.php?t=2471151
i suppose you have installed htc usb drivers?! If not --> http://forum.xda-developers.com/showthread.php?t=2217396
Boot your One S into bootloader mode (Pressing "Vol down + power") ad connect it to your pc. Open the toolkit from the upper link and perform:
-> Fastboot commands --> "Get MID"
it will show you the model id. PJ401xxxx = ville ///// PJ402xxxx = ville c2
Click to expand...
Click to collapse
ok, i got:
mid: PJ4011000
finished. total time: -0.000s
So its a Ville. S4 right? Nice.
To achieve S-off, i used Hasoon2000's tool. i remember DLing this : http://d-h.st/sE6 in the process.
(PJ4010000-OneS.zip)
Ok, waiting on you now.
Still S-OFF // Unlocked Bootloader?
Still S-Off // Unlocked-BL?
LS.xD said:
Still S-Off // Unlocked-BL?
Click to expand...
Click to collapse
Yes. Bootloader is telling me its S-Off, Unlocked and Tampered.
Sheleby121 said:
Yes. Bootloader is telling me its S-Off, Unlocked and Tampered.
Click to expand...
Click to collapse
Here you find valid 2.15 Firmware --> http://forum.xda-developers.com/showthread.php?t=2322755
LS.xD said:
Here you find valid 2.15 Firmware --> http://forum.xda-developers.com/showthread.php?t=2322755
Click to expand...
Click to collapse
Was i NOT supposed to flash 2.16? I will follow the instructions of that link, but at the moment, if i try to flash 2.15, i get an error, Failed Not allowed
Sheleby121 said:
Was i NOT supposed to flash 2.16? I will follow the instructions of that link, but at the moment, if i try to flash 2.15, i get an error, Failed Not allowed
Click to expand...
Click to collapse
I'm lookin' for a solution...
Just edit your CID with WinDroid Toolkit to "HTC__001"
and FLASH stock recovery --> http://forum.xda-developers.com/attachment.php?attachmentid=2622663&d=1394422408 also using the WinDroid Toolkit
btw here is the link for downgradin' instructions http://forum.xda-developers.com/showthread.php?t=2591607
Post #2 says --> just flash 2.15 and you're fine
LS.xD said:
I'm lookin' for a solution...
Click to expand...
Click to collapse
Im back at hboot 2.15.
I tried flashing cyanogenmod 10.2 and wasnt stuck at bootlogo.
i got alot of errors in recovery. SDcard said it was 0mb. I mounted usb storage inside TWRP and formatted in windows. Si Then flashed cyanogenmod.
Entered cyanogenmod but getting an error inside cyanogenmod: Encryption Unsuccesful, to resume using your phone, you need to factory reset.
So i went into TWRP and did factory reset.
I am now successfully inside cyanogenmod. Thank you. But how can i fix errors in recovery?
Sheleby121 said:
Im back at hboot 2.15.
I tried flashing cyanogenmod 10.2 and wasnt stuck at bootlogo.
i got alot of errors in recovery. SDcard said it was 0mb. I mounted usb storage inside TWRP and formatted in windows. Si Then flashed cyanogenmod.
Entered cyanogenmod but getting an error inside cyanogenmod: Encryption Unsuccesful, to resume using your phone, you need to factory reset.
So i went into TWRP and did factory reset.
I am now successfully inside cyanogenmod. Thank you. But how can i fix errors in recovery?
Click to expand...
Click to collapse
FLASH the stock recovery from the download link --> boot One S into bootloader --> perform "factory reset + clear storage"
THIS will only work with STOCK recovery!!! When finished you can flash a custom recovery and a new rom. I recommend you some KitKat rom. Simply the best I'll get some links for the needed files for you
BTW it does not hurt pressing the "thanks" button
...
LS.xD said:
FLASH the stock recovery from the download link --> boot One S into bootloader --> perform "factory reset + clear storage"
THIS will only work with STOCK recovery!!! When finished you can flash a custom recovery and a new rom. I recommend you some KitKat rom. Simply the best I'll get some links for the needed files for you
BTW it does not hurt pressing the "thanks" button
...
Click to expand...
Click to collapse
Do i NEED to flash stock recovery? stock recovery was ALREADY on phone, after i did the process. i couldnt get passed the ! Screen.
After that, i flashed TWRP back with fastboot and flashed cyanogenmod and am now on cyanogenmod. Thank you very much for your time and help. I think i will stay on cyanogenmod, but first i want to see if i can use my nandroid backup to downgrade to stock whenever i want.
Im a bit afraid of using other custom roms. On every android phone, i try to install cyanogenmod, it makes me feel safe/stable. I feel the USB file transfer is slower than on stock though.
New rom and so on ...
Use this recovery TWRP 2.7.0.0 --> http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.7.0.0-ville.img
I run TwistedKat Rom 2.4 --> awesome --> http://forum.xda-developers.com/showthread.php?t=2584591
Newest GApps package --> http://goo.im/devs/BaNkS/GApps/4.4.2/3-15_GApps_Minimal_4.4.2_signed.zip
IceCode Kernel March 17th --> https://www.androidfilehost.com/?w=files&flid=11833
And last but important: SuperSU --> http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
---------- Post added at 04:36 AM ---------- Previous post was at 04:34 AM ----------
Sheleby121 said:
Do i NEED to flash stock recovery? stock recovery was ALREADY on phone, after i did the process. i couldnt get passed the ! Screen.
After that, i flashed TWRP back with fastboot and flashed cyanogenmod and am now on cyanogenmod. Thank you very much for your time and help. I think i will stay on cyanogenmod, but first i want to see if i can use my nandroid backup to downgrade to stock whenever i want.
Im a bit afraid of using other custom roms. On every android phone, i try to install cyanogenmod, it makes me feel safe/stable. I feel the USB file transfer is slower than on stock though.
Click to expand...
Click to collapse
So you're fine again BUT TwistedKat is really great May be you'll give it a try some other day
gn8
LS.xD said:
Use this recovery TWRP 2.7.0.0 --> http://techerrata.com/file/twrp2/ville/openrecovery-twrp-2.7.0.0-ville.img
I run TwistedKat Rom 2.4 --> awesome --> http://forum.xda-developers.com/showthread.php?t=2584591
Newest GApps package --> http://goo.im/devs/BaNkS/GApps/4.4.2/3-15_GApps_Minimal_4.4.2_signed.zip
IceCode Kernel March 17th --> https://www.androidfilehost.com/?w=files&flid=11833
And last but important: SuperSU --> http://download.chainfire.eu/382/SuperSU/UPDATE-SuperSU-v1.93.zip
---------- Post added at 04:36 AM ---------- Previous post was at 04:34 AM ----------
So you're fine again BUT TwistedKat is really great May be you'll give it a try some other day
gn8
Click to expand...
Click to collapse
Thanks again, LS.xD. Great help from you, phone is up and running again. i will look into TwistedKat, and consider it.
Now, if someone could answer, WHAT WAS HAPPENNING in this situation, why would cyanogenmod boot? what did i do to fix it. I dont understand. Im grateful and Im happy , but i would like to understand what happenned too.
Sheleby121 said:
Thanks again, LS.xD. Great help from you, phone is up and running again. i will look into TwistedKat, and consider it.
Now, if someone could answer, WHAT WAS HAPPENNING in this situation, why would cyanogenmod boot? what did i do to fix it. I dont understand. Im grateful and Im happy , but i would like to understand what happenned too.
Click to expand...
Click to collapse
Flashing a Kernel can sometimes mess up your SD-Card (But you know now how to fix it )
+
With HBOOT 2.16 CM 10.2 CANT boot properly.
I can't exactly recognize what messed up your phone BUT can give some tip for your next instllation:
Before you perform a change, make sure that you're well informed about what you're going to do
When you're S-OFF you don't have to flash the kernel (boot.img) manually! Just Flash Rom.zip and you're done
Always use recommended (or compatible) recovery version + HBOOT version
NEVER try mixing kernels from a rom with another rom! Only use included kernel, or a compatible custom kernel.
LS.xD said:
Flashing a Kernel can sometimes mess up your SD-Card (But you know now how to fix it )
+
With HBOOT 2.16 CM 10.2 CANT boot properly.
I can't exactly recognize what messed up your phone BUT can give some tip for your next instllation:
Before you perform a change, make sure that you're well informed about what you're going to do
When you're S-OFF you don't have to flash the kernel (boot.img) manually! Just Flash Rom.zip and you're done
Always use recommended (or compatible) recovery version + HBOOT version
NEVER try mixing kernels from a rom with another rom! Only use included kernel, or a compatible custom kernel.
Click to expand...
Click to collapse
on hboot 2.15, i couldnt boot properly either. Now all that`s left is to remove "TAMPERED" from bootloader. Do you know how to do this?
Sheleby121 said:
on hboot 2.15, i couldnt boot properly either. Now all that`s left is to remove "TAMPERED" from bootloader. Do you know how to do this?
Click to expand...
Click to collapse
sure
LS.xD said:
sure
Click to expand...
Click to collapse
Maybe u can help me one last time? i can only find guide for HTC One (M7)
Sheleby121 said:
Maybe u can help me one last time? i can only find guide for HTC One (M7)
Click to expand...
Click to collapse
You'll find a how-to on the first page here --> http://forum.xda-developers.com/showthread.php?t=1777223
You should use this tool to safely change your HBOOT from 2.15.0000 --> 1.14.0004 --> 2.15.0000 --> modded 2.15.0000
HBOOT-flasher --> http://d-h.st/DxE
When finished tampered + warning are gone
Later you also can flash a custom Splash screen (The HTC picture when power on the phone). I use inverted original (black background + white text + green htc logo )
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)