I have HTC One X. unlocked bootloader, rooted. Stock version 2.20. Tried to flash CM10 nightly build 01042013 through TWRP. First copied the roms into internal storage. Then used fastboot flash boot boot.img, then entered TWRP to wipe everything, factory reset, then try to flash rom, says error and failed. Tried several times, didn't work. I tried to reboot, the phone enters endless bootloop. Tried to use power+vol to enter fastboot again. Select recovery, phone bootloop, never enters recovery. Then I tried to flash CWM touch to phone. Still cannot enter recovery.
What's worse is that when the phone is on, it cannot charge. When usb is not connected, I can turn the phone off by keep holding power. But once the usb is connected the phone will turn on by itself, and the charging stops -- this way the remaining battery is kept being drained.
Please help! Thanks!!!
Try installing TWRP again via adb.
There is no CWM Touch for our version of the One X (only the non-touch version of CWM, and its not recommended). So you may have flashed a recovery for the wrong device. It doesn't sound like that was the initial cause of your woes, but it may have made the issue worse.
You can also try to relock the bootloader, RUU and start over again (re-unlock, install TWRP and flash).
You sure you downloaded CM10 for our (Snapdragon S4) version, and not the Tegra3 version of the One X? There is no reason that flashing a ROM would mess with recovery, unless you flashed the wrong version.
redpoint73 said:
Try installing TWRP again via adb.
There is no CWM Touch for our version of the One X (only the non-touch version of CWM, and its not recommended). So you may have flashed a recovery for the wrong device. It doesn't sound like that was the initial cause of your woes, but it may have made the issue worse.
You can also try to relock the bootloader, RUU and start over again (re-unlock, install TWRP and flash).
You sure you downloaded CM10 for our (Snapdragon S4) version, and not the Tegra3 version of the One X? There is no reason that flashing a ROM would mess with recovery, unless you flashed the wrong version.
Click to expand...
Click to collapse
I downloaded the ROM through this link
http://forum.xda-developers.com/showthread.php?t=1786696
which brought me to the download site:
http://get.cm/?device=endeavoru
I guess my battery is well below 30% now. I saw people said if I relock it with such low battery, I may end up not able to do anything after. Will that happen? I'll try to flash TWRP first. Thanks
Also, I cannot do adb at this time since I cannot enter system and if I use adb command in cmd on my PC, it says cannot find device.
Do you have a AT&T one x or international? How many cores does it have?
Sent from my HTC One XL using xda app-developers app
HTC One X = International
area51avenger said:
Do you have a AT&T one x or international? How many cores does it have?
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
The one is AT&T HTC one x. I think that's the most standard ATT version, I don't know how many cores it has though ..
qb200210 said:
The one is AT&T HTC one x. I think that's the most standard ATT version, I don't know how many cores it has though ..
Click to expand...
Click to collapse
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
HTC_Phone said:
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
Click to expand...
Click to collapse
I can still enter fastboot and can flash things into it using cmd from PC usb connection. It's just nothing worked: not able to boot pass htc white screen, keeps rebooting, turns on when usb connected, not able to charge, cannot enter recovery. Tried to re-flash TWRP, didn't work, still cannot enter recovery.
If you can get to fastboot, you're not bricked. Be sure you're pushing the right (Evita) version of TWRP; so far you've loaded your phone up with endeavour stuff.
Does adb devices show your phone? What are you seeing in Device Manager when it's plugged in? Are you sure you have all the HTC drivers installed? You might try switching USB ports and using a different cable.
HTC_Phone said:
Well if it says AT&T on the top of the phone it's most definitely a dual-core version, instead of the quad-core. But you downloaded a CM-endeavoru ROM which is the international. We here have the device codenamed "evita". It sounds to me that you've bricked your phone, unfortunately. However if it's still booting to the white HTC Screen there might be some hope.
I don't have the link handy, but if you wanna find the unbricking thread, it may help if you have knowledge of Linux
Click to expand...
Click to collapse
Thanks for pointing it out. Now I flashed boot.img from evita version and it enters recovery. Now the only question is that how can I download the correct rom into my phone since I don't think I can enter the system? Thanks!
iElvis said:
If you can get to fastboot, you're not bricked. Be sure you're pushing the right (Evita) version of TWRP; so far you've loaded your phone up with endeavour stuff.
Does adb devices show your phone? What are you seeing in Device Manager when it's plugged in? Are you sure you have all the HTC drivers installed? You might try switching USB ports and using a different cable.
Click to expand...
Click to collapse
Now I can enter TWRP, which I used to root this phone before without problems. Now I just need to push the right rom. However, if I choose Mount USB storage, my PC is asking me to format the disk. Should I do that or is there other ways I can push ROM into my phone? Thanks!
qb200210 said:
Now I can enter TWRP, which I used to root this phone before without problems. Now I just need to push the right rom. However, if I choose Mount USB storage, my PC is asking me to format the disk. Should I do that or is there other ways I can push ROM into my phone? Thanks!
Click to expand...
Click to collapse
Now in TWRP, I'm able to use adb push update.zip / to push the CM10 evita ROM into the phone. But when I tried to install, it still reports error:
Updating partition details ...
E: Unable to mount '/sdcard'
E: Unable to mount storage.
E: Mount: Unable to find partition for path '/update.zip'
Error flashing zip '/update.zip'
Updating partition details...
E: Unable to mount '/sdcard'
E: Unable to mount storage.
This happens with or without USB cable connected to PC. Thanks!
Format the sdcard to fat32
Sent from my HTC One XL using xda app-developers app
qb200210 said:
Should I do that or is there other ways I can push ROM into my phone? Thanks!
Click to expand...
Click to collapse
As stated, go ahead and format. It's quite common when having these problems to corrupt your sdcard, esp. when using CWM on this phone.
iElvis said:
As stated, go ahead and format. It's quite common when having these problems to corrupt your sdcard, esp. when using CWM on this phone.
Click to expand...
Click to collapse
Thanks for the tips! Now I formatted it into fat32, reboot into recovery, and I'm able to successfully install the CM10 evita ROM. However, after the reboot, the phone keeps the bootloop. The battery is 50% +. Is there something else I did wrong? Thanks!
qb200210 said:
Thanks for the tips! Now I formatted it into fat32, reboot into recovery, and I'm able to successfully install the CM10 evita ROM. However, after the reboot, the phone keeps the bootloop. The battery is 50% +. Is there something else I did wrong? Thanks!
Click to expand...
Click to collapse
Did you remember to flash the boot.img separately?
iElvis said:
Did you remember to flash the boot.img separately?
Click to expand...
Click to collapse
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
dan6677 said:
HTC One X = International
Click to expand...
Click to collapse
What??? Incorrect, and how can an AT&T user be saying this? The dual core S4 version is called the One X in US (AT&T) and Canada (Rogers), and called the One XL elsewhere.
Outside Canada and US, its true that One X refers to the quad core Tegra3 version. But the term "international" is a bit obsolete at this point, now that the S4 version has been released in some 6 or 7 countries.
The OP said he was on stock 2.20 firmware, which is AT&T. So I knew he had the AT&T version from the start.
To the OP, stick with ROMs and mods from this forum section to avoid the same mistake in the future: http://forum.xda-developers.com/forumdisplay.php?f=1538
---------- Post added at 10:17 PM ---------- Previous post was at 10:14 PM ----------
qb200210 said:
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
Click to expand...
Click to collapse
I know in the past, at least one nightly build of CM10 had a faulty kernel that caused the phone to be stuck on the boot splash. Flashing an older kernel made the ROM boot right up. Maybe that is the case with the one you tried. Or maybe just a bad download.
qb200210 said:
I have HTC One X. unlocked bootloader, rooted. Stock version 2.20. Tried to flash CM10 nightly build 01042013 through TWRP. First copied the roms into internal storage. Then used fastboot flash boot boot.img, then entered TWRP to wipe everything, factory reset, then try to flash rom, says error and failed. Tried several times, didn't work. I tried to reboot, the phone enters endless bootloop. Tried to use power+vol to enter fastboot again. Select recovery, phone bootloop, never enters recovery. Then I tried to flash CWM touch to phone. Still cannot enter recovery.
What's worse is that when the phone is on, it cannot charge. When usb is not connected, I can turn the phone off by keep holding power. But once the usb is connected the phone will turn on by itself, and the charging stops -- this way the remaining battery is kept being drained.
Please help! Thanks!!!
Click to expand...
Click to collapse
I had the same issue today, was trying to flash jellybam. I fastboot flash boot boot.img then entered TWRP and wiped then flashed the ROM and when I tried booting up I was in a boot loop. What I did is entered boot loader mode and factory reset ( which wiped my internal storage) and then I was able to enter recovery.
Sent from my HTC One XL using Tapatalk 2
qb200210 said:
Yes, I did that. But CM10 didn't work whatever I tried. Then I flashed boot.img of CleanROM and installed CleanROM. Finally it works! Thanks a lot for all the help!
Click to expand...
Click to collapse
Glad to hear you got it working. Too many damn bricks around these parts for my taste.
Related
I would not post unless i was absolutely stuck so here goes:
I have the AT&T One X and managed to unlock the bootloader with no problem. I want to flash CWM, root, and ultimately install the latest cyanmod.
Im stuck trying to get a functional recovery mod working. I have tried a few different methods of flashing the recovery and a few different versions as well, mostly newer ones ie recovery-clockwork-touch-5.8.3.1-endeavoru and 5.8.4.0. I tried the automatic flash and i have done the commands myself. In the end my phone will not boot recovery, i just get the HTC screen that says something about development purposes only.
I could really use some help as i believe i just bricked my phone as well.
Thank you much
Endeavour is the tegra version of the One X and that's the cwm version you flashed. I have no idea what the consequences of doing that are but you may have bricked your phone. I also suggest using TWRP instead of CWM if you do get your phone working again.
Sent from my One XL using xda-developers app
The fact that you are seeing the HTC screen is promising. You definitely want to be using TWRP instead of CWM if you have the North American HTC One XL (ie. "evita", NOT "endeavor" ). I think you need to download an evita version of TWRP, boot into the bootloader (by holding volume down during boot) and then flash it using fastboot.
OigMan said:
I would not post unless i was absolutely stuck so here goes:
I have the AT&T One X and managed to unlock the bootloader with no problem. I want to flash CWM, root, and ultimately install the latest cyanmod.
Im stuck trying to get a functional recovery mod working. I have tried a few different methods of flashing the recovery and a few different versions as well, mostly newer ones ie recovery-clockwork-touch-5.8.3.1-endeavoru and 5.8.4.0. I tried the automatic flash and i have done the commands myself. In the end my phone will not boot recovery, i just get the HTC screen that says something about development purposes only.
I could really use some help as i believe i just bricked my phone as well.
Thank you much
Click to expand...
Click to collapse
As he said your lucky u Can still get the white screen with a phone as fragile with flashing as this I would of done a bibit more research if I were you...but ultimately your going to hhave to use fastboot commands to get your thing back running I believe go check out many of ththe million " I bricked my phone by flashing a tegra thing " you'll see many trust me best of luck to you and once u get everything settled out don't flash cwm. Its unofficial and bad go with twrp. Great recovery but do your research with a device like this
I managed to unbrick my phone by reinstalling the stock RUU but im still stuck trying to instal CWM. What is the correct version i should be using with my AT&T One x?
OigMan said:
I managed to unbrick my phone by reinstalling the stock RUU but im still stuck trying to instal CWM. What is the correct version i should be using with my AT&T One x?
Click to expand...
Click to collapse
Do not use CWM. Install TWRP by downloading GooManager from the market, opening it, hitting menu and choosing "install openrecovery". That will install TWRP for you.
Sent from my One X using xda premium
OigMan said:
I managed to unbrick my phone by reinstalling the stock RUU but im still stuck trying to instal CWM. What is the correct version i should be using with my AT&T One x?
Click to expand...
Click to collapse
Facepalm downloadgoo manager and install from there
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
He probably forgot to flash boot.img in fastboot.
If you are bricked, this phone will not turn on and be listed as QHSUSB_DLOAD in windows.
edit: cwm + evita(htc one xl) = bad.
he needs TWRP
wiiareonfire said:
So get this: I've got a friend who owns this One X, right? He got it replaced, and he got back a phone running the "new OTA", which I'm assuming is 2.20. He unlocked his bootloader and got root, and tried to flash a custom recovery (CWM from what he tells me), and then it died. He knows that I'm good at the whole Android thing, so he gave me the phone with the task of bringing it back to life.
Given that my regular phone is a GNex, "bricked" and "softbricked" aren't terms I use often, so I'm not entirely sure it's applicable to this situation. But, I'll tell you everything I know about the situation.
When I power it up, it comes up with the htc splash, then the "This build is for development purposes only..." message. It stays like that for a little bit, then the screen goes off. It comes back within five seconds, and it just continues ad nauseum.
I'm able to get into hboot and fastboot (booting into the bootloader with power+voldown) and execute fastboot commands, but I really don't know what I should do, and even if I do, I don't have the files I need.
The bootloader has this information; I'm fairly sure it can help...
Code:
evita pvt ship s-on rl
HBOOT 1.14.0002
eMMC boot
Radio - 0.19as.32.09.11_2
I executed a fastboot command (I forget which one), and I wrote down the value...
Code:
mainver: 2.20.502.7
I assume this is the installed system version, or something similar, but please correct me if I'm wrong xD
All I'm trying to do is to get this thing to boot into Android. If I can do that much, I'm sure he'd be more than elated. Thing is, I'm not entirely sure what's wrong with this phone, much less what I'd have to do to fix it.
TL;DR
My friend's phone is screwed up, how do I fix it?
Click to expand...
Click to collapse
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Crappyvate said:
sounds like your FRIEND needs to flash in fastboot the boot.img that came with his rom...
Click to expand...
Click to collapse
absolutelygrim said:
He probably forgot to flash boot.img in fastboot.
Click to expand...
Click to collapse
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
wiiareonfire said:
Would I be able to get a stock boot.img and system.img from the 2.20 RUU? Should I even use the RUU for this?
Click to expand...
Click to collapse
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
First, extract boot.img onto comp. Move boot.img into adb files. Rezip Rom and transfer to sdcard. Fire up command prompt where you stored boot.img. type --> fastboot flash boot boot.img
Once successful, flash Rom IN RECOVERY. profit
Tell your FRIEND to follow posts before blindly flashing, he'd be more prepared
sent from my venom injected, blazingly fast as f#&k OneXL via xda premium
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
absolutelygrim said:
what ROM did he flash. copy the boot.img from that ROM and flash it in fastboot, then flash the ROM
Click to expand...
Click to collapse
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
subarudroid said:
Can you get into boot loader? Hold the volume down whilst the phone boots. Flash TWRP!! Clockworkmod is not supported for our device. Oh and very first. Make sure you have the Evita not the international one x.
Check this thread out. Might help
http://forum.xda-developers.com/showthread.php?p=33303798
Sent from my One X using xda premium
Click to expand...
Click to collapse
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
wiiareonfire said:
He didn't flash any ROM, only CWM. He wasn't ever able to get into recovery to flash anything.
Just did that, and it's still not working. Can't even boot into recovery.
I'm gonna need a boot.img, but he started from stock OTA. I don't know how the boot.img could've gone bad from flashing a bad recovery, but I'll try that anyway.
Question is, where would I get a boot.img for the stock sense ROM? Or, how would I be able to flash a ROM without being able to get into recovery?
Click to expand...
Click to collapse
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Crappyvate said:
hold your horses, let's take a deep breath here. Have you tried to reboot in recovery through adb ? If that does not work why don't you try to fastboot flash a proper recovery for the one x, TWRP http://forum.xda-developers.com/showpost.php?p=33179690&postcount=1
Click to expand...
Click to collapse
Code:
C:\Android>adb reboot recovery
error: device not found
Surprisingly enough, you need to be booted into android for adb commands to work. Even the bootloader option for "recovery" gets me nowhere.
Out of nowhere, he tells me he tried to flash a rom.
Ali: the rom that i flashed hmmm.
if i sent that to you would you be able to do anything?
well, tried flashing?
Me: a download link would be preferable
but yes, i'll need that
Ali Haider: got it.
give me a few minutes.
what if the rom wasn't supported?
because i can't completely remember which of the several roms i tried to flash were the problem
Me: what do ya mean "not supported"
Ali:
like clockwork- it apparently doesn't work
Me:
gimme whichever you flashed most revently
a link
i'll need the boot.img
and if you don't know which rom, gimme a list to narrow it down
and i'll go one by one
Click to expand...
Click to collapse
TL;DR, he flashed with CWM and that's why it's screwed up.
Ladies and gents, we might be getting somewhere with this. Albeit, slowly, thanks to my friend who can't read the posts.
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Sent from my One X using xda premium
subarudroid said:
I think Crappyvate has the right idea here. You need to flash a proper recovery.
Click to expand...
Click to collapse
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
wiiareonfire said:
So I've flashed TWRP at least three different times, and I can't the phone to boot into it.
I've flashed two different boot.img files, no avail.
He claims all he's done is fastboot flash CWM, and then the thing went down the drain. Splash screen over and over again, exactly what I'm seeing here. Is there any reason that flashing TWRP over it wouldn't work? Is there a fastboot command I can use to make sure the partition is clean?
Click to expand...
Click to collapse
What happens after flashing twrp in flashboot ? what msg do you get ?
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
wiiareonfire said:
Okay, scratch that. I flashed TWRP again and again through fastboot, and instead of using "recovery", I used "factory reset", and it opened up TWRP.
Fun fact: it's not able to mount the /sdcard, so using adb to push the zip for the ROM just crashes TWRP. That was my last-ditch plan to get the ROM file onto the phone to flash it. Anyone else got any idea how to get a file on there?
Click to expand...
Click to collapse
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Crappyvate said:
thats a cwm classic it corrupted the SD card. you need to reformat the sd card, can you mount usb through twrp ?
Click to expand...
Click to collapse
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
I believe Fat32, but I may be wrong on that.
And you can use windows built in formatter.
wiiareonfire said:
I formatted it... I think correctly? NTFS, right? If not, what file system, and what program should I use to format it that way?
Click to expand...
Click to collapse
yep fat 32, dunno windows sorry...
Yup fat32. That what I did. My first hox I soft bricked as well with cwm
Sent from my One X using xda premium
I formatted with FAT32... It's still not accepting the file. TWRP crashes when the adb push command is finished. Is there something I'm missing?
So I (foolishly) tried to root and flash the Android Revolution ROM onto my phone but as I should have expected, I failed.I have a plethora of problems, and I am not sure what my best course of action is:
so
1) I factory reset, so I have no recovery or ROM on my phone currently
2)My phone is in a bootloop (loads the HTC screen with a disclaimer saying "this build is for development... yadda yadda yadda" and then reboots
3)My phone will NOT powerdown, I have tried to power down my phone through bootloader, and it re"boots" and returns to bootloader once again.
4)I cannot flash any files from my PC to my phone, for example: When I try to flash boot_signed.img from the Rogers Evita Stock ROM, using
fastboot flash boot boot_signed.img, I get an error message saying "FAILED <remote: signature verify fail>" and this occurs for all files I have tried to flash
5)I have tried using ARUWizard to try and get the stock ROM onto my phone with no avail. From reading the forums I believe it is because my phone is using version 1.94.631.3 but the ARUWizard can only update to previous versions which is not allowed? (I am still very confused about this) one alternative I found on the forums was to create something called a goldcard but that required a microSD card which my phone does not have capabilities for.
So this is my dilemma, I think I am thoroughly screwed... any help or advice would be appreciated
You should still have twrp recovery even if you factory reset. Reboot into twrp, mount sd, transfer over a Rom that will work, wipe all and flash
Sent from my One X using xda premium
The_Zodiac said:
You should still have twrp recovery even if you factory reset. Reboot into twrp, mount sd, transfer over a Rom that will work, wipe all and flash
Sent from my One X using xda premium
Click to expand...
Click to collapse
I go to recovery, and it just goes immediately back to bootloader :s
I suggest starting with this thread and see what results you get.
You flashed a ROM for a different device that has a different partition layout, and that ROM installer may have possibly wiped out your partitions and left the device unrecoverable except through a JTAG brick repair
Have you tried flashing twrp again?
Sent from my One X using Xparent Green Tapatalk 2
If you're getting to the splash screen, you're not bricked. Don't start the unbricking stuff yet.
You need to get to bootloader and push a new recovery image. You probably screwed up your recovery partition when you flashed that Tegra 3 rom.
Once you've got recovery back, you just need to flash a correct rom.
If that doesn't work, try running a ruu from bootloader.
iElvis said:
If you're getting to the splash screen, you're not bricked. Don't start the unbricking stuff yet.
You need to get to bootloader and push a new recovery image. You probably screwed up your recovery partition when you flashed that Tegra 3 rom.
Once you've got recovery back, you just need to flash a correct rom.
If that doesn't work, try running a ruu from bootloader.
Click to expand...
Click to collapse
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again
paoul.sukii said:
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again
Click to expand...
Click to collapse
If you have recovery again why not try the method I listed?
Sent from my One X using xda premium
paoul.sukii said:
Okay, Ive got recovery back, but I need help either flashing the rom or running a ruu from bootloader. I am unsure of how to do either.
I tried flashing my ROM using:
fastboot flash ROM PJ83IMG.zip
but then I got the FAILED <remote: signature verify fail> message again
Click to expand...
Click to collapse
Just go into your custom recovery, mount sdcard, move the rom over, and flash in recovery.
The_Zodiac said:
If you have recovery again why not try the method I listed?
Sent from my One X using xda premium
Click to expand...
Click to collapse
Alright, well i tried installing the ZIP I had, and it said it failed...
Maybe I should try a different zip? could someone suggest a good ROM for me that is compatible with my phone? (dont want to make the same mistake again)
I just want a ROM that has Sense, and is running at least ICS. Stability and speed are my main concerns, thanks!
paoul.sukii said:
Alright, well i tried installing the ZIP I had, and it said it failed...
Maybe I should try a different zip? could someone suggest a good ROM for me that is compatible with my phone? (dont want to make the same mistake again)
I just want a ROM that has Sense, and is running at least ICS. Stability and speed are my main concerns, thanks!
Click to expand...
Click to collapse
Before you do anything else, you should probably double check what phone you have.
Android Revolution HD (http://forum.xda-developers.com/showthread.php?t=1562603) is NOT for the AT&T/Rogers One X or the Telstra One XL.
If you have an international One X, then you're in the wrong place. If you do have one of the phones listed above, then you need to go here and download one of those roms. Then flash using what The_Zodiac suggested.
jeffwyeh said:
Before you do anything else, you should probably double check what phone you have.
Android Revolution HD (http://forum.xda-developers.com/showthread.php?t=1562603) is NOT for the AT&T/Rogers One X or the Telstra One XL.
If you have an international One X, then you're in the wrong place. If you do have one of the phones listed above, then you need to go here and download one of those roms. Then flash using what The_Zodiac suggested.
Click to expand...
Click to collapse
If I have the HTC One X Evita with Rogers, will http://forum.xda-developers.com/showthread.php?t=1868236&highlight=rogers work?
paoul.sukii said:
If I have the HTC One X Evita with Rogers, will http://forum.xda-developers.com/showthread.php?t=1868236&highlight=rogers work?
Click to expand...
Click to collapse
Yessir, that'll work. (I've heard good things about that ROM, though I haven't tried it myself).
Just FYI, the One X on AT&T and Rogers is known internationally as the One XL, and as far as codenames go, is known as the Evita, as you pointed out. The international One X is the Endeavor, and ROMs are not cross-compatible. If you stay in the "AT&T, Rogers HTC One X, Telstra One XL" sub-forums here, you should be alright.
What version of twrp are you using? Try rolling back to a 2.3.x version. 2.4.x seems to have some issues.
iElvis said:
What version of twrp are you using? Try rolling back to a 2.3.x version. 2.4.x seems to have some issues.
Click to expand...
Click to collapse
Okay, I think I am going to go to bed, and try to approach this problem tomorrow.
I am running TWRP 2.4.x so I may try and downgrade that tomorrow. I used adb to push the ROM to my phone and it is on my sdcard
However, when I try to install the ROM, it tells me that it failed... I tried clearing all caches etc but i keep getting the same errors. The weirdest part is that when I reboot my phone, the ROM disappears...
The error that I am getting is:
E:Unable to mount '/sdcard'
E:Unable to recreate android secure folder.
E:Unable to mount '/sdcard'
E:unable to mount '/sdcard'
Updating partition details...
E:Unable to mount storage.
E:Unable to mount /sdcard during GUI startup.
Running boot script...
Finished running boot script.
E:Unable to mount /sdcard when trying to read settings file.
E:Unable to mount '/sdcard'
E:Unable to mount '/sdcard'
Click to expand...
Click to collapse
This is the message that is displayed in recovery, to the letter, I'm not sure if this helps...
Obviously something to do with my sdcard is wrong, preventing connection between the sdcard and something else, but maybe you guys could dig deeper, past the elementary
Thank you guys for the help you've given me so far, the outlook for my phone is much brighter now, I will check back tomorrow and continue to try and fix my phone!
Your sdcard is indeed corrupted.
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Walk through that guide using the files for the Evita on that page, it should fix your sdcard. After that you can go ahead and push the rom to the sdcard again and then reflash and see if that does the trick!
jeffwyeh said:
Your sdcard is indeed corrupted.
http://forums.team-nocturnal.com/sh...ountable-internal-storage-on-the-HTC-One-X-XL
Walk through that guide using the files for the Evita on that page, it should fix your sdcard. After that you can go ahead and push the rom to the sdcard again and then reflash and see if that does the trick!
Click to expand...
Click to collapse
Thank all of you so much! my problem is resolved! Phone is working great!
paoul.sukii said:
Thank all of you so much! my problem is resolved! Phone is working great!
Click to expand...
Click to collapse
Awesome! Glad to hear it!
Hi, everything messed up from using the stupid TWRP 2.6.0.0 .... I was going to flash a custom rom , but it didn't let me, so I did a little research that I need 2.3.3.0 in order to instal any custom rom.So I tried to switch to 2.3.3.0 but it didn't let me... after that I tried to push stock recovery and now i'm stuck at the white HTC Entering Recovery ( pink letters) screen, ( The recovery just doesn't load) ... I just want to finish with this , and go back to my stock htc rom with not roots or anything.. im tired of this seriously.....
When I try to run RUU I get stuck at the Black HTC Letters screen , the the setup stops and says that it will try to repair my phone, sadly with no result every time.. I think that I don't have any OS on my phone right now, because when RUU starts it shows :
Change image version from : ( blank space)
To: ..... bla bla bla , ( the version of the ruu) ...
I have no problems with entering fastboot and unlocking/relocking my Hboot.
Any help about restoringmy phone will be appreciated . Thanks , I'm online all the time so if I get any responses I'll answer quick.
P.S. I can't mount my usb storage from anywhere, and it doesn't show up on my PC when i connect the usb
looperman said:
Hi, everything messed up from using the stupid TWRP 2.6.0.0 .... I was going to flash a custom rom , but it didn........................
P.S. I can't mount my usb storage from anywhere, and it doesn't show up on my PC when i connect the usb
Click to expand...
Click to collapse
Don't lose hope, don't panic.
Tell me which RUU did you use?
Also, what is your CID?
How did you flash your recovery ?
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
Don't lose hope, don't panic.
Tell me which RUU did you use?
Also, what is your CID?
How did you flash your recovery ?
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
looperman said:
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Rad io_16.21.20.02U_16.09.20.11_M2_release_286571_sign ed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_ 1.06s.50.02.27_2_10.08.50.04L__release_271119_sign ed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
Click to expand...
Click to collapse
If you downloaded RUUs from androidruu, then it's a case of bad RUU.
Sent from my HTC One S using Tapatalk 4 Beta
khan.orak said:
If you downloaded RUUs from androidruu, then it's a case of bad RUU.
Sent from my HTC One S using Tapatalk 4 Beta
Click to expand...
Click to collapse
well what am I supposed to do ?
looperman said:
well I think that it doesn't really matter which RUU I "used" because it doesn't even get me in the process of installing...
still , tried these two:
RUU_VILLEC2_U_ICS_40_S_HTC_Europe_2.15.401.100_Radio_16.21.20.02U_16.09.20.11_M2_release_286571_signed
RUU_Ville_U_ICS_40_S_HTC_Europe_2.21.401.10_Radio_1.06s.50.02.27_2_10.08.50.04L__release_271119_signed
I flashed all recoveries with ONE S all in one tool kit,
first i was with TWRP 2.5 i think , then i flashed 2.6, and 2.3.3.... now I flashed the stock recovery , still stuck...
Click to expand...
Click to collapse
Okay, just now I noticed. You used two Different RUUs for two different versions.
The 1st one is for S3/C2 version, the 2nd one is for S4 version.
Use This Thread to download RUU's only for your version (S4 or S3 whichever you have got). In your case, it does matter which RUU you use.
If you need any help further just ask away.
the thing is that the RUU doesn't get to the process of installing , and I have used those RUU's before....
I need some solution the get to a working recovery and instal some kind of OS because the last time I could get in my recovery it said that I don't have any OS installed...
looperman said:
the thing is that the RUU doesn't get to the process of installing , and I have used those RUU's before....
I need some solution the get to a working recovery and instal some kind of OS because the last time I could get in my recovery it said that I don't have any OS installed...
Click to expand...
Click to collapse
okay you gonna need fastboot for this. What I have been successful with is:
1. Download an RUU (VERSION SPECIFIC!).
2. Go into Bootloader -> Then select FASTBOOT
3. Connect your Phone to PC. It should say Fastboot - USB mode.
4. Run the RUU, it will get you through all the steps.
khan.orak said:
okay you gonna need fastboot for this. What I have been successful with is:
1. Download an RUU (VERSION SPECIFIC!).
2. Go into Bootloader -> Then select FASTBOOT
3. Connect your Phone to PC. It should say Fastboot - USB mode.
4. Run the RUU, it will get you through all the steps.
Click to expand...
Click to collapse
doesn't work as I've told you , it happens with every RUU ... I get the Black screen with white HTC letters...
I think that what RUU does is : it updates the version my software I think it just doesn't place a new software right away( just an update), but as TWRP said I don't have OS installed...
can anyone help me ?
looperman said:
doesn't work as I've told you , it happens with every RUU ... I get the Black screen with white HTC letters...
I think that what RUU does is : it updates the version my software I think it just doesn't place a new software right away( just an update), but as TWRP said I don't have OS installed...
Click to expand...
Click to collapse
Man you're making this difficult. The more I want to help you, the more you become hasty.
RUU doesn't do what you think. It puts New software, updates firmware (hboot, radio, RECOVERY), so yes it is basically a one-stop solution.
Please calm down as panicking won't help.
Tell me your One S version (S3/S4) at least? so that we can move forward in right direction. and also your CID
Tell me what recoveries and RUU you tried. and what errors do you get while you run them.
EDIT: Thanks to @tivofool I forgot to mention that you have to RELOCK your bootloader before running RUU
I'm with S3
I wrote the 2 RUU's I tried to use,
before that i tried TWRP 2.5.0.0,2.3.0.0.,2.6 and finally I flashed factory stock recovery that's it and both my carrier and bl are unlocked
P.S. : Yeah i knew about the relocking but still stuck on black screen with white HTC Letters
looperman said:
I'm with S3
I wrote the 2 RUU's I tried to use,
before that i tried TWRP 2.5.0.0,2.3.0.0.,2.6 and finally I flashed factory stock recovery that's it and both my carrier and bl are unlocked
P.S. : Yeah i knew about the relocking but still stuck on black screen with white HTC Letters
Click to expand...
Click to collapse
Black Screen with HTC is the oem update screen.
Okay do this please and we'll try to see if there's a problem with the HBOOT. Give me this info and We'll reflash HBOOT.
Go to fastboot and connect your phone to PC.
Enter this command from your PC:
Code:
fastboot getvar all
post results here (MINUS IMEI AND SERIAL #)
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
looperman said:
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
Click to expand...
Click to collapse
That was fast.
I am using Viper ROM and it's very good. Customization and speed.
For a better battery life, BULLETPROOF KERNEL.
Edit: how did you get it to work by the way.
Viper rom is for s4 only isn't it ?
looperman said:
just a second, I got a working recovery... I mean i can get in it and everything and I can mount the USB Storage too.
What Rom would you recommend ?
Click to expand...
Click to collapse
Make sure you flash a S3 Rom (you mentioned having a s3 right?)
Sent from my HTC VLE_U using Tapatalk 2
looperman said:
Viper rom is for s4 only isn't it ?
Click to expand...
Click to collapse
Oh yes sorry.
okay, so ... I'm going to explane everything I did, I hope I'll help some other people too.
I flashed TWRP from One_S_All-In-One_Kit_v4.0 but without luck, then i flash the factory stock recovery, still the phone was letting me into any of these two recoveries, then i decided reflash the same TWRP again and it worked,
First I couldn't mount the storage from the recovery , but it was still showing in "My Computer" , I had only one option and it was to Format the Storage. So I did.. then copied this rom with gapps on it ---> http://forum.xda-developers.com/showthread.php?t=2164406
Fully wiped --> Flash Rom , then Flash Gapps, ---> then I booted in fastboot to boot from CMD the "boot.img" with "fastboot flash boot boot.img" from the Pacman Rom and then I Rebooted the HTC and Done
Huge thanks to @khan.orak
I hope I helped someone with the same ****tyass problem.
looperman said:
okay, so ... I'm going to explane everything I did, I hope I'll help some other people too.
I flashed TWRP from One_S_All-In-One_Kit_v4.0 but without luck, then i flash the factory stock recovery, still the phone was letting me into any of these two recoveries, then i decided reflash the same TWRP again and it worked,
First I couldn't mount the storage from the recovery , but it was still showing in "My Computer" , I had only one option and it was to Format the Storage. So I did.. then copied this rom with gapps on it ---> http://forum.xda-developers.com/showthread.php?t=2164406
Fully wiped --> Flash Rom , then Flash Gapps, ---> then I booted in fastboot to boot from CMD the "boot.img" with "fastboot flash boot boot.img" from the Pacman Rom and then I Rebooted the HTC and Done
Huge thanks to @khan.orak
I hope I helped someone with the same ****tyass problem.
Click to expand...
Click to collapse
Glad it worked for you buddy.
So I bought a HTC One Mini recently (maybe a month back or so). I loved it, and I decided to root it, (I'm S-ON btw) but I didn't know what custom ROMs were. So I decided to try getting one,(the onedroid one) and failed many times because it said failed. I had TWRP, so when I tried to flash the zip, and when it failed, it said clear cache/davlik or whatever, and I clicked it. Ever since, I've been stuck in a boot loop, and whenever I tried to press recovery, or factory reset, it would say Entering Recovery... at the top, and then the teamwin logo part would flash for a split second and keep flashing for like 3 seconds, and the bootloop would start all over again.
I tried to fastboot erase cache, I even fastboot oem lock 'd, but now it's relocked and whenever I try to enter recovery or factory reset, it just puts me back into the bootloop/bootloader. I really need help on this please.
I've also flashed a new recovery when my bootloader was unlocked, and that didn't work either. Please help, thanks!
alright so update: I fixed that problem, my internal s torage was 0 MB so I formatted my data, and I have storage now as well. I don't know what to do from this point on, I tried factory resetting but theres no OS on the SDCard or anywhere, so... yeah. I'm downloading a stock android 4.2.2/sense 5 (which was what was on my HTC one before **** went down) to see if I can flash it on there and just install it on. Will give feedback when I'm done.
Okay, so now I am completely stuck. I can get into recovery, but I don't know what to do at all now. Help me please.
Omarion23145 said:
Okay, so now I am completely stuck. I can get into recovery, but I don't know what to do at all now. Help me please.
Click to expand...
Click to collapse
download a rom and sideload it. next time do a nandroid backup.
Omarion23145 said:
So I bought a HTC One Mini recently (maybe a month back or so). I loved it, and I decided to root it, (I'm S-ON btw) but I didn't know what custom ROMs were. So I decided to try getting one,(the onedroid one) and failed many times because it said failed. I had TWRP, so when I tried to flash the zip, and when it failed, it said clear cache/davlik or whatever, and I clicked it. Ever since, I've been stuck in a boot loop, and whenever I tried to press recovery, or factory reset, it would say Entering Recovery... at the top, and then the teamwin logo part would flash for a split second and keep flashing for like 3 seconds, and the bootloop would start all over again.
I tried to fastboot erase cache, I even fastboot oem lock 'd, but now it's relocked and whenever I try to enter recovery or factory reset, it just puts me back into the bootloop/bootloader. I really need help on this please.
I've also flashed a new recovery when my bootloader was unlocked, and that didn't work either. Please help, thanks!
Click to expand...
Click to collapse
1st. Rule of hacking up your device.
- Never flash any Rom that's not found in its own device forum. So since your in the mini forum flash only the roms that are available or you'll have a paper weight ( brick ) ... So that's your whole issue with device bootlooping ...
Omarion23145 said:
alright so update: I fixed that problem, my internal s torage was 0 MB so I formatted my data, and I have storage now as well. I don't know what to do from this point on, I tried factory resetting but theres no OS on the SDCard or anywhere, so... yeah. I'm downloading a stock android 4.2.2/sense 5 (which was what was on my HTC one before **** went down) to see if I can flash it on there and just install it on. Will give feedback when I'm done.
Click to expand...
Click to collapse
Again only flash HTC One Mini roms. Not HTC One roms. Your going to nuke your device by not knowing the basics of flashing. So grab a HTC One Mini rom. And if all is still boot looping unlock your bootloader and obtain a stock recovery for this device and flash it then factory reset from bootloader, it will fix corrupt partitions.. Then flash philz latest recovery from our One Mini forums..
Also need to know your hboot version. Is it 2.21 or 2.22??
Omarion23145 said:
Okay, so now I am completely stuck. I can get into recovery, but I don't know what to do at all now. Help me please.
Click to expand...
Click to collapse
Like I said download a Rom from our development forums found in the One Mini forums.. but like I said I need your hboot version to decide what rims you may flash.
Sent from my HTC One mini using Tapatalk
xXminiWHOOPERxX said:
1st. Rule of hacking up your device.
- Never flash any Rom that's not found in its own device forum. So since your in the mini forum flash only the roms that are available or you'll have a paper weight ( brick ) ... So that's your whole issue with device bootlooping ...
Again only flash HTC One Mini roms. Not HTC One roms. Your going to nuke your device by not knowing the basics of flashing. So grab a HTC One Mini rom. And if all is still boot looping unlock your bootloader and obtain a stock recovery for this device and flash it then factory reset from bootloader, it will fix corrupt partitions.. Then flash philz latest recovery from our One Mini forums..
Also need to know your hboot version. Is it 2.21 or 2.22??
Like I said download a Rom from our development forums found in the One Mini forums.. but like I said I need your hboot version to decide what rims you may flash.
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2665746
Would sideloading that (the purestock version) work? My HBOOT is 2.21, S-ON.
Omarion23145 said:
http://forum.xda-developers.com/showthread.php?t=2665746
Would sideloading that (the purestock version) work? My HBOOT is 2.21, S-ON.
Click to expand...
Click to collapse
Yes, but since your s-on you'll have to flash boot.img manually
Sent from my HTC One mini using Tapatalk
xXminiWHOOPERxX said:
Yes, but since your s-on you'll have to flash boot.img manually
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
Wait so do I just adb sideload it or do I just "fastboot flash boot boot.img" ?
Omarion23145 said:
Wait so do I just adb sideload it or do I just "fastboot flash boot boot.img" ?
Click to expand...
Click to collapse
Adb sideload the Rom.. Flash the Rom... Then enter fastboot and flash boot.img with the command line you just wrote dealing with fastboot
Sent from my HTC One mini using Tapatalk
xXminiWHOOPERxX said:
Adb sideload the Rom.. Flash the Rom... Then enter fastboot and flash boot.img with the command line you just wrote dealing with fastboot
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
Haha, sorry! Recently got the HTC One Mini so I'm not really used to all this (I just made the switch from iOS to Android a month ago). Anyways, thanks! I'll update if it worked or not.
Omarion23145 said:
Haha, sorry! Recently got the HTC One Mini so I'm not really used to all this (I just made the switch from iOS to Android a month ago). Anyways, thanks! I'll update if it worked or not.
Click to expand...
Click to collapse
HTC are the best android smartphones. Just wait and you'll see
Sent from my HTC One mini using Tapatalk
xXminiWHOOPERxX said:
HTC are the best android smartphones. Just wait and you'll see
Sent from my HTC One mini using Tapatalk
Click to expand...
Click to collapse
Haha. That fixed it! Thanks a lot man, I really appreciate it. I thought it would never get fixed .