I posted in the Q&A of the general One X forum and they told me to post my problem here.
I tried flashing CM10 mod on my One X and because I am a noob I omitted to do a backup of my phone when I wiped everything. I then proceeded as usual, flashed the boot.img then opened the zip to install CM10, then flashed boot.img again but it didnt work.
I don't know how but after that I successfully messed up my phone. I have no ROM, Lost TWRP, have no backup and the only thing I can use is Fastboot and Bootloader.
My phone lo longer appears on my computer so I cannot move files onto it.
I relocked my phone and flashed all the RUU's that I could find. Used the ARUwizard to try the PJ83IMG to no avail.
Every answer I found on the internet did not work so far and I'm getting desperate. Nothing seems to work. Is there a solution?
PS: Is it just me or is the rogers HTC One X harder and more complicated to mod than other versions of the phone? If I were to buy a new phone which one should I buy?
PPS: Buying a new phone is my last option. I do not want to resort to that. I will if I have to.
This is why 1 click unlocks are so bad for the community. People mindlessly unlock their phones and screw it up.
As for your situation, if you run a RUU successfully but your phone still won't boot then you're probably SOL. Go ask Niceppl and see if he can help you.
And no, Rogers is the easiest to mod. HTCDev supports Rogers HOX bootloader unlock. After that, the rest is the same.
thedauntlessone said:
This is why 1 click unlocks are so bad for the community. People mindlessly unlock their phones and screw it up.
As for your situation, if you run a RUU successfully but your phone still won't boot then you're probably SOL. Go ask Niceppl and see if he can help you.
And no, Rogers is the easiest to mod. HTCDev supports Rogers HOX bootloader unlock. After that, the rest is the same.
Click to expand...
Click to collapse
Everytime I try an RUU it says I have the wrong RUU for the device... I tried all of them that I could download. Do I need to do anything else before flashing the RUU maybe?
You didn't SuperCID which is essential for ATT RUU. Right now you basically have a phone with Rogers ID trying to install ATT RUU so it fails.
If you can't get 1.73 rogers RUU working then I have no clue what you can do.
Can you unlock the phone still from fastboot?
If you can have tried to reflash twrp from fastboot?
If it works you may be able to mount the sd card from twrp and move rom to your sd card and flash it.
Just throwing out some ideas since nothing you have tried has worked so far.
Sent from my Nocturnalized Beast
E.Cadro said:
Can you unlock the phone still from fastboot?
If you can have tried to reflash twrp from fastboot?
If it works you may be able to mount the sd card from twrp and move rom to your sd card and flash it.
Just throwing out some ideas since nothing you have tried has worked so far.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
I cannot mount my virtual sd card to my computer.
I tried to mount my system in TWRP but on my computer it says I cant access it and I need to format it.
Should I format it or will that indefinitely kill my phone.
LimesAreOranges said:
I cannot mount my virtual sd card to my computer.
I tried to mount my system in TWRP but on my computer it says I cant access it and I need to format it.
Should I format it or will that indefinitely kill my phone.
Click to expand...
Click to collapse
Hmm. That sounds like it got corrupted, which may be why your phone cant access anything. Your comp should only be able see the partition that acts like the external sd, so formatting it SHOULD be ok, but get a few more opinions on that before you do it. If so then you can copy a rom on and flash it in twrp.
Could it be -?
I've been trying and trying.
I've been told by someone that maybe I could plug in an SD card reader into my phone. It wasn't recognized.
Could it be my firmware update?
My phone in RUU or ARUwizard or "getvar version-main" says my phone rom version is 1.94.631.3
The rogers RUU out there is 1.73.631.1
Could that be why I cannot install anything on this brick?
LimesAreOranges said:
I've been trying and trying.
I've been told by someone that maybe I could plug in an SD card reader into my phone. It wasn't recognized.
Could it be my firmware update?
My phone in RUU or ARUwizard or "getvar version-main" says my phone rom version is 1.94.631.3
The rogers RUU out there is 1.73.631.1
Could that be why I cannot install anything on this brick?
Click to expand...
Click to collapse
I believe that is the new Rogers OTA. I believe it may have the hboot update which is not rootable. If you have already relocked your boot loader and have the updated hboot, you may have a bookend I am afraid.
All you can do is unlock your bootloader again, push twrp recovery via fastboot, then mount the SD from recovery and copy a rooted custom ROM to your SD and flash it.
Hopefully someone will chime in and tell me I am wrong for your sake....
Beamed from my TN Special Edition powered HOXL on Rogers.
GibMcFragger said:
I believe that is the new Rogers OTA. I believe it may have the hboot update which is not rootable. If you have already relocked your boot loader and have the updated hboot, you may have a bookend I am afraid.
All you can do is unlock your bootloader again, push twrp recovery via fastboot, then mount the SD from recovery and copy a rooted custom ROM to your SD and flash it.
Hopefully someone will chime in and tell me I am wrong for your sake....
Beamed from my TN Special Edition powered HOXL on Rogers.
Click to expand...
Click to collapse
If only my VSD worked... I gave you a thanks anyways. I'll wait for something to come up I guess. I'm kinda fed up with trying and nothing working over and over again.
If you have fastboot why not go through htcdev bootloader unlock? Every in here has suggested it.
Once unlocked flash new recovery and install a rom?
Ps force reboot the phone also by holding the power button for 10seconds.
Thank you for your imput. But my problem lies in the fact I cannot access my phone storage to install a custom rom nor can I flash a working RUU.
LimesAreOranges said:
I cannot access my phone storage to install a custom rom.
Click to expand...
Click to collapse
I found force reboot of phone fixed my sd card when I had a similar problem when I couldnt write to it successfully.
twistedddx said:
I found force reboot of phone fixed my sd card when I had a similar problem when I couldnt write to it successfully.
Click to expand...
Click to collapse
Didnt work. thanks though
Update on the situation
So I just tried TWO different methods and both did not work .
1.) I tried pushing a custom rom (Nocturna) to my SD card.
I cannot access ADB unless I am in TWRP, and pushing a file that big to my SD just crashes my phone. My SD also still cannot mount, I still cannot partition it, I still cannot do anything regarding my sd.
So I tried pushing the zip to other folders on my phone and I got a Process error like before on cmd promt as well as a crash TWRP.
So then I tried a second method.
2.) Downgrading software.
Since my firmware version was 1.94.xxx.x I tried this method http://forum.xda-developers.com/showthread.php?t=1671135
Everything went fine. Bootloader shows 1.11.0000 even though I wrote 1.00.000.0 and in the RUUs it shows 1.00.000.0.
But now that my phone is relocked, suprise! NONE of the RUUs work. I thought this would certainly fix the problem but aparently not.
Any suggestions?
LimesAreOranges said:
So I just tried TWO different methods and both did not work .
1.) I tried pushing a custom rom (Nocturna) to my SD card.
I cannot access ADB unless I am in TWRP, and pushing a file that big to my SD just crashes my phone. My SD also still cannot mount, I still cannot partition it, I still cannot do anything regarding my sd.
So I tried pushing the zip to other folders on my phone and I got a Process error like before on cmd promt as well as a crash TWRP.
So then I tried a second method.
2.) Downgrading software.
Since my firmware version was 1.94.xxx.x I tried this method http://forum.xda-developers.com/showthread.php?t=1671135
Everything went fine. Bootloader shows 1.11.0000 even though I wrote 1.00.000.0 and in the RUUs it shows 1.00.000.0.
But now that my phone is relocked, suprise! NONE of the RUUs work. I thought this would certainly fix the problem but aparently not.
Any suggestions?
Click to expand...
Click to collapse
Edit
If your on 1.94 then you also have the upgraded hboot you can not downgrade and ruu a lower version it will fail you can only ruu 1.94
Sent from my Nocturnalized Beast
E.Cadro said:
Edit
If your on 1.94 then you also have the upgraded hboot you can not downgrade and ruu a lower version it will fail you can only ruu 1.94
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Thank you!!! So basically I need to wait for it to come out and I'm all set?
LimesAreOranges said:
Thank you!!! So basically I need to wait for it to come out and I'm all set?
Click to expand...
Click to collapse
Yes if there was a 1.94 ruu it might work but I don't think I've seen one but I could be wrong.
On another note am I understanding you correctly you were able to mount your sd via twrp if so I'm surprised it crashed It's how I always move rom zips over to my phone.
Sent from my Nocturnalized Beast
Yeah, my sd is kaput. I hope the RUU will fix it when it comes out. How long do you think it is going to take? I'm paying way too much for a plan if I'm not going to be using a smartphone.
LimesAreOranges said:
Yeah, my sd is kaput. I hope the RUU will fix it when it comes out. How long do you think it is going to take? I'm paying way too much for a plan if I'm not going to be using a smartphone.
Click to expand...
Click to collapse
I recently had this issue cause i was messing around and I hit wipe in TWRP by accented. So it wipped everything on my phone to include the Hboot so no version showed up when i tried to flash the RUU. I grabbed the OTA 2.20 update with the kernal and now everything works minus the battery its drains crazy fast.
Related
Okay so my sisters sensation would freeze up every time she got calls from certain people so I told her to let me root it. Since this is something I have done many times before I didn't think I would have any problems, but I do.
I can only boot into bootloader and then recovery. I can flash ROMs, restore, and do anything else you do in recovery, except afterwords when I choose reboot the phone just turns off and nothing happens and I can't boot into recovery for several minutes (during these minutes the phone has to be charging). I've been up for literally 5 hours, 1-6 am, trying to figure this out. Someone PLEASE help me. Seriously WILLING TO PAY for an answer that works.
Thank you.
Boot into the bootloader and then flash the RUU back to stock. If that works then perhaps try again
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
JayIce11 said:
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
Click to expand...
Click to collapse
I doubt that's the problem. If he forgot to remove PG58IMG.zip, then every time he boots into bootloader, it would just try to update, not prevent him from booting up the phone.
Have you tried SuperWiping first, then flashing the FW, then the ROM? I don't think this would make a difference but since you've tried FW -> SW -> ROM, can't hurt to mix it up.
EDIT: Just thought of this: did you flash a FW for your region? If not, you might need to super CID.
JayIce11 said:
Hi i had similar after flashing new firmware, I hadnt renamed deleted the f/w package. this may not be your particular problem, but it is normally an oversight like this.
file name of PG58IMG.zip, if this is on root of ya sd, i do beleive it will always boot into recovery. worth a check?
Click to expand...
Click to collapse
Yea I've taken it off the sd and tried that didn't work either man
tr1p7s said:
I doubt that's the problem. If he forgot to remove PG58IMG.zip, then every time he boots into bootloader, it would just try to update, not prevent him from booting up the phone.
Have you tried SuperWiping first, then flashing the FW, then the ROM? I don't think this would make a difference but since you've tried FW -> SW -> ROM, can't hurt to mix it up.
EDIT: Just thought of this: did you flash a FW for your region? If not, you might need to super CID.
Click to expand...
Click to collapse
See my problem with super CID is the guide that I see for it http://forum.xda-developers.com/showthread.php?t=1459767 requires me to be able to actually use my phone and I screwed that up lol. I tried that fastboot method too and it didn't work. I fear I've really messed this up.
EddyOS said:
Boot into the bootloader and then flash the RUU back to stock. If that works then perhaps try again
Click to expand...
Click to collapse
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
brandonsmooth said:
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
Click to expand...
Click to collapse
Should be able to find your phones RUU in the development part of the forums.
Also most of the major Western carriers have the firmware posted on this forum. Did you download the correct one?
brandonsmooth said:
there is no RUU on my sd to flash... I don't think there is anyway..... maybe that's my problem?
Click to expand...
Click to collapse
Download an RUU from here http://forum.xda-developers.com/showthread.php?t=1074559 to your pc making sure it is the appropriate one for your device (give me more details if you are unsure), boot your phone into fastboot (volume down and power), plug the usb cable into your phone and pc. Your device should now say fastboot usb then double click the RUU.exe that you have downloaded to your pc. This will restore your device to stock.
So problem is the rom refuses to boot, but recovery, bootloader does?
Check whatever fw you flashed is compatible with the rom you are trying to boot. If not change one.
If this does not help then use Eddy's suggestion and run correct ruu. Make sure your CID supports the one you use, or forget this if you have superCID.
Sent from my Pyramid-T
Do what is said here: http://forum.xda-developers.com/showthread.php?t=1192300 (the superCID part) and skip steps 5,6 and 7 just boot into bootloader manually. Then, flash the firmware you need, you won't have to worry about the CID. Get it from here: http://forum.xda-developers.com/showthread.php?t=1459767
Having almost the exact same problem after flashing the firmware..
Def. Gonna try this.
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?
Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.
abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172
If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update
abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.
iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.
I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261
The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.
OK so I have Rooted Phone and i am currently running viper very nice, But when going into settings>storage i notice that the SD not showing :S.
i have booted to recovery and the recovery also cant mount, format or even recognize the SDcard.
As the so called SDcard is build in and is none removable i need some help getting it back.
I have tried a few RUU but keep getting 155 error ( wrong version ) Its hard to find the correct one and i have a few downloading as i type.
Yes i have re-locked the bootloader.
Will Using a RUU magically fix the sdcard or is it still going to be unreachable, or have i missed something.
O i currently have all the 1's as my CID but have also tried 2 others without success.
Thank you for any help you guys can offer i have search the forum but no one with a HTC one S seems to have the same prob.
Stock recovery will be the fix, not RUUs.
Flash that, boot into bootloader, click recovery.
Didn't work? Boot into bootloader, click clear storage.
Ta-dah!
kylepont said:
Stock recovery will be the fix, not RUUs.
Flash that, boot into bootloader, click recovery.
Didn't work? Boot into bootloader, click clear storage.
Ta-dah!
Click to expand...
Click to collapse
Thank you for your quick response.
I flashed Stock recovery didnt work then cleared storage and still nothing
is it possible for the phone to have swoped install location ie the internal is now the external and as a result cant find other storage ?
its got me stumped
zeroplayer said:
Thank you for your quick response.
I flashed Stock recovery didnt work then cleared storage and still nothing
is it possible for the phone to have swoped install location ie the internal is now the external and as a result cant find other storage ?
its got me stumped
Click to expand...
Click to collapse
I also have Red ! Tryangle on recovery with the stock
No. The SD card is corrupt, and the phone can't read corrupt storage. The stock recovery is usually the fix, is the bootloader unlocked?
Sent from my One S using xda premium
Hi All,
I know this might sound like a redundant topic to you all (since there are many discussions about this on here) but after having gone to MANY threads on forums, MANY different websites and trying MANY different things to correct this, to no avail, i'm still stuck!!! :crying:
I am on Evita...running:
S-ON
HBoot-1.14.0002
Radio-0.19as.32.09.11_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
AT&T Stock RUU 2.20
I've relocked the device, flashed stock RUU (via fastboot), erased the cache, factory reset, wiping from TWRP recovery.....NOTHING is working!
All the phone does is boot to the "HTC quietly brilliant" screen, hang for a few moments then restart.
Any help someone can provide, would be greatly appreciated! This is my kid's phone and he's bugging about wanting to get it back. Thanks!:good:
Start with rooting step first.....http://forum.xda-developers.com/showthread.php?t=1952038
And for further guide.... http://forum.xda-developers.com/showthread.php?t=1671237
Swyped from T3DRO1CS RedHoXence
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
timmaaa said:
Hang on. You'll need to provide more information, saying you've tried many things could mean anything. What exactly have you tried with this phone? I'm assuming it has been unlocked and rooted in the past? Does it have SuperCID?
Also, you said you flashed an RUU via fastboot, but an RUU is an exe file which runs by itself so flashing via fastboot isn't correct. Where did you get this alleged RUU and how did you run it?
@ted77usa
Just wait a minute, we need to properly identify what has been done to this device before going any further.
Sent from my Evita
Click to expand...
Click to collapse
Thanks so much for taking your time to reply, guys.
Sorry, I didn't give full details. Yes, the phone has been rooted, unlocked and running CM10.1 fine for several months. All of a sudden, it got into this weird bootloop. So, I tried doing some of the tricks that people have posted about relocking the bootloader and flashing the stock rom via fastboot. That didn't work so I tried running the RUU...that didn't work. I went back in and tried a factory reset from the bootloader...nothing. I did a erase cache from fastboot and fastboot flashing the boot.img...still doing it. I went into TWRP recovery and wiping Delvik, Cache and Factory Reset....again, still stuck in bootloop.
Sorry to be lengthy but I'm trying to retrace as many steps as possible for you guys.
Ok, just to be clear, you ran the full RUU exe file?
Sent from my Evita
Stupid question.....
I just had a thought. I have the same exact HOX as my son. It's rooted, unlocked and running same CM10.1 rom as his was and it's running fine. Could I try backing up from my phone's clean nandroid file? So, it ends up just acting as a mirror of my phone?
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
timmaaa said:
Yes, you can create a backup on your son's phone using TWRP, copy the backup to a pc, copy it to your phone, and restore the backup. Being that you're s-on though you'll need to manually flash the boot.img from that ROM using fastboot. Do you still have a copy of the ROM zip?
Sent from my Evita
Click to expand...
Click to collapse
Yes, I do. I always keep a copy of the rom on my phone for emergencies. Now, the other question is, my phone is running 1.85. The messed up phone is running 2.20 (both S-ON). Will it not work or...coming from a nandroid backup, does that not matter? Never tried doing a mirror before...
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
timmaaa said:
The firmware version that either phone is on won't make a difference as the backup tool can't touch that partition.
Sent from my Evita
Click to expand...
Click to collapse
So, I need to just make sure the phone is back to being rooted, unlocked and running TWRP, then mount it and load the nandroid to the SD card. Should I do backup from fastboot or TWRP?
Do you think it will throw it out of that bootloop? I've spent two days on this and I'm ready to be done!
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
timmaaa said:
Add long as you have TWRP installed it should work just fine. You have to do the backup using the backup tool in TWRP. When you create the backup on your son's phone you will find it on the sd card at TWRP/backups/serial number, you need to put it in the same file tree on your sd card.
Whether or not it's going to solve your problem I'm not sure, but anything is worth a shot.
Sent from my Evita
Click to expand...
Click to collapse
Thanks, well..here goes nothing. I will report back the progress! I really appreciate the time for your advice. :good:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
timmaaa said:
It's no problem at all, I'm always happy to help someone get their phone back on track.
Sent from my Evita
Click to expand...
Click to collapse
Well, I've got the phone loading into TWRP 2.5.0.0 and when I try to do a wipe Delvik, Cache and Factory Reset...it's telling me it can't find the SD Card.
"E: Unable to mount '/sdcard'
E: Unable to mount storage"
Phone says it's still CID: 11111111
Bootloader: Unlocked.
Any clue how to get the phone to read/write to the SD Card so I can back up to a nandroid?
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
timmaaa said:
Did you mention doing a factory reset from bootloader? If so, you'd corrupted the sd card and you'll need to format it using Windows before you can use it. Also, you'll need to flash TWRP 2.6 because 2.5 is full of bugs.
Sent from my Evita
Click to expand...
Click to collapse
I did! Thanks for remembering. :good:
Any special way I should format the sd card when I do it on Windows? Thanks for the tip on 2.6!
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
timmaaa said:
It should come up as fat32 as the default, if not just make sure you format it to fat32 and that's it. It'll probably take twenty minutes or so.
Sent from my Evita
Click to expand...
Click to collapse
Got it! Flashed 2.6 in getting ready to back up from my phone's nandroid. Fingers crossed!:fingers-crossed:
After I back up from my nandroid in TWRP, should I flash the boot.img from fastboot?
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
timmaaa said:
Yes you'll need to flash the boot.img afterwards, good luck.
Sent from my Evita
Click to expand...
Click to collapse
How can I get it to see my nandroid backup? I have it installed inside the TWRP folder just like it would be on my phone but when I go to Restore, it shows nothing on my sd card. wtf?? I think I'm getting one step closer and another hurdle arrises!! ugh...
Thanks for your help btw, timmaaa!! :good: