Database Info

[Q] desire s freezes in htc logo

Hi, I introduce myself, I'm Lorenzo from Italy, and I have come to you only after I've have tried to solve a problem with my Desire S.
I unfortunately found too late that the phone that I bought used had been modified with teh Revolutionary patch and when I
loaded an update downloaded from the official website from this moment the phone freezes on the screen HTC and goes no further.
I tried alone to search the web, using the various guides available to try to unlock the phone but with no success.
The current state is as follows:
the phone is S-ON
This is the state:
version: 0.5
version-bootloader:2.00.0002
version.baseband 3822.10.08.04_m
version-cpld: none
version-microp: none
version.main: 2.10.401.8
serialno:XXXXXXXXXXX
imei: XXXXXXXXXXX
product: saga
platform: HBOOT-7230
modelid: PG8810000
cidnum: HTC_E11
battery-status: good
battery-voltage: 4061V
partition-layout: Generic
securityn
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: ebd3df7d
hbootpreupdate: 12
gencheckpt: 0
At this time I replaced Revolutionary with ClockworkMod Recovery v5.8.1.5 as I would like to load ice cream.
I also tried to follow a post that explained how to restore the original software, but I believe that in the current state it is necessary to install
the sdk to work at a lower level.
Thanks in advance for the attention you will give to my post.

I think you forgot to flash the boot. img
Sent from my supercharged :tank:

I've tryed to flash differents boot.img and hboot.img ( original and non ) without success, in fact the action fails verification. Is the device to be switched at S-Off state? Thanks.

mine is S on and after flashing every rom i have flash the boot image and also the first boot taked about 5 to 7 minutes for me.
i thought my phone was bricked but it does take bit time in booting.
So flash with fastboot flash boot boot.img
that should help.

AW: [Q] desire s freezes in htc logo
Is the bootloader locked or unlocked?

When I switch on the devce with volume down pressed the first raw say *** UNLOCKED ***, I think this mean that bootloader is unlocked.

rohitbaba said:
mine is S on and after flashing every rom i have flash the boot image and also the first boot taked about 5 to 7 minutes for me.
i thought my phone was bricked but it does take bit time in booting.
So flash with fastboot flash boot boot.img
that should help.
Click to expand...
Click to collapse
I haven't a boot.img file, I've tryed to flashing boot with a hboot.img from the archive "revent to stock" but it say "remote image error ( bootmagic check fail"
What version of boot.img is suitable for my situation? Thanks.

fabbrim123 said:
I haven't a boot.img file, I've tryed to flashing boot with a hboot.img from the archive "revent to stock" but it say "remote image error ( bootmagic check fail"
What version of boot.img is suitable for my situation? Thanks.
Click to expand...
Click to collapse
what ROM are you on? boot. img is the kernel and hboot. img is for the hboot.do not flash things that you don't even know what it does!!!!! it will brick your phone!!!!
Sent from my supercharged :tank:

hisname said:
what ROM are you on? boot. img is the kernel and hboot. img is for the hboot.do not flash things that you don't even know what it does!!!!! it will brick your phone!!!!
Sent from my supercharged :tank:
Click to expand...
Click to collapse
I've loaded the boot.img from cm-7.2.0-saga, and now I've loaded the same zip from recovery and phone is alive! thanks for all. Bye.

I having this kind of problem when the time OTA 2.3.6 come to Desire S but i have forgot i'm have using Revolution to unlock my phone.
http://forum.xda-developers.com/showthread.php?t=1701137
this link did save my phone but i cant remember the HBoot inside this thread is the one at the end i'm using. That HBOOT can let us downgrade our HBOOT to 0.98 from 6.xx, i'm using that after downgrade the HBOOT and flash with official HBOOT 0.98 then flash HTC Official gingerbread and when ICS release with official RUU i have upgrade it to ICS. good luck

Can't flash JB roms on HTC One S C2

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

Help i killed my Phone:D

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!

[Q] Bricked XL Evita? Only Boots to CWM

Hi
A few days ago I tried to unlock my HTC XL Evita and then flash a custom rom. I'm not entirely sure exactly what I have done.
** TAMPERED **
** UNLOCKED **
Evita PVT SHIP S-On RL
HBOOT-2.18.0000
RADIO-1.34a.32.45.21
OpenDSP-v33.1.0.45.1128
eMMC-boot
Nov 15 2013
At the moment it boots directly into CWM 6.0.4.4
CWM reports that it can not mount basically anything, including the USB Storage. Hence CWM has no usefulness.
From the bootloader, I can run FASTBOOT commands. This is what happens if I try to send a zipped rom
C:\.android>fastboot flash zip KarbonKat-v1.0-14-20140531-1251-evita.zip
sending 'zip' (178295 KB)...
OKAY [ 7.930s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 7.963s
If I try to upgrade CWM to 6.0.4.8 it works, but after a full reboot it reverts to 6.0.4.4
If I 'send' a rom zip via CWM, it appears to install correctly, but when it reboots it just goes back into CWM.
I'm a little lost with what to try next. Would appreciate some help. Do I need to provide any more information?

WiZeR said:
Hi
A few days ago I tried to unlock my HTC XL Evita and then flash a custom rom. I'm not entirely sure exactly what I have done.
** TAMPERED **
** UNLOCKED **
Evita PVT SHIP S-On RL
HBOOT-2.18.0000
RADIO-1.34a.32.45.21
OpenDSP-v33.1.0.45.1128
eMMC-boot
Nov 15 2013
At the moment it boots directly into CWM 6.0.4.4
CWM reports that it can not mount basically anything, including the USB Storage. Hence CWM has no usefulness.
From the bootloader, I can run FASTBOOT commands. This is what happens if I try to send a zipped rom
C:\.android>fastboot flash zip KarbonKat-v1.0-14-20140531-1251-evita.zip
sending 'zip' (178295 KB)...
OKAY [ 7.930s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 7.963s
If I try to upgrade CWM to 6.0.4.8 it works, but after a full reboot it reverts to 6.0.4.4
If I 'send' a rom zip via CWM, it appears to install correctly, but when it reboots it just goes back into CWM.
I'm a little lost with what to try next. Would appreciate some help. Do I need to provide any more information?
Click to expand...
Click to collapse
You can't flash a ROM using fastboot, you flash ROMs through the recovery. If you've performed a factory reset from the bootloader that's why you can't mount your sd card. This is a bug common to this device, it corrupts the sd card, so never perform a factory reset from the bootloader. My advice right now would be to flash TWRP recovery instead of CWM, you'll find TWRP builds for our device here:
http://goo.im/devs/OpenRecovery/evita
Check the How-To Guide For Beginners thread in my signature for detailed instructions on how to do this, and many other basic operations. You should also check the Evita FAQ thread in my signature.
Anyway, once you have TWRP installed you can use the wipe menu to wipe the sd card (if indeed you did corrupt it by performing a factory reset from the bootloader). Use the mount menu to mount the sd card (mount usb storage) and copy a ROM across. Then use proper process to flash a ROM.
Sent from my Evita

ooooh you beautiful ozzie bastard!! I could kiss you on the mouth I've been f*cking about with this for 3 days straight!
Your beginner thread helped. Although I could not get it to install via the SD card/internal storage for some reason. In the end I tried sideload and that did it. Re-flashed boot.img and now I'm booting into KarbonKat
Thanks again. Appreciate the help.
Should I bother with S-Off? Will that give me anything extra above custom roms?

WiZeR said:
ooooh you beautiful ozzie bastard!! I could kiss you on the mouth I've been f*cking about with this for 3 days straight!
Your beginner thread helped. Although I could not get it to install via the SD card/internal storage for some reason. In the end I tried sideload and that did it. Re-flashed boot.img and now I'm booting into KarbonKat
Thanks again. Appreciate the help.
Should I bother with S-Off? Will that give me anything extra above custom roms?
Click to expand...
Click to collapse
Lol, I'll just take the thanks [emoji13]
Having s-off is definitely something you should do, there are some great benefits:
- You'll no longer need to flash the boot.img via fastboot every time you change ROMs or kernels.
- You'll be able to flash radios.
- You can run any Evita RUU.
- There are other benefits I can't think of right now.
Facepalm S-off (requires SuperCID)
Rumrunner S-off (doesn't require SuperCID, but I'm not sure how reliable this method is with an aosp ROM installed)
I find it odd that installing from the sd card didn't work. I'm thinking that's possibly because you don't have the correct recovery version installed (TWRP 2.7.0.8 is required for current aosp ROMs due to an updated fstab layout that's been introduced by CM). It's worth flashing that version, you'll find a thread for it by @pandasa123 in our Android Development Section.
Sent from my Evita

Ahh bollix, I fuxed it!
I needed to unlock the Orange sim on my Evita and realised, after I bought an unlock code, that it would only work on stock roms. I started trying to flash a stock rom and failed. FAILED I TALL YE!!
I tried following this thread to flash a stock rom. However it failed and when I rebooted, I got stuck in a bootloop to the bootloader. Fixed that by re-flashing the recovery. However, now it does not boot the phone anymore (hangs on the boot logo). I can't mount the SDCard. So last resort, I tried sideloading the stock rom. This is what happened:
C:\.android>adb sideload OTA_EVITA_UL_JB_45_S_Orange_UK_3.17.zip
* failed to write data 'protocol fault (no status)' *62%
Click to expand...
Click to collapse
Here's where I'm at.
C:\.android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.18.0000
(bootloader) version-baseband: 1.34a.32.45.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8311000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4171mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c20bff6f
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.069s
Click to expand...
Click to collapse
** TAMPERED **
** UNLOCKED **
Evita PVT SHIP S-On RL
HBOOT-2.18.0000
RADIO-1.34a.32.45.21
OpenDSP-v33.1.0.45.1128
eMMC-boot
Nov 15 2013
Click to expand...
Click to collapse
I'm befuzzled

What recovery version do you have installed? And exactly which ROM did you attempt to install?
Sent from my Evita

Hey
So I was playing with it into the early hours and managed to get some progress. Was using TWRP 2.7.0.8, I installed an older version of CMR (6.0.4.8) and was able to properly 'wipe'/format the SDCard partition. After this, I could mount the SDCard and transfer ROMs from Windows. The first ROMs I tried where the stock Orange Roms from this thread. But I got a failed message on both. I then tried the last ROM I had working, which was KarbonKat-v1.0-14-20140531 - That flashed fine and booted. So just for kicks I thought I'd try the Slim-Evita-4.4.4.build.6-Unofficial - That flashed fine, but it buggy as hell.
So I can go back to KarbonKat and be up and running, but it does not solve my problem of needing to unlock it to use another simcard.
What should I do next?

WiZeR said:
Hey
So I was playing with it into the early hours and managed to get some progress. Was using TWRP 2.7.0.8, I installed an older version of CMR (6.0.4.8) and was able to properly 'wipe'/format the SDCard partition. After this, I could mount the SDCard and transfer ROMs from Windows. The first ROMs I tried where the stock Orange Roms from this thread. But I got a failed message on both. I then tried the last ROM I had working, which was KarbonKat-v1.0-14-20140531 - That flashed fine and booted. So just for kicks I thought I'd try the Slim-Evita-4.4.4.build.6-Unofficial - That flashed fine, but it buggy as hell.
So I can go back to KarbonKat and be up and running, but it does not solve my problem of needing to unlock it to use another simcard.
What should I do next?
Click to expand...
Click to collapse
Those Orange files you found aren't ROMs, they're OTA files, they're not flashable via recovery. Nothing from that thread you linked to is flashable via recovery, they're all RUU's and OTA's.
KarbonKat is a pretty good ROM and you should have a pretty good experience on that one. You'll need to flash a Sense ROM in order to use your SIM unlock code, you'll find Sense ROMs in the Android Development Section.
Sent from my Evita

timmaaa said:
Those Orange files you found aren't ROMs, they're OTA files, they're not flashable via recovery. Nothing from that thread you linked to is flashable via recovery, they're all RUU's and OTA's.
KarbonKat is a pretty good ROM
Click to expand...
Click to collapse
Ok, thanks. I'm downloading 'CleanROM' and will try that.
I had a pretty annoying issue with KarbonKat, in that it kept locking up and rebooting. Wasn't running any major apps or overclocking it. It would reboot just sitting on the side doing nothing. Often would lockup when I pressed the power button to wake it up. Would that be a hardware fault?

Further testing on different ROMs will tell you whether you have a hardware problem or not.
Sent from my Evita

I had a similar issue with aosp roms. Relieved it by turning off MP-Decision with Trickster MOD (should be possible with other kernel tuners.) I'd try flashing other roms first to be sure it isnt rom/flash related.

Thanks
So I finally got CleanMod on there and it's now fully booted and the simcard is unlocked.
If I now flash an AOSP KitKat ROM, will I loose the sim unlock? Other than KarbonKat, are there any other 4.4 roms you would recomend?

WiZeR said:
Thanks
So I finally got CleanMod on there and it's now fully booted and the simcard is unlocked.
If I now flash an AOSP KitKat ROM, will I loose the sim unlock? Other than KarbonKat, are there any other 4.4 roms you would recomend?
Click to expand...
Click to collapse
You'll never lose the SIM unlock, no matter how many ROMs you flash. Asking which ROM is best/most stable/fastest/prettiest, or asking for a suggestion isn't allowed so I can't answer that, here's why. To say one ROM is better is to infer that the others are inferior in some way. This is disrespectful to the devs who spend their spare time bringing us these awesome ROMs free of charge. Each user has different tastes anyway, the best way to see which ROM suits you is to flash a few and find out for yourself. We have plenty to choose from.
Sent from my Evita

Understood, thanks

Problem with Custom Roms

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