My device is currently in a rebooting loop, and every time I try and Install the latest nightly for my HTC One A9 (GSM - US) I get the error(s):
Found blacklisted SBL1 Version, update your firmware
assert failed: hiae.verify_sbl1(" 0.0.020.1.50") == "1
Updater process ended with ERROR: 7
I tried deleting some code in the META-INF/com/google/android/updater.script file that checked for "assert" and I got the CM ROM to install, but only to find out that my phone is in a constant reboot loop.
EXTRA: when I run "fastboot getvar all" I get the message:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeul
(bootloader) version: 1.0
(bootloader) imei: ********
(bootloader) version-main: 1.27.502.5
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ912000
(bootloader) cid: CWS__001
ALSO:
AT&T (Cingular)
modelid: 2PQ912000
cidnum: CWS__001
Have you tried listening to the error updating your firmware?
You are running 1.27 you need 1.57.X
You need to use sunshine and s-off then use the thread to convert to HTC one a9 USA unlocked. Use firmware package 1.57.x
kamredos said:
My device is currently in a rebooting loop, and every time I try and Install the latest nightly for my HTC One A9 (GSM - US) I get the error(s):
Found blacklisted SBL1 Version, update your firmware
assert failed: hiae.verify_sbl1(" 0.0.020.1.50") == "1
Updater process ended with ERROR: 7
I tried deleting some code in the META-INF/com/google/android/updater.script file that checked for "assert" and I got the CM ROM to install, but only to find out that my phone is in a constant reboot loop.
EXTRA: when I run "fastboot getvar all" I get the message:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeul
(bootloader) version: 1.0
(bootloader) imei: ********
(bootloader) version-main: 1.27.502.5
(bootloader) boot-mode: download
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ912000
(bootloader) cid: CWS__001
ALSO:
AT&T (Cingular)
modelid: 2PQ912000
cidnum: CWS__001
Click to expand...
Click to collapse
You are running firmware 1.27* and 1.5* is required.
Go the A9 RUU thread in this forum, find the 1.5* RUU that corresponds to your device, download it, put it in the SD card, reboot the A9 in download mode and update the firmware. Then you can flash CM.
If there is no 1.5* for your device, then S-off will be necessary to change it.
Ultramanoid said:
You are running firmware 1.27* and 1.5* is required.
Go the A9 RUU thread in this forum, find the 1.5* RUU that corresponds to your device, download it, put it in the SD card, reboot the A9 in download mode and update the firmware. Then you can flash CM.
If there is no 1.5* for your device, then S-off will be necessary to change it.
Click to expand...
Click to collapse
Yes, but in the original post, the model was att (no 1.5.x yet) S-off is required ?
Ultramanoid said:
You are running firmware 1.27* and 1.5* is required.
Go the A9 RUU thread in this forum, find the 1.5* RUU that corresponds to your device, download it, put it in the SD card, reboot the A9 in download mode and update the firmware. Then you can flash CM.
If there is no 1.5* for your device, then S-off will be necessary to change it.
Click to expand...
Click to collapse
Thanks for the reply, I will look into that.
If I get S-off, then what RUU will I download then?
Edit: Nvm, I read The Scam's reply and that answered my question.
The_scam said:
Have you tried listening to the error updating your firmware?
You are running 1.27 you need 1.57.X
You need to use sunshine and s-off then use the thread to convert to HTC one a9 USA unlocked. Use firmware package 1.57.x
Click to expand...
Click to collapse
Do you think a version of CM will ever be available for my firmware version S-on?
kamredos said:
Do you think a version of CM will ever be available for my firmware version S-on?
Click to expand...
Click to collapse
Only if ATT updates firmware to 1.5*, otherwise no. I didn't know if ATT had done it, apparently not.
( I have an unlocked, carrier-independent hiaeuhl, came with 1.10, I updated to 1.56, still S-on. )
CM can't support older firmware because hTC's latest kernel requires 1.5* firmware.
This is one of many problems of getting a carrier-locked device. Like the previous post says, if you get S-off, then you can modify the firmware as you wish, right now that is the only option you have to run CM 14.
The_scam said:
Have you tried listening to the error updating your firmware?
You are running 1.27 you need 1.57.X
You need to use sunshine and s-off then use the thread to convert to HTC one a9 USA unlocked. Use firmware package 1.57.x
Click to expand...
Click to collapse
I have an AT&T HTC One A9. Am I able to update to the 2.18.617.10 unlocked ROM if I follow the steps (sunshine and s-off), or do I need to track down 1.57.x? I'm on 1.27.502.5 now.
chadrebuck said:
I have an AT&T HTC One A9. Am I able to update to the 2.18.617.10 unlocked ROM if I follow the steps (sunshine and s-off), or do I need to track down 1.57.x? I'm on 1.27.502.5 now.
Click to expand...
Click to collapse
Yes.
The_scam said:
Yes.
Click to expand...
Click to collapse
I did use sunshine to do the s-off then set the cid to the unlocked cid of BS_US001. I didn't change the mid as it was already 2PQ912000
I did not have any luck updating direct to 2.x, so I ended up installing an older version of 1.x (2PQ9IMG_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6_signed.zip) and then went through hours of updates (maybe a dozen) via the normal device update process until my device was finally updated to the latest os. I found out that the htc software just kept crashing on my win 10 pc, and on my win 7 pc it still had trouble. I installed the rom update by placing it in the root dir of my sd card and renaming it to 2PQ9IMG.zip, then booting into download mode. Initially, I couldn't update directly to 2.x using this same method either. It was failing with a 12 ru_zip error.
The AT&T latest os had problems dropping wifi for me so it made it unusable for pandora or any streaming service. Now the phone works fine and I've found no other issues yet. I was initially planning to install lineage os but I'll just keep on the stock htc software for now since android 7.0 is working good on there. Why would AT&T not continue with the updates HTC makes available? The phone is worthless with the AT&T version of software. I'm surprised to see a decent resale value on AT&T HTC One A9. I was hoping to find them for $20 so I could get another one but I don't want to pay $100.
chadrebuck said:
I did use sunshine to do the s-off then set the cid to the unlocked cid of BS_US001. I didn't change the mid as it was already 2PQ912000
I did not have any luck updating direct to 2.x, so I ended up installing an older version of 1.x (2PQ9IMG_HIA_AERO_UL_M60_SENSE7GP_ATT_NA_Gen_Unlock_1.12.617.6_signed.zip) and then went through hours of updates (maybe a dozen) via the normal device update process until my device was finally updated to the latest os. I found out that the htc software just kept crashing on my win 10 pc, and on my win 7 pc it still had trouble. I installed the rom update by placing it in the root dir of my sd card and renaming it to 2PQ9IMG.zip, then booting into download mode. Initially, I couldn't update directly to 2.x using this same method either. It was failing with a 12 ru_zip error.
The AT&T latest os had problems dropping wifi for me so it made it unusable for pandora or any streaming service. Now the phone works fine and I've found no other issues yet. I was initially planning to install lineage os but I'll just keep on the stock htc software for now since android 7.0 is working good on there. Why would AT&T not continue with the updates HTC makes available? The phone is worthless with the AT&T version of software. I'm surprised to see a decent resale value on AT&T HTC One A9. I was hoping to find them for $20 so I could get another one but I don't want to pay $100.
Click to expand...
Click to collapse
I don't have this device anymore, so pardon me if I am confused, but when I had the ATT version, I don't see any reason to downgrade the firmware to 1.27?? If your looking to install stock and get updates, most users have had success by flashing 1.57 firmware, then 1.57 rom. The signing key in 1.57 is different than 1.27, so you have to extract 1.57 firmware from the 1.57 ruu and flash it, or update to 1.57 using a 1.27 ota.
The_scam said:
I don't have this device anymore, so pardon me if I am confused, but when I had the ATT version, I don't see any reason to downgrade the firmware to 1.27?? If your looking to install stock and get updates, most users have had success by flashing 1.57 firmware, then 1.57 rom. The signing key in 1.57 is different than 1.27, so you have to extract 1.57 firmware from the 1.57 ruu and flash it, or update to 1.57 using a 1.27 ota.
Click to expand...
Click to collapse
My phone had 1.27 and I tried to install the 1.57 ruu without success. Maybe there is a way to get it to work by installing 1.57 firmware first then the 1.57 ruu but I'm new at this so I went with what I thought should work. For the unlocked version I could not find a 1.27 ruu, so I went with 1.12. Then I went through about a dozen ota updates to get to the latest release.
chadrebuck said:
My phone had 1.27 and I tried to install the 1.57 ruu without success. Maybe there is a way to get it to work by installing 1.57 firmware first then the 1.57 ruu but I'm new at this so I went with what I thought should work. For the unlocked version I could not find a 1.27 ruu, so I went with 1.12. Then I went through about a dozen ota updates to get to the latest release.
Click to expand...
Click to collapse
Ok yes, so what you need to do is install the unlocked version 1.27 without rooting it, then ota to 1.57 nougat. You could flash 1.57 firmware first, although I don't remember how to extract it properly. If you want to try, here's a quote from the ruu thread that might be helpful. I believe you can flash the firmware using "fastboot oem flash firmware "blah blah.zip/img I forget"
alray said:
If you can use adb/fastboot you can use the decrypt tool, its not harder.
https://forum.xda-developers.com/ch...niversal-htc-ruu-rom-decryption-t3382928/amp/
Take the time to read the first few posts, there are instructions with examples.
Click to expand...
Click to collapse
Now Lineage OS support hotspot so don't need to try the old roms with old firmware 1.x or 1.5x, install the latest firmware and update to Lineage OS
Related
First of, a bunch of thanks to you for helping me get from a complete and utter noob to a just complete noob. Managed to root, install roms and get out of a LOT of soft bricks (i just don't give up!) with your awesome help, all by searching older posts. However, this time i find myself in a pickle.
I own an HTC One S C2 with Hboot 2.0.9, had stock ICS when i bought it with no option to update to JB (which is why i rooted it in the first place). Something about this particular version of the phone not being updated by HTC global, which i found out about after i bought it, duh. Anyway. I've tried installing JB roms from this thread http://forum.xda-developers.com/showthread.php?t=2239265 with no luck. Phone just keeps getting into HTC logo screen loops. Right now i am on backtobasics v3 rom. Here's how i tried installing them JB roms and also the rom i am using right now (using TWRP 2.4.1 because newest version wouldn't work with backtobasics rom):
(note: some roms had sliiiightly different directions, i just followed each and every one's description closely)
1) Download Rom.zip
2) Extract boot.img from Rom.zip to fastboot folder
3) Enter Recovery
4) Mount SD card
5) Copy Rom.zip to SD card
6) Unmount
7) Wipe data, system, cache, dalvik cache and factory reset
8) Install Rom.zip
9) Reboot Bootloader
10) Go to fastboot USB mode
11) dem commands: fastboot flash boot boot.img then fastboot erase cache then fastboot reboot
12) BOOM! HTC LOGO LOOPS!
I've also tried installing a RUU but i couldn't find any for my CID. Then i thought about getting a SuperCID but, frankly, i scrached that thought the minute i saw the how to do it thread. Here's the phone info
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA335W400602
imei: 352911052281278
product: villec2
platform: HBOOT-8260
modelid: PJ4021000
cidnum: BSTAR301
battery-status: good
battery-voltage: 4170mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
Thank you, in advance, for any advice you may be able to provide me with
Mkay, since i got no answer i went back to searching again! Unfortunately, i still have no asolution to my problem
From what i understand i have to: find a RUU to get from android version 4.0.3 up to JB version. Then i will be able to flash JB roms. But there is no RUU for CID BSTAR301.
I did find a thread with nandroid backup for a BSTAR301 which updates the version without a RUU but it was for HTC One X, i guess i shouldn't use that at all.
I am thinking about doing a SuperCID to install a RUU, then get back to my actual CID and flash a custom JB rom..
Would appreciate any advice
Tateh said:
Mkay, since i got no answer i went back to searching again! Unfortunately, i still have no asolution to my problem
From what i understand i have to: find a RUU to get from android version 4.0.3 up to JB version. Then i will be able to flash JB roms. But there is no RUU for CID BSTAR301.
I did find a thread with nandroid backup for a BSTAR301 which updates the version without a RUU but it was for HTC One X, i guess i shouldn't use that at all.
I am thinking about doing a SuperCID to install a RUU, then get back to my actual CID and flash a custom JB rom..
Would appreciate any advice
Click to expand...
Click to collapse
Yes, in your case S-OFF, Changing CID to something which has a JB RUU would do the trick. I think SuperCID is not necessary.
Sent from my Nexus 7 using Tapatalk HD
heakit Purpose
khan.orak said:
Yes, in your case S-OFF, Changing CID to something which has a JB RUU would do the trick. I think SuperCID is not necessary.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
THANK you! Currently trying to S-OFF it!
Tateh said:
THANK you! Currently trying to S-OFF it!
Click to expand...
Click to collapse
did you get S-OFF?
Not yet.. So exhausted. I tried the moonshine method but, just like trhe instructions state, i should have JB and be on stock for it to work properly, which is not possible since my phone has a BSTAR301 CID and is stuck on 4.0.3 with no stock roms available.
From what i've read, my only hope of S-OFF is to wait for the fellas working on Revolutionary method for S-OFF to release the correct version for this phone. I just hope it's soon and I thank them for their efforts, i'm so disappointed at this phone
Tateh said:
Not yet.. So exhausted. I tried the moonshine method but, just like trhe instructions state, i should have JB and be on stock for it to work properly, which is not possible since my phone has a BSTAR301 CID and is stuck on 4.0.3 with no stock roms available.
From what i've read, my only hope of S-OFF is to wait for the fellas working on Revolutionary method for S-OFF to release the correct version for this phone. I just hope it's soon and I thank them for their efforts, i'm so disappointed at this phone
Click to expand...
Click to collapse
same here. I just wrote to them asking for that
S-OFF done
I did S-OFF already. Now i need to know what CID put in my phone?? and which RUU install on it??
My MID is: PJ4021000
so i don't know if the Europe RUU's work in my phone. Maybe the radio have problem or no?? because the RUU say MID version: PJ4020000. Someone knows about this??
I have heard that JB update for BSTAR is now available.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
I have heard that JB update for BSTAR is now available.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah it's done. But I would change CID not have to wait for another update Brightstar in so long.
gustavoegg said:
Yeah it's done. But I would change CID not have to wait for another update Brightstar in so long.
Click to expand...
Click to collapse
Be sure to match MID or you'll end up having problems with future updates.
Sent from my HTC One S using Tapatalk 4 Beta
Episcopal yupdfir
khan.orak said:
Be sure to match MID or you'll end up having problems with future updates.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Where i can find a RUU for Model ID: PJ4021000?? Because i need update for OTA after install the RUU
gustavoegg said:
Where i can find a RUU for Model ID: PJ4021000?? Because i need update for OTA after install the RUU
Click to expand...
Click to collapse
You have to manually check the ANDROID-INFO.TXT to match CID + MID
Sent from my HTC One S using Tapatalk 4 Beta
Tateh said:
First of, a bunch of thanks to you for helping me get from a complete and utter noob to a just complete noob. Managed to root, install roms and get out of a LOT of soft bricks (i just don't give up!) with your awesome help, all by searching older posts. However, this time i find myself in a pickle.
I own an HTC One S C2 with Hboot 2.0.9, had stock ICS when i bought it with no option to update to JB (which is why i rooted it in the first place). Something about this particular version of the phone not being updated by HTC global, which i found out about after i bought it, duh. Anyway. I've tried installing JB roms from this thread http://forum.xda-developers.com/showthread.php?t=2239265 with no luck. Phone just keeps getting into HTC logo screen loops. Right now i am on backtobasics v3 rom. Here's how i tried installing them JB roms and also the rom i am using right now (using TWRP 2.4.1 because newest version wouldn't work with backtobasics rom):
(note: some roms had sliiiightly different directions, i just followed each and every one's description closely)
1) Download Rom.zip
2) Extract boot.img from Rom.zip to fastboot folder
3) Enter Recovery
4) Mount SD card
5) Copy Rom.zip to SD card
6) Unmount
7) Wipe data, system, cache, dalvik cache and factory reset
8) Install Rom.zip
9) Reboot Bootloader
10) Go to fastboot USB mode
11) dem commands: fastboot flash boot boot.img then fastboot erase cache then fastboot reboot
12) BOOM! HTC LOGO LOOPS!
I've also tried installing a RUU but i couldn't find any for my CID. Then i thought about getting a SuperCID but, frankly, i scrached that thought the minute i saw the how to do it thread. Here's the phone info
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA335W400602
imei: 352911052281278
product: villec2
platform: HBOOT-8260
modelid: PJ4021000
cidnum: BSTAR301
battery-status: good
battery-voltage: 4170mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
Thank you, in advance, for any advice you may be able to provide me with
Click to expand...
Click to collapse
Hi, I have same problem with you. Have you got any solution?
Unfortunately not yet, I switched back to my old xperia ray while i wait for the revolutionary team to release a version for HTC One S
I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.
Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita
I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33
Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita
Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off
:thumbup:
Sent from my Evita
Btw.... If I helped you, please press the thanks button.
Sent from my Evita
Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app
Will this RUU work if I have a locked bootloader and s-on?
Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita
guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?
Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita
3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.
Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?
I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: *************
imei: **************
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s
Jojo1992 said:
I was on Maximus HD 10.0
Then i tried another rom. but i don't like, so i downloaded 10.2 latest nightly but it on my internal storage-->full wipe-->and then i can't install cm10.2 then i want to but another rom on my internal storage but i can't put anything on the phone without an running rom...
then i changed my recovery to CWM 6. cause i knower there was an option to mount usb storage, but it don't work nothings happened when i click on it. Pleas help me i can do nothing
Some more Infos:C:\test>fastboot getvar all
version: 0.5
version-bootloader: 2.16.0000
version-baseband: 1.20.50.05.16
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-OFF
serialno: SH26RW404047
imei: 359901049107937
product: vle
platform: HBOOT-8960
modelid: PJ4010000
cidnum: 11111111
battery-status: good
battery-voltage: 4128mV
partition-layout: Generic
security: off
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-4958290506
hbootpreupdate: 11
gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.
Jojo1992 said:
I hope this Infos can help to solve my Problem, i have access via Fastboot!
The best would be if i can go back to stock.
Click to expand...
Click to collapse
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7
tivofool said:
You need the old firmware like you had before you updated to Maximus.
Run a RUU.exe and clear storage/factory reset in bootloader when you have the stock recovery back on.
From your other thread I posted more details
http://forum.xda-developers.com/showpost.php?p=47586067&postcount=7
Click to expand...
Click to collapse
i downloaded an RUU:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
then i make this:
fastboot devices
fastboot oem lock
then start RUU, but error no connection to device but in cmd i get a connection
I have a CID 111111 is that the Problem?
Jojo1992 said:
I have a CID 111111 is that the Problem?
Click to expand...
Click to collapse
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.
tivofool said:
I've never changed my CID, no need to. So I'm not an expert.
But from what I have read here:
"You can use any ruu while s-OFF, just simply plug phone to computer and run ruu. No need to relock bootloader.
For the supercid, it is recommended to change it back to original with fastboot command.
Fastboot oem write cid xxxxxxxx.
There has been a few bricks takin Jb ota while still supercid. "
So, not a problem, unless you install a OTA (over the air) update while SuperCid.
Here's a good guide from another forum
http://androidforums.com/one-s-all-things-root/691874-guide-how-run-ruu-your-htc-one-s.html
Glancing at that, I noticed it recommends running the RUU on the PC as administrator, maybe it's something simple like that.
Click to expand...
Click to collapse
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?
Jojo1992 said:
I changed my CID back to HTC__102
and tried zwo different RUU.exe one ICS on JB but both have an error...
i relocked my boot loader how can i unlock again?
Click to expand...
Click to collapse
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151
tivofool said:
When trying the RUU did you go to bootloader (fastboot USB)?
To Unlock
Locate your Unlock_code.bin on your pc, probably saved it somewhere or it is still in your fastboot folder.
Type this into your command prompt window fastboot flash unlocktoken Unlock_code.bin
or go through the process of getting a new one http://forum.xda-developers.com/showthread.php?t=1583427
Nice tool (Windroid)
http://forum.xda-developers.com/showthread.php?t=2471151
Click to expand...
Click to collapse
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again
Jojo1992 said:
Yes I was in fast boot USB
I will try it one time again and when it don't work then unlock again
Click to expand...
Click to collapse
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.
tivofool said:
Oh yeah, I've also read from someone that they got error 155 then they flashed stock recovery and relocked bootloader and then RUU proceeded to work.
Click to expand...
Click to collapse
I unlocked and now i could flash:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5
Jojo1992 said:
I unlocked and now i could flash:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
that worked for me.
So which is the latest CM what i could install now?
Hboot: 1.14.0002
UNLOCKED
S-OFF
Running:
Android 4.0.4 HTC Sense4.1 Softwarenumber:2.31.401.5
Click to expand...
Click to collapse
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755
tivofool said:
Glad you were able to get the RUU working. But right now you won't be able to flash many ROMs with that low of a Hboot. You will need to update the firmware.
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
Or...this firmware update thread
http://forum.xda-developers.com/showthread.php?t=2322755
Click to expand...
Click to collapse
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???
Jojo1992 said:
where can i find stock recovery?
flash it like this or?: fastboot flash recovery recover.img
and relock bootloader with: fastboot oem lock ???
Click to expand...
Click to collapse
There is a stock recovery here
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/
The SECOND download is the stock one
Unless you change the name of the recovery the command will probably look more like this:
fastboot flash recovery ville_recovery_signed.img
And yes
fastboot oem lock
after you have flashed the stock recovery of course
tivofool said:
Since you put your CID back, you would have to put back stock recovery and relock bootloader. Then you could go through settings and do the OTA to update to 2.15 hboot.
[/url]
Click to expand...
Click to collapse
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5
tominozh said:
Or he could just change cid to HTC__001 and flash jb ruu. (The European version)
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
That don't work
I tried:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?
Jojo1992 said:
That don't work
I tried:
RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4
I will try it over ota now --> my Handy ist loading the update 4.1.1 i will report as soon as it is ready
Ok edit:
Hboot 2.15.0000
Unlocked
can i now flash CM10.2?
O.T.: Is CM10.2 running stable?
Click to expand...
Click to collapse
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895
tivofool said:
Eh.. It is stable besides for some bootlooping. Like you start it up and it bootloops a few times before finally loading. I like the Avatar Rom which is CM 10.2 based, and noticed a little bootlooping. But it wasn't terrible, just something that happened a few times.
So if that doesn't bother you, go for it. Other than that you would need to stick with sense based roms for stability.
Gosh, so many to choose from you will have to try some out.
http://forum.xda-developers.com/showthread.php?t=2243895
Click to expand...
Click to collapse
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan
Jojo1992 said:
Is the Avatar Rom really 10.2 based? cause on their page they tell 10.1 based or?
but i can install now any rom or?
with the flashed rue which i have actually i don't get mobile internet working. just wlan
Click to expand...
Click to collapse
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)
tivofool said:
Ya, guess you are right, 10.1
You can flash any as long as they don't require hboot 2.16 (which they state in the first page OP)
Click to expand...
Click to collapse
ok thank you very much for the help!
ok here's the thing..
i lost my backup for the stock rom which came with my HTC One XL,and i've been facing alot of issues with custom roms ,the major thing was the capacitive buttons stopped working without a reason !
now being S-ON,unable to go back to stock except with RUU's with the matching CID,,ok so i tried searching for the right RUU with matching CID which is J15 and the only one i found on androidRUU website didnt work for me as its a different hboot version (not sure if that's why it refused or not but thats what i understood from reading in the forums)
so i spent hours and hours trying to find the correct RUU with matching CID and hboot version but was invain,,
another option searching for NANDROID,,still didnt find any matching results
tried getting SuperCID to make it easier to find a matching RUU,,but i found in order to get SuperCID i need to be S-OFF,,and in order to get S-OFF i need to get SuperCID first...its a bit frustrating i know
also another weird thing that when i tried to relock the bootloader,it says "FAILED (status read failed (Too many links))"
so any help on how to either :
1.Full stock restore either with a matching RUU or NANDROID
2.Getting a full stock rom with the latest firmware update so that hopefully the capacitive buttons work again..
would be really appreciated
and here are my info :
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3848mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0
lordofegypt said:
ok here's the thing..
i lost my backup for the stock rom which came with my HTC One XL,and i've been facing alot of issues with custom roms ,the major thing was the capacitive buttons stopped working without a reason !
now being S-ON,unable to go back to stock except with RUU's with the matching CID,,ok so i tried searching for the right RUU with matching CID which is J15 and the only one i found on androidRUU website didnt work for me as its a different hboot version (not sure if that's why it refused or not but thats what i understood from reading in the forums)
so i spent hours and hours trying to find the correct RUU with matching CID and hboot version but was invain,,
another option searching for NANDROID,,still didnt find any matching results
tried getting SuperCID to make it easier to find a matching RUU,,but i found in order to get SuperCID i need to be S-OFF,,and in order to get S-OFF i need to get SuperCID first...its a bit frustrating i know
also another weird thing that when i tried to relock the bootloader,it says "FAILED (status read failed (Too many links))"
so any help on how to either :
1.Full stock restore either with a matching RUU or NANDROID
2.Getting a full stock rom with the latest firmware update so that hopefully the capacitive buttons work again..
would be really appreciated
and here are my info :
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT2CNW302531
imei: 354370050060697
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3848mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Long story short, there is no RUU for your CID. But there is a thread in our General Section that contains stock backups for your device.
I'll also just clear up some confusion you seem to have about s-off and SuperCID. There are two s-off methods for the Evita, Facepalm and Rumrunner. Facepalm requires SuperCID to work, Rumrunner does not require SuperCID to work. If you don't have SuperCID and want it you can use the Rumrunner s-off method to get s-off and then change your CID using a fastboot command.
Either way, don't use any of the RUUs that match other CIDs, they'll most likely brick your phone. Just find the thread in General and you'll be able to download a nandroid backup.
Sent from my Evita
timmaaa said:
Long story short, there is no RUU for your CID. But there is a thread in our General Section that contains stock backups for your device.
I'll also just clear up some confusion you seem to have about s-off and SuperCID. There are two s-off methods for the Evita, Facepalm and Rumrunner. Facepalm requires SuperCID to work, Rumrunner does not require SuperCID to work. If you don't have SuperCID and want it you can use the Rumrunner s-off method to get s-off and then change your CID using a fastboot command.
Either way, don't use any of the RUUs that match other CIDs, they'll most likely brick your phone. Just find the thread in General and you'll be able to download a nandroid backup.
Sent from my Evita
Click to expand...
Click to collapse
and concerning that backup you're talking about,,does it have to be matching my CID or any of my details ? or just any backup is fine ?
The backup I'm talking about is specifically for the middle eastern variant of this phone.
Sent from my Evita
timmaaa said:
The backup I'm talking about is specifically for the middle eastern variant of this phone.
Sent from my Evita
Click to expand...
Click to collapse
thx for the help,,ok so currently i found the needed NANDROID,,made the restore and am back to stock android 4.1.1 with relocked bootloader and stock recovery flashed,,i tried searching for software updates and it says no updates found when my neighbor got the same device and he recieved an update for 4.2.2 ??
however am not quite sure if the stock recovery flashed successfully or not ,,in the fastboot it said that the flashing was successful but when i tried to access the recovery from the boot it just went blank screen ,,is that ok and am not supposed to enter the stock recovery but then why it doesnt make the update ? or there's something wrong with the recovery i got ?
You should be able to enter the stock recovery, I believe there's something wrong with the recovery you flashed.
Sent from my Evita
ngiyal 457
timmaaa said:
You should be able to enter the stock recovery, I believe there's something wrong with the recovery you flashed.
Sent from my Evita
Click to expand...
Click to collapse
ok i found the recovery ,flashed it and able to access the recovery nw,,but in order to do so i had to unlock the bootloader again other wise it will just keep on booting into the bootmode which is kinda wierd...
anyway you got any ideas why am unable to receive the OTA ?
I'm not sure why you're not receiving it, sorry. If you can find the OTA you can install it manually.
Sent from my Evita
timmaaa said:
I'm not sure why you're not receiving it, sorry. If you can find the OTA you can install it manually.
Sent from my Evita
Click to expand...
Click to collapse
surprisingly i just got an update for the "people" app through searching for software updates (not through playstore)...does that mean that my OTA is working fine and its just a delay or something like that for the full software,,or this app update has nothing to do with the OTA's ?
The people app itself is separate from the OTA.
Sent from my Evita
j15 version of evite doesn't recieve 4.2.2 update yet
i have the same of your phone and i flashed stock ROM of telstra and it works fine for me
madoooz said:
j15 version of evite doesn't recieve 4.2.2 update yet
i have the same of your phone and i flashed stock ROM of telstra and it works fine for me
Click to expand...
Click to collapse
Could I ask where you got that stock Rom and for a link as well. With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement. So this would be greatly appreciated.
Thank You
jnthnbgg said:
Could I ask where you got that stock Rom and for a link as well. With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement. So this would be greatly appreciated.
Thank You
Click to expand...
Click to collapse
Just have a look in our Android Development section, you'll find it in there, along with some great custom ROMs you might want to try.
Sent from my Evita
jnthnbgg said:
Could I ask where you got that stock Rom and for a link as well.
Click to expand...
Click to collapse
All the links you will likely ever need are here:
http://forum.xda-developers.com/showthread.php?t=1671237
jnthnbgg said:
With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement.
Click to expand...
Click to collapse
Did you factory reset in hboot and corrupt the SD? Because a factory reset in recovery or in the OS should not wipe the SD (including nandroids).
redpoint73 said:
All the links you will likely ever need are here:
http://forum.xda-developers.com/showthread.php?t=1671237
Did you factory reset in hboot and corrupt the SD? Because a factory reset in recovery or in the OS should not wipe the SD (including nandroids).
Click to expand...
Click to collapse
Yes it did it in Hboot of all things while I had Clean Rom installed which was giving me grief (blackscreen after HTC load screen)
jnthnbgg said:
Yes it did it in Hboot of all things while I had Clean Rom installed which was giving me grief (blackscreen after HTC load screen)
Click to expand...
Click to collapse
What are your bootloader details? I might be able to diagnose why you were having problems before the factory reset.
Sent from my Evita
timmaaa said:
What are your bootloader details? I might be able to diagnose why you were having problems before the factory reset.
Sent from my Evita
Click to expand...
Click to collapse
Well I know it is the S-On as I saw even though I was doing all according to the instructions I could find. I had Unlock, SU CID, just could not get that S-OFF. I tried it manually, via the toolkits people have out there, using a 2.0 USB cable. But without the S-OFF I did not get the firmware installed so that was my source of headache with that I just had a bit of lag in the bootloader screen and i click one to many times past recovery and viola up the crick without a canoe lol
Once you have a ROM installed, forget the toolkits and get s-off manually, it's really easy. There are two methods you can try:
Facepalm S-off
Rumrunner S-off
Sent from my Evita
timmaaa said:
Once you have a ROM installed, forget the toolkits and get s-off manually, it's really easy. There are two methods you can try:
Facepalm S-off
Rumrunner S-off
Sent from my Evita
Click to expand...
Click to collapse
So going the route of Palm as I can not get adb to connect but I can fastboot USB, The first attempt ends with FAILED remote:92 supercid! please flush image again immediately. The second attempt ends in FAILED remote:99 unknow fail
You're gonna need to get adb working, both methods require it. I'm in a good mood so I'm gonna give you the solution to the error 99 problem, but please in future search properly before posting, the solution to that problem has been posted dozens of times in the Facepalm thread.
When you get error 99 after flashing the zip, you need to force a reboot to the bootloader and start the process again and you should get error 92 again.
Why isn't adb working? What ROM are you on? Have you updated your drivers? Do you have usb debugging turned on in Developer Options?
Sent from my Evita
Hi there i tested these ROMS on mine HTC One S Ville S4 (International).
Here the Results:
Maximus 10.0.0 - http://forum.xda-developers.com/showthread.php?t=2445392
I´ve followed all steps but no luck, the phone reach splash screen and all i get is all 3 lights on the bottom and a green on the top illuminated.
LIBERTY ROM - The Sixth Element 4.4.2/4.4.3
Almost the same situation with Maximus Rom but with Black splash screen this time on the 2 versions of this Rom
At the moment i have the ViperOneS 3.2.0 but i would like test other Roms.
Here my specs:
----> Start <----
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.13.0000
(bootloader) version-baseband: 0.16.31501S.17_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: SH24PW******
(bootloader) imei: ***************
(bootloader) product: vle
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ4010000
(bootloader) cidnum: HTC__304
(bootloader) battery-status: good
(bootloader) battery-voltage: 3873mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d92cc658
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
----> End <----
you need a specific hboot to try the rom. i think is 2.15 and you have 1.13.. so..... i think that is the problem.
first of all you'd update all that is possible to lates ver. (hboot, recovery), may be you should try hboot 2.16 and roms for it...
grorg said:
first of all you'd update all that is possible to lates ver. (hboot, recovery), may be you should try hboot 2.16 and roms for it...
Click to expand...
Click to collapse
No luck with RUUs
vic_111 said:
No luck with RUUs
Click to expand...
Click to collapse
You will need to update HBOOT to version 2.15 or 2.16 depending on which rom you want to install. HTC__304 is Europe/Spain so the Europe RUU should be fine for you. Its pretty easy:
Download FIRMWARE HBOOT 2.15
Extract the included recovery and flash it using fastboot:
fastboot flash recovery recovery.img
Relock your bootloader (in case it's actually locked)
fastboot oem lock
Then flash the firmware215.zip:
fastboot oem rebootRUU
fastboot flash zip firmware215.zip
fastboot flash zip firmware215.zip (First time you probably get an error, so just retype the command!!!)
fastboot reboot-bootloader (to get back into bootloader mode)
LS.xD said:
You will need to update HBOOT to version 2.15 or 2.16 depending on which rom you want to install. HTC__304 is Europe/Spain so the Europe RUU should be fine for you. Its pretty easy:
Download FIRMWARE HBOOT 2.15
Extract the included recovery and flash it using fastboot:
fastboot flash recovery recovery.img
Relock your bootloader (in case it's actually locked)
fastboot oem lock
Then flash the firmware215.zip:
fastboot oem rebootRUU
fastboot flash zip firmware215.zip
fastboot flash zip firmware215.zip (First time you probably get an error, so just retype the command!!!)
fastboot reboot-bootloader (to get back into bootloader mode)
Click to expand...
Click to collapse
He's S-On, are you sure it'll work like this? Flashing firmware is not possible unless you're S-Off. He should first try to achieve S-Off via rumrunner or other method (since he's already using Viper or a close-to-stock ROM). Then he might try flashing 2.15/2.16 firmware
Rapier said:
He's S-On, are you sure it'll work like this? Flashing firmware is not possible unless you're S-Off. He should first try to achieve S-Off via rumrunner or other method (since he's already using Viper or a close-to-stock ROM). Then he might try flashing 2.15/2.16 firmware
Click to expand...
Click to collapse
I'm sure. Flashing "SIGNED" zips will totally work with S-ON.
LS.xD said:
I'm sure. Flashing "SIGNED" zips will totally work with S-ON.
Click to expand...
Click to collapse
I will give it a try , hope I don't get a brick
But I have two questions:
1What you mean "locked" I have my boot loader unlocked!
When I finish the flash process I can unlock again?
Sent from my HTC One S
vic_111 said:
I will give it a try , hope I don't get a brick
But I have two questions:
1What you mean "locked" I have my boot loader unlocked!
When I finish the flash process I can unlock again?
Sent from my HTC One S
Click to expand...
Click to collapse
You can unlock it at any time, but you will have to lock it before upgrade the firmware.
LS.xD said:
You can unlock it at any time, but you will have to lock it before upgrade the firmware.
Click to expand...
Click to collapse
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!
vic_111 said:
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Click to expand...
Click to collapse
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!
vic_111 said:
No luck, upgraded sucessfully but now i have a blank screen blinking
Update: Should i update to 2.16? If yes where i can get it?
Update URGENT: I cant install any rom now help please
Update 2: I tried install 2.16 but unsucessfull
Update 3:Anyone can find a RUU for me , because i cant :crying:
Update 4: Well i am on ViperOneS again , somehow (flashed boot.img before aroma-installer),but i would like test Liberty one you think you can send me hboot 2.16 signed , i tried find but only for s-off
Update 5 [LAST ONE]: Finally i get it Liberty Rom works 100% thanks for all the help guys , REALLY!!!
Click to expand...
Click to collapse
I'm glad you finally made it. HBOOT 2.16 works with S-OFF only, thats why I uploaded 2.15. As @Rapier mentioned earlier, you can use rumrunner.us for easily getting S-OFF
Mind you that hboot 2.16 gives you shared internal storage. E.g. all free space is available to all partitions. This may come tot be necessary for you if flashing lollipop roms since the "foot print" of installed aps on lollipop becomes much larger. This has to do with runtime environment... Kitkat runs with Dalvik Cache whereas Lollipop runs with the Android Runtime aka ART.
So, staying on hboot 2.15 give you the old partition layout with approx. 1 GByte(??) free for apps and 7 as internal SD.
While hboot 2.16 serves all your free internal storage to all partitions. This saves you headache of internal space for apps running out.
(Someone may deel to fill in the technical gaps i left in)
Cheers , happy hboot 2.16 user.
Verstuurd vanaf mijn One S met Tapatalk