[Q] [q] stupid question in regards to flash - AT&T, Rogers HTC One X, Telstra One XL

friend gave me his one X because his dialer and sms app force close when its used and says htc xxx is not responding. I have tried to reflash a new rom/ flash boot.img and the new rom installs and the same thing occurs. I know if i flash a default rom i will have to relock the BL but i will lose the ability to flash anything in the future?
some details you wil probably need on my screen
evita pvt ship S-on RL
S-ON( i have a feeling it has to do with this)
h-boot 1.09
radio 0.17.32
i have tried clean rom and viper rom and i get the same issue. suggestions?

all htc onexl are s-on so that isnt a problem. since the phone is already unlocked you have supercid. you could relock the bootloader "fastboot oem lock" and run the 1.85 ruu. then get another unlock token from htcdev or if he gave you his token use that.
since you came from 1.85 firmware you don't need to flash boot.img separate.
before ruu you could also make sure you have the newest twrp 2.3.1.0 evita on it. you could try fixing permissions in twrp. in fastboot you could run this command "fastboot erase cache". if you still have the problem try wiping everything in twrp and reflashing the rom.

DJSYNTHVIRUS said:
friend gave me his one X because his dialer and sms app force close when its used and says htc xxx is not responding.
Click to expand...
Click to collapse
This is a known symptom of Clockworkmod being used on the phone. Change recovery to TWRP, as previously recommended.

DvineLord said:
all htc onexl are s-on so that isnt a problem. since the phone is already unlocked you have supercid. you could relock the bootloader "fastboot oem lock" and run the 1.85 ruu. then get another unlock token from htcdev or if he gave you his token use that.
since you came from 1.85 firmware you don't need to flash boot.img separate.
before ruu you could also make sure you have the newest twrp 2.3.1.0 evita on it. you could try fixing permissions in twrp. in fastboot you could run this command "fastboot erase cache". if you still have the problem try wiping everything in twrp and reflashing the rom.
Click to expand...
Click to collapse
im going to fix permissions and see if i can reflash clean rom if that doesnt work i will try to update twrp then repeat. thanks for the help

hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP

redpoint73 said:
This is a known symptom of Clockworkmod being used on the phone. Change recovery to TWRP, as previously recommended.
Click to expand...
Click to collapse
can you suggest anything i cant figure out why its force closing like that? please and thank you

DJSYNTHVIRUS said:
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
Click to expand...
Click to collapse
Boot into bootloader, then select recovery. You'll be able to tell which one you have then.
---------- Post added at 02:53 PM ---------- Previous post was at 02:51 PM ----------
DJSYNTHVIRUS said:
can you suggest anything i cant figure out why its force closing like that? please and thank you
Click to expand...
Click to collapse
CWM is not supported by the HTC One X/XL. TWRP does, which is why you're having some issues. I would recommend flashing TWRP over before you flash anything else. Doing something wrong on CWM could lead you in the path of being a proud owner of a $500 paper weight.

DJSYNTHVIRUS said:
hmm i dont see a CWM icon anywhere in my OS? and i am using TWRP
Click to expand...
Click to collapse
If its always been on TWRP since you owned it, the previous owner may have had CWM on it, then switched to TWRP. I think (not sure) the problem persists even after switching.
Not sure, but I think some folks had to jump thru some hoops to clear this bug up, involving flashing (counter-intuitively) CWM, then a AOSP ROM, then TWRP. Let me see if I can find the thread.

redpoint73 said:
If its always been on TWRP since you owned it, the previous owner may have had CWM on it, then switched to TWRP. I think (not sure) the problem persists even after switching.
Not sure, but I think some folks had to jump thru some hoops to clear this bug up, involving flashing (counter-intuitively) CWM, then a AOSP ROM, then TWRP. Let me see if I can find the thread.
Click to expand...
Click to collapse
thnx to all of you, when booting into recovery i get into TWRP so it is most likely as you say my buddy who gave it to me most likely flashed CWM then TWRP , so your suggesting doing the above in that order?

Here it is. Look at post #7: http://forum.xda-developers.com/showthread.php?t=1846657
But I'd try to confirm if your friend ever had Clockworkmod on the phone. It sounds an awful lot like the bug from the thread above. But I don't want to send you down the wrong path, either.

ill try it thanks
QUOTE=redpoint73;33819696]Here it is. Look at post #7: http://forum.xda-developers.com/showthread.php?t=1846657
But I'd try to confirm if your friend ever had Clockworkmod on the phone. It sounds an awful lot like the bug from the thread above. But I don't want to send you down the wrong path, either.[/QUOTE]

Related

[Q] deleted htc framework file and phone doesnot start

deleted htc framework file and phone doesnot start.
After rooted my htc One X. In the process of removing at&t crap ware I accidentally deleted something that said htc frame work.
From then on my phone would not start. I unlocked my phone as well. How ever I didnot have any custom ROM installed or didnot have any back up done.
When I tried to reboot my phone after deleting the htc frame work file, it would not start. HTC icon would show up and it would not go further.
These are the things I did.
1. I flashed CWM.
2.I flashed TWRP.
3.I finally flashed CWM. 5.8.3
Then I went to fastboot mode and
removed Dalvik Cache, Erased the sd card
and tried to 'mount usb storage' but it would say
"unable to open ums lunfile(no such file or directory)SD card space free:10169MB"
My phone though shows as a removable disk , when i click on the icon it would say " Please insert disk into removable disk." I tried to save a custom ROM on my memory card and flash it but my system doesnot detect my phone.
Can some one please help me?
Thank you.
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Lock bootloader run ruu start over. Next time the very first thing you do is make a nandroid back up.
redpoint73 said:
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Thanks for the quick reply.
When I tried to mount my phone as usb it would not. I mentioned that as well.
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online. Without installing a custom ROM and run RUU , do you think my phone works
Adding a note to it. my phone is s-on and did not have android sdk installed on my machine. i tried all this using fastboot files and twrp img.
Thank You
in00b said:
When I tried to mount my phone as usb it would not.
Click to expand...
Click to collapse
You mentioned you tried to mount USB using fastboot (I've never mounted USB using fastboot, so I can't comment on that). Try mounting USB within TWRP, and see if that works. FYI, the USB mount feature in CWM does not work, and CWM does not really support our device, and has major issues. That's why its strongly recommended you use TWRP and not CWM.
in00b said:
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online.
Click to expand...
Click to collapse
Website seems to be too busy now. As long as its not 2.20, it should be okay. Normally, I would caution against randomly searching around the internet for things and flashing them, and instead getting them here instead. But briefmobile is Kenneth Penn's website, and he is a known developer on XDA.
in00b said:
Without installing a custom ROM and run RUU , do you think my phone works
Click to expand...
Click to collapse
You deleted part of the OS, so I'd say no. It doesn't boot does it? Then it doesn't work.
Also, please click "Thanks" to the post that help you.
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
No, you can only have one recovery. Flash one, you overwrite whatever you had before.
in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
I'd stay away from CWM. I know it used to cause problems, but I don't know if it does anymore.
Most everybody here (in the One XL forums) prefer TWRP anyways.
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
in00b said:
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
Click to expand...
Click to collapse
Did you lock your bootloader before running the RUU?
Butters619 said:
Did you lock your bootloader before running the RUU?
Click to expand...
Click to collapse
nope my phone was boot loader unlocked and s-on.
in00b said:
nope my phone was boot loader unlocked and s-on.
Click to expand...
Click to collapse
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Butters619 said:
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Click to expand...
Click to collapse
thanks i will try unlocking my phone and get back to you.
in00b said:
how do i relock my phone.that doesnt turn on at all. all i see is htc screen and it wouldnt go any further.
Click to expand...
Click to collapse
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
qwertyaas said:
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
Click to expand...
Click to collapse
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
But in almost every thread things have to be said 2-3 times which is ridiculous
Butters619 said:
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Click to expand...
Click to collapse
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
in00b said:
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
Click to expand...
Click to collapse
See that thanks button. Go through this entire thread and press it for everyone who helped you (aka everyone). Especially gunny.
And remember, things that sound important (framework, build., etc...) typically are important random assassinations typically get the shooter in trouble
18th.abn said:
random assassinations typically get the shooter in trouble
Click to expand...
Click to collapse
lol
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
Butters619 said:
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
Click to expand...
Click to collapse
Maybe he's more a fan of the Butters cartoon character than he is Totoro?

Assistance with Flashing roms please.

My boot loader and phone is rooted.
AT&T Htc one X
I have tried to flash a couple roms + the boot.img but the device pauses at HTC splash screen (I DID clear caches)
but its constant and I have to go into Fastboot-Usb and reinstall the RUU in order to try again.
Does anyone have any ideas?
viprk24 said:
My boot loader and phone is rooted.
AT&T Htc one X
I have tried to flash a couple roms + the boot.img but the device pauses at HTC splash screen (I DID clear caches)
but its constant and I have to go into Fastboot-Usb and reinstall the RUU in order to try again.
Does anyone have any ideas?
Click to expand...
Click to collapse
why don't you start by reading this http://forum.xda-developers.com/showthread.php?t=1957193
If you have ruu'ed you have to root again and unlock your bootloader again.
What recovery did you install ?
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
viprk24 said:
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
Click to expand...
Click to collapse
did you flash a recovery yet and if so which one ? if you want help you need to give us some details ?
What rom did you try to flash ? How did you go about it ?
Thank the android gods it wasn't an international ROM.
Did you flash superuser or supersu. We will need a little more information in the steps you've taken. Can you make a list of the steps for us?
The link crappyvate sent is a great tool for help.
Sent from my One X using xda premium
viprk24 said:
My bootloader is unlocked and my phone is rooted*
And I used TWRP or what ever its called. I can root fine and ez from it Trying to get Viperxl
Click to expand...
Click to collapse
Crappyvate said:
did you flash a recovery yet and if so which one ? if you want help you need to give us some details ?
What rom did you try to flash ? How did you go about it ?
Click to expand...
Click to collapse
apparently he did and some did not read the information
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
CheesyNutz said:
apparently he did and some did not read the information
Click to expand...
Click to collapse
surprise...that would be a first
---------- Post added at 11:07 PM ---------- Previous post was at 11:05 PM ----------
subarudroid said:
Thank the android gods it wasn't an international ROM.
Did you flash superuser or supersu. We will need a little more information in the steps you've taken. Can you make a list of the steps for us?
The link crappyvate sent is a great tool for help.
Sent from my One X using xda premium
Click to expand...
Click to collapse
don't think so since apparently he still gets the htc splash screen but need more info.
viprk24 said:
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
Click to expand...
Click to collapse
what exactly is it doing im not understanding is it freezing ? just not installing what error code is it giving
Are you flashing the boot image for your ROM in adb?
Sent from my One X using xda premium
viprk24 said:
I have flashed TWRP recovery or what ever I have installed Supersu successfuly and full root. I restarted booted into recovery now and wiped system cleared cache now I'm going to attempt to flash it one more time.
Click to expand...
Click to collapse
ok. i'm not gonna beg if you want help I need DETAILS not vague s***t like "TWRP or whatever".. So evidently you can boot into recovery with no problem. What rom are you trying to flash ? You need to extract the boot.img from the rom.zip and flash that in fastboot and then flash the rom.zip in recovery.
If you're not booting it's most likely because your phone is not finding a kernel (boot.img)
So more details or more reading
Good luck to you
Crappyvate said:
ok. i'm not gonna beg if you want help I need DETAILS not vague s***t like "TWRP or whatever".. So evidently you can boot into recovery with no problem. What rom are you trying to flash ? You need to extract the boot.img from the rom.zip and flash that in fastboot and then flash the rom.zip in recovery.
If you're not booting it's most likely because your phone is not finding a kernel (boot.img)
So more details or more reading
Good luck to you
Click to expand...
Click to collapse
from what i can make out
hes flashed the boot.img
installed twrp
superSU
but with no details on what ERROR its giving we as a help teams are FUBARD
CheesyNutz said:
from what i can make out
hes flashed the boot.img
installed twrp
superSU
but with no details on what ERROR its giving we as a help teams are FUBARD
Click to expand...
Click to collapse
not sure the boot.img was flashed the right way...or in the right place
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
viprk24 said:
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
Click to expand...
Click to collapse
Its not a good idea to ask for help and then flame. Honestly what was hard about posting this the first time? I thought maybe English wasn't your language or something. How could you flash a recovery before unlocking???
If you wiped everything, you should reflash bootimage in adb. Then flash your ROM. Please be nice.
Sent from my One X using xda premium
viprk24 said:
Calm down trolls I simply said
I flashed TRWP
Flashed Supersu
Flashboot oem unlock (Successful)
Relaunched back into bootloader
I fastboot boot.img
Then to Recovery where I Cleared cache and wiped System.
I then reflashed recovery because i wiped system.
I relaunched back into recovery and flashed rom
Click to expand...
Click to collapse
yea bash the folks attempting to help you ... thats like biting the hand that feeds you .. im out have fun
CheesyNutz said:
yea bash the folks attempting to help you ... thats like biting the hand that feeds you .. im out have fun
Click to expand...
Click to collapse
likewise. Over and out.

[Q] Cannot find the resources to undo this soft brick.

I have an AT&T HTC One x. Its ***Tampered*** ***Unlocked*** HBOOT 1 .09. 0000 S-ON
I had been running an older version of TWRP, and decided I was going to clear my phone and do a fresh start. I know, I know, I should have made a backup, but I felt pretty confident in what I was doing, and was in too much of a hurry to rationalize this.
I wiped both the OS and previous version of TWRP in order to update to the new ones. While in fastboot I flashed CLEANrom and the new version of TWRP, and my administrative command prompt confirmed that they were installed successfully. Even cleared the cache afterwards. Now is the difficult part. I've researched, and researched, and cannot find a solution for this problem. I keep having a Boot Loop.... I'm stumped guys... I need some sort of help, be it technical, or something to drink lol
Previous ROM was CM 10, with TWRP and PA GAPPS :good:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
timmaaa said:
Check the Evita FAQ thread in my signature, your answer probably lies within.
Sent from my Evita
Click to expand...
Click to collapse
I don't see anything in your FAQ that I haven't already tried unfortunately.....
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
timmaaa said:
Exactly which version of TWRP is currently installed? Did you flash the boot.img via fastboot?
Sent from my Evita
Click to expand...
Click to collapse
It's the newest version of TWRP that is out, and yes, I flashed it via Fastboot, and it says successful on both the recovery install and ROM install.
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
1332858898
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
Click to expand...
Click to collapse
TWRP 2.7. And yes, I have flashed about 4 Roms all succeeded according to fastboot and still getting the boot sequence.:good:
Yes I have extracted the boot.img
timmaaa said:
Have you tried flashing another ROM? I asked for the exact recovery version for a reason, please provide that information.
Sent from my Evita
---------- Post added at 03:48 PM ---------- Previous post was at 03:43 PM ----------
Also it isn't completely clear to me that you're flashing the boot.img from the ROM zip via fastboot after flashing the ROM in TWRP. Are you extracting the boot.img from the ROM zip and doing that or not?
Sent from my Evita
Click to expand...
Click to collapse
yes the boot.img file was extracted. I get a confirmation that it was successful when I flash it on fastboot
Exactly which ROMs have you tried to flash?
Sent from my Evita
timmaaa said:
Exactly which ROMs have you tried to flash?
Sent from my Evita
Click to expand...
Click to collapse
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
outcold32 said:
CM 10.2, CM 11, CLEANrom 7.0. all via fastboot with confirmations.
Click to expand...
Click to collapse
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
exad said:
Why are you flashing roms via fastboot? -_- You're making your life difficult. Wipe everything in TWRP then flash in TWRP. ALso, you should really s-off and update your firmware/hboot. via RUU. You will likely encounter issues running a newer software on an such an old firmware.
Click to expand...
Click to collapse
If you would have read the thread, you would have noticed, that I am in bootloop, therefor I cannot access the recovery. And I have to have access to the ROM on my phone in order to flash anything via TWRP so this is moot. My question isn't how to flash roms, it's why am I getting a loop when I am successful on a clean partition and clean flash of both the recovery and ROM? And to me, fastboot is way easier than TWRP. I guess I could get a UART and try to debug the sequence myself, but I have more important things to do than that. I was posting to see if anyone had any similar problems. And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place. I ran the RUU after I re-locked the bootloader, and I'm at least out of the loop. I'm just going get to a more stable version so that this process will be more streamline when I re do my unlock and stuff.
So I guess the only solution at this point I have for any problem like this is to use the proper RUU. I tried a couple of times with no success, and it seemed the charm was to re lock the bootloader ( Fastboot oem lock) in order to properly and successfully get the RUU to work.:good:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
exad said:
Wth are you even on about? Of course you can access recovery in a bootloop. How are you getting to fastboot without accessing the bootloader? from the bootloader you can access recovery. If recovery isn't loading SCREW flashing a rom, reflash your recovery, 2.7 TWRP preferably. and then boot to recovery, mount your USB, copy the rom and flash it. Recovery is more important than having a ROM.
I know what I am talking about, do you know what you're talking about?
FFS I am trying to help you, there's no reason for you to be an ass. You're having issues BECAUSE you're flashing your rom via fastboot. You cannot flash a rom via fastboot.
Click to expand...
Click to collapse
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Okie dokie. No point in arguing. You're right. I'm wrong. Glad it's all working now.
Sent from my One XL using xda app-developers app
outcold32 said:
You didn't read the thread. I'm not being an ass. The information is already there.I can not access the recovery at all. That's why I am in in this situation. And again, if you had read the whole thread, or the even the original post, you would know that I cannot access the recovery. The only reason I'm being as detailed as I am is so I don't have to repeat myself, as well as for other people who may encounter this problem. And Yes I know what I am talking about. If I didn't I probably wouldn't have gotten to this point, right?
Click to expand...
Click to collapse
Exad is right in saying that the reason you're having problems is because you're attempting to flash ROMs with fastboot. That isn't how it's done. The correct way is to flash your ROM with recovery. You're barking up the wrong tree, not only that but you're arguing with experienced people who are only attempting to help get you out of the mess that you've gotten yourself into. You came here for advice, but there's no point in asking for advice if you're just going to argue and dismiss what you're being told to do.
You said you can't access your ROM so you can't flash anything, that makes absolutely no sense, which leads me to believe you don't really know what you're doing. Get out of the mindset that you need to use fastboot, it's wrong. You're dealing with people who have extensive and intimate knowledge of this device, trust us, we know what we're talking about.
Exactly why can't you access recovery? If you can issue fastboot commands that means you can access your bootloader, if you can access your bootloader that means you can use your volume keys to scroll through the options and the power button to select recovery. What happens when you do that? Exactly which recovery have you flashed to your device? I need to the full filename of the recovery that you've flashed.
Sent from my Evita
outcold32 said:
And this phone is an original model and I haven't really bothered with the security off, since I only wanted to get rid of sense in the first place. It was unlocked well before any commercial unlocker was available for the evita(Literally no stable CM10 at all at the time), so it's a little finicky in the first place.
Click to expand...
Click to collapse
S-on is a downright dangerous place to be, if the phone is also SuperCID (which is very likely, since its the AT&T variant). exad is right in recommending s-ff, as he is about a good many things.

[Q] Help: stucked TAMPERED LOCKED S-ON

Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
VictorCic said:
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
Click to expand...
Click to collapse
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
old.splatterhand said:
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
Click to expand...
Click to collapse
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
VictorCic said:
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
Click to expand...
Click to collapse
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
old.splatterhand said:
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
Click to expand...
Click to collapse
Im sorry That error is from the twrp recovery when i try to install superuser.. It says unable to mount int sd.. I think internal memory
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
old.splatterhand said:
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
Click to expand...
Click to collapse
Sorry i had update it to 4.2.2
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
old.splatterhand said:
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
Click to expand...
Click to collapse
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
VictorCic said:
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
Click to expand...
Click to collapse
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
VictorCic said:
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
Click to expand...
Click to collapse
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
VictorCic said:
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
Click to expand...
Click to collapse
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
old.splatterhand said:
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
Click to expand...
Click to collapse
Also system yes. And if i wiped the internal sd?
anyway after installing the rom, from twrp internal storage is 0 MB
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
old.splatterhand said:
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
Click to expand...
Click to collapse
Yes, used the latest TWRP recovery.
the recovery say to me no md5 file, is this the problem?
How can I check the md5 now?
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
old.splatterhand said:
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
Click to expand...
Click to collapse
Checked, the codes matches..
Then i think your device has a defect
old.splatterhand said:
Then i think your device has a defect
Click to expand...
Click to collapse
Hi, i managed to change the motherboard, so trying to put a mod, the phone now stuck on the htc logo...
I unlocked it with htcdev, then installed the recovery but this one doesn't work, it says starting recovery but doesn't start..(trying to install a different recovery, it seems unable to rewrite it)
trying to do something i flashed with fastboot the stock boot.img and now the phone doesn't start anymore..
what can i do now? :crying:

[Q] one xl bricked need help

I have a one xl cid rogers001 hboot 2.14, baseband 0.23a.3 2.09.29.... jb 4.1 with sense 4+
I tried unlock bootloader by htcdev => ok
install recovery => ok. and when i installed this rom: http://forum.xda-developers.com/showthread.php?t=1868236, it was stuck in bootloader. i fogot root my phone before.
so i relock my device, and tried to flash this stock rom using adb : OTA_EVITA_UL_JB_45_S_Rogers_WWE_3.17.631.2_0.23a.3 2.09.29_10.128.32.34a_release_299850qstr7rxdbfuofl 6j.zip (was found in this thread: http://forum.xda-developers.com/showthread.php?t=2119610)
On cmd via fastboot i type fastboot erase cache =>ok
fastboot oem rebootRUU => ok
fastboot flash zip "filename.zip" It says " (remote: 12 signature verify fail") in the end cmd
What should i do now?
Thanks for reading and help me pls!!!!
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
timmaaa said:
Ok, first mistake is that you thought you needed to be rooted to flash the Viper ROM, you don't. All you need is an unlocked bootloader and custom recovery, which you had. You were probably stuck in the bootloader because you forgot to flash the boot.img from the ROM zip with fastboot, you need to do this because you're s-on.
The next mistake you made was attempting to flash an OTA. I don't know what made you think that you could do that but it definitely wasn't found in this forum (or anywhere for that matter). An OTA is only a partial OS, it relies on the correct stock OS to already be installed on the device to build on top of to update the existing OS. It failed for obvious reasons.
Unlock your bootloader again, flash a custom recovery again, and flash the ROM again. Make sure you flash the boot.img this time and it should boot right up. I'd strongly recommend you read the Evita FAQ thread and the How-To Guide For Beginners thread in my signature. Diving into modifying your device without the proper level of knowledge is a really bad idea.
Sent from my Evita
Click to expand...
Click to collapse
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
somebody help me pls
veveve said:
somebody help me pls
Click to expand...
Click to collapse
Please be patient, we all have lives outside XDA.
veveve said:
fisrt, thanks for helping me. but i've flash boot boot.img file in .zip after i install rom from sdcard. after that, phone stuck in bootloader.
i've unlock bootloader and flash recovery again, and now it says can't mount sdcard. how can i copy viper rom into internal storage? sideload? flash zip? and after all, my phone still not root, can flash viper rom without root?
sorry for my english. thanks again!
Click to expand...
Click to collapse
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
timmaaa said:
Please be patient, we all have lives outside XDA.
Did you perform a factory reset from the bootloader at some point? If so you've corrupted your sd card, you should never perform a factory reset from the bootloader. If this is the case you'll need to use TWRP to wipe your sd card, then you should be able to mount it to Windows and use Windows Explorer to format. Once this is done you can for a ROM across again.
Exactly which build of Viper did you try to flash? What's the exact filename? Did you check the md5 before flashing?
Sent from my Evita
Click to expand...
Click to collapse
yes, i did it more than once, now it's fixed, but when i mount it to Windows using TWRP, nothing happen, so i can't format it. and the same things when i tried to sideload. But in fastboot mode, it usual.
and i flashed the newest rom in this thread: http://forum.xda-developers.com/showthread.php?t=1868236 ViperXL 4.2 and i didn't check the MD5
back to my previous question, can i fash a custom rom without root?
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
nem1yan said:
Yes, you can flash a custom Rom without root. He already answered that. I strongly recommend reading up on your device before flashing anything else. I'd suggest starting with getting your phone s-off.
Click to expand...
Click to collapse
I disagree. I think it's a better idea for him to get his head around the simple operations like flashing ROMs before attempting s-off.
Sent from my Evita
timmaaa said:
I asked for the exact filename of the ROM for a reason, I need that please. Also, exactly which recovery are you using?
Sent from my Evita
Click to expand...
Click to collapse
Full ROM:
Jelly Bean - Android 4.2.2 / Sense 5
ViperXL 4.2.0
Main Link: http://www.androidfilehost.com/?fid=23134718111254927
Mirror 1: http://goo.im/devs/Turge/ViperXL/ViperXL_4.2.0.zip
Mirror 2: http://d-h.st/z4Q
Click to expand...
Click to collapse
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/showthread.php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Thanks!
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
timmaaa said:
I know which ROM you're flashing, I need the filename, as it appears in your file browser or Windows Explorer or something. Like this:
Code:
Romname.zip
Sent from my Evita
---------- Post added at 01:19 AM ---------- Previous post was at 01:18 AM ----------
And you should always check the md5 of anything you're about to flash. You should do that now to make sure the file isn't corrupt.
Sent from my Evita
Click to expand...
Click to collapse
it is ViperXL_4.2.0.zip
i'll do it next time!
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
veveve said:
it is ViperXL_4.2.0.zip
i'll do it next time!
Click to expand...
Click to collapse
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
You might be onto something.
Sent from my Evita
timmaaa said:
Did you check the md5? Does it match?
Sent from my Evita
---------- Post added at 08:49 AM ---------- Previous post was at 08:49 AM ----------
You might be onto something.
Sent from my Evita
Click to expand...
Click to collapse
I mean, i didn't do it and i will do it next time
bzhmobile said:
No sure, but i think you need to have an older version of twrp to flash the Viper like 2.6.1.0...
Click to expand...
Click to collapse
thanks, i will try.
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
timmaaa said:
Make sure you check the md5 before flashing. A corrupt zip could brick your phone.
Sent from my Evita
Click to expand...
Click to collapse
but i still have trouble with mounting internal storage using TWRP on windows, should i try the older TWRP?
What version do you have installed?
Sent from my Evita
timmaaa said:
What version do you have installed?
Sent from my Evita
Click to expand...
Click to collapse
here
and at the first time, i used ClockworkMod Touch 6.0.2.8 Official from here: http://forum.xda-developers.com/show....php?t=2148909
after, i used this: twrp-2.7.0.8-evita.img
Click to expand...
Click to collapse

Categories

Resources