So in the process of trying to fix the Cyanogenmod install (it wouldn't go past the boot animation) I managed to erase all the data, including backups, on my phone. All I have left is the bootloader screen and TWRP 2.5.0.0. Is there any way I can fix this?
IamHERC said:
So in the process of trying to fix the Cyanogenmod install (it wouldn't go past the boot animation) I managed to erase all the data, including backups, on my phone. All I have left is the bootloader screen and TWRP 2.5.0.0. Is there any way I can fix this?
Click to expand...
Click to collapse
Plug into computer and enter twrp and hit the mount usb option to connect the phone to the computer and copy new Rom over.
Sent from my Elemental Sense 5 S-off HTC One XL
majortaylor said:
Plug into computer and enter twrp and mount the phone to the computer to see your phone and copy new Rom over.
Sent from my Elemental Sense 5 S-off HTC One XL
Click to expand...
Click to collapse
Thanks for the quick response. Should I try to copy cyanogenmod over download another ROM (maybe stock) to try?
IamHERC said:
Thanks for the quick response. Should I try to copy cyanogenmod over download another ROM (maybe stock) to try?
Click to expand...
Click to collapse
I'm personally on magio Rom and loving it but by all means choose whatever you want as there are many greats roms and devs here.
Sent from my Elemental Sense 5 S-off HTC One XL
majortaylor said:
I'm personally on magio Rom and loving it but by all means choose whatever you want as there are many greats roms and devs here.
Sent from my Elemental Sense 5 S-off HTC One XL
Click to expand...
Click to collapse
So I tried to do that and it failed.
It gives me these two errors: Error executing updater binary in zip [name of ROM] & Error flashing zip [name of ROM]
Here's what my bootloader says if that helps:
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.39.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
IamHERC said:
So I tried to do that and it failed.
It gives me these two errors: Error executing updater binary in zip [name of ROM] & Error flashing zip [name of ROM]
Here's what my bootloader says if that helps:
***TAMPERED***
***UNLOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.39.06
OpenDSP-v34.1.0.45.1219
eMMC-boot
Click to expand...
Click to collapse
What Rom are you trying to flash
Sent from my Elemental Sense 5 S-off HTC One XL
If you're trying to flash MagioROM it'll do that. Reboot recovery and try again.
Sent from my evita
RollTribe said:
If you're trying to flash MagioROM it'll do that. Reboot recovery and try again.
Sent from my evita
Click to expand...
Click to collapse
TWRP 2.5 was the "not good" TWRP version...right? I had trouble flashing Sense based ROMs with TWRP 2.5...same errors OP is getting. Flash CM, get set back up, go to OP of the Magio ROM and download & flash the 2.3 TWRP that Magio listed there.
Should be good to go to flash Sense based ROMs after that.
tropazr said:
TWRP 2.5 was the not very good TWRP version...right? I had trouble flashing Sense based ROMs with TWRP 2.5...same errors OP is getting. Flash CM, get set back up, go to OP of the Magio ROM and download & flash the 2.3 TWRP that Magio listed there.
Should be good to go to flash Sense based ROMs after that.
Click to expand...
Click to collapse
Or, get 2.6. No one has had any problems with it yet. Myself included.
Sent from my evita
RollTribe said:
Or, get 2.6. No one has had any problems with it yet. Myself included.
Sent from my evita
Click to expand...
Click to collapse
Correct. 2.3 works great for me though and its easily flashable for OP.
Your should be on twrp 2.6 & s off
Sent from my HTC One X using xda premium
The_Zodiac said:
Your should be on twrp 2.6 & s off
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Benefits of 2.6 vs 2.3? Also, would you like to explain to OP the steps of upgrading to TWRP 2.6? My solution was geared towards someone who calls himself a "n00b"....I am sure he can figure it out but I didn't feel like typing out all the steps. It's almost time for bed.
majortaylor said:
What Rom are you trying to flash
Sent from my Elemental Sense 5 S-off HTC One XL
Click to expand...
Click to collapse
Ive tried cyanogenmod 10.1 and that Magio ROM
RollTribe said:
If you're trying to flash MagioROM it'll do that. Reboot recovery and try again.
Sent from my evita
Click to expand...
Click to collapse
I tried your method and I'm still getting the same failed message. I've even tried sideloading the ROM
Did you change your recovery like suggested? Your recovery version is the problem.
Sent from my Evita
tropazr said:
Benefits of 2.6 vs 2.3? Also, would you like to explain to OP the steps of upgrading to TWRP 2.6? My solution was geared towards someone who calls himself a "n00b"....I am sure he can figure it out but I didn't feel like typing out all the steps. It's almost time for bed.
Click to expand...
Click to collapse
They are on 2.5 which typically has issues.
2.6 is new and shiny.
Lol me neither
Sent from my HTC One X using xda premium
Yeah I think his point was that there is a flashable zip available for 2.3 though, which might be easier for a noob to get done lol. I'd still suggest 2.6 because the wipe feature is better than on 2.3, I'm more than happy to walk the OP through how to flash 2.6
Sent from my Evita
timmaaa said:
Yeah I think his point was that there is a flashable zip available for 2.3 though, which might be easier for a noob to get done lol. I'd still suggest 2.6 because the wipe feature is better than on 2.3, I'm more than happy to walk the OP through how to flash 2.6
Click to expand...
Click to collapse
Agree. The best way to remove yourself from the "n00b" category is to learn how to use critical tools like fastboot/adb, instead of taking the easy way out.
timmaaa said:
Did you change your recovery like suggested? Your recovery version is the problem.
Sent from my Evita
Click to expand...
Click to collapse
I did and it worked. Thanks for your help guys!
Now I'm trying to get S-Off but when I do the "adb push soffbin3 /data/local/tmp/" command i get:
"adb server out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error: "
I found a thread where someone else had this problem so I'll go there.
Related
I didn't have this problem before.But now everytime i flash a cm rom,it flashes with no problems but when it finishes flashing and i reboot,it gets stuck on the htc logo,then reboots and does the same and the same all over again till the battery dies.I tried getting on recovery mode/bootloader but it doesnt seem to work.It's kinda as if the buttons didn't work.This happened to me already 2 days ago and fixed it,but had to wait till the battery died,then connect to pc,that way my phone was somehow reconized and i was able to adb(even though i wasn't on recovery or bootloader,just plugged to the pc)
what is causing this problem with cm roms?what should i do?
Do I need to downgrade/upgrade my hboot or something?
Thank you guys,and sorry for my english.
avlbj6 said:
I didn't have this problem before.But now everytime i flash a cm rom,it flashes with no problems but when it finishes flashing and i reboot,it gets stuck on the htc logo,then reboots and does the same and the same all over again till the battery dies.I tried getting on recovery mode/bootloader but it doesnt seem to work.It's kinda as if the buttons didn't work.This happened to me already 2 days ago and fixed it,but had to wait till the battery died,then connect to pc,that way my phone was somehow reconized and i was able to adb(even though i wasn't on recovery or bootloader,just plugged to the pc)
what is causing this problem with cm roms?what should i do?
Do I need to downgrade/upgrade my hboot or something?
Thank you guys,and sorry for my english.
Click to expand...
Click to collapse
If you can get into bootloader try flashing the boot.img via fastboot
ronnie498 said:
If you can get into bootloader try flashing the boot.img via fastboot
Click to expand...
Click to collapse
I can't get into bootloader
If you have adb access, what happens when you do:
Code:
adb reboot bootloader
hi_cannon said:
If you have adb access, what happens when you do:
Code:
adb reboot bootloader
Click to expand...
Click to collapse
He won't have adb access because that requires the phone to be booted into the OS.
Sent from my Evita
then connect to pc,that way my phone was somehow reconized and i was able to adb
Click to expand...
Click to collapse
:fingers-crossed:
hi_cannon said:
If you have adb access, what happens when you do:
Code:
adb reboot bootloader
Click to expand...
Click to collapse
my question wasnt "how to get adb access" or "how to get to recovery/bootloader"..I just wanted to know why my phone is having problems with those roms.It works fine with sense based roms but not with cm based.
avlbj6 said:
my question wasnt "how to get adb access" or "how to get to recovery/bootloader"..I just wanted to know why my phone is having problems with those roms.It works fine with sense based roms but not with cm based.
Click to expand...
Click to collapse
Did you run the 3.18 RUU?
What hboot and firmware version are you on?
Sent from my Evita
Hboot 1.09
Sent from my HTC One XL using Tapatalk 2
hi_cannon said:
Did you run the 3.18 RUU?
Click to expand...
Click to collapse
No I didn't.is that so?
Sent from my HTC One XL using Tapatalk 2
timmaaa said:
What hboot and firmware version are you on?
Sent from my Evita
Click to expand...
Click to collapse
Hboot 1.09
Sent from my HTC One XL using Tapatalk 2
odd problem until now since newest aosp need 3.18 base or 2.14 hboot.
I keep confusing quote with reply smh lol
DvineLord said:
odd problem until now since newest aosp need 3.18 base or 2.14 hboot.
Click to expand...
Click to collapse
So which ruu 3.18 should I use?do you have a link?also,should I upgrade the hboot?
Sent from my HTC One XL using Tapatalk 2
avlbj6 said:
So which ruu 3.18 should I use?do you have a link?also,should I upgrade the hboot?
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
This is the 3.18 RUU, it'll also update your hboot to the latest (2.14), so you don't need to do that manually:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You will need to s-off first though, here's the link:
http://forum.xda-developers.com/showthread.php?t=2155071
So flash a Sense ROM like MagioRom Sense 5, Viper, Hatka, Cleanrom, or one of the stock Sense ROMs. Then get s-off using the method I linked to above. Then run the RUU. Then you should be good to go.
Sent from my Evita
timmaaa said:
This is the 3.18 RUU, it'll also update your hboot to the latest (2.14), so you don't need to do that manually:
http://dl3.htc.com/application/RUU_..._10.130.32.34_release_signed_With_Partial.exe
You will need to s-off first though, here's the link:
http://forum.xda-developers.com/showthread.php?t=2155071
So flash a Sense ROM like MagioRom Sense 5, Viper, Hatka, Cleanrom, or one of the stock Sense ROMs. Then get s-off using the method I linked to above. Then run the RUU. Then you should be good to go.
Sent from my Evita
Click to expand...
Click to collapse
Thanks man.And I'm already s-off and I been running magiorom since he released it.But ima do the ruu part now
Sent from my HTC One XL using Tapatalk 2
Hi guys,
I was flashing sense 5 3.6+ota updates on my Rogers Evita, i had 3.5 before and it all went well surprisingly.
now i flash TWRP for evita 2.6 as recommended, i was able to get in, clean cache, flash ROM, flash the new boot.img as suggested, and got stuck on a bootloop.
Tried going back in TWRP, and now i see the Teamwin screen, then to htc screen than hangs.
I tried version 2.5 and 2.6 of TWRP get same results, same with clockwork. So My guess is that my problem doesnt come from the recovery file, but elsewhere ..
Current phone status:
S-On
Hboot 2.14
Radio 0.23a
Thanks!
xatomicx said:
Hi guys,
I was flashing sense 5 3.6+ota updates on my Rogers Evita, i had 3.5 before and it all went well surprisingly.
now i flash TWRP for evita 2.6 as recommended, i was able to get in, clean cache, flash ROM, flash the new boot.img as suggested, and got stuck on a bootloop.
Tried going back in TWRP, and now i see the Teamwin screen, then to htc screen than hangs.
I tried version 2.5 and 2.6 of TWRP get same results, same with clockwork. So My guess is that my problem doesnt come from the recovery file, but elsewhere ..
Current phone status:
S-On
Hboot 2.14
Radio 0.23a
Thanks!
Click to expand...
Click to collapse
Boot to fastboot and type
Fastboot erase cache. That will probably get you into twrp
Sent from my HTC One XL using xda premium
31ken31 said:
Boot to fastboot and type
Fastboot erase cache. That will probably get you into twrp
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
That worked for the bootloader, so far so good.
I'm back to bootlooping, probably need a different boot image. Flushed the whole SD started from scratch, and still bootlooping hehe
xatomicx said:
That worked for the bootloader, so far so good.
I'm back to bootlooping, probably need a different boot image. Flushed the whole SD started from scratch, and still bootlooping hehe
Click to expand...
Click to collapse
Rom includes boot image. Reflash the rom. Then fastboot flash the boot.img from the rom. You just installed, wipe cache, and dalvik. A factory reset after woukdnt hurt either
Sent from my HTC One XL using xda premium
31ken31 said:
Rom includes boot image. Reflash the rom. Then fastboot flash the boot.img from the rom. You just installed, wipe cache, and dalvik. A factory reset after woukdnt hurt either
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah i always flash the rom included in the zip file, thats why i'm surprised about bootlooping.
This may sound silly, but you're flashing 3.6 on top of r3 right?
Sent from my Evita
xatomicx said:
Yeah i always flash the rom included in the zip file, thats why i'm surprised about bootlooping.
Click to expand...
Click to collapse
Did you verify the md5 of the downloads? Could be a corrupted file
Sent from my HTC One XL using xda premium
timmaaa said:
This may sound silly, but you're flashing 3.6 on top of r3 right?
Sent from my Evita
Click to expand...
Click to collapse
Yes i am
I tried Cyanogen, just for fun of trying another room, i get the same boot freeze as with Sense 5
I don't know why it's looping, it shouldn't be if you're following the correct procedure. Are you doing a full wipe, then flashing the ROM, and then flashing the boot.img from that ROM in fastboot?
Sent from my Evita
What does it say in the bootloader screen? Just the top part don't post your imei.
Sent from my HTC One XL using xda premium
31ken31 said:
What does it say in the bootloader screen? Just the top part don't post your imei.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah, it doesnt bootloop anymore, it hangs now.
And i am closely following steps for rom installation, i wipe the whole shazam, cache and dalvik and such, it always worked well, until now.
Bootloader screen
Tampered
Unlocked
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
Radio-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
So you're wiping system/factory reset/cache/dalvik cache? Then flashing ROM, then rebooting to bootloader and flashing boot.img?
Sent from my Evita
xatomicx said:
Yeah, it doesnt bootloop anymore, it hangs now.
And i am closely following steps for rom installation, i wipe the whole shazam, cache and dalvik and such, it always worked well, until now.
Bootloader screen
Tampered
Unlocked
Evita PVT SHIP S-ON RL
HBOOT-2.14.0000
Radio-0.23a.32.09.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Click to expand...
Click to collapse
Did you flash boot.img from the rom after installing it? If not it will never boot being your s-on and on hboot 2.14
Fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
31ken31 said:
Did you flash boot.img from the rom after installing it? If not it will never boot being your s-on and on hboot 2.14
Fastboot flash boot boot.img
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah, i am always flashing the boot included in roms, but somehow my bootloader always show 2.14 after flashing ... that might be why i cant get it to work
Your bootloader will always show 2.14 unless you get a firmware update. Flashing ROMs does not change your hboot.
Sent from my Evita
timmaaa said:
Your bootloader will always show 2.14 unless you get a firmware update. Flashing ROMs does not change your hboot.
Sent from my Evita
Click to expand...
Click to collapse
Well anyone knows what's the solution? flashing the embedded boot.img did not help.
It's really difficult to diagnose the problem without actually being there. Can you please provide a detailed step-by-step account of what you're doing when you flash the ROM and boot.img.
Sent from my Evita
timmaaa said:
It's really difficult to diagnose the problem without actually being there. Can you please provide a detailed step-by-step account of what you're doing when you flash the ROM and boot.img.
Sent from my Evita
Click to expand...
Click to collapse
Sure,
1 log in twrp
2 wipe cache / dalvik
3 flash rom + updates
4 wipe cache again
5 log on fastboot usb
6 pull off boot.img from rom .zip
7 fastboot flash boot boot.img
8 hit reboot in bootloader
9 system hangs
xatomicx said:
Sure,
1 log in twrp
2 wipe cache / dalvik
3 flash rom + updates
4 wipe cache again
5 log on fastboot usb
6 pull off boot.img from rom .zip
7 fastboot flash boot boot.img
8 hit reboot in bootloader
9 system hangs
Click to expand...
Click to collapse
What version of twrp you using?
Edit: I see 2.6
What version of cm did you try? See if you can get Scott's clean rom booted. That one has flashed and booted for a couple other people having issues. And make sure you verify md5 before you flash it
Sent from my HTC One XL using xda premium
31ken31 said:
What version of twrp you using?
Edit: I see 2.6
What version of cm did you try? See if you can get Scott's clean rom booted. That one has flashed and booted for a couple other people having issues. And make sure you verify md5 before you flash it
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
i tried nightly 10.1
And sense 5 3.6,
i am now on sense 5 3.6, flash the 3 first, then 3.6 and 3.6.1
ill see for your "scott's clean rom", never heard of it, will try.
Hey Guys,
This is my first post, so excuse me if I sound like I don't know what I'm talking about.
a few days ago i tried to connect to my wifi at home and it was not picking it up although i was inside my own house. so i thought i should restart my phone. well after trying to restart it it got stuck in a boot loop. it would load the htc screen then start loading the venom logo then it shuts off and reboots the htc screen. i tried installing the back up, re installing the latest venom rom and even trying to put on a entire new rom but nothing has worked(it wont even let me install a new rom it errors out when i try) i doubt you will even get this but its my last effort Ive spent the entire day and all night looking for some way to fix this but i have yet to find anything. please if anyone one has any know how about this i could really used the help. i rooted my att htc one xl(evita) about 7 months ago using the method from onexroot.com and have never had an issue with this phone till now.
when i try to install a new rom via twerp it said install failed, im really stuck with this and could use some help thanks in advance.
just incase its not clear the phone is rooted running a custom rom(team venom) and im using twerp as my recovery program
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendep-v29.1.0.45.0622
emcc-boot
not sure if that helps at all
dtk0kai said:
Hey Guys,
This is my first post, so excuse me if I sound like I don't know what I'm talking about.
a few days ago i tried to connect to my wifi at home and it was not picking it up although i was inside my own house. so i thought i should restart my phone. well after trying to restart it it got stuck in a boot loop. it would load the htc screen then start loading the venom logo then it shuts off and reboots the htc screen. i tried installing the back up, re installing the latest venom rom and even trying to put on a entire new rom but nothing has worked(it wont even let me install a new rom it errors out when i try) i doubt you will even get this but its my last effort Ive spent the entire day and all night looking for some way to fix this but i have yet to find anything. please if anyone one has any know how about this i could really used the help. i rooted my att htc one xl(evita) about 7 months ago using the method from onexroot.com and have never had an issue with this phone till now.
when i try to install a new rom via twerp it said install failed, im really stuck with this and could use some help thanks in advance.
just incase its not clear the phone is rooted running a custom rom(team venom) and im using twerp as my recovery program
evita pvt ship s-on rl
hboot-1.14.0002
radio-0.19as.32.09.11_2
opendep-v29.1.0.45.0622
Click to expand...
Click to collapse
flash twrp 2.6 advanced wipe everything except sd card, reflash.
also since youre s-on you have to extract the boot.img from the rom zip and flash it with fastboot after flashing most roms. should not be the case with viper but i would do it anyway if vier doesn't boot after the above steps.
fastboot flash boot boot.img
reply
exad said:
flash twrp 2.6 advanced wipe everything except sd card, reflash.
Click to expand...
Click to collapse
this is going to sound bad but how do i do that again? i really dont remember how to flash twerp
dtk0kai said:
this is going to sound bad but how do i do that again? i really dont remember how to flash twerp
Click to expand...
Click to collapse
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.
exad said:
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.
Click to expand...
Click to collapse
ok im going to go try that ill post results
exad said:
download: http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.6.0.0-evita.img
Place img in your fastboot folder
put phone in hboot/fastboot mode
open command prompt within fastboot folder (shift right click - open command prompt here)
fastboot flash recovery openrecovery-twrp-2.6.0.0-evita.img
navigate to recovery in hboot menu, select recovery.
Click to expand...
Click to collapse
when you say reflash you mean my rom right?
Yep
Sent from my HTC One XL using xda app-developers app
exad said:
Yep
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
when flashing my rom it said error kernal not installed but then it said new rom flashed successfully will that be a problem?(viperxl-3.2.7)
exad said:
Yep
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
well so far nothing has changed.
Like Exad said, you're s-on so you need to manually flash the boot.img from the ROM using fastboot.
Sent from my Evita
timmaaa said:
Like Exad said, you're s-on so you need to manually flash the boot.img from the ROM using fastboot.
Sent from my Evita
Click to expand...
Click to collapse
yea i tried that too nothing changed
off to bed still no luck loads part of the viper logo and then resets back to htc screen x.x
dtk0kai said:
yea i tried that too nothing changed
off to bed still no luck loads part of the viper logo and then resets back to htc screen x.x
Click to expand...
Click to collapse
Try running an RUU. This fault (or at least a very similar fault) happened with my fiance's phone and now there's only one ROM that will boot on it (an old build of cm10.1). You may be facing a hardware fault (that's what's wrong my fiance's phone), but I'd suggest running an RUU to see if that helps.
Sent from my Evita
You might brick if you ruu, I would try flashing other roms first. Make sure to check the md5 to make sure that the download isn't corrupt.
But
If you must ruu make sure it isn't 3.18. And you will have to change your cid back and relock.
Fastboot oem writecid CWS__001
To change your cid back.
If you ruu, you cannot ever the the 3.18+ ota until you reroot and achieve s-off
Sent from my HTC One XL using xda app-developers app
exad said:
Nononono he's s-on remember! He might brick of he RUUs
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Oh gosh, my bad, I'm having a weird day today.
Sent from my Evita
Well so long as it's not 3.18 it Should be OK I think?
Sent from my HTC One XL using xda app-developers app
exad said:
Well so long as it's not 3.18 it Should be OK I think?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
so i should just try a diffrent rom? when doing that i should flash the boot img using fastboot then install the rom and then do a cache whipe correct?
Did you Wipe system in advanced Wipe last time before flashing the rom?
For any rom you ever flash always follow the steps I layer out in my earlier post. It will not be different for any rom.
Sent from my HTC One XL using xda app-developers app
exad said:
Did you Wipe system in advanced Wipe last time before flashing the rom?
For any rom you ever flash always follow the steps I layer out in my earlier post. It will not be different for any rom.
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
yes i did the entire wipe just like you said then installed the rom like you said and it started up and loaded the venom screen longer but then restarted, im going to try flashing the cm 10 and see if that dose anything
now cm10 is in a boot loop after i tried to flash gapps
Try flashing the 20130304 build from the get.cm/evita page.
Sent from my Evita
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
Hey guys,
I have an HTC One X with the bootloader unlocked that has Venom Viper installed on it and I want to S-OFF the phone so that I can install the beast mode kernel. I want to do this because the phone has some issues like a dropping SIM card and random reboots. I have another friend with the same phone that I installed Viper on and she had the same issues. I over the phone talked her through the S-OFF method and once we finally got it and installed the kernel the phone worked perfectly.
One thing that was odd is that the method (FacePalm) wasn't working until we flashed the phone back to stock (not a backup but a stock release with a flashable SU bin that was on XDA somewhere). Once we did that the phone was S-OFF after rebooting into the bootloader.
This time around though I'm starting to wonder whether the fact it worked when we flashed back to stock was a coincidence because I did the SAME EXACT THING with this current phone, flashed to the same stock rom with the same method of SU, and it just won't work. I run through the whole process and get no errors (except when you are supposed to) and when I reboot into recovery it is not S-OFF. One thing I noticed though is that on another site it said "The last step is to confirm the SU request you get on your phone". I cannot remember if my friend got a popup but on this phone I never get one.
Therfore I am thinking the problem is with the flashable SU bin not working properly and was going to ask if anyone had their hands on a prerooted stock. There is a thread for one on here but the link is dead.
So basically does anyone have such a rom or know anything about the S-OFF method only working with stock or odex/deodex or something of that sort.
Thanks.
I got s-off with viper
Sent from my VENOMized HoxL
area51avenger said:
I got s-off with viper
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
I guess Ill just keep trying it. Did you use the files from xda?
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
timmaaa said:
Do you have the One X (Endeavoru) or the One XL (Evita)?
Sent from my Evita
Click to expand...
Click to collapse
Just the X (Endeavoru)
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
timmaaa said:
Ok you're in the wrong forum then, this is the One XL forum.
Sent from my Evita
Click to expand...
Click to collapse
Actually it is the XL I just forget its not called that. Im sure because its black, from AT&T, and not the international version.
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
timmaaa said:
The colour is irrelevant, but if it's from at&t you have the Evita. Are you sure you have superuser installed and usb debugging is enabled in developer options? Which Android version is the ROM you're using?
Sent from my Evita
Click to expand...
Click to collapse
Ya both because i saw the SU app and I used adb so debugging is enabled.
Android ver 4.2.2
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Ok thanks for the tip.
timmaaa said:
Downgrade to Android 4.0 or 4.1, people have had heaps of problems getting s-off while on a 4.2 ROM.
Sent from my Evita
Click to expand...
Click to collapse
Sigh. After trying to flash a 4.1.1 Rom the phone now boot loops and flashing any other rooms or restoring the TWRP backup (just system, boot, and data) that I had of viper have had no effect.
Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
Not during the first boot, but after I realized my error I rebooted into fastboot and did it. Is it imperative that its done before booting?
EDIT:
OK so I just tried flashing the stock rom I tried for S-OFF before and even flashed the boot.img and its still boot looping.
It pisses me off that the security system has to be this obnoxious. I'm used to my own samsung phones where theres barely any security and bricking is practically impossible with Odin.
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
timmaaa said:
It isn't obnoxious if you know what you're doing. You're s-on so you must flash the boot.img for each ROM every time you flash a ROM. Install ROM, reboot to bootloader, flash boot.img, reboot to system. Once you have s-off you will no longer need to do this. Are you flashing the right boot.img?
Sent from my Evita
Click to expand...
Click to collapse
Ok well, I changed ONE simple thing that I would think wouldn't matter, but apparently it does. Instead of rebooting after the rom flashing and then during the boot loop holding vol down and power to get into bootloader again, AND THEN flashing the boot.img, I simply hit home in twrp after flashing the room and used the "reboot" function to go directly to boot loader and then flashed the boot.img
The phone now got past the developer warning screen and is showing the htc one beats audio screen. However it now seems to be frozen there :|
This is the rom I used: http://forum.xda-developers.com/showthread.php?t=2181891
It is a step further at least, and now that I see how to properly flash the boot.img I will try a few other roms and see if they work any better, unless you have any other suggestions.
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
timmaaa said:
It looks as though you've done it correctly. Which recovery version are you using?
Sent from my Evita
Click to expand...
Click to collapse
2.6.3.0
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
timmaaa said:
Are you certain you're flashing the boot.img from the ROM you've just installed and not another one by mistake? TWRP 2.6.3 should be ok, but you could try 2.6 instead if you want to, I've seen a couple of bugs on 2.6.3 but I can't remember what they were.
Sent from my Evita
Click to expand...
Click to collapse
Yes I am sure. Ill try a different ROM snd if that doesn't work ill downgrade TWRP