Database Info

[Q] [Help thread] Hands in my hair for last 6 days!!

Searched a whole lot but no solution!!
My sensation xe is stuck at splash screen with every rom or firmware I flash on it... I checked the MD5sums, corresponding firmware with rom and even the actual method of flashing.
Sensation xe is stuck. I am new to android flashing but have read almost everything about the sensation just not the solution.

Have you removed firmware pg58img.zip from SD card after updating?
Sent from my Pyramid-T

Yes, I have. I was aware of that from the first time I flashed firmware.

Are you able to boot to recovery? Did you superwipe before flashing?

Yes, superwipe. I am also able to boot to recovery.
I took all the necessary precautions as I have been bricked in the past. The thing is every rom you flash on the device gets stuck at boot screen.

hmmm...why not flash a RUU and do it all again? i mean re-do s-off,root and supercid

Is there maybe a way to create a device image or error script to see where it goes wrong because I have followed every guide to the letter here on the sensation forum.
I went trough firmware differences, flashing method, other bootloops/stucks threads. But there is no one with a solution or even the same problem.
So if you would have any Ideas I would appreciate it or do you know a developer here?

matt95 said:
hmmm...why not flash a RUU and do it all again? i mean re-do s-off,root and supercid
Click to expand...
Click to collapse
I have tried it with the appropriate Europe version and the latest beta of ICS(both XE dedicated). They boot got stuck on bootscreen to.
I am Revolutionary | pyramid ship s-off | 1.27.1100 | 11.22.3504.07_M

i am referring to flash the RUU with hboot 1.17 not the ics one

Will try that right now and I will get back to you.

What was the fw version and roms that you tried? Did you superCID?
Sent from my Pyramid-T

stringer7 said:
What was the fw version and roms that you tried? Did you superCID?
Sent from my Pyramid-T
Click to expand...
Click to collapse
Sorry missed a few posts, hope above works.
Sent from my Pyramid-T

Flashing right now. Method used.
Firmware 1.17 from(http://forum.xda-developers.com/showthread.php?t=1459767)
and then superwipe from ARHD.
and then this rom (http://forum.xda-developers.com/showthread.php?t=1259085)
Will get back to you in 10 minutes as it is flashing now.

stringer7 said:
Sorry missed a few posts, hope above works.
Sent from my Pyramid-T
Click to expand...
Click to collapse
Yes, I have tried to as precise as possible when flashing all the roms. The right fw with the right rom. But they just wont start. Even stock RUU wont start.

mitchelleersel said:
Yes, I have tried to as precise as possible when flashing all the roms. The right fw with the right rom. But they just wont start. Even stock RUU wont start.
Click to expand...
Click to collapse
did you get errors?

matt95 said:
did you get errors?
Click to expand...
Click to collapse
Nope no errors whatsoever just the boot screen staring me in the face for hours.

I've always flashed super wipe, then rom, then updated firmware in that order. Perhaps worth a go?
Sent from my Pyramid-T

stringer7 said:
I've always flashed super wipe, then rom, then updated firmware in that order. Perhaps worth a go?
Sent from my Pyramid-T
Click to expand...
Click to collapse
better super wipe, flash fw, super wipe, install the rom and reboot
however try downloding the ruu and run it from the pc

matt95 said:
better super wipe, flash fw, super wipe, install the rom and reboot
however try downloding the ruu and run it from the pc
Click to expand...
Click to collapse
Have tried that several times in the order you suggested. It does not work for me.
RUU also gets stick on bootscreen. Have you heard about this earlier.

Did you SuperCID? If not, are you using the right firmware package for your CID, and also If you are trying to upgrade your firware for a new ROM, and it's stuck at the HTC splash screen, maybe that's because the ROM you had before isn't compatible with the firmware, so just try to flash the new ROM in this case.

[Q] From ICS to JB

Hi, I have a HTC ONE XL for AT&T with S-OFF and unlocked bootloader. I have the nocturnal ROM based on ICS. Also HBOOT 1.01.0000.
I want to install a rom based on JB (This particular CleanROM 6.5 - ★ | Jellybean 4.1.1! |).
My question is with this hboot, can i flash a jb rom from ICS? Because I'm not sure if flash from recovery the zip of this rom bricked me.

It won't brick you. I'm not sure if you'll experience issues using such an old firmware with a ROM based on the latest softwate
Sent from my One X using xda app-developers app

Thanks. Is there any way to update the software?

Rafanjani said:
Thanks. Is there any way to update the software?
Click to expand...
Click to collapse
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB

between ynelsol
GroovyGeek said:
Yes install the Ruu, then push twrp, then install CR. This will give you the latest firmware. CR by itself does not so it, and some gave experienced random reboots with older wifi firmware. Just be aware that a small subset of HOXL phones do not work well with Maps/nav under JB
Click to expand...
Click to collapse
thanks for reply! I did brick my phone when i try to install an official ruu 2 months ago, but i did fix this ($$$$). The problem is that I can not install because I have CID 111111 and CR root, bootloader unlocked etc

With s-off you won't brick running an ruu. Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Sent from my HTC One X using xda app-developers app

exad said:
Though my phone will no longer ruu properly but that's another story. I may post a thread about it in case others experience it so they know how to recover.
Click to expand...
Click to collapse
I'm curious about this. What happened?
Sent from my HTC One

ECEXCURSION said:
I'm curious about this. What happened?
Sent from my HTC One
Click to expand...
Click to collapse
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^

exad said:
Something went wrong while RUUing and my hboot partition cannot be written over without clearing the cache first. So the RUU will get to the end and then fail. Everything flashed except the hboot. It's kind of funny because it looks like a brick when it happens but it remains in RUU mode so I can just fastboot flash the hboot seperately after and everything works but RUUs will no longer complete successfully Always half bricks.
How did it happen? Well I think it's because I was RUUing in a VM as I was running linux exclusively at the time. But during RUU the phone looses connection and I have to manually reconnect to my phone and I didn't realize so it interrupted the RUU. I'm just lucky I didn't end up with a full brick! ^_^
Click to expand...
Click to collapse
how i can flash hboot using fastboot? I wish to have jb

Rafanjani said:
how i can flash hboot using fastboot? I wish to have jb
Click to expand...
Click to collapse
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?

exad said:
flashing hboot with fastboot won't give you JB......
Is your phone S-ON or S-OFF?
SuperCID? Yes or no?
Bootloader locked or unlocked?
Click to expand...
Click to collapse
I know! but it's the first step to upgrade to jb

Rafanjani said:
I know! but it's the first step to upgrade to jb
Click to expand...
Click to collapse
No it isn't

How to obtain s-off for One S(S4) Hboot 2.15

I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?

S1pk3 said:
I have a European One S (S4) with Hboot 2.15. Unlocked via htcdev. I cant figure out how to get s-off. Writing supercid doesnt work.. How to fix it?
Click to expand...
Click to collapse
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.

Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app

S1pk3 said:
Ok, thanks for your reply. I want to flash cm 10.2. That should be possible without s-off?
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Yeah. It is just recommended that you are s-off.
As the guy said before you need to flash boot.img (the kernel) afterwards.
Sent from my One S using xda app-developers app

Will give it a try. Thanks.
Sent from my HTC One S using xda app-developers app

Stuck while flashing firmware in htc one s
I got stuck while installing htc one s with maximus hd..
http://forum.xda-developers.com/showthread.php?t=2445392&highlight=sense+5
I did till fastboot flash recovery TWRP2.6.1.0.img ...but aftr fast boot reboot it dint take memory...without that i cant copy ROM to memory...i did unlock bootloader not s off.... i got an error99 while flashing firmware.. icant on the device now....please help me...

tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?

sylvantino said:
I just noticed this thread.
I also have a similar problem. I cannot achieve s-off with my (S4) htc one s , running the exact same hboot as op.
To upgrade to jb 4.2.2 sense 5 which we should be getting for which we now won't despite them making the update.
Will we be able to upgrade to this new patch with s-on using the flash boot?
Click to expand...
Click to collapse
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.

Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.

sylvantino said:
Hi thanks for your reply.
Do you know of any such roms that don't require the s-off?
I installed odyssey, its got no google playstore..suddenly my computer no longer recognizes my sd card / phone.
I tried adb push, managed to get a stock orang001 tmobile uk package to the root folder, but when i turn off the mount, it says its bad..which is a little odd.
Seems thought I got odyssey installed / flashed etc, its so bare as its practically useless to me unless i have google, plus its got weird glitches on boot up, taking forever, always booting into the developers screen etc.
Click to expand...
Click to collapse
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.

tivofool said:
With Odyssey you have to flash slim gapps after you install the rom.
Your Sd card (partition) may be corrupted, the way to fix that is to put the stock recovery back on your phone then go to bootloader and "clear storage"
All of the other Roms don't require S-off, MagioRom is being actively developed with the sense 5 and 4.2.2.
Click to expand...
Click to collapse
thanks for the information. i read through magiorom thread. trying to download now.seems a flaky webhost

tivofool said:
Moonshine
http://forum.xda-developers.com/showthread.php?t=2325590
If you aren't on the supported firmware it won't work. So, if that doesn't work for you then I would just leave it S-on. It isn't hard to fastboot flash a boot.img before flashing a rom in recovery.
Click to expand...
Click to collapse
Hi would moonshine work for hboot 2.16 ?

cyberusman said:
Hi would moonshine work for hboot 2.16 ?
Click to expand...
Click to collapse
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)

tivofool said:
No, it is hard enough to get it to work on the supported firmware. (I would love to be proven wrong, for the handful of people that need this)
Click to expand...
Click to collapse
Well i have hboot 2.16 and i need to s-off i get this error when trying to flash the ruu its error 99 unknown fail i get it twice

tivofool said:
Maximus HD --- No you need S-off for this. The firmware updates your Hboot, Radio, and you flash a different recovery and finally Rom
You might check out other Rom's that have Sense 5 4.2.2 features. They do not require S-off like Maximus does.
Click to expand...
Click to collapse
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.

santo_2k said:
I was able to load Maximus HD ROM with S-On but only issue I had was wireless.
Click to expand...
Click to collapse
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app

rolo143 said:
Please tell me how did you manage to install MaximusHD ROM without S-off!
I'm a little scared since I read they have a lot of problems while installing this ROM.
I'm using CM10.1 right now, but I would like to have sense 5 on my HTC One S.
I have unlocked boot loader and TWRP recovery.
I read there are other ROMS with sense 5 like MagioRom, which doesn't require S-Off (As far as I know)
Is there a great difference between MagioRom and MaxiumusHD? All I want is Sense 5 on my phone without all the terrible of S-offing!!
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I tried Maximus with CWM, did i using sideload and them flash the boot.img file. but it was a disaster as my device didn't connect to wifi and had some call drops then I tried flashing twrp and then sideloaded magicrom 4.0 and flas boot.img, it looks lot better now but only issue right now is my phone keeps on rebooting and am still waiting for a stable rom to be released.

I read MagioRom comments and they say with that ROM phone reboots a lot. So I think the only way is with MaximusHD. The WiFi problem I think it can be fixed. I don't know about the call drops, but many have this ROM as daily use so I guess it's ok. I will try S-off with moonshine method, then try install Maximus. Hope my phone survives.
Sent from my One S using xda app-developers app

[Q] HBOOT 2.15 killing me...

*** WHAT MY PROBLEM IS***
PLEASE can someone confirm any AOSP ROM that works with 2.15 HBOOT?
***WHAT I KNOW***
( i know the CM 10.2 thread says that RUU 3.18 which will make the hboot 2.14 but since 2.15 is latest i assume it should support)
(i also know that [HBOOT 2.15 is essential for SENSE 5 4.2.2 to run,i believe that's the only reason people go for 2.15)
***WHAT I HAVE TRIED***
NOW from what i have tried is that the 1st stable cm 10 release doesn't work with 2.15 (obviously too old build) my screen also became responsive(i believe that because of touch panel firmware) then with the latest stable release of cm 10.1 it specified that it needs hboot 2.14 and hence couldn't flash.
with PAC 4.3 it does gets installed but screen is unresponsive and infinite bootloops!:silly:
***WILL THIS WORK***
so now if i RUU 3.18 i will have to unlock boot loader and root it (M SOFF SUPER CID) which i m not really ready to do!
now there are methods that can help u downgrade/upgrade your firmware , can i do that?
also will using torched kernel help in me in any way?
***WHY DO I WANT AOSP***
Viper XL 4.2.2 best ROM ever hats off but the thing is i dont know why but i have Signal issues i tried flashing the recommended RADIO version.
since the vendor had already RUUd my device that was meant from some ASIAN region and already came with SENSE 5 and i dint mess up with it in any way still i had signal issues (which are unpredictable) i found by GSAM BATTERY monitor that around 30 to 40% of my battery is consumed by RADIO.
also the best signal is around -81db
i also had some issues with camera!
and then there is the numerous options i can have with AOSP.
****LASTLY CAN ANYONE HELP****
:angel:

Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.

I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL

954wrecker said:
He makes it hard to understand but he is S-ON so he is screwed at this point
Sent from my HTC One XL
Click to expand...
Click to collapse
no no no i am SOFF i know for sure!!!

exad said:
Just RUU. Your bootloader will remain unlocked and your S-OFF will remain
After the RUU you can flash recovery and flash a rom. You can technically just flash the 2.14 firmware.zip by extracting it from an OTA or an RUU, but easier to just ruu. and you get a nice clean wipe too.
Click to expand...
Click to collapse
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?

954wrecker said:
I misread the m soff part sorry. You could have just run the ruu and twrp and been done in the time it took you to write that post.
Sent from my HTC One XL
Click to expand...
Click to collapse
LOL u are right thanks!
its just that m kinda paranoid cause every day in the Help and Troubleshooting section there is some thread dats says BRICKED so always to be on the safer side!

Sonone said:
jus for the sake for reassurance:
after RUU:
will Bootloader remain Unlocked?
will it still be SOFF?
and SUPERCID?
so these things will survive the RUU?
Click to expand...
Click to collapse
yes

exad said:
yes
Click to expand...
Click to collapse
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?

Sonone said:
thanks a lot EXAD!!!:good::good:
btw earlier you mentione its possible to extract the firmware file?
how can it be done?
Click to expand...
Click to collapse
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.

exad said:
the easiest way is to extract firmware.zip from a 3.17/3.18 ota file for your carrier.
Click to expand...
Click to collapse
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.

redpoint73 said:
I wouldn't mess with extracting the firmware files from the OTAs manually. If one of the hboot modules is missing, a brick can result. The OP is probably OK, since he has already manually updated to hboot 2.15. But RUU is still seems the safest way.
Click to expand...
Click to collapse
as always thank you...
since u recoomend thats the safest way i will try out that.
have to download the RUU 3.18!!!
*waiting*

[Q] Issue with super CID and S-Off

Hey Guys!
I have an issue with my HTC One XL.
I want to run the Viper XL Rom with Sense 5. But i always get Data and Signal drops, so i wanted to update my Firmware.
But in order to update my firmware, I have to get S-Off. And in order to get S-Off I have to get the super CID.
I tried to change the CID of my HOXL with the One-Click tool, but the only thing that happens after running this tool is that my screen is freezed and my HOXL is ****ed up.
So I tried the HEX-Edit method. So I changed the CID with Hex-Edit and pushed it back on my HOXL. But after rebooting it, my CID is still the old one.
Does any of you guys know a solution for my Problem? I really want to go S-Off ):
Sorry for my bad english! I hope it's not that hard to understand.
Facts about my HOXL:
Unlocked via HTC Dev
Rooted
HBoot 2.14
S-On
ViperXL 3.2.8
Bulletproof Kernel

Read.
But since english doesn't seem to be your first language update to 2.15 hboot or install beastmode kernel
Sent from my VENOMized HoxL

area51avenger said:
Read.
But since english doesn't seem to be your first language update to 2.15 hboot or install beastmode kernel
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
But to install Beastmode i need to be S-Off, don't I?

Kureno7 said:
But to install Beastmode i need to be S-Off, don't I?
Click to expand...
Click to collapse
Nope. You can flash kernels using fastboot with s-on.

redpoint73 said:
Nope. You can flash kernels using fastboot with s-on.
Click to expand...
Click to collapse
But I read that there is no boot.img for Beastmode?
If there is one, that whole thing is much more easier then I expected

Kureno7 said:
But I read that there is no boot.img for Beastmode?
If there is one, that whole thing is much more easier then I expected
Click to expand...
Click to collapse
I actually haven't been following Beastmode. How does it install, an AROMA installer (I see the download is a zip)?
If so, just flash in recovery (s-off not needed).

redpoint73 said:
I actually haven't been following Beastmode. How does it install, an AROMA installer (I see the download is a zip)?
If so, just flash in recovery (s-off not needed).
Click to expand...
Click to collapse
With Bulletproof Kernel I always had to flash the .zip file in recovery and the "boot.im" separately via fastboot, otherwise I was stuck in Bootloop.

Kureno7 said:
With Bulletproof Kernel I always had to flash the .zip file in recovery and the "boot.im" separately via fastboot, otherwise I was stuck in Bootloop.
Click to expand...
Click to collapse
That's because boot.img won't install in recovery with s-on (and hboot 1.14 or higher). But AROMA bypasses this, which is why I ask if Beastmode uses an AROMA installer or not. I think it does, but someone with actual experience with Beastmode will need to confirm.

redpoint73 said:
That's because boot.img won't install in recovery with s-on (and hboot 1.14 or higher). But AROMA bypasses this, which is why I ask if Beastmode uses an AROMA installer or not. I think it does, but someone with actual experience with Beastmode will need to confirm.
Click to expand...
Click to collapse
Ahh, alright! But I see, that there is a Wifi issue with the Beastmode Kernel.
What about upgrading my HBoot to 2.15. Does that also solve my problem with data drops and reboots?
Is it safe to upgrade HBoot?

Kureno7 said:
What about upgrading my HBoot to 2.15. Does that also solve my problem with data drops and reboots?
Is it safe to upgrade HBoot?
Click to expand...
Click to collapse
Yes and yes
Sent from my VENOMized HoxL

Kureno7 said:
Ahh, alright! But I see, that there is a Wifi issue with the Beastmode Kernel.
What about upgrading my HBoot to 2.15. Does that also solve my problem with data drops and reboots?
Is it safe to upgrade HBoot?
Click to expand...
Click to collapse
The Beastmode kernel uses an aroma installer so you should be ok to flash it while s-on. A few people have reported WiFi problems but I personally never experienced this at all. The only way to find out is flash it, so I suggest doing that. You can always revert if you want to by dirty flashing ROM.
The 2.15 firmware package doesn't just update the hboot, it updates hboot, radio, WiFi modules, and media modules. You need s-off to update to the 2.15 firmware package.
All of this information is readily available in the Viper thread if you took the time to search properly.
Sent from my Evita

Kureno7 said:
What about upgrading my HBoot to 2.15. Does that also solve my problem with data drops and reboots?
Is it safe to upgrade HBoot?
Click to expand...
Click to collapse
I think you mean the 2.15 "firmware" package, which contains not only hboot, but also new radio, WiFi and media modules. Its the radio that seems to be the culprit, so only updating hboot will likely not solve the issue.
I personally feel this is a more comprehensive solution (update to 2.15 firmware), as it will persist even after flashing other ROMs; and its how I addressed the signal issue.
Yes, upgrading hboot is relatively safe. But be aware that any update of hboot (even on a stock device) carries a small chance of bricking the phone if for some reason the update does not go completely right (such as a corrupted file or interrupted flash). But the chances are very small.
---------- Post added at 11:40 AM ---------- Previous post was at 11:12 AM ----------
timmaaa said:
The Beastmode kernel uses an aroma installer so you should be ok to flash it while s-on.
Click to expand...
Click to collapse
Thanks for confirming.

I would suggest Going S-off Its not that hard to do and is so useful.
Beastmode RELOADED 3.5
-Updated aroma installer binaries
-Fixed module installation
When I was on ViperXL It fixed my wifi/data issues (Mostly)
Going s-off and AOSP is the way to go

Hey guys. I don't mean to hijack the thread at all but I'm got the same conundrum at the moment. Running Viper XL 4.2.0 on an unlocked Telstra One XL with Hboot 2.14. I've already tried flashing beastmode 3.5. to no success as I get a boot loop. So I'd preferably like to just get the phone to a complete stock state and then use the WinDroid all in one tool to get where I need to go; S-Off and SuperCID.

Counterflak said:
Hey guys. I don't mean to hijack the thread at all but I'm got the same conundrum at the moment. Running Viper XL 4.2.0 on an unlocked Telstra One XL with Hboot 2.14. I've already tried flashing beastmode 3.5. to no success as I get a boot loop. So I'd preferably like to just get the phone to a complete stock state and then use the WinDroid all in one tool to get where I need to go; S-Off and SuperCID.
Click to expand...
Click to collapse
You don't need to go to a stock state to get SuperCID and s-off, that's taking an unnecessarily long route. To get SuperCID you just need to use the hex edit method. To get s-off you'll probably need to flash an older ROM though as people on Android 4.2.2 have had many problems succeeding.
Sent from my Evita

After some research i found the "solution" for my problem with getting super cid.
My HOXL is branded from Vodafone and the guys from Vodafone "locked" the part in system where you can change the CID.
So it's read only.
Finally, there is no way to go S-Off for me i guess.. ):
Or have u guys other ways except of "Hex-Edit" and "All in one Tool" ?
Greetz!

timmaaa said:
You don't need to go to a stock state to get SuperCID and s-off, that's taking an unnecessarily long route. To get SuperCID you just need to use the hex edit method. To get s-off you'll probably need to flash an older ROM though as people on Android 4.2.2 have had many problems succeeding.
Sent from my Evita
Click to expand...
Click to collapse
Managed to pull the file and edit it ok, but I get the following went trying to push the file back I get the following:
Code:
[email protected]:/ # >dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
>dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
sh: can't create dd: Read-only file system
The last OTA I downloaded was the update that included a touch screen firmware before flashing Viper, but I believe this had some sort of write protection on it as well (Not sure where I read that, might have been on whirlpool) . Of course, the only way to downgrade it that I can find requires S-OFF as well as SuperCID.

Counterflak said:
Managed to pull the file and edit it ok, but I get the following went trying to push the file back I get the following:
Code:
[email protected]:/ # >dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
>dd if=/sdcard/mmcblk0p4 of=/dev/block/mmcblk0p4
sh: can't create dd: Read-only file system
The last OTA I downloaded was the update that included a touch screen firmware before flashing Viper, but I believe this had some sort of write protection on it as well (Not sure where I read that, might have been on whirlpool) . Of course, the only way to downgrade it that I can find requires S-OFF as well as SuperCID.
Click to expand...
Click to collapse
Haha same here mate! Hope one of the experienced members have a solution:crying:

Sorry for disturbing you again guys!
I tried the following ways:
Flash Viper 4.2.0 -> Flash boot.img = Bootloop
Flash Viper 4.2.0 -> Flash Beastmode 3.5 = Bootloop
Flash Viper 4.2.0 -> Flash Beastmode 2.0 -> Flash Beastmode 3.5 = Bootloop
Flash Viper 4.2.0 -> Flash Beastmode 2.0 -> Flash Beastmode 3.5 -> Flash Beastmode 2.0 boot.img = Bootloop
So I restored my data via Backup. Now I'm on Viper 3.2.8 again.
Does any1 of you know a great rom, that I can use on my HOXL, without going S-Off or updating Firmware?
What about this one:
http://forum.xda-developers.com/showthread.php?t=2064724
Is it possible to use AOKP on my phone? Or do I need to downgrade my touchscreen's firmware or stuff like that?
Thx 4 your help !

I believe those older builds of AOKP do require downgraded ts firmware, which in turn requires s-off. I'm puzzled as to why Viper is looping for you though, did you make sure the md5 was correct?
Sent from my Evita