I believe I may have bricked my Desire S also.
I rooted my Desire S through the official HTC method. (I have since relocked)
I then attempted to flash a custom ROM.
The custom ROM (Reaper 2.2) got stuck in (what I believe to be a boot loop) so I attempted to revert to the backup I made - that failed.
I did manage to get CyanogenMod 7 working but with missing functionality
Now I could not get beyond the white HTC screen (or the Black screen with the circle/number pattern on Reaper)
My desire S originally was on Vodafone (Ireland)
Whem I try to load the error is:
SD Checking
Loading...[PG88DIAG.zip]
No image!
Loading...[PG88DIAG.nbh]
No image or wrong image!
Loding...[PG88IMG.zip]
No image!
Loading...[PG88IMG.nbh]
No image or wrong image!
My phone was on 2.3.5 and Sense 3.0
Other details I obtained:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0002
(bootloader) version-baseband: 3822.10.08.04_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.161.3
(bootloader) serialno: xxxxxxxxxxx
(bootloader) imei:xxxxxxxxxxxxxxx
(bootloader) product: saga
(bootloader) platform: HBOOT-7230
(bootloader) modelid: PG8810000
(bootloader) cidnum: VODAP001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ebd3df7d
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
I have spent hours upon hours trawling through forums, posts and guides but nothing has worked.
I have tried RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.080 5U_38.03.02.11_M_release_177977_signed.exe and got error [170]:device not detected and I have tried from the command line via fastboot....
I really need help here please.
OR is my Desire S totally bricked beyond repair
If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.
eyahl said:
If you unlock with htcdev, you need to extract the boot.img from your desired ROM and flash manually through adb after flashing the ROM. I'm 99% sure this will solve your problem. And you'll have to do this each time you flash a new ROM, or backup.
if you s-off your phone rather than using htcdev, you would not suffer from this procedure.
Don't be afraid, there is no brick
Sent by my fingers to your head.
Click to expand...
Click to collapse
this and bootloader need to be ****unlocked**** in order to boot custom rom, and ***re-locked*** when installing RUU
Thanks for the reply's guys.
I managed to get the RUU working this evening but the phone was still ***unlocked***... I got some error (didn't make note of it)
I will re-read both posts when I am not so tired and try the suggestions
Thanks again
(I will post my results)
Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom
GSR-James said:
Ok, now I think I really have messed it up
I tried to flash RUU to the phone and now I cant get recovery to mount the sd card.
Can anyone suggest which RUU I should be using as the RUU app told me I was using the wrong image
I am totally at my wits end....I cannot even go back to the CyanogenMod rom
Click to expand...
Click to collapse
Did you read what I wrote?? Do what I said or search forum about that if you need more information. It is definitely necessary, you won't succeed without flashing boot.img separately.
Sent by my fingers to your head.
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
Yes, that's what I meant
Sent by my fingers to your head.
GSR-James said:
I am so sorry, I did try to flash the boot.img but it didn't seem to work....
Am I right in my understanding: go to the .zip file >> open in win zip>> extract boot.img to the adb folder >> fastboot flash boot.img?
Click to expand...
Click to collapse
YEs that sounds about right, although the full command is
Code:
fastboot flash boot boot.img
Thank you both for the reply's.
I will try this when I sober up in the morning
Now that I am sober I want to thank eyahl, nenad_l and ben_pyett for your input.
I managed to get the rom working last night (drunk and all as I was )
I am now running a MIUI rom
Baseband version: 20.4801.30.0822U_3822.10.08.04_M
I need to ask a couple more questions if I may?
The interface is not what I am used to and don't particularly like it. It reminds me of the UI I had on my old Galaxy I9000. Is this as a result of my kernel version?
Kernel version: [email protected]#1 Thur Oct 6 14:48:57 BST 2011
My understanding of what I have done by flashing the boot.img is that my kernel is that of the rom from where the boot.img was taken and the MIUI rom sits atop - is this correct?
So if I extract a boot.img from a different rom and then flash I will have a different kernel version and subsequently return my UI to (SENSE) that I'm more familiar to?
Sorry for the n00b questions but I am only learning about this at the moment
Thanks guys
No problem, and your understanding is not really correct, the UI is determined by the ROM not the boot image (which is ultimately the kernel), so to get sense back you need to flash a sense ROM like Endy
Every time you flash a new ROM simply flash the associated boot
You shouldn't flash a boot from one ROM under another, it's not mix and match, well that's not completely true.
Swyped form ym Dersie S unsig XAD Permuim
Thanks Ben.
I will look for the 'Endy' rom you suggested.
Ok, so I dl the zip, extract the boot.img, write it from cmd and then flash the rom like normal?
I find it very frustrating to find roms.....almost every time I select a rom to dl I'm redirected to a bad link or to a referral to another referral etc....
If anyone has a source for roms please post it!
Best source for roms is the development section here at desire s xda. Just look through the threads, you will find good quality and stable roms. Endy=endymion ROM
You can look to the index thread, additionally zac made a torrent thread where you can find torrents for the most used roms
Sent by my fingers to your head.
Thanks eyahl
I have dl Endy and will try it now.
I'll have a look where you suggested
Thanks
You must wipe your device (all partitions except sd) prior to each ROM flash
Swyped form ym Dersie S unsig XAD Permuim
Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again
GSR-James said:
Just want to thank everyone for helping me resolve my issue.
I now have an Endy rom sunning stable for the most part.
Can this thread be marked resolved?
Thanks again
Click to expand...
Click to collapse
You're welcome
Yes, you can mark the thread solved
Sent by my fingers to your head.
Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!
GSR-James said:
Is there a 'button' or a tool that I can use to mark as solved or does it have to be done by a mod...
or can I just do this:
SOLVED!!!
Click to expand...
Click to collapse
Go to your first post, click EDIT, then on the edit panel, click on ADVANCED and then modify the topic of your thread by adding [SOLVED] in front of it.
You're done.
Related
I have my HTC Sensation XE which has originally the 2.3.4 Gingerbread.
I would like to have an assistance on how to do it?
Do I need to flash specific firmwares? Where could I get it? and is it safe to use the backup I made before with that Gingerbread Rom?
Thank you.
I used SUPERCID method.. Therefore I'm not exactly sure whats my CID number and RUU but im pretty sure its either HTC__038 or HTC__044 asia or wwe_asia.
If it helps , I had some Starhub apps, Singtel or whatever, so I assume its more of an HTC__044 CID number?
Thank you.
If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium
stringer7 said:
If you did superCID you don't need to worry about which ruu you use. There is a stock GB ruu link in the s-on section of the sticky guide to everything in the dev forum.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.
ardom said:
Thank you for the response. But im trying to get the OTA also.
That's why I want to be sure about my RUU. and CID ^^, Thank you.
Click to expand...
Click to collapse
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium
stringer7 said:
OK, you can find your original cid by entering "getprop ro.cid" in terminal emulator.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
I had changed my CID when i rooted mine i used supercid method and changed it to 11111111 i forgot my original ru. Im nt sure exactly too if its wwe_asia or asia but im sure its either of the two. I had Starhub app too so i have a premonition that it could be htc__044 or asiawwe singapore version.
Im confused lol. I Want to go back to my stock ruu and cid. Or least the cid so i could restore my backup if possible. Then if ever i ota update. Less prblems could be encountered.
Sent from my HTC Sensation XE with Beats Audio
What are the steps I need to do?
Which to flash? any firmware?
THank you.
This is a prime example of making sure you check for the RUU BEFORE you flash anything new
Do what is said above and it will tell you your original CID. We can then see if we can find the RUU
Good luck. I just updated my xe to ics by simply reading a lot of posts on this site. And simply following all instructions.
At first tho, I mistakenly flashed sensation and not sensation xe. But again, found the correct files here on this site. All sorted and now have beats audio back, now with sense and ics latest.
So many helpful people here, so I hope you too get your fine sorted to the way you want yours. Although curious as to why you wanna go back to gb.
Surely ics is better?
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA
hi
hi guys, do you have any link for official Gingerbread RUU 1.73 with beats audio for sensation XE? i just turn my sensation XE to s-on and flash the RUU but i flashed a wrong ruu.thanks guys.i want to update my sensation XE to ics through system update
Are you S-ON again now? If so, you'll need to S-OFF before you can flash the XE RUU (which you can find here):
https://www.yousendit.com/download/M3BtWmd2YWJ6NE5qQTlVag
Its already 1111111 for my CID. Im planning to go back to stock gb so i can get the ota ics and try it out.
Sent from my HTC Sensation XE with Beats Audio
Yes my phone is s-on again, so how do I flash the ruu?and just s-off? No need to do rooting?thanks
Help ~ Loop boot
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much
soldierforus said:
I was gonna revert to my stock Gingerbread 2.3.4, I was trying to achieve ICS 4.x and Cyanogen mod 9, but I n00bed it up and wound up in a boot loop. I've read several different tutorials and I gathered I need to flash back to Stock GB. Do I just need a link to a Stock GB that fits my CID?
CID = T-MOB010
No Super CID
No RUU
Thanks much
Click to expand...
Click to collapse
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution
ganeshp said:
yes yes stock GB would do ..also ..you have stock ICS for that cid too want that ?
GB RUU for TMOB USA
ICS RUU for TMOB USA (post #1 section #3 has the link to RUU's)
but
care to explain more what happened ?..it probably might be a small solution
small details would do ..
complete details present in the bootscreen (a screenshot would do too)
also
a complete output of the following command (except IMEI and serail number)
fastboot getvar all
then i can give you a perfect solution
Click to expand...
Click to collapse
Sorry to double post, I thought this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later I found a cynaogen tutorial to help with boot loop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So how do the RUU's function exactly? I read the glossary term in wiki, but I don't fully understand the concept. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again
soldierforus said:
Sorry to double post, I though this may be a dead thread since the previous post had a question and no reply in 4 months.
_____________________________________________
The Details:
Boot loop began after I flashed to firmware 3.32 using:
Universal Firmware 3.32 Universal (Non-TMOUS): Since I am on TMO, I gather I should have used the TMOUS flash?
DOWNLOAD: http://d-h.st/afS
MD5: 8f50e9f4f3fab7edcd4013015703f81c
From this tutorial: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154
I later found a cynaogen turoial to help with bootloop and followed these steps:
1) Set to factory reset
2)Cleared Delvick (sp?) Cache
____________________________________________
Current Boot Screen:
Revolutionary
Pyramid PVT SHIP S-OFF RL
HBOOT 1.27.1100
RADIO-11.22.3504.07_M
OpenADSP-v02. 6. 0. 226.00.0131
eMMC-boot
_____________________________________________
Getvar all Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.27.1100
(bootloader) version-baseband: 11.22.3504.07_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.401.3
(bootloader) product: pyramid
(bootloader) platform: HBOOT-8260
(bootloader) modelid: PG5810000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 3816mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 617f0a98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.490s
So How the RUU's function exactly. They will update my ROM through window? I guess I need to be able to kill this boot loop first though.
Thanks again
Click to expand...
Click to collapse
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU
No-Go
ganeshp said:
for RUU ..you need to connect the phone in bootloader to pc ..and then just double click on it ...that will do
one last try for flashing custom rom ..still not worked then go for RUU
btw what recovery you are using ?
if using cwm ...can you switch to 4EXT recovery ?
get the recovery image from the below db link (recovery.img inside the zip)
4EXT DB link
and flash it via fastboot
fastboot flash recovery recovery.img
got to the recovery
4EXT->wipe|format->format all partitions except sdcard
then back to main menu ...and flash the rom (what ever custom rom you want)
then reboot and see..if it still stuck at boot logo
then extract the boot.img from the rom zip file
and flash it manually
fastboot flash boot boot.img
then reboot
still stuck ?
then reflash the firmware (be sure to check the md5 of the firmware you have downloaded)
still stuck?
then RUU
Click to expand...
Click to collapse
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?
soldierforus said:
So it wouldn't let me flash 4ext, it says: "cannot load 'recovery.img'" I didn't unzip it or even leave the zip in the root, I took only the recovery.img and left it in to sd root.
You said to flash the custom ROM, but this is my first attempt, and although I have downloaded CM9, the instructions I have read from other tutorials tell me I have to upgrade first to firmware 3.32, then to firmware 3.33, then I can install CM9, which will give me ICS/4.x Am I correct so far?
I don't even know if the 3.32 flash was a success (Do you?) since now I am in a boot loop. Could it be because I should have used the TMOUS instead of the non-TMOUS universal for 3.32? I picked the non-TMOUS because I didn't realize what TOUS stood for at the time, and the other link said universal (and the android-info had my cid/mid)
Also thanks for the RUU links, but I don't know what good the ICS will do if I don't have it yet. Those RUU's will do what exactly? Update to the latest ROM ? Also, is that for all roms or just 3rd party? Looking at the getvar log I sent you, I gather the 3.32 did work, So I should download the ICS 3.32 RUU link you sent me. That's what I am going to try now
EDIT
________________________________
I re-installed cm9, AND EUREKA!!!!!! My first custom ROM. Many thanks to all who helped! Now which RUU do I use, and how often should I run it?
Click to expand...
Click to collapse
RUU is rom update utility.. It's official htc file
Ruu is complete software for your phone
It wipes everything.. Rom, recovery firmware.. Everything and flashes the corresponding stock One...
So when you run ics ruu.. You will have complete ics stock rom of tmobile US
And the recovery flash you did earlier was wrong..
You need to keep that recovery file in the adb folder (it should be in pc) Then the command will fetch the file.. As you have kept it on top of sdcard.. It can't find it..
Sent from my pyramid.. Through blazing fast sonic waves
Tampered
unlocked
Evita PVT ship s-on RL
Hboot-1.09.0000
radio-0.19as.32.09.09_L
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.09.0000
(bootloader) version-baseband: 0.19as.32.09.09_L
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) serialno: HT246W318545
(bootloader) imei: 359691041******
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4073mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: e964c535
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.064s
I bought this phone from someone and it already had CM10 on it. I want to return it back to stock and I have had no luck at all. I have exhausted every avenue I could think of. There is no backup for the original.
Once I remove root, re-lock it, run RUU it gets stuck at the HTC screen and does nothing. On the computer it says sending.........
As you can see the version-main: is blank, so I do not know the correct version to flash. No idea. Help
Currently running CM10 with Twrp recovery 2.3.1
Throwing info out there....
When i re-lock it it still says **tampered
**Locked
HTC brilliant screen shows underneath in red this is for development purposes.....
Give me ideas I will try it.
Wrong section boss
Sent from my HTC One XL using xda app-developers app
I need a ticket to One X Q&A, Help & Troubleshooting please.
Or close this one I will open over there.
sorry
Join Date: Feb 2010
smh still doing it wrong
CheesyNutz said:
Join Date: Feb 2010
smh still doing it wrong
Click to expand...
Click to collapse
It was an accident jack a**
Maybe edit out your imei number.
WR
Injected from My ViperXL
Did not know this was in development now, I would of thought One X Q&A, Help & Troubleshooting
Threads been lost in shuffle.
WR
Injected from My ViperXL
Palmetto_X said:
I need a ticket to One X Q&A, Help & Troubleshooting please.
Or close this one I will open over there.
sorry
Click to expand...
Click to collapse
The easy way to get it moved is to click on the report button and select thread move, one of the mods will move it to the Q&A section for you. :good:
My radio says??
radio-0.19as.32.09.09_L
This matches with this.........
RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.
My thinking is that I am flashing the wrong RUU. I dont know.
I unlocked it again, flashed the stock recovery.img, relocked it
Now I am going to try the RUU again
RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105
Palmetto_X said:
My thinking is that I am flashing the wrong RUU. I dont know.
Click to expand...
Click to collapse
That is the first thing I thought of (flashing wrong RUU) when I first started reading your post. As long as your PC is recognizing the phone (sounds like it is) and the bootlaoder is locked (you said it was) then RUU failing is almost always becuase of the wrong RUU. You need the right RUU for your carrier version, and it has to be equal to or newer than the firmware and hboot currently on the phone.
Palmetto_X said:
RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.
Click to expand...
Click to collapse
I assume you have the AT&T version. If so, this is absolutely the wrong RUU. Its obviously for the Asian version. You need an AT&T RUU.
Palmetto_X said:
Now I am going to try the RUU again
RUU_Evita_UL_ATT_US_1.44.502.1_Radio_0.15.3201.09_release_249105
Click to expand...
Click to collapse
Where the heck did you get that? 1.44 firmware? You want ATT 1.73 or 1.85 (those match with hboot 1.09).
Try one of the RUU links in my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
That is the first thing I thought of (flashing wrong RUU) when I first started reading your post. As long as your PC is recognizing the phone (sounds like it is) and the bootlaoder is locked (you said it was) then RUU failing is almost always becuase of the wrong RUU. You need the right RUU for your carrier version, and it has to be equal to or newer than the firmware and hboot currently on the phone.
I assume you have the AT&T version. If so, this is absolutely the wrong RUU. Its obviously for the Asian version. You need an AT&T RUU.
Where the heck did you get that? 1.44 firmware? You want ATT 1.73 or 1.85 (those match with hboot 1.09).
Try one of the RUU links in my Index thread: http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
Thanks I'll try that
Is there anything I can do with the ROM.zip that is extracted when you start the RUU....exe?
It is extracted to
C:\Users\%username%\AppData\Local\Temp\
Palmetto_X said:
Is there anything I can do with the ROM.zip that is extracted when you start the RUU....exe?
It is extracted to
C:\Users\%username%\AppData\Local\Temp\
Click to expand...
Click to collapse
Don't know.
But it brings up a good point. If you just want to return to a stock Sense ROM, and keep custom recovery, etc. then just flash a stock rooted ROM, which can be found in the Development section.
http://forum.xda-developers.com/showthread.php?t=1671237
Or for that matter, just flash a custom ROM like CleanROM or ViperXL, that are based on stock Sense, but cleaned up of bloat, and with some cool extra features.
redpoint73 said:
Don't know.
But it brings up a good point. If you just want to return to a stock Sense ROM, and keep custom recovery, etc. then just flash a stock rooted ROM, which can be found in the Development section.
http://forum.xda-developers.com/showthread.php?t=1671237
Or for that matter, just flash a custom ROM like CleanROM or ViperXL, that are based on stock Sense, but cleaned up of bloat, and with some cool extra features.
Click to expand...
Click to collapse
Same response after I tried to flash bot RUU 1.8 & 1.7. Hung at HTC
I flashed TWRP recovery and deleted everything
I also tried to flash from the ROM.zip in the RUU 1.8 boot_signed.img & system.img
fastboot flash boot boot_signed.img
that went fine
fastboot flash system system.img
I got
FAILED (remote: data length is too large)?
I wonder if that is what is hanging it in RUU
stock rooted ROM as in which ones? Something like this radavs-pablo11-TelstraJB-stock?
Palmetto_X said:
stock rooted ROM as in which ones? Something like this radavs-pablo11-TelstraJB-stock?
Click to expand...
Click to collapse
That is a stock rooted one, yes. In my index thread I posted previously, they are all listed under "Stock Rooted (Odexed/De-Odexed)" below "CUSTOM ROMs"
Here is the link again: http://forum.xda-developers.com/showthread.php?t=1671237
You can flash any of them. But the AT&T ones are the easiest to get up and running (1.85, 2.20). The others, you will need to manually enter AT&T's APN info to get a cellular data connection.
And please click the "Thanks" button for any of my posts you found helpful.
---------- Post added at 04:02 PM ---------- Previous post was at 03:56 PM ----------
Palmetto_X said:
Same response after I tried to flash bot RUU 1.8 & 1.7. Hung at HTC
Click to expand...
Click to collapse
Strange. Its an AT&T branded version? It actually says has the AT&T logo on the front of the phone, over the top of the screen?
redpoint73 said:
Strange. Its an AT&T branded version? It actually says has the AT&T logo on the front of the phone, over the top of the screen?
Click to expand...
Click to collapse
Yes it is AT&T at the top of the phone
Palmetto_X said:
Yes it is AT&T at the top of the phone
Click to expand...
Click to collapse
Odd, then I don't know why the 1.73 and 1.85 RUUs are not working, as long as you have the AT&T CID or SuperCID.
Just try flashing a stock rooted ROM from TWRP, like I suggested above. To me, its really the best place to be if the phone is new to you, and you might want to later flash any custom ROMs or mods. You get to start off with the stock ROM to get familiar with the phone, before seeing what features or mods you might want in a custom ROM. But the phone would still be bootloader unlocked, rooted, and custom recovery, so it will be ready to go when you are ready for some mods.
redpoint73 said:
Odd, then I don't know why the 1.73 and 1.85 RUUs are not working, as long as you have the AT&T CID or SuperCID.
Just try flashing a stock rooted ROM from TWRP, like I suggested above. To me, its really the best place to be if the phone is new to you, and you might want to later flash any custom ROMs or mods. You get to start off with the stock ROM to get familiar with the phone, before seeing what features or mods you might want in a custom ROM. But the phone would still be bootloader unlocked, rooted, and custom recovery, so it will be ready to go when you are ready for some mods.
Click to expand...
Click to collapse
Ran the 2.2 RUU from another machine and got it going. Thank you very much for your help
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
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
My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.
anpayy said:
My HTC One SV (LTE europe version ) stuck while booting, it displays white logo screen only,
now i unlocked bootloader and tried to flash rom, but failed,
How i can flash a custom rom or original oerating systedm in my phone,
please help me.
Click to expand...
Click to collapse
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.
Yes
thearif said:
Can you get into the bootloader? If you can, you can flash TWRP recovery via fastboot and flash a custom Rom with the recovery.
Click to expand...
Click to collapse
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?
anpayy said:
i can get into bootloder, but where can i get TWRP recovery and custom rom file ?
Click to expand...
Click to collapse
Go to http://forum.xda-developers.com/showthread.php?t=2292432 . Read through and find the recovery there. It is pretty well explained there. I am on my mobile so I am not sure of the link will take you to the first page. It is on the first page. Make sure you get the correct recovery for your phone model.
Original rom
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
That I do not know, but if my memory serves me right, there was a thread either in android development or general sections with the latest OTAs. You might wanna search for that...
anpayy said:
Where i can get original ROM for HTC ONE SV LTE k2ul_4.2.2_3.11.401.1 ???
Click to expand...
Click to collapse
You've already got the link to my index thread, but it seems you are to lazy to have a look at it. You even only need to watch for the software number and you will easily find what you are searching for.
Os intallation failed
i tried to install OTA update through TWRP recovery , but it failed
You can't flash this in recovery. Use TWRP recovery and flash the rom (not the Ota). Links are in my index thread.
Installed rom
Sucessfully instaled Viper SV rom,
but still phone did not booting,
Did you also flash boot.img of the rom in fastboot?
no
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif
Nice
anpayy said:
I missed to boot boot.img,
Now phone is working perfectly...........
Thanks all........specially old.splatterhand & thearif
Click to expand...
Click to collapse
Good to hear that...
Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?
miegas said:
Hi all,
I'm new in this forum so I post there.
My problems starts after try to updete htc one sv k2_ul. After update I get red triangle and then my phone freezed on white screen with logo.
Try to do factory reset from bootloader, but nothing happen. After few days looking information I unlock bootloader and try flash new boot, but after that I get Tampered. I found if I must s-off, but how I can get it? My pc found phone only on fastboot mode. Any ideas?
Click to expand...
Click to collapse
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all
old.splatterhand said:
You can't get S-off, without working OS.
You don't have an OS anymore on your phone?
Are you running a custom recovery like TWRP?
Run this fastboot cmd and copy the output here (remove your imei & serial number):
Code:
fastboot getvar all
Click to expand...
Click to collapse
My os just stop working.
I don't try TWRP, today will look more about that.
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 1.15.40a.00.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.14.401.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) product: k2_ul
(bootloader) platform: HBOOT-8930
(bootloader) modelid: PL8010000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4143mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.075s
edit
I flashed TWRP and I make restore, but phone won't start anyway. Maybe need to flash new os?
Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.
old.splatterhand said:
Flash the stock rom in TWRP, and don't forget to flash boot.img of the rom in fastboot.
Links are in my index thread.
Make a backup in recovery (just in case) and a wipe (advanced -> everything except int & ext sdcard) before.
Click to expand...
Click to collapse
Something I make wrong. I flashed TWRP, then installed ViperSV, phone restarted and booted TWRP. Then I found boot.img in yours index thead.
Then in fastboot flashed new boot, but phone still booting in TWRP. What I make wrong?
You need to flash the boot.img thats inside the ViperSV.zip, not any from my index thread.