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
Related
First of, a bunch of thanks to you for helping me get from a complete and utter noob to a just complete noob. Managed to root, install roms and get out of a LOT of soft bricks (i just don't give up!) with your awesome help, all by searching older posts. However, this time i find myself in a pickle.
I own an HTC One S C2 with Hboot 2.0.9, had stock ICS when i bought it with no option to update to JB (which is why i rooted it in the first place). Something about this particular version of the phone not being updated by HTC global, which i found out about after i bought it, duh. Anyway. I've tried installing JB roms from this thread http://forum.xda-developers.com/showthread.php?t=2239265 with no luck. Phone just keeps getting into HTC logo screen loops. Right now i am on backtobasics v3 rom. Here's how i tried installing them JB roms and also the rom i am using right now (using TWRP 2.4.1 because newest version wouldn't work with backtobasics rom):
(note: some roms had sliiiightly different directions, i just followed each and every one's description closely)
1) Download Rom.zip
2) Extract boot.img from Rom.zip to fastboot folder
3) Enter Recovery
4) Mount SD card
5) Copy Rom.zip to SD card
6) Unmount
7) Wipe data, system, cache, dalvik cache and factory reset
8) Install Rom.zip
9) Reboot Bootloader
10) Go to fastboot USB mode
11) dem commands: fastboot flash boot boot.img then fastboot erase cache then fastboot reboot
12) BOOM! HTC LOGO LOOPS!
I've also tried installing a RUU but i couldn't find any for my CID. Then i thought about getting a SuperCID but, frankly, i scrached that thought the minute i saw the how to do it thread. Here's the phone info
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA335W400602
imei: 352911052281278
product: villec2
platform: HBOOT-8260
modelid: PJ4021000
cidnum: BSTAR301
battery-status: good
battery-voltage: 4170mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
Thank you, in advance, for any advice you may be able to provide me with
Mkay, since i got no answer i went back to searching again! Unfortunately, i still have no asolution to my problem
From what i understand i have to: find a RUU to get from android version 4.0.3 up to JB version. Then i will be able to flash JB roms. But there is no RUU for CID BSTAR301.
I did find a thread with nandroid backup for a BSTAR301 which updates the version without a RUU but it was for HTC One X, i guess i shouldn't use that at all.
I am thinking about doing a SuperCID to install a RUU, then get back to my actual CID and flash a custom JB rom..
Would appreciate any advice
Tateh said:
Mkay, since i got no answer i went back to searching again! Unfortunately, i still have no asolution to my problem
From what i understand i have to: find a RUU to get from android version 4.0.3 up to JB version. Then i will be able to flash JB roms. But there is no RUU for CID BSTAR301.
I did find a thread with nandroid backup for a BSTAR301 which updates the version without a RUU but it was for HTC One X, i guess i shouldn't use that at all.
I am thinking about doing a SuperCID to install a RUU, then get back to my actual CID and flash a custom JB rom..
Would appreciate any advice
Click to expand...
Click to collapse
Yes, in your case S-OFF, Changing CID to something which has a JB RUU would do the trick. I think SuperCID is not necessary.
Sent from my Nexus 7 using Tapatalk HD
heakit Purpose
khan.orak said:
Yes, in your case S-OFF, Changing CID to something which has a JB RUU would do the trick. I think SuperCID is not necessary.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
THANK you! Currently trying to S-OFF it!
Tateh said:
THANK you! Currently trying to S-OFF it!
Click to expand...
Click to collapse
did you get S-OFF?
Not yet.. So exhausted. I tried the moonshine method but, just like trhe instructions state, i should have JB and be on stock for it to work properly, which is not possible since my phone has a BSTAR301 CID and is stuck on 4.0.3 with no stock roms available.
From what i've read, my only hope of S-OFF is to wait for the fellas working on Revolutionary method for S-OFF to release the correct version for this phone. I just hope it's soon and I thank them for their efforts, i'm so disappointed at this phone
Tateh said:
Not yet.. So exhausted. I tried the moonshine method but, just like trhe instructions state, i should have JB and be on stock for it to work properly, which is not possible since my phone has a BSTAR301 CID and is stuck on 4.0.3 with no stock roms available.
From what i've read, my only hope of S-OFF is to wait for the fellas working on Revolutionary method for S-OFF to release the correct version for this phone. I just hope it's soon and I thank them for their efforts, i'm so disappointed at this phone
Click to expand...
Click to collapse
same here. I just wrote to them asking for that
S-OFF done
I did S-OFF already. Now i need to know what CID put in my phone?? and which RUU install on it??
My MID is: PJ4021000
so i don't know if the Europe RUU's work in my phone. Maybe the radio have problem or no?? because the RUU say MID version: PJ4020000. Someone knows about this??
I have heard that JB update for BSTAR is now available.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
I have heard that JB update for BSTAR is now available.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah it's done. But I would change CID not have to wait for another update Brightstar in so long.
gustavoegg said:
Yeah it's done. But I would change CID not have to wait for another update Brightstar in so long.
Click to expand...
Click to collapse
Be sure to match MID or you'll end up having problems with future updates.
Sent from my HTC One S using Tapatalk 4 Beta
Episcopal yupdfir
khan.orak said:
Be sure to match MID or you'll end up having problems with future updates.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Where i can find a RUU for Model ID: PJ4021000?? Because i need update for OTA after install the RUU
gustavoegg said:
Where i can find a RUU for Model ID: PJ4021000?? Because i need update for OTA after install the RUU
Click to expand...
Click to collapse
You have to manually check the ANDROID-INFO.TXT to match CID + MID
Sent from my HTC One S using Tapatalk 4 Beta
Tateh said:
First of, a bunch of thanks to you for helping me get from a complete and utter noob to a just complete noob. Managed to root, install roms and get out of a LOT of soft bricks (i just don't give up!) with your awesome help, all by searching older posts. However, this time i find myself in a pickle.
I own an HTC One S C2 with Hboot 2.0.9, had stock ICS when i bought it with no option to update to JB (which is why i rooted it in the first place). Something about this particular version of the phone not being updated by HTC global, which i found out about after i bought it, duh. Anyway. I've tried installing JB roms from this thread http://forum.xda-developers.com/showthread.php?t=2239265 with no luck. Phone just keeps getting into HTC logo screen loops. Right now i am on backtobasics v3 rom. Here's how i tried installing them JB roms and also the rom i am using right now (using TWRP 2.4.1 because newest version wouldn't work with backtobasics rom):
(note: some roms had sliiiightly different directions, i just followed each and every one's description closely)
1) Download Rom.zip
2) Extract boot.img from Rom.zip to fastboot folder
3) Enter Recovery
4) Mount SD card
5) Copy Rom.zip to SD card
6) Unmount
7) Wipe data, system, cache, dalvik cache and factory reset
8) Install Rom.zip
9) Reboot Bootloader
10) Go to fastboot USB mode
11) dem commands: fastboot flash boot boot.img then fastboot erase cache then fastboot reboot
12) BOOM! HTC LOGO LOOPS!
I've also tried installing a RUU but i couldn't find any for my CID. Then i thought about getting a SuperCID but, frankly, i scrached that thought the minute i saw the how to do it thread. Here's the phone info
version-bootloader: 2.09.0001
version-baseband: 16.05.20.24_M
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: FA335W400602
imei: 352911052281278
product: villec2
platform: HBOOT-8260
modelid: PJ4021000
cidnum: BSTAR301
battery-status: good
battery-voltage: 4170mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: f616909f
hbootpreupdate: 11
gencheckpt: 0
Thank you, in advance, for any advice you may be able to provide me with
Click to expand...
Click to collapse
Hi, I have same problem with you. Have you got any solution?
Unfortunately not yet, I switched back to my old xperia ray while i wait for the revolutionary team to release a version for HTC One S
I have had this great phone for around 3-4 months now. In the second week of owning it, I already unlocked the bootloader and rooted my phone. It is not S-OFF, because I'm under the impression that you need to buy extra hardware.
What I want to know is if there is any way that I can flash 3.18 RUU on my AT&T branded (but I use T-Mobile) evita? If there is, can you provide me with a link?
Again, I'm already rooted and I'm bootloader unlocked. Thanks
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Thanks, mate. I appreciate the fast answer. Naturally, I hate being left behind; and seeing that most of the new ROMs require S-Off for the 3.4 kernel, I decided it was time to upgrade. I'll give it a try, as I'm currently trying to flash a ROM because I mistakenly flashed one of ^. Now, it's stuck on the the HTC splash screen, and I guess it's just the first boot scenario. However, it has taken a curious amount of time.
Yeah it's pretty much gonna be essential from now on anyway so you might as well get it outta the way.
What ROM did you try to flash? Also, what firmware/hboot are you currently on?
Sent from my Evita
I tried flashing CarbonROM. It gave me that (Status 7) error so I figured it was the 3.4 kernel giving me problems. After that, I tried flashing a previous version of CarbonROM, and it'd just stay stuck in the splashscreen (This is the ROM that I was discussing in my previous post). Now I tried to flash RageXL, and it's bootlooping. So I'm figuring that I should just go to a stock ROM and get this procedure done, and THEN flash a custom ROM. #BadLuckw3r3w0lv33
Ok. Yep it's the fact that you haven't yet upgraded via the RUU that these ROMs won't boot. Try flashing something like MagioRom or ViperXL just to get the s-off procedure done.
Sent from my Evita
Hmph. I'm pretty sure I've downloaded the latest Google and HTC USB drivers. Still, when I enter "adb reboot bootloader", this pops up:
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device offline
I have enabled USB debugging on my HOXL. Perhaps, it's the HTC Sync Manager? I have no clue beyond that point. I even tried restarting my phone AND computer.
EDIT: Nevermind, I just manually rebooted to the bootloader and continued from there. I am now S-Off
:thumbup:
Sent from my Evita
Btw.... If I helped you, please press the thanks button.
Sent from my Evita
Help me please
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
hirias said:
Can i install 2.20 firmware after installing 3.8 firmware.. I have s-off and unlocked bootloader and had my AT&T htc one x evita rooted before i installed 3.18 firmware... please help i cant root my phone on 3.18....
Click to expand...
Click to collapse
If you are already s-off, just install custom recovery, then flash a rooted ROM or SU to get root.
Sent from my HTC One XL using xda app-developers app
Will this RUU work if I have a locked bootloader and s-on?
Chudawg62 said:
Will this RUU work if I have a locked bootloader and s-on?
Click to expand...
Click to collapse
As I said earlier in the thread, SuperCID + s-on + jb RUU = brick.
Sent from my Evita
guys can you please help me here?
my phone is
*** LOCKED ***
EVITA PVT SHIP S_OFF RL
CID-11111111
HBOOT-1.14.0002
RADIO-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Junn 11 2012,14:36:28
i dont understand thiss phone that well so can you please tell me if its safe to install the stock jellybean RUU on my phone?
Yes you're s-off so you can run the RUU with minimal risk.
Sent from my Evita
3.17 or 3.18?
Hi,
First off, thanks everyone - this forum has provided me a wealth of information.
I'm wondering if I can run non-sense based roms (ex. Cyanogenmod 10.2 or 11) without downgrading the touchpanel firmware. Here are my phone specs:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT27XXXXXXXX
(bootloader) imei: 359691XXXXXXXXX
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4050mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Currently running ViperXL Android 4.2.2, stock kernel. Had to upgrade to HBOOT 2.15 to get rid of the random reboots and signal drop.
Before I upgraded HBOOT from 2.14 to 2.15 I was pretty sure I was on 3.17. I'm not even sure how to check this again? Would the upgrade to hboot 2.15 put me on 3.18? Sorry for the n0ob questions, help would be appreciated.
Current aosp ROMs no longer require you to down the ts firmware, they haven't since about June. You're a bit confused about the terminology, you didn't just upgrade to the 2.15 hboot, you upgraded to the 2.15 firmware, so you're currently on the 2.15 firmware. The hboot is only one component of the firmware as a whole.
Long story short, yes you can flash non-sense ROMs.
Sent from my Evita.
timmaaa said:
You don't need to buy any hardware or modify your phone physically to gain s-off, all you need to do is follow the instructions on this thread.
If you have SuperCID (which you most likely do) and try to RUU while you're s-on you'll brick your phone. So my advice is to go to the s-off thread I linked to before, and follow the instructions.
Once you've done that you can run the 3.18 RUU.
Sent from my Evita
Click to expand...
Click to collapse
can i run this RUU if i'm on CM10.2 ? and it says it will delete ALL from my phone, do i need to flash a rom and gapps right after i did that or will it still boot on CM10.2 ?
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
timmaaa said:
The RUU returns your phone to a stock configuration (ROM/recovery). You need to flash TWRP recovery again afterwards and then your ROM.
Sent from my Evita.
Click to expand...
Click to collapse
it doesn't work, i'm getting the usb connection error (170) but the cmd adb devices works just fine and the rumrunner s-off procedure went fine too...maybe i'm missing something ?
I decided to write this, even though it was already written by SO many people already, to have it in an easily accessible spot
YOU MUST ALSO BE SUPERCID!!
YOU MUST BE S-OFF!!!!!!! http://forum.xda-developers.com/showthread.php?t=2155071
So here we go!
2.15 Firmware: http://www.androidfilehost.com/?fid=23060877490004040
2.18 Firmware: https://www.androidfilehost.com/?fid=23329332407572084
Download the firmware zip. Put it in a folder where you have the fastboot sdk tool
Plug your phone in with USB Debugging
Reboot into bootloader:
adb reboot bootloader
Click to expand...
Click to collapse
Open a command window in the folder with fastboot sdk
Once the phone gets to bootloader, go into fastboot
Check if fastboot commands are working:
fastboot devices
Click to expand...
Click to collapse
Now the fun starts:
fastboot oem rebootRUU
fastboot flash zip <WhateverYouCalledYourFirmwareZip.zip>
Click to expand...
Click to collapse
if it shows FAILED (remote: 90 hboot pre-update! please flush image again immediately)":
fastboot flash zip <WhateverYouCalledYourFirmwareZip.zip>
Click to expand...
Click to collapse
If it ends with "INFO..... OK", reboot to the bootloader:
fastboot reboot-bootloader
Click to expand...
Click to collapse
Verify everything was successful by running:
fastboot getvar all
Click to expand...
Click to collapse
This is what you're supposed to see:
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.15.0000 (2.18.0000 if you used the 2.18 zip)
(bootloader) version-baseband: 1.31a.32.45.16_2
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.08.111.2 (5.18.xxx.x if you used 2.18 zip)
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: evita
(bootloader) platform: HBOOT-8960
(bootloader) modelid: PJ8310000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4140mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-de589c6eef
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Reboot into Android:
fastboot reboot
Click to expand...
Click to collapse
Reboot into Recovery:
fastboot reboot-recovery
Click to expand...
Click to collapse
Thanks to Turge and everyone else who helped with this firmware and Sense 5
Thanks @24ky for 2.18 firmware zip
CLICK THANKS IF I HELPED!!!!!!
I might be wrong, but this probably belongs in the General section as it isn't your own development.
Sent from my Evita
Moved to General.
Yeah sorry guys. Was in a rush to create this between classes and wasn't paying attention to the section.
Sent from my HTC One XL using XDA Premium 4 mobile app
Worked fine
I saw this in other threads but used this one since it was right there at the top. Everything went fine, thanks
Madcat8686 said:
I saw this in other threads but used this one since it was right there at the top. Everything went fine, thanks
Click to expand...
Click to collapse
can you do update to firmware 2.15 with S-ON and no SuperCID (it's still Roger001)?
cause I'm getting lost connection and random reboots with Viper XL 4.2.0
I tried Beastmode kernel but WiFi stopped working..
No you can't. Maybe it's time you got SuperCID and s-off, it's a good thing to have anyway.
Sent from my Evita
timmaaa said:
No you can't. Maybe it's time you got SuperCID and s-off, it's a good thing to have anyway.
Sent from my Evita
Click to expand...
Click to collapse
believe me I want to!
but I'm not sure how to do it yet.
(chicken-egg situation, lol)
I've read conflicting things, like you have to have SuperCID first before you S-off..
but then I read that you need to S-off first
which one is it?
If you can't read and understand the instructions in the S-OFF thread you are not ready
Sent from my HTC One XL
Get s-off before they patch it in the next update. Besides, you can fully customize your systems with kernels easily
Did I mention no fastboot commands?
Sent from my HTC One XL using XDA Premium 4 mobile app
clockwars said:
believe me I want to!
but I'm not sure how to do it yet.
(chicken-egg situation, lol)
I've read conflicting things, like you have to have SuperCID first before you S-off..
but then I read that you need to S-off first
which one is it?
Click to expand...
Click to collapse
It's stated pretty clearly in the s-off thread that you must have SuperCID first. I'm not sure where you think you read that s-off is required for SuperCID but that's 100% incorrect.
Sent from my Evita
timmaaa said:
It's stated pretty clearly in the s-off thread that you must have SuperCID first. I'm not sure where you think you read that s-off is required for SuperCID but that's 100% incorrect.
Sent from my Evita
Click to expand...
Click to collapse
no offence!
I'm not accusing anyone of anything! lol
and I'm obviously not an Android guru..
As you can see from my number of posts, I'm not a regular here!
so I wasn't following the progress of things..
and I'm not familiar with the specific thread you guys mention.
I was mostly using Google,
and trying to find someone with a Rogers version, to see how they did it.
And almost every bit I found would read "SuperCID for S-off" so I assumed that you need an S-off device in order to get SuperCID..
Ok, I wouldn't suggest going to any site for info other than XDA, you could end up with incorrect information as other sites don't properly distinguish between models. Long story short, stay on XDA and specifically within this forum.
You can get SuperCID using hex edit method. Then you can get s-off using Facepalm S-off.
Sent from my Evita
clockwars said:
no offence!
I'm not accusing anyone of anything! lol
and I'm obviously not an Android guru..
As you can see from my number of posts, I'm not a regular here!
so I wasn't following the progress of things..
and I'm not familiar with the specific thread you guys mention.
I was mostly using Google,
and trying to find someone with a Rogers version, to see how they did it.
And almost every bit I found would read "SuperCID for S-off" so I assumed that you need an S-off device in order to get SuperCID..
Click to expand...
Click to collapse
You are definitely on the right site but you need to read through the directions and understand what they mean. It's important that you know just what S-Off and Super CID mean to the phone before you try these procedures out. Taking a test drive without getting ALL the steps (and there are more) in order and correct CAN and WILL brick your phone. Bottom line...spend the time researching what you need to do to get where you want to be. Good luck out there.
Madcat8686 said:
You are definitely in the right sight but you need to read through the directions and understand what they mean. It's important that you know just what S-Off and Super CID mean to the phone before you try these procedures out. Taking a test drive without getting ALL the steps (and there are more) in order and correct CAN and WILL brick your phone. Bottom line...spend the time researching what you need to do to get where you want to be. Good luck out there.
Click to expand...
Click to collapse
Yeah I can see this site is a wealth of information.
A lot of brilliant people here!
timmaaa said:
Ok, I wouldn't suggest going to any site for info other than XDA, you could end up with incorrect information as other sites don't properly distinguish between models. Long story short, stay on XDA and specifically within this forum.
You can get SuperCID using hex edit method. Then you can get s-off using Facepalm S-off.
Sent from my Evita
Click to expand...
Click to collapse
thanks a million!
you sir are a true gentleman.
I followed the SuperCID instructions and everything seemed to work perfectly.
Now when I type: fastboot oem readcid in fastboot I get: (bootloader) cid: 11111111
which is great, but I also have an app called CID Getter (with a cupcake icon), and that app is telling me that my CID is [ROGER001].
Before I go any further, I need your help!
what does it mean?
I rebooted in fastboot again and fastboot oem readcid command still gives me 11111111
CID Getter doesn't display the correct CID, I'm not sure where it pulls it from but it's incorrect. The 11111111 you get from the fastboot command is your true CID so you can go ahead and proceed with s-off.
Sent from my Evita
Hi i am pretty new to the forums but have been flashing roms for awhile. I have super cid and s-off and recently upgraded to 2.15 after I was having a lot of random reboots/boot loops/no signal on CM10.2, CarbonJB, Beanstalk. I could only get my phone to boot with the 2.14 hboot when i flashed KickDroid but there were still no signal problems and some random reboots.
This seems to be fixed with the 2.15 hboot but I've been wanting to return to a pure android rom for awhile. I hear 2.15 does not work with any non-sense roms and indeed when i tried to flash CM10.2 again it would bootloop. I have heard however, in random threads throughout the forums that i could possibly use 2.15 hboot along with the Beastmode kernel to run Beanstalk.
Does anybody who is more knowledgeable than me at these things know which roms are now compatible with the 2.15 update?
Hailfire said:
Hi i am pretty new to the forums but have been flashing roms for awhile. I have super cid and s-off and recently upgraded to 2.15 after I was having a lot of random reboots/boot loops/no signal on CM10.2, CarbonJB, Beanstalk. I could only get my phone to boot with the 2.14 hboot when i flashed KickDroid but there were still no signal problems and some random reboots.
This seems to be fixed with the 2.15 hboot but I've been wanting to return to a pure android rom for awhile. I hear 2.15 does not work with any non-sense roms and indeed when i tried to flash CM10.2 again it would bootloop. I have heard however, in random threads throughout the forums that i could possibly use 2.15 hboot along with the Beastmode kernel to run Beanstalk.
Does anybody who is more knowledgeable than me at these things know which roms are now compatible with the 2.15 update?
Click to expand...
Click to collapse
AOSP-wise, I'm pretty sure CFX is 2.15 compatible
Sent from my HTC One XL using XDA Premium 4 mobile app
CM10.2 is definitely compatible with the 2.15 firmware package, the bootloop was likely caused by the current bugs with the ROM itself.
Sent from my Evita
timmaaa said:
CM10.2 is definitely compatible with the 2.15 firmware package, the bootloop was likely caused by the current bugs with the ROM itself.
Sent from my Evita
Click to expand...
Click to collapse
4.3 just wasn't a good run for aosp
Sent from my HTC One XL using XDA Premium 4 mobile app
ok here's the thing..
i lost my backup for the stock rom which came with my HTC One XL,and i've been facing alot of issues with custom roms ,the major thing was the capacitive buttons stopped working without a reason !
now being S-ON,unable to go back to stock except with RUU's with the matching CID,,ok so i tried searching for the right RUU with matching CID which is J15 and the only one i found on androidRUU website didnt work for me as its a different hboot version (not sure if that's why it refused or not but thats what i understood from reading in the forums)
so i spent hours and hours trying to find the correct RUU with matching CID and hboot version but was invain,,
another option searching for NANDROID,,still didnt find any matching results
tried getting SuperCID to make it easier to find a matching RUU,,but i found in order to get SuperCID i need to be S-OFF,,and in order to get S-OFF i need to get SuperCID first...its a bit frustrating i know
also another weird thing that when i tried to relock the bootloader,it says "FAILED (status read failed (Too many links))"
so any help on how to either :
1.Full stock restore either with a matching RUU or NANDROID
2.Getting a full stock rom with the latest firmware update so that hopefully the capacitive buttons work again..
would be really appreciated
and here are my info :
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3848mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0
lordofegypt said:
ok here's the thing..
i lost my backup for the stock rom which came with my HTC One XL,and i've been facing alot of issues with custom roms ,the major thing was the capacitive buttons stopped working without a reason !
now being S-ON,unable to go back to stock except with RUU's with the matching CID,,ok so i tried searching for the right RUU with matching CID which is J15 and the only one i found on androidRUU website didnt work for me as its a different hboot version (not sure if that's why it refused or not but thats what i understood from reading in the forums)
so i spent hours and hours trying to find the correct RUU with matching CID and hboot version but was invain,,
another option searching for NANDROID,,still didnt find any matching results
tried getting SuperCID to make it easier to find a matching RUU,,but i found in order to get SuperCID i need to be S-OFF,,and in order to get S-OFF i need to get SuperCID first...its a bit frustrating i know
also another weird thing that when i tried to relock the bootloader,it says "FAILED (status read failed (Too many links))"
so any help on how to either :
1.Full stock restore either with a matching RUU or NANDROID
2.Getting a full stock rom with the latest firmware update so that hopefully the capacitive buttons work again..
would be really appreciated
and here are my info :
version: 0.5
version-bootloader: 2.10.0000
version-baseband: 3.12.38.00.24
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT2CNW302531
imei: 354370050060697
product: evita_utl
platform: HBOOT-8960
modelid: PJ8350000
cidnum: HTC__J15
battery-status: good
battery-voltage: 3848mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-b27b8968
hbootpreupdate: 11
gencheckpt: 0
Click to expand...
Click to collapse
Long story short, there is no RUU for your CID. But there is a thread in our General Section that contains stock backups for your device.
I'll also just clear up some confusion you seem to have about s-off and SuperCID. There are two s-off methods for the Evita, Facepalm and Rumrunner. Facepalm requires SuperCID to work, Rumrunner does not require SuperCID to work. If you don't have SuperCID and want it you can use the Rumrunner s-off method to get s-off and then change your CID using a fastboot command.
Either way, don't use any of the RUUs that match other CIDs, they'll most likely brick your phone. Just find the thread in General and you'll be able to download a nandroid backup.
Sent from my Evita
timmaaa said:
Long story short, there is no RUU for your CID. But there is a thread in our General Section that contains stock backups for your device.
I'll also just clear up some confusion you seem to have about s-off and SuperCID. There are two s-off methods for the Evita, Facepalm and Rumrunner. Facepalm requires SuperCID to work, Rumrunner does not require SuperCID to work. If you don't have SuperCID and want it you can use the Rumrunner s-off method to get s-off and then change your CID using a fastboot command.
Either way, don't use any of the RUUs that match other CIDs, they'll most likely brick your phone. Just find the thread in General and you'll be able to download a nandroid backup.
Sent from my Evita
Click to expand...
Click to collapse
and concerning that backup you're talking about,,does it have to be matching my CID or any of my details ? or just any backup is fine ?
The backup I'm talking about is specifically for the middle eastern variant of this phone.
Sent from my Evita
timmaaa said:
The backup I'm talking about is specifically for the middle eastern variant of this phone.
Sent from my Evita
Click to expand...
Click to collapse
thx for the help,,ok so currently i found the needed NANDROID,,made the restore and am back to stock android 4.1.1 with relocked bootloader and stock recovery flashed,,i tried searching for software updates and it says no updates found when my neighbor got the same device and he recieved an update for 4.2.2 ??
however am not quite sure if the stock recovery flashed successfully or not ,,in the fastboot it said that the flashing was successful but when i tried to access the recovery from the boot it just went blank screen ,,is that ok and am not supposed to enter the stock recovery but then why it doesnt make the update ? or there's something wrong with the recovery i got ?
You should be able to enter the stock recovery, I believe there's something wrong with the recovery you flashed.
Sent from my Evita
ngiyal 457
timmaaa said:
You should be able to enter the stock recovery, I believe there's something wrong with the recovery you flashed.
Sent from my Evita
Click to expand...
Click to collapse
ok i found the recovery ,flashed it and able to access the recovery nw,,but in order to do so i had to unlock the bootloader again other wise it will just keep on booting into the bootmode which is kinda wierd...
anyway you got any ideas why am unable to receive the OTA ?
I'm not sure why you're not receiving it, sorry. If you can find the OTA you can install it manually.
Sent from my Evita
timmaaa said:
I'm not sure why you're not receiving it, sorry. If you can find the OTA you can install it manually.
Sent from my Evita
Click to expand...
Click to collapse
surprisingly i just got an update for the "people" app through searching for software updates (not through playstore)...does that mean that my OTA is working fine and its just a delay or something like that for the full software,,or this app update has nothing to do with the OTA's ?
The people app itself is separate from the OTA.
Sent from my Evita
j15 version of evite doesn't recieve 4.2.2 update yet
i have the same of your phone and i flashed stock ROM of telstra and it works fine for me
madoooz said:
j15 version of evite doesn't recieve 4.2.2 update yet
i have the same of your phone and i flashed stock ROM of telstra and it works fine for me
Click to expand...
Click to collapse
Could I ask where you got that stock Rom and for a link as well. With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement. So this would be greatly appreciated.
Thank You
jnthnbgg said:
Could I ask where you got that stock Rom and for a link as well. With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement. So this would be greatly appreciated.
Thank You
Click to expand...
Click to collapse
Just have a look in our Android Development section, you'll find it in there, along with some great custom ROMs you might want to try.
Sent from my Evita
jnthnbgg said:
Could I ask where you got that stock Rom and for a link as well.
Click to expand...
Click to collapse
All the links you will likely ever need are here:
http://forum.xda-developers.com/showthread.php?t=1671237
jnthnbgg said:
With a bit of help from lag I managed to factory reset and lose my backup just before I was going to get in on my pc, imagine my excitement.
Click to expand...
Click to collapse
Did you factory reset in hboot and corrupt the SD? Because a factory reset in recovery or in the OS should not wipe the SD (including nandroids).
redpoint73 said:
All the links you will likely ever need are here:
http://forum.xda-developers.com/showthread.php?t=1671237
Did you factory reset in hboot and corrupt the SD? Because a factory reset in recovery or in the OS should not wipe the SD (including nandroids).
Click to expand...
Click to collapse
Yes it did it in Hboot of all things while I had Clean Rom installed which was giving me grief (blackscreen after HTC load screen)
jnthnbgg said:
Yes it did it in Hboot of all things while I had Clean Rom installed which was giving me grief (blackscreen after HTC load screen)
Click to expand...
Click to collapse
What are your bootloader details? I might be able to diagnose why you were having problems before the factory reset.
Sent from my Evita
timmaaa said:
What are your bootloader details? I might be able to diagnose why you were having problems before the factory reset.
Sent from my Evita
Click to expand...
Click to collapse
Well I know it is the S-On as I saw even though I was doing all according to the instructions I could find. I had Unlock, SU CID, just could not get that S-OFF. I tried it manually, via the toolkits people have out there, using a 2.0 USB cable. But without the S-OFF I did not get the firmware installed so that was my source of headache with that I just had a bit of lag in the bootloader screen and i click one to many times past recovery and viola up the crick without a canoe lol
Once you have a ROM installed, forget the toolkits and get s-off manually, it's really easy. There are two methods you can try:
Facepalm S-off
Rumrunner S-off
Sent from my Evita
timmaaa said:
Once you have a ROM installed, forget the toolkits and get s-off manually, it's really easy. There are two methods you can try:
Facepalm S-off
Rumrunner S-off
Sent from my Evita
Click to expand...
Click to collapse
So going the route of Palm as I can not get adb to connect but I can fastboot USB, The first attempt ends with FAILED remote:92 supercid! please flush image again immediately. The second attempt ends in FAILED remote:99 unknow fail
You're gonna need to get adb working, both methods require it. I'm in a good mood so I'm gonna give you the solution to the error 99 problem, but please in future search properly before posting, the solution to that problem has been posted dozens of times in the Facepalm thread.
When you get error 99 after flashing the zip, you need to force a reboot to the bootloader and start the process again and you should get error 92 again.
Why isn't adb working? What ROM are you on? Have you updated your drivers? Do you have usb debugging turned on in Developer Options?
Sent from my Evita
hi all,
iv got my HTC One X bricked, well i installed recovery, unlocked bootloader and forgot to make an S-OFF and flashed rom, now i see only a black screen device not boots, i tried install RUU but says invalid utility version try another, i think it just need a S-OFF and thats it it should boot, and what to do? how to back to stock or s-off on rooted? NOTE: Device is factory unlocked (sim-free)
P.S well fact that i have AT&T + unlocked bootloader means i have changed CID also
TY ADVANCED
Can you access bootloader?
---------- Post added at 01:21 PM ---------- Previous post was at 01:16 PM ----------
Maybe your ruu isn't running cuz its not compatible. What x do you have...Evita or endevarou?
marknoll said:
Can you access bootloader?
---------- Post added at 01:21 PM ---------- Previous post was at 01:16 PM ----------
Maybe your ruu isn't running cuz its not compatible. What x do you have...Evita or endevarou?
Click to expand...
Click to collapse
yes i can, i have Evita
Then if you can, u are not bricked. You should post bootloader details so we can properly assist you
marknoll said:
Then if you can, u are not bricked. You should post bootloader details so we can properly assist you
Click to expand...
Click to collapse
Unlocked
EVITA PUT SHIP S-ON RL
HBOOT 2.14.0000
Radio 0.24p.32.09.06
OpenDSP v34.1.0.45.1219
eMMC - boot
thats a basic what i see in phone, should i post a fastboot command`s obtained detailed info?
Yea. Do that. Fastboot getvar all..let's see it all. Lol
version: 0.5
version-bootloader: 2.14.0000
version-baseband: 0.24p.32.09.06
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: HT26KW305284
imei: ***
product: evita
platform: HBOOT-8960
modelid: PJ8310000
cidnum: 11111111
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-97c9a06e
hbootpreupdate: 11
gencheckpt: 0
P.S its messed up, i already used exploit on non booting time and since i couldnt boot, cant use ADB to push soffbin3
I would suggest you look under timaaas signature to properly run a ruu,flash recovery and facepalm (s_off) you having Cid 11111111 may be a deterrent
marknoll said:
I would suggest you look under timaaas signature to properly run a ruu,flash recovery and facepalm (s_off) you having Cid 11111111 may be a deterrent
Click to expand...
Click to collapse
i have custom recovery but how to flash a facepalm s- off since it need booted android to push ?
I think you're going to have to ruu then go from there. I could be wrong though. Tim will see your post and assist you. He's on this q&a frequently
marknoll said:
I think you're going to have to ruu then go from there. I could be wrong though. Tim will see your post and assist you. He's on this q&a frequently
Click to expand...
Click to collapse
okay ty
Youre welcome. Having certain things on your device could prevent you from s offing. Wait it out for tim. Don't flash anything. ? he can properly assist you
What ROM did you flash? Did you remember to flash the boot.img via fastboot afterwards? It'd be a good idea for you to read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain vital information for beginners (for anyone really) that you probably really need at this stage.
I don't think an RUU is required at this point, my guess is that you probably just forgot to flash the boot.img after flashing the ROM. Getting s-off will be your next step but we need to get your phone booted first.
But, provide the above info and we'll take it from there.
Sent from my Evita
timmaaa said:
What ROM did you flash? Did you remember to flash the boot.img via fastboot afterwards? It'd be a good idea for you to read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature, they contain vital information for beginners (for anyone really) that you probably really need at this stage.
I don't think an RUU is required at this point, my guess is that you probably just forgot to flash the boot.img after flashing the ROM. Getting s-off will be your next step but we need to get your phone booted first.
But, provide the above info and we'll take it from there.
Sent from my Evita
Click to expand...
Click to collapse
i flashed a CM 11, nope not flashed a boot.img since idk which to flash and ye i followed ur guide, but i forgot s-off
ahaaa, understnad i think, flashing a boot.img would make my rom work?
Prerevision said:
i flashed a CM 11, nope not flashed a boot.img since idk which to flash and ye i followed ur guide, but i forgot s-off
ahaaa, understnad i think, flashing a boot.img would make my rom work?
Click to expand...
Click to collapse
Hahah thats it, flashing boot.img got it work thanks all
Prerevision said:
Hahah thats it, flashing boot.img got it work thanks all
Click to expand...
Click to collapse
Go ahead and get s-off now and you won't need to worry about flashing the boot.img anymore. Plus it enables you to flash kernels and radios, and run any Evita RUU (which is extremely valuable if you ever get in trouble).
Sent from my Evita
Which recovery did you flash?out of curiosity
Sense 5 roms will work only on bootloader version 2.17 or more than it . If you didnt s off you should flash a rom which is not sense 5 . After rom you must flash boot.img which is in your rom . Good luck
Sent by my lovely lumia 925
bijooo said:
Sense 5 roms will work only on bootloader version 2.17 or more than it . If you didnt s off you should flash a rom which is not sense 5 . After rom you must flash boot.img which is in your rom . Good luck
Sent by my lovely lumia 925
Click to expand...
Click to collapse
That isn't right. You can use Sense 5 ROMs as long as you're on the 2.15 (not 2.17) firmware (not bootloader) or above. And why are you suggesting to flash an earlier ROM if he doesn't have s-off?
Sent from my Evita
I miss my hoxl
Sent from my SPH-D710 using XDA Premium 4 mobile app