[Q] Bricked HOX? Please help. - AT&T, Rogers HTC One X, Telstra One XL

I have an ATT One X, which I recently rooted. Yesterday I tried to flash a JB ROM and it said it was successful. However, now when I turn it on it just stays on the Quietly Brilliant screen indefinitely.
I can get into fastboot, and TWRP is there too.
I can't mount from within TWRP, as my computer just says the drive must be formatted before it can be used. I tried to run an RUU but it doesn't recognize that the phone is connected. Anytime I go to reboot, etc from within TWRP it tells me I have no OS.
Help? Please?

Reference the other 20,000 threads opened and answered about this topic

emylibef said:
I have an ATT One X, which I recently rooted. Yesterday I tried to flash a JB ROM and it said it was successful. However, now when I turn it on it just stays on the Quietly Brilliant screen indefinitely.
I can get into fastboot, and TWRP is there too.
I can't mount from within TWRP, as my computer just says the drive must be formatted before it can be used. I tried to run an RUU but it doesn't recognize that the phone is connected. Anytime I go to reboot, etc from within TWRP it tells me I have no OS.
Help? Please?
Click to expand...
Click to collapse
If it tells you in needs to be formatted... FORMAT IT!! Mount in twrp and right click removable storage. Choose format. Look down about 2 threads.. I literally just explained the process to another guy. Gotta read bro.
Sent from my HTC One XL using Tapatalk 2

I think these people need some tough love so they do some research and learning
Sent from my HTC One XL

Ya, I just stopped replying to these threads

My new years resolution didn't last long I passed on a few but OMFG how can so many people be so lazy and not see all the answers
Sent from my HTC One XL
---------- Post added at 11:14 AM ---------- Previous post was at 11:09 AM ----------
Maybe next year I'll be a more patient person
2013 is not the year for me sorry noobs at least titan will be ready to hold your hand.
Titan you are my idol
Sent from my HTC One XL

emylibef said:
I have an ATT One X, which I recently rooted. Yesterday I tried to flash a JB ROM and it said it was successful. However, now when I turn it on it just stays on the Quietly Brilliant screen indefinitely.
I can get into fastboot, and TWRP is there too.
I can't mount from within TWRP, as my computer just says the drive must be formatted before it can be used. I tried to run an RUU but it doesn't recognize that the phone is connected. Anytime I go to reboot, etc from within TWRP it tells me I have no OS.
Help? Please?
Click to expand...
Click to collapse
If you have no OS, download cleanrom 5.1, and trasnfer it to your phone. Flash that in twrp and you'll have your phone back... If you want to venture further, pm me and ill help you through it
Sent from my HTC One XL using Tapatalk 2

Do not worry, ur phone not brick, just you did not flash kernel before flash rom. Always remember this, if you are on Hboot 1.14 or higher, flash kernel (boot.img) before flash rom. Now just extract the boot.img from the JB rom, hook phone to PC (make sure fastboot USB), using kernel flasher, and flash the kernel. Then bingo, your phone back to life!
*** Remember this, always nandroid backup, and as long as you can get into recovery mode, it means ur phone never been bricked!

Related

HTC Thunderbolt Issues - Stuck at HTC Logo... Recovery not working, etc...

here is my issue.
2 weeks ago, i rooted my phone. all was well. flashed CWM Recovery 5.0.2.1 for my Thunderbolt. I made a backup just before i rooted so that in case ANYTHING went wrong, it would unroot me and fix any problems. So, here i am, backing up apps with Titanium Backup, and it backed up fine. The next thing i did was start to uninstall HTC Bloatware... I knew which ones were the ones i could remove, plus even if i removed the wrong one, i could just restore using my image backup. After removal, the phone instantly ran better. i had over 65% free memory space... This was all well and good, until i rebooted the phone. the instant i rebooted my phone, i was getting the flashing HTC Quietly Brilliant screen. i had done NOTHING to it to cause this. It would alternate from HTC splash to Thunderbolt animation.
So, knowing what was wrong, (UI not loading) i went to recover my image from CWM. that went fine. but things just got worse. After a successful recovery (according to CWM) i rebooted, but to my surprise, now its worse. its stuck at the HTC boot logo. ALL MANNER OF ROMS DO NOT WORK!!! recoveries, new OS, anything, all the same result. AT LEAST with the thunderstick full blown ROM, i can get back to the looping splash screen, but not any further. i DONT KNOW what is wrong but i am hoping one of you mad phone geniuses out there can get my phone working. i tried getting s-off with revolutionary, but it failed because the phone has to be booted up for it to work, and is something i obviously cant do at this point... relocking the phone made things worse too because i unlocked using the HTCdev method.
This is not a boot loop, as it doesnt loop. it just sits there. i have tried every available resource on this, and other sites. i must have read over 1,000 posts in the past week to try and gather what the devil happened to my phone... If its any help, i did accidently delete the settings storage APK file, but a restore should have fixed that. i want to lock up the phone to send it in for repair but i cant gain s-off to flash a new radio with the phone in its current state. i know how to do all if these things but the phone wont let me.
Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium
Does your computer recognize your device?
Sent from my ADR6400L using xda app-developers app
i am nearly pulling my hair out...
smtom said:
Reformat the sd card to fat32 and flash an RUU file to put you back to stock.
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...
cyberkeeper1 said:
any RUU downloads that would have been available on multiupload.com are disabled and redirects to to "the internet vs., holywood". besides, as i said, any attempt to flash any rom no matter what it is fails. Well, technically it FLASHES ok, but doesnt actually work. as far as i know, the phone has 2 bootloaders in any given android phone. There is the primary HTC Bootloader (Hboot) and a secondary ROM UI Bootloader. (Android Boot) i think what has happened is that this part has become corrupted and i wanted to know how to access this and reformat that. supposedly you cant because its partitioned, and formatting the partitions would fix my issue. problem is that i have done all of this. to answer the second reply, yes, i can get the phone to be recognized in any mode as long as its fastboot, or recovery. Fastboot.exe works, and adb recognizes it in recovery as being IN recovery mode. unfortunately, with my device still locked, i cannot flash a new bootloader, which might solve my problem. this is not like any issue currently on XDA so far as i read, so this is why i created a new thread.
I am sure the Moderators will agree that my problem seems to be unique. After reading what seems to be hundreds of forums, i cannot solve the issue. While technically i am a newbie here, i am no stranger to modding phones. i have been at it for over 4 years now. THIS problem is absolutely a first for me. At least before i could restore using CWM, but even that failed. i checked my MD5 Sum for CWM backup and it checked out.
If someone can provide me a link to an ORIGINAL, unmodded, RUU that shipped with the phone, (PRE OTA 2012) that ISNT that stupid file-factory corrupted crap, i would be extremely indebted to that person. last time i used File-factory, it took THREE hours and the download was corrupted according to CWM. it refused to flash the phone even though Chrome said it completely downloaded (Error: Bad - Installation Aborted). There was no MD5 SUM to compare with so thats also another problem. i absolutely need that info to properly flash the phone. All the other ROMS i downloaded like TSGB and Lightning Rom technically flashed fine after a full wipe, but refused to go past their own "Open Mobile" splash screen.
So you see, i am at a loss with this phone, as all i did was reboot after rooting it, and nothing i did could have possibly caused this kind of failure...
Click to expand...
Click to collapse
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2
will this really work??!? lol
trter10 said:
https://dl.dropbox.com/u/61129367/Stock-ROM.zip
013CBDD3A9B28BC894631008FA2148E2
Click to expand...
Click to collapse
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.
new problem... i think...
cyberkeeper1 said:
If this works, i will be forever grateful. and something that mere Custom ROMS wont do, is repair any boot issues and lock up my phone again right? i hope at least it fixes the issue.
Click to expand...
Click to collapse
ok. so the download finished fine so far as i know, but now CWM says ITS bad too. i will try again but i cant seem to flash any stock rom no matter if its OTA or pre-OTA from CWM. is there a way to flash a rom from the PC via adb or something?
Ohh! They're not flashed through CWM. They're flashed through hboot. Just rename it to PG05IMG.zip and put on SD card and boot to hboot it will ask you to flash
Sent from my ADR6400L using Tapatalk 2
i will try that. previous hboot flashes always fail. it reads the archive, but never goes to "checking zip". it loads, checks, and then parses. i was successful with my evo shift earlier today, but that thing is ancient compared to my thunderbolt. With the Shift, i was able to gain root AND s-off with an old bootloader and i dont even need a new one.
i wanted to do the same with my bootloader in case another disaster hits because then i can flash whatever RUU i want with s-off. i will make sure the MD5 SUM matches before flashing. i forgot to do that anyhow.
Hboot flash failed. went through the motions of scanning it and it scanned the whole thing and then did nothing. it returned me to Boot Choices. Like Fastboot, recovery, etc... i tried twice. are you absolutely certain that is the shipping firmware that formats the entire phone, and not just updates it? i cant send it to verizon even though they know it was illegal to lock up my phone... Anyhow, i realy need this thing working and i have racked my brain enough to damage it already... lol. if it fails again i will try to redownload it. So far it loads and does NOT ask me to start the update. could be a version issue because it does not complain about anything else.
Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app
lemew said:
Have you tried following the instructions in the return to stock thread in the android development section stickies? This may help you.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
yes i have. i cannot do what it asks because it requires my phone to be functional to flash it using hboot. i need a signed copy of an older RUU. hboot doesnt do anything with it. its a valid copy, and i can see all the images and contents in windows and linux, but all i can get hboot to do is read it, then it doesnt ask me to update. i dont know what to do now.
I believe there is a ruu image without hoot download there.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 06:39 PM ---------- Previous post was at 06:34 PM ----------
Try http://shipped-roms.com/index.php?category=android&model=Mecha
Sent from my ADR6400L using xda app-developers app
ok well i will literally try ALL of the signed images. i will see if hboot will update it.
If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app
How i fixed my tbolt stuck at the white HTC screen
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.
mpcapps said:
I had this exact same problem literally yesterday (stuck at HTC screen) with some different cwm symptoms. I'm guessing my cwm was corrupted because the phone would reboot after about 30 seconds being in cwm, preventing me from flashing any roms. oh, and my backup image was corrupted as well. awesome. Flashing other CWMs did not fix the CWM problem.
Your problem sounds similar in the fact the CWM won't flash properly. You're trying to fix it by trying to flash a rom in HBOOT that isn't configured to be flashed that way. for example, i put the skyraider rom (named properly) in the root folder and tried to flash with HBOOT. it scanned and parsed but didn't give me the option to flash.
What I did was go here and grab a stock like image:
androidforums.com/thunderbolt-all-things-root/418539-thunderbolt-root-unroot-thread.html
(won't let me make a link, i'm too new)
Go to the "Putting current stock firmware and s-on back onto the phone" section.
Download file 1 and flash it using HBOOT. I had to pull my sd card to get the file on there since cwm was crashing. Only flash that rom and nothing else. It flashed for me; if it doesn't flash for you then maybe your HBOOT is corrupted, and if so i don't know if you can fix it.
Once that flashes, reboot the phone and it should return to some level of functionality. You'll have S-off but no recovery or root tools installed. I ran revolutionary at this point, which recognized i already had S-off...then it offered to load CWM. This i did. in the meantime i deleted the unrooted image and put the image of the rom i wanted on the sd card. i then booted into recovery(it won't flash in HBOOT) and loaded that rom (skyraider zeus). That worked fine and the cwm didn't crash out.
I hope this works for you. I was getting ready to fire back up my OG droid before i did this.
Click to expand...
Click to collapse
I have read that post you provided probably 100 times its not working for me. flashing a custom rom actually got me past the HTC white screen and into a splash screen loop (Open Mobile). Also, I havent even been able to use the REV tool because my phone is not recognized by it without it being fully functional. you have to be fully booted up for the REV tool to use adb and start the process. thats why i need a signed copy of an older ROM with hboot flashing capability so i can fully restore my phone. i am 100% sure its a corruption issue, but i am out of clues as to how to actually get it to flash over while being s-on. with the evo shift it worked perfectly. it only took me 20 minutes to root, s-off and flash a custom rom. this phone has been a thorn in my side ever since i accepted that STUPID FOTA... i regret not knowing before hand what that OTA was and what it prevented. Now i know, too little / too late.
without s-off, i cant unlock hboot to flash it, and the fastboot mw whatever command failed also because its locked tight.
lemew said:
If your hboot is flashed with revolutionary I believe you have to unlock it before anything thing else can be flashed over that. Hboot or emmc could be corrupted as well.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
thats what i thought. is there a way to change out that eMMC, or remove it to format it manually? i mean based on the description, its technically external which implies removable.
Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app
lemew said:
Yes you can format emmc I do not know if this will solve your problem. You wipe abd format through adb but need to see if it is being mounted first.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
too bad i cannot repartition it to allow for more RAM instead of app space. i dont care about app space because i have a 32gb card... lol. i just want that phone to be faster than what it is currently once i finally get it running.

bricked one x

So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX
tae_254 said:
Ruu back to stock 2.20
Edit.
If you can mount then connect to computer and try reinstalling boot image and the rom you were trying to install. Or adb
swagged out rooted jelly bean HOX
Click to expand...
Click to collapse
so from mounting
im trying to install the Android Revolution HD 9.7.2 Ice Cream Sandwich
it allows me to choose settings, and such and start install.
after starting install, it goes through the files and such, but when it gets to /system/lib/ it just closes on itself, and goes back to twrp screen and recovery home. the rom never finishes installing. right now im gonna re-download the rom and see if that works.
if i cannot install the custom rom, how can i go back to stock exactly?
do i need to find the stock ruu?
fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?
hopefully you aren't using cwm anymore and flashed twrp for the evita.
chinaman_chong said:
fixed it.
turns out im stupid and was using a rom not compatible with this phone.
i flashed http://forum.xda-developers.com/showthread.php?t=1907324 so far, and it seems to be working
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942
CleanROM on Viper XL
---------- Post added at 12:14 PM ---------- Previous post was at 12:13 PM ----------
chinaman_chong said:
however, i prefer something closer to stock. can anyone suggest a rom?
Click to expand...
Click to collapse
CleanROM or Viper XL
redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Stick to the ROMs listed in our section of the forum (AT&T, Rogers HTC One X, Telstra One XL) in "Android Development" and "Original Android Devepment" here: http://forum.xda-developers.com/forumdisplay.php?f=1538
Or just use my handy index, which is an organized list of all our ROMs and mods:
http://forum.xda-developers.com/showthread.php?t=1671237
And apparently, you missed these:
http://forum.xda-developers.com/showthread.php?t=1813839
http://forum.xda-developers.com/showthread.php?t=1944712
http://forum.xda-developers.com/showthread.php?t=1952942
Click to expand...
Click to collapse
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:
Crappyvate said:
OMFG ..how did you get all these results, did you by any chance use that esoteric SEARCH functionality ?
Now all i have to do is read ?? Could you also pre-chew my food please ? :silly:
Click to expand...
Click to collapse
I didn't even have to use the search function. 2 are near the top of General. The remaining has slipped past the first page, but its still pretty high up there.
People who flash a ROM for the international version are simply neglecting to do any basic reading and learning before flashing things willy-nilly, that's my point.
thanks for the help guys. i flashed viper xl yesterday night right after, loving it thus far. i was just so used to the sense keyboard already, and hated the cramped jb keyboard, and this rom has simple little tweaks
i did read, but i guess not thoroughly enough. in hindsight, i wasnt aware that the one x was different than the xl, its fairly easy to miss that the other roms are not compatible with this phone. and is completely different alltogether.
if i had known that, i wouldnt have flashed cwm, and would not have need to post a help thread. all "solutions" i attempted on my own were based off readings of the hox, rather than the evita, once again causing more problems. it was easily enough fixed once i figured that bit of information out.
i am a noob, but this phone is not my first time rooting, so with my prior knowledge i felt i was more than ready to tackle this rom flashing, im sure plenty of others will make the same mistake as i did.
the other phones ive rooted and flashed had their one model of phone only, so all the roms available were compatible.
im just glad my phone is not bricked, and i now have root access
chinaman_chong said:
So earlier i attempted to do the 2.2 root.
i managed to get as far as rooting, installing superuser and CWM
now, the problem is when i went to flash the rom, i tried to run the super wipe, but was getting errors about the sdcard not being able to be mounted. and the wipe was not performed/failed/aborted etc
i tried to run flash the rom still, it loaded, but still gave an error at the end and did not work.
reboot the phone, and i get the HTS quietly brilliant screen with red text that says"this build is for development purposes only...." and from here it does nothing but constantly reboot to this screen.
i am able to get to the bootloader screen, and fastboot works.
ive tried factory resetting the phone, as well as using the CWM recovery. i am unable to do any. as the CWM cannot write to e:\sd card
its not mounted, and i cannot mount it, when i try to reformat the sd card, it says it is unmounted.
mount usb storage was not working either, and said files were missing.
i read on other threads about needing the sd card reformatted, but the one x has an internal card.
please help
i feel like it can be fixed, but im really worried my phone is bricked
eta: i tried to revert to the stock ruu, but i think i should have read it more clearly.
so i guess i flashed the ruu that was NOT 2.2
now my CWM is gone, and i can only get onto the bootloader and fast boot
under fastboot devices my device's serial does show up
ETA: i reflashed with twrp, managed to wipe my sdcard, and am now able to mount.
from here my phone is still not able to boot up.
i can attempt to run the super wipe, but am still getting an error
"E:error in /sdcard"
Click to expand...
Click to collapse
Do not use CMW it causes lot of problems(not recommended for our device) . Use TWRP recovery instead
Sent from my HTC One XL using xda premium
redpoint73 said:
I knew what you did the second I saw the words "Android Revolution", as that ROM does not exist for our phone.
Click to expand...
Click to collapse
That and Superwipe. I remember that zip from other phones I used that rom on.
Sent from my HTC One XL
Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Subscribe to the OneXL forums and stay here till you recognize your community!
Sent from my HTC One XL using xda app-developers app
can't brick from it after 2.20
DvineLord said:
can't brick from it after 2.20
Click to expand...
Click to collapse
Good thing eh
Sent from my HTC One XL using xda app-developers app
InflatedTitan said:
Dang you guys are slipping through the cracks in the bricks lol, excuse my pun. You are lucky. You're the only person I've seen that has flashed android revolution and not overwrite boot and having a beautiful brick lol.
Click to expand...
Click to collapse
From what others are saying, the newer hboot that came with 2.20 is write protected. Hboot can't be overwritten by flashing a ROM for the international One X. ROM just fails to flash, and you get a recoverable condition like this one, as opposed to hard bricks on the older hboot.
Yea, at least there's one good thing that came with the dreaded update
Sent from my HTC One XL using xda app-developers app
How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help
h1m said:
How do i ruu back to stock 2.20? I unlocked my device. Tried flashing the boot.img but after I couldnt mount my sdcard to flash the rest of the ROM. I can enter recovery and bootloader though. Really need some help
Click to expand...
Click to collapse
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu
omario8484 said:
If you want to ruu grab the ruu file...lock your bootloader from within fastboot and run the ruu
Click to expand...
Click to collapse
Where do i get the ruu file? I can't mount my sdcard

Super Bricked (not hard bricked)

Hi my phone the at&t htc one x 2.20 firmware viperxl 2.4.0 beastmode kernel(mpdescision, gpu oc, 2.1ghz oc, etc) has been bricked after a teacher took my phone and gave it to the dean. I had a custom boot animation(about a month now) which it is now stuck on. But after putting a backup on the problem persisted. After multiple different things I tried including the idiot idea of factory reset in bootloader, i have the same problem and no memory space. I have 97 percent battery. Also I don't have any drivers because I had to wipe hard drive(java exploit). Is there a way to install usb drivers when in fastboot. I don't want to have to pay 350+ dollars for a new phone and my dad is pissed off even though he doesn't pay the phone bill or for the phone. I have ubuntu and windows 7. I installed adb and fastboot on ubuntu.
i assume you already relocked bootloader and ran ruu?
I would relock and run the respective ruu ...
I dont know what happened when the dean got your phone... But See what happened is you corrupted the sdcard by factory resetting. You'll need to get on a computer and reformat your SD. Download cleanrom 5.1 and Drag the rom onto your phone and flash it in recovery.
Sent from my One X using Tapatalk 2
"Super brick"? People are making up even more brick terms now?
If the phone's screen turns on, its not bricked (soft, hard, super or otherwise). It just means you don't know what to do in the particular situation, which is not a brick.
---------- Post added at 09:39 AM ---------- Previous post was at 09:38 AM ----------
boss1019 said:
Is there a way to install usb drivers when in fastboot.
Click to expand...
Click to collapse
Installing drivers on your computer has nothing to do with whether the phone is in fastboot or not. Just find the drivers, and install on your Windows PC.
InflatedTitan said:
I would relock and run the respective ruu ...
I dont know what happened when the dean got your phone... But See what happened is you corrupted the sdcard by factory resetting. You'll need to get on a computer and reformat your SD. Download cleanrom 5.1 and Drag the rom onto your phone and flash it in recovery.
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
thanks yeah i think i'll do this. To be honest I don't even know how he did it. My system had been stable for about two weeks now.
Haha he seen a sick @$$ android and he wanted to try it out!
Don't know if your on hboot 1.14 or not, but cleanrom 5.1 flashes boot.img automatically. So you'll be able to flash with no problems.
I'm assuming your recovery is still good? You're still able to boot into twrp?
Sent from my One X using Tapatalk 2
InflatedTitan said:
Haha he seen a sick @$$ android and he wanted to try it out!
Don't know if your on hboot 1.14 or not, but cleanrom 5.1 flashes boot.img automatically. So you'll be able to flash with no problems.
I'm assuming your recovery is still good? You're still able to boot into twrp?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
yeah sadly bricked before and had to ruu so I'm hboot 1.14. I'll have to download 5.1, thankfully my recovery is still good.
it works!!!!!!!!!!!!!!!! dude you are awesome. Sadly lost all data though, but it is recoverable. Thank you so much.
boss1019 said:
it works!!!!!!!!!!!!!!!! dude you are awesome. Sadly lost all data though, but it is recoverable. Thank you so much.
Click to expand...
Click to collapse
Awesome man, glad you got a phone again. At least it'll run better since your on a clean slate lol
Sent from my One X using Tapatalk 2

[Q] Help, may have bricked

A little foreshadow. I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install. I was silly and decided to clear the system... Which erased my OS completely.
For a while I was able to get to the TWRT(?) screen where I could mount my sd card, etc. While researching the problem I came across this:
a solution of fastbooting a recovery.img
I ran the fastboot recovery.img. The only problem is the only screen I can now access is the bootloader. I have bootloader 1.14.0002 loaded onto my phone if that helps.
Is there anyway to try to get a operating system or flash a rom onto this phone still or is it bricked for good? Also if I was able to put a rom onto it, what do you sugggest?
When I try to go to Recovery or Factory Reset, I get the HTC screen with the red text underneath it and it never goes any further.
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
That is the information listed in my bootloader as of now. I am not showing it listed as a drive in my computer when connected to USB. Also when I 'power off' I am in a reset cycle that doesn't stop.
I really appreciate any help in advance. This was a big wake up call to myself about how I should be a lot more careful when messing with these things.
Thank you to everyone that answers!
http://forum.xda-developers.com/showthread.php?p=38909732
[Public Service Announcement] Read before installing the AT&T Jellybean OTA or RUU
You might be hosed. Can you get into bootloader?
Sent from my One X using xda premium
Read before doing anything. Such a simple task. It's easy to read, it's hard to come back from a brick.
Sent from my One XL using XDA Premium
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer. http://goo.im/devs/OpenRecovery/evita/openrecovery-twrp-2.3.3.0-evita.img
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Not only does fastboot erase cache not take long it avoids many stupid little issues. I would say it's a must when flashing a new recovery.
Sent from my One X using xda app-developers app
sinkthehalffoot said:
I attempted to install the jellybean update on a rooted ATT phone. I ended up getting sent to the TWRT (?) screen on the install.
Click to expand...
Click to collapse
The reason it went to recovery is very simple. The OTA needs to have stock recovery in order to install. You don't have stock recovery on your phone anymore, you have custom recovery (TWRP). So the OTA stalled there, when it didn't find stock recovery.
sinkthehalffoot said:
I was silly and decided to clear the system... Which erased my OS completely.
Click to expand...
Click to collapse
Of course it did, what were you expecting to happen? Wiping the OS is the very definition of what happens when you wipe system. If you didn't know what wiping system would do, you shouldn't have done it. For that matter, you shouldn't be doing anything on your phone if you don't know what its for.
A lot of this points to a fundamental lack of reading and understanding:
- Don't know the name of the custom recovery installed on the system
- Wiping things without knowing what they are
- Basic rule (that many folks here seem to ignore, for reasons unknown): Don't install any OTA on a rooted device without first researching what will happen
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
You aren't bricked. With very few exceptions (and this isn't one of those) if the screen turns on, and you can get into hboot, the phone is recoverable. And probably fairly easily so, with the right steps. But you need to do some homework before proceeding.
redpoint73 said:
Lack of basic understanding which spells almost certain doom when modding smartphones. I would highly suggest a few solid hours of research before messing with your phone anymore. I'm not saying this to be a jerk. I'm saying it so you don't brick your phone.
Click to expand...
Click to collapse
+1000
This is exactly the kind of situation that occurs when people get in over their heads and start blundering around.
http://forum.xda-developers.com/showthread.php?t=2232141
InflatedTitan said:
You are not bricked, you are not even close to bricked... If you are already rooted, get the official jellybean update of your head. Clear your thoughts and lock it away. There are tons of custom jellybean ROMs available, a couple based on atts JB update... Flash one of those. If you can get to bootloader you're fine. If you can still access twrp, even better... Which version of twrp do you have IF you can still access? We'll start with that. If not You'll have to fastboot a recovery. 2.3.3.0 is your safest bet, I think the community will agree this is one of the most stable versions for our device.. Just in case you have to push it, download from here onto your computer.
Now drop that image file into your adb/fastboot folder. Right click your adb/fastboot folder and open a command prompt from there. Shoot this command.
Fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img
Now from bootloader choose to boot into recovery. Awwww yea now we on to something!
Now you can download the rom of choice onto your computer. Since you opted for official JB, take a look at Scotts CleanRom. It uses ATT firmware as base :thumbup: once downloaded, double click the zip file (rom) it'll show contents, and youll see a boot.img. simply drop the boot.img into your fastboot/adb folder.
Now on your phone. Choose "mount" in recovery. Make sure it mounts and shows files on your computer. From here drag the entire rom zip (cleanrom) onto your SD card. Now "unmount" hell yea we getting close. I can feel it!
Back out and choose "install" find cleanrom.zip, and swipe to flash. F*ckin rite, this is what android is all about.
Once its completed, DO NOT REBOOT SYSTEM. Since your s-on and have 1.14 hboot, you'll have to fastboot the boot.img you put in your adb folder. Choose to boot into bootloader! Make sure once again it says fastboot usb
Fire up command prompt inside that folder.
Shoot the command ---> fastboot flash boot boot.img
Sending.......
Okay....
Finished.....
OMG success!!! Some people will say to ---> fastboot erase cache
I don't necessarily do this, but it definitely won't hurt. Now reboot system and enjoy Scotts hard work. They don't calls his ROMs the most stable ROMs on the planet for nothing
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
In case anyone ends up stumbling here with a similar issue, this solution worked to a 'T'. Thank you again InflatedTitan.
To everyone else, yes I know, I should of read more than I had. I saw the jellybean update and have been wanting it for a while and acted with haste. I learned a valuable lesson from it all.
Lol this "solution" was around before you posted. You just didn't read or search enough.
Sent from my One X using xda app-developers app
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Lol :beer:
Sent from my HTC One X using xda app-developers app
Venomtester said:
F**kin right! That's what android is all about. Hahaha!
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
InflatedTitan said:
Its almost like a high every time I slide to flash lol
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
I thought I was the only one. In fact I just rooted a nook tablet and installed twrp. Slides to flash... And I could swear I was on cloud 9.
But bravo on the explanation sir. Love a good write up. Even though i already know it, feels good to read it.
Sent from my Carbon-ize Evita using xda-developers app
[HELP] Not sure if bricked or hardware issue?
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
pharrjw said:
I know this is my first post, but I really need the help.
(Also, I'm sorry if this is a bit long)
I've have searched the HOX Evita and Android Q&A forums countless time in the past 3 days trying to figure this out. This thread and this one: "http://forum.xda-developers.com/showthread.php?t=2156665&highlight=fastboot+usb+hangs", are the most similar to what I think is happening to my phone.
Just a little background:
- Bought a used HTC One X, but has a cracked digitizer which I'll be replacing this weekend. (Not sure if this is causing the problems, could it?)
- I was told that the OS was still stock, but I know that's not true now.
- During the first 12 hours I used it, I had no problems.
- Then while I was playing music it rebooted and went to the HTC boot up screen with the red text. Stopped then rebooted again to the normal HTC boot up screen but just hanged there and vibrated nonstop.
- I then used the power button to force a shut down and haven't been able to use it since then.
Here's where I'm at now:
- I'm able to get to the bootloader screen sometimes with the VOL DOWN+PWR method, but most of the time it goes to the QHSUSB mode.
- When I can get to the bootloader, I try to get to Fastboot or Recovery mode but once I press the power button it just stops and does nothing.
- The few times I have gotten into fastboot, and plug in an USB cable, it hangs.
- So far I have NOT gotten it to show "FASTBOOT USB" therefore I haven't been able to use a RUU or flash a boot.img.
- I have reinstalled the drivers almost 5 times now, and tried with different sources from here and HTC Sync. And also tried with 3 different cables and USB ports on my laptop. But still no signs of a connection with my laptop.
- And at one time I (before I knew I shouldn't have) I did try to Factory Reset from the bootloader, but nothing happened. I hope that won't become my downfall.
But yeah, sorry again for the long post, just trying to be thorough. If anyone has an idea of what I can do, please I need your help. It really doesn't matter to me whether my HOX goes back to stock, or use a ROM like CleanROM 6, as long as I can use it again.
Also here's the info at the bootloader screen.
***TAMPERED***
***LOCKED***
Evita PVT Ship S-ON RL
HBOOT-1.14.0002
Radio-0.19as 32.09.11_2
OpenDSP-V29.1.0.45.0622
eMMC-boot
Jun 11 2012, 14:36:28
Click to expand...
Click to collapse
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
exad said:
You will have to get a proper fastboot connection before you can do anything. Then unlock the bootloader then you can flash a recovery on there. Is this an AT&T phone?
Click to expand...
Click to collapse
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Sent from my HTC One X using xda app-developers app
pharrjw said:
Thanks for the reply. Yes, it is an AT&T phone. I understand that I need a fastboot connection, I'm just having difficulties timing it. Is it normally this difficult to get a FASTBOOT USB connection? Or is there something else that I could be missing, or any other method?
I have thought about booting Windows XP on my laptop from a flash drive then trying to connect from that. Does XP have a better record when it comes to unlocking and flashing with android?
Click to expand...
Click to collapse
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Thanks again for the replies guys.
31ken31 said:
If you did a factory reset from bootloader your sd is corrupted. When you can get into the bootloader what does it do if you click on recovery?
Click to expand...
Click to collapse
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
exad said:
There's nothing to time. Drivers and fastboot/adb are all you need. HTC Sync can get in the way so kill or uninstall it if it's running. When you boot to Bootloader, select fastboot, plug in the phone, if you have the the drivers it should go into fastboot USB. I have seen people having issues before due to something interfering with the HTC drivers but it's not common. You can try creating a VM for a clean environment with less chance of anything interfering.
Click to expand...
Click to collapse
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
pharrjw said:
Thanks again for the replies guys.
I was just able to get back into Bootloader, and tried to go into recovery, but with no luck. It just hangs at the bootloader screen. :
EDIT: Not sure if relevant, but after that it eventually shut down, and when I checked it in the Device Manager it appeared again as QHSUSB-DLOAD.
I'm gonna try it again with HTC Sync uninstalled. But if I get the same results I'll probably will endup creating a VM, and hopefully get better results.
I would also like to add that when I do try to get to the bootloader I get various results. Sometimes it goes into QHSUSB like I said in my first post. Then sometimes just nothing but a blank screen and the LED light blinking like the battery is low, or it's solid as if it is charging even though my HOX isn't plugged in to anything. That's what I was referring to when I said I was having difficulties timing it.
Click to expand...
Click to collapse
factory reset in bootloader corrupts the SD card. We wont worry about that just yet as there's nothing we can do about it until we can get recovery on there.
You're going to have to be very careful because it sounds like your EMMC partitions might have some issues. if you can get it to bootlaoder KEEP IT AT THAT SCREEN. don't power it off or anything, leave it there. Because one wrong move could be a perma brick. If we can get a rom on there to S-OFF with, we can RUU to restore your emmc partitions.

[Q] Stuck in ''entering recovery...'' htc one s

What's up everybody! This is my first post here and I am what you would call a noob!
First of all I got tired of the 4.2.2 jb upgrade never coming to my htc one s and decided to give cyanogenmod 10.1 a shot (my first attempt ever tampering with mobile software)!
So I have unlocked the bootloader on my phone following a guide. It now says ''unlocked''
After that, I have tried to flash the paul recovery.img from this post http://forum.xda-developers.com/showthread.php?t=1583427 .
I have done it through adb with the command promt as it says on the article above!
The command promt apparently managed to do the job and it said ''finished'' as it should!
Then i rebooted the phone into recovery mode through the bootloader menu but it then stucks there doing nothing...I have left it for 5 minutes and it was still like that and i thought that the recovery wasn't succesful (i ve seen it going very fast at the clockworkmod menu at videos on youtube while mine was stuck). I then rebooted it by holding down the power button and it went to the sence screen normally.
Then i have tried the other recovery img described at the article...Same thing happened...Then the other one! Same thing again!
Every time i am trying to flash the recovery image the phone stucks in ''entering recovery...'' screen, doing nothing.
Am I doing something wrong?
Please help, it will be much appreciated! I really want to dig custom roms...I' m a total geek
Thanks in advance!!
letakgr said:
What's up everybody! This is my first post here and I am what you would call a noob!
First of all I got tired of the 4.2.2 jb upgrade never coming to my htc one s and decided to give cyanogenmod 10.1 a shot (my first attempt ever tampering with mobile software)!
So I have unlocked the bootloader on my phone following a guide. It now says ''unlocked''
After that, I have tried to flash the paul recovery.img from this post http://forum.xda-developers.com/showthread.php?t=1583427 .
I have done it through adb with the command promt as it says on the article above!
The command promt apparently managed to do the job and it said ''finished'' as it should!
Then i rebooted the phone into recovery mode through the bootloader menu but it then stucks there doing nothing...I have left it for 5 minutes and it was still like that and i thought that the recovery wasn't succesful (i ve seen it going very fast at the clockworkmod menu at videos on youtube while mine was stuck). I then rebooted it by holding down the power button and it went to the sence screen normally.
Then i have tried the other recovery img described at the article...Same thing happened...Then the other one! Same thing again!
Every time i am trying to flash the recovery image the phone stucks in ''entering recovery...'' screen, doing nothing.
Am I doing something wrong?
Please help, it will be much appreciated! I really want to dig custom roms...I' m a total geek
Thanks in advance!!
Click to expand...
Click to collapse
To boot into recovery, Hold VolumeDown + Power.
Edit: maybe you've done that, but make sure that you choose the correct recovery version. that is, match the version of your phone S3/S4 with the recovery.
Specific recovery for specific phone.
khan.orak said:
To boot into recovery, Hold VolumeDown + Power.
Edit: maybe you've done that, but make sure that you choose the correct recovery version. that is, match the version of your phone S3/S4 with the recovery.
I have booted of course into recovery by doing that!
Can you tell me where i can find the right recovery for my S3 model?
Click to expand...
Click to collapse
Here link
Sent from my HTC One S using Tapatalk 4 Beta
Thank you! Have you tried it yoursef?
Problem solved thanks to the mister above!!!!!Thank you very much! I'm now getting the jb upgrade!!!
letakgr said:
Problem solved thanks to the mister above!!!!!Thank you very much! I'm now getting the jb upgrade!!!
Click to expand...
Click to collapse
Have the same problem (HTC one at&t) and that link he has that I clicked gives you a page of LIKE A WHOLE LIST of versions.. How do you know which one to choose?
plus spent all night trying to download the recovery.img from clockworkmod.com as well as other links and all I get is this LONG encrypted script page displayed, and not an actual FILE that prompts you to download. going crazy here!
Chri5topher said:
Have the same problem (HTC one at&t) and that link he has that I clicked gives you a page of LIKE A WHOLE LIST of versions.. How do you know which one to choose?
plus spent all night trying to download the recovery.img from clockworkmod.com as well as other links and all I get is this LONG encrypted script page displayed, and not an actual FILE that prompts you to download. going crazy here!
Click to expand...
Click to collapse
The link works, i ve managed to do it but twrp is useless if you want to flash any roms...I have tried every known version of cm for htc one s and I can't flash any of them in my phone through the twrp recovery...Always fails for no apparent reason! If you want my advise, do not waste your time, cause it's almost certain that ig you flash any custom rom, you will loose the advantages of htc sense, including the camera performance and special effects and also the beautiful widgets...If anyone though knows how to flash a REALLY nice rom with twrp we will be glad to hear his/her suggestions!
letakgr said:
The link works, i ve managed to do it but twrp is useless if you want to flash any roms...I have tried every known version of cm for htc one s and I can't flash any of them in my phone through the twrp recovery...Always fails for no apparent reason! If you want my advise, do not waste your time, cause it's almost certain that ig you flash any custom rom, you will loose the advantages of htc sense, including the camera performance and special effects and also the beautiful widgets...If anyone though knows how to flash a REALLY nice rom with twrp we will be glad to hear his/her suggestions!
Click to expand...
Click to collapse
sad part is I'm not going for anything fancy.. When I bought the phone (last week) it had version 4.1 on there and all I want to do is upgrade it to 4.2... and no it's NOT available through AT&T in anyways what's so ever.. hence the flash recovery chaos.
If no one response with a solid solution, then I'm just gonna let it be like you said.
Chri5topher said:
sad part is I'm not going for anything fancy.. When I bought the phone (last week) it had version 4.1 on there and all I want to do is upgrade it to 4.2... and no it's NOT available through AT&T in anyways what's so ever.. hence the flash recovery chaos.
If no one response with a solid solution, then I'm just gonna let it be like you said.
Click to expand...
Click to collapse
Tell me what do you want to do to your phone?
State in points, easy for me
blah
No it wont affect.
By the way, TWRP recovery has been the most successful one with The One S.
Google twrp and Download it for VILLE (THE S4 MODEL HTC ONE S) and then flash it.
Sent from my Nexus 7 using Tapatalk HD
khan.orak said:
No it wont affect.
By the way, TWRP recovery has been the most successful one with The One S.
Google twrp and Download it for VILLE (THE S4 MODEL HTC ONE S) and then flash it.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
but.. I don't have the one S.. I have.. just.. the ONE .. HTC ONE ha ha.. dude.. I don't know, cause I've been using the iphone since it's FIRST generation! so ALL this is new to me, but I am tech savvy enough to try to go the distance on this phone.
Chri5topher said:
but.. I don't have the one S.. I have.. just.. the ONE .. HTC ONE ha ha.. dude.. I don't know, cause I've been using the iphone since it's FIRST generation! so ALL this is new to me, but I am tech savvy enough to try to go the distance on this phone.
Click to expand...
Click to collapse
The One. Try the specific threads for the One.
Sent from my Nexus 7 using Tapatalk HD
HTC ONE S Stuck with "Entering Recovey" message
letakgr said:
Problem solved thanks to the mister above!!!!!Thank you very much! I'm now getting the jb upgrade!!!
Click to expand...
Click to collapse
how did you resolved this issue, currently I am facing same issue, mobile got stuckn with the message "entering recovery". Please help.

Categories

Resources