Related
I was one of the unlucky testers before Steve0007 closed the thread. Did anyone figure out how to save our Sensation after the bad flash? My phone does not light up or respond to any button presses but when plugged into the computer it is recognized as an "unrecognized device."
I guess this is the risk we run being early testers. Hopefully someone figures it out otherwise I've got myself very expensive paper weight.
I assume no two button rescue? And this should be in q/a or general
Can you get to the bootloader?
Sent from my Sensation using xda premium
what did he brick people's phones with what was it supposed to be?
Wrong section. And that happened to me when i got an hd2 and i bricked it. Luckily it was 2 days after i bought it so tmobile gave me another because they thought something was wrong with it. But next time please post in the right section. Thanks.
nba1341 said:
what did he brick people's phones with what was it supposed to be?
Click to expand...
Click to collapse
Its probably only a soft brick
Sent from my Sensation using xda premium
Thank god I didn't flash it, I just finished downloading it when people started reporting issues.
Anyway, I'm sure he didn't mean for it to happen. If you have a spare battery, have you tried putting that one in?
These things are usually flash at your own risk.
I would never flash a ruu, unless it's official it could cause problems.
Sent from my Sensation using Tapatalk
Also, if it doesnt work and if you have tmo. Tell them bs and they will get you one. Just some advice and please dont flame me.
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Yes as I said, this happened to me exactly when i had a tmo HD2 and flashed a european ruu and it was dead. I tried everything. You will have better luck to talk to your insurance company.
Have you got ADB installed on your pc? If not start downloading and installing it. I will find some links, in just a sec.
Edit:
New to ADB CLICK HER
More to set up path CLICK HERE
http://www.mediafire.com/?rrwi4f258lie1r7
Extract to system 32 or sysWOW64 (64bit)
Try 3 finger salute (VOL UP,VOL DOWN + POWER) with your phone plugged into pc and pc volume up see if it makes a sound like a device has connected.
Whats was this RUU anyway?
if you just need ADB you dont need all of the stuff above or to set up a path if its extracted to those folders
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
This is excatly what happened to me.Computer wont see the phone though,so no adb fix can be applied.Mnn i'm so pissed as i dont have insurance.
usually blagging HTC will do the trick for a repair,dont mention XDA, ROOT, ICS or basically anything except your phone said update was available and the battery died
Click to expand...
Click to collapse
roflcopter is 10chars
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
What does it recognize it as?
unrecognized usb device
Ok guys, it looks like the firmware that I posted to another thread from 3.06 bricked few devices. I have flashed it and it worked fine, so i tried again with the package i posted and indeed it is corrupted as it bricked also mine
My device does not respond, so I would think it is dead
I feel sorry for those who have bricked also theirs based on the package i posted.
I am closing my Rom thread and starting now my Rom developments will be for my own use. I will not publish anymore my work.
Again I feel sorry for those who have lost their devices.
Steve
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Arrrggghhhh,This could not have come at a worse time
nba1341 said:
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Click to expand...
Click to collapse
Because as far as I know no way to get them back
I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?
TinnuiN said:
I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?
Click to expand...
Click to collapse
Can you still get into AP fastboot?
Sent from my MB865 using xda premium
There's totally still hope
It takes some pretty bad luck for this to actually kill it
just needs to run again, maybe manually
BUT, we need more detail to help. what version of the phone (ATT, SEARET, etc), what os version were you on before (ICS leak 1, 2, ota, GB, etc), what step was it on when it failed, what does the phone do now (totally dead, white light only, can turn on into fastboot with boot failure, etc.)
also, how much battery did you have when you tried to flash.
be specific, and we can help, do not lose hope quite yet.
lkrasner said:
There's totally still hope
It takes some pretty bad luck for this to actually kill it
just needs to run again, maybe manually
BUT, we need more detail to help. what version of the phone (ATT, SEARET, etc), what os version were you on before (ICS leak 1, 2, ota, GB, etc), what step was it on when it failed, what does the phone do now (totally dead, white light only, can turn on into fastboot with boot failure, etc.)
also, how much battery did you have when you tried to flash.
be specific, and we can help, do not lose hope quite yet.
Click to expand...
Click to collapse
I can still boot to AP fast boot, in fact thats all it boots from, i was running SVC6, so 2.3.6 and i was trying to roll back to 2.3.5 so i could update to ota ICS. when i turn the phone on all it does is boot to AP fast boot.
Its an AT&T atrix 2, the battery was at 70% when flashing, and i was on step 6, i tried re running it, it stayed on step 1 for hours.
Did you make sure to patch the fxz?
Sent from my MB865 using xda premium
Axis_Drummer said:
Did you make sure to patch the fxz?
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
after it was to late.
TinnuiN said:
after it was to late.
Click to expand...
Click to collapse
If you can still access fastboot, you're still ok. Just try it again. Once you patch the file, you shouldn't have to do it again.
If it's not playing well try a different computer.
If you can't access fastboot, and no lights at all will come on, you may be out of luck man..
Sent from my MB865 using xda premium
TinnuiN said:
I'm pretty sure i screwed myself here, but hopefully there might be a chance to fix it. I was flashing my phone back to stock gingerbread by using RSD, my phones data cord wiggled itself out when i bumped my desk, now its bricked. :\ any possibility of fixing this?
Click to expand...
Click to collapse
Have you tried this????
http://forum.xda-developers.com/showthread.php?t=1539167
Sent from my MB865 using xda premium
Okay, now i have a new problem, the battery is to low to program, if i plug the phone into the wall then i can get it to boot to the AP menu, and if i plug it into my computer i can get it to show a white solid light. any ideas?
TinnuiN said:
Okay, now i have a new problem, the battery is to low to program, if i plug the phone into the wall then i can get it to boot to the AP menu, and if i plug it into my computer i can get it to show a white solid light. any ideas?
Click to expand...
Click to collapse
You need to charge your battery somehow if you don't have wall charger try Mcgrubber method...
Sent from my MB865 using xda premium
Tried installing a ROM, and being the noob that I am it was an International Rom. I used TeamWin. Can't post outside links because I'm new. The rom was IceColdJelly AOKP ROM from onexroot.com
I realize I was stupid. I just want out of this situation and I'll be really careful for now on. Is my HOX a lost cause? I bought it about 2 weeks ago (Really unlucky with the whole price drop...). And now, I've done this.
I get it, I've learned my lesson. XDA please help me out. How can I fix this brick? (If it is a brick? I'm assuming.)
Epsilon707 said:
Tried installing a ROM, and being the noob that I am it was an International Rom. I used TeamWin. Can't post outside links because I'm new. The rom was IceColdJelly AOKP ROM from onexroot.com
I realize I was stupid. I just want out of this situation and I'll be really careful for now on. Is my HOX a lost cause? I bought it about 2 weeks ago (Really unlucky with the whole price drop...). And now, I've done this.
I get it, I've learned my lesson. XDA please help me out. How can I fix this brick? (If it is a brick? I'm assuming.)
Click to expand...
Click to collapse
Yes, it's a brick, but there is a fix if you have access to a Linux computer and know what you're doing.
beaups said:
when the device is bricked (qhusb mode), after pushing and holding power for ~10 seconds - in linux shortly thereafter all of the partitions will enumerate and expose themselves to linux for about 5 seconds (you'll see sdX1, sdX3, sdX8, about 30 partitions alltogether). During that quick 5 seconds you can DD whatever you feel like back to those partitions.
.
This is how I've recovered bricks. Corrupt hboot --> Brick device. DD back correct hboot while in this mode --> unbricked
Click to expand...
Click to collapse
It successfully flashed? Than yes follow his directions only way out if it successfully flashed and your device is unresponsive
omario8484 said:
It successfully flashed? Than yes follow his directions only way out if it successfully flashed and your device is unresponsive
Click to expand...
Click to collapse
Good point, if you were on stock 2.20 before, it's not bricked, you just need to get back into recovery and flash something else.
bricked
iElvis said:
Good point, if you were on stock 2.20 before, it's not bricked, you just need to get back into recovery and flash something else.
Click to expand...
Click to collapse
It was stock 2.20. I bought the phone a week or two ago. HBOOT 1.14. But the phone still won't turn on?
Epsilon707 said:
It was stock 2.20. I bought the phone a week or two ago. HBOOT 1.14. But the phone still won't turn on?
Click to expand...
Click to collapse
Can your computer see it? Was it fully charged before?
Try plugging into the charger for a while. The battery in this phone has a weird tendency to suddenly lose all its charge.
iElvis said:
Can your computer see it? Was it fully charged before?
Try plugging into the charger for a while. The battery in this phone has a weird tendency to suddenly lose all its charge.
Click to expand...
Click to collapse
Computer cannot see it. Atleast constantly. My computer makes a noise like a drive was plugged in, then shortly after an error-like similar sound.
I'll try charging it for a few hours. Thanks!
Epsilon707 said:
Computer cannot see it. Atleast constantly. My computer makes a noise like a drive was plugged in, then shortly after an error-like similar sound.
Click to expand...
Click to collapse
That's not good. What does it look in explorer like when it shows up? Do you see QHSUSB anywhere?
The new hboots won't allow flashing of an incompatible Rom. Make sure you charge it for a while hold power button and volume down for a few seconds and see if capacitive buttons flash. If so, release power button but continue to hold volume down and see what happens
Sent from my HTC One XL using xda app-developers app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Word of advice bro, don't flash anything what so ever from anywhere except xda. You'll be asking for trouble
Sent from my HTC One XL using xda app-developers app
iElvis said:
That's not good. What does it look in explorer like when it shows up? Do you see QHSUSB anywhere?
Click to expand...
Click to collapse
Nope. I'm running Windows by the way. I don't have access to a Linux computer right now, but I will later.
Epsilon707 said:
Nope. I'm running Windows by the way. I don't have access to a Linux computer right now, but I will later.
Click to expand...
Click to collapse
Okay, try what InflatedTitan suggested and see what happens.
InflatedTitan said:
The new hboots won't allow flashing of an incompatible Rom. Make sure you charge it for a while hold power button and volume down for a few seconds and see if capacitive buttons flash. If so, release power button but continue to hold volume down and see what happens
Sent from my HTC One XL using xda app-developers app
---------- Post added at 12:19 AM ---------- Previous post was at 12:18 AM ----------
Word of advice bro, don't flash anything what so ever from anywhere except xda. You'll be asking for trouble
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Zero response. I'll keep trying.
Epsilon707 said:
Zero response. I'll keep trying.
Click to expand...
Click to collapse
Let it charge for a few hours and try again.
Still no avail. Any other ideas?
I could really use some help. Anyone have an idea or a suggestion on what to do? I also don't suppose this is covered under my warranty
Okay, a couple of questions:
-Are you certain you were on 2.20? I ask because there have been cases of people buying One Xs recently and getting phones on 1.85.
-The phone is completely unresponsive despite being plugged into an outlet (not your computer) for a couple of hours?
iElvis said:
Okay, a couple of questions:
-Are you certain you were on 2.20? I ask because there have been cases of people buying One Xs recently and getting phones on 1.85.
-The phone is completely unresponsive despite being plugged into an outlet (not your computer) for a couple of hours?
Click to expand...
Click to collapse
Yes, I am certain. I remember checking it in the About Phone section of settings.
Completely unresponsive, but I'll keep trying.
Epsilon707 said:
Yes, I am certain. I remember checking it in the About Phone section of settings.
Completely unresponsive, but I'll keep trying.
Click to expand...
Click to collapse
Okay, one last thing. Open up Device Manager in Windows and expand the whole directory tree. Check "DVD/CD-ROM devices" in particular. Plug your phone in and see what happens.
If nothing happens at all, try leaving it plugged in overnight and see if anything is different. If it's still dead, it's bricked, whatever you did with it. Since it's new, you should be able to return it and get a new one.
Idk what to say if you were on 2.20 it should of failed the Rom flash...but it successfully flashed ?
omario8484 said:
Idk what to say if you were on 2.20 it should of failed the Rom flash...but it successfully flashed ?
Click to expand...
Click to collapse
I'm f'ing baffled myself mate.
Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Can you get into Odin mode or download mode? If you can, follow this thread. http://forum.xda-developers.com/showthread.php?t=1974114
Sent from my SCH-I535 using xda premium
darthsentinel said:
Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Click to expand...
Click to collapse
Just so you know, it isn't the USB debugging. I just did the same procedure using Windows 7 and Odin 3.07 with debugging on, and it worked first shot. Could be Windows 8, but I can't say for certain.
m-cat said:
Can you get into Odin mode or download mode? If you can, follow this thread. http://forum.xda-developers.com/showthread.php?t=1974114
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Nope, it was quite literally hard bricked. No getting it into anything.
a.demarco said:
Just so you know, it isn't the USB debugging. I just did the same procedure using Windows 7 and Odin 3.07 with debugging on, and it worked first shot. Could be Windows 8, but I can't say for certain.
Click to expand...
Click to collapse
Hrmm, well that is annoying, as I don't have access to a Windows 7 Computer to try it again... But thanks for the heads-up!
Are you SURE you followed DroidmodderX's instructions to the T? I've seen this happen from flashing the file in the wrong slot in Odin. Did you make sure to put it in the PDA slot?
I too used this method to root and unlock a while back. I would feel confident using it again if I needed to.
nicholi2789 said:
Are you SURE you followed DroidmodderX's instructions to the T? I've seen this happen from flashing the file in the wrong slot in Odin. Did you make sure to put it in the PDA slot?
I too used this method to root and unlock a while back. I would feel confident using it again if I needed to.
Click to expand...
Click to collapse
Yes, I was very sure to put it in the PDA slot. In fact, I remember double-checking that I did that because I thought it was unusual.
darthsentinel said:
Yes, I was very sure to put it in the PDA slot. In fact, I remember double-checking that I did that because I thought it was unusual.
Click to expand...
Click to collapse
Hmm. Are you sure you got a good download of the bootchain?
nicholi2789 said:
Hmm. Are you sure you got a good download of the bootchain?
Click to expand...
Click to collapse
Almost completely positive. At the very least, the MD5 Matched.
darthsentinel said:
Almost completely positive. At the very least, the MD5 Matched.
Click to expand...
Click to collapse
Okay. So you've installed the correct drivers for your phone as well right? It shows up as SCH-I535 on your computer?
Sent from my MOAR'D Galaxy S3 via tapatalk 2
nicholi2789 said:
Okay. So you've installed the correct drivers for your phone as well right? It shows up as SCH-I535 on your computer?
Sent from my MOAR'D Galaxy S3 via tapatalk 2
Click to expand...
Click to collapse
Yes, it does indeed.
Did you uncheck Auto Reboot when you were supposed to?
darthsentinel said:
Normally, I wouldn't ask for help with a problem like this, but I'm rather concerned and could use assistance. Several days ago, I attempted to unlock and root my Verizon GS3. I followed the instructions from the XDA article, along with the ones provided in DroidModd3rX's YouTube video exactly on my VZW GS3, build JZO54K. I hard bricked my phone after flashing the VRALEC bootchain. It only showed up in the Device Manager on Windows 8 as QHSUSB_DLOAD. It was stuck like that as soon as I flashed the bootchain. Is there something I've done wrong that I could have done differently to prevent it from happening? I had just purchased it the day before, so I was able to get a replacement, but I'm highly interested in rooting my device (I've successfully rooted every other phone I've had) and want to ensure this doesn't happen again. Is it a problem with Windows 8, is it the build my phone is running on, or is it perhaps because I had USB Debugging checked on? I just find it odd that I've had this problem when I followed all the proper protocol. And yes, I did check the MD5, it was fine.
Click to expand...
Click to collapse
I have always followed the guide here. Not sure what version of the OS you have but I odin my phone back to the original factory and then run the root posted here http://forum.xda-developers.com/showthread.php?t=1762709
Super Interesting
I just received two phones from verizon and I followed the same exact instructions, on the first phone it worked like a charm. And on the second phone - at the very same step - it just blinked off and that was all she wrote. I tried a full power cycle, charging all night, and using the USB > PC connection to maybe kick it out of its funk. All I got was the QHSUSB_DLOAD popup when I plugged it in. Searching for that turns up a few things, but mostly for HTC phones. I also installed Keis and tried to redo all the driver junk with that, still nothing. So sad.
I have to ask the most obvious. Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
m-cat said:
I have to ask the most obvious? Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The battery was charging all night, I had meant to put this in an edit but had to wait five minutes and wandered off . I also forgot to add that it was a VZW SGS 3 running 4.1.2. I followed these (youtube DOT com SLASH watch?v=K4b9hcWHrW8) instructions. As I said before, it worked fine with the first phone. Second one died on the first step.
Anyways, my friend convinced me to just send it back. I'm not worried as the ROM and everything is stock.
a.demarco said:
Did you uncheck Auto Reboot when you were supposed to?
Click to expand...
Click to collapse
I didn't get to the point, it was hard bricked as soon as I flashed the VRALEC bootchain, which still said it needed auto-reboot checked.
khymbote said:
I have always followed the guide here. Not sure what version of the OS you have but I odin my phone back to the original factory and then run the root posted here http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
The version of the OS I had at the time was 4.1.2. Are you able to flash an earlier version of the OS through Odin?
m-cat said:
I have to ask the most obvious. Hows your battery? I thought I had hard bricked my device too one time and it was just a dead battery.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Sounds like the other guy here had the same problem. My battery was full at the time of flashing. And QHUSB_DLOAD is pretty much a sure sign of a hard brick and not a battery issue as far as I can tell.
Delete thanks
The version of the OS I had at the time was 4.1.2. Are you able to flash an earlier version of the OS through Odin?
Yes I have the OS from the initial release of the phone back in July of last year. I keep it just in case I need to factory restore my phone.
I have tried rooting my HTC One X and I installed the wrong rom onto it after rooting it. I wasn't able to boot, but I could get to the fastboot screen by holding down the down button and the power button. I ran out of time to work on it, so I unplugged it before I had figured it out. Now I cannot get it to that screen, or even to show the charging indicator. Any ideas of how I can get it booted up again? Is there any other info you need to help me figure this out? I searched for a solution but I haven't been able to find one yet. Thanks in advance.
Firstly, do you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)?
Which ROM did you flash?
Do you know what your bootloader details were?
Sent from my One X using XDA Premium 4 mobile app
timmaaa said:
Firstly, do you have the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)?
Which ROM did you flash?
Do you know what your bootloader details were?
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have the AT&T One X Evita. I tried putting on CM Recovery. Also I did get it rooted and unlocked. I was installing the ROM and I flashed one that kept the OS from starting. It showed the loading screen but stuck on that. I could always get back to the HBOOT though. Now it isn't possible to get there. It may be from the battery dying but the battery isn't charging according to the light. There is no light at all when I plug it in.
Ok, you answered the first question but what about the other two? If you want help you need to answer the questions that are asked, with as much specific detail as possible. Answering that you "flashed a ROM that kept the OS from starting" doesn't answer the question. I can't help properly unless you give me the information I need.
In terms of the LED not showing that it's charging, it does happen sometimes. Plug the phone into a wall outlet and leave it connected for eight hours, then try to boot into the bootloader using the power + volume down button combination. Don't do anything else yet though until you've answered the questions and we've ascertained exactly what's going on with your phone.
Sent from my One X using XDA Premium 4 mobile app
timmaaa said:
Ok, you answered the first question but what about the other two? If you want help you need to answer the questions that are asked, with as much specific detail as possible. Answering that you "flashed a ROM that kept the OS from starting" doesn't answer the question. I can't help properly unless you give me the information I need.
In terms of the LED not showing that it's charging, it does happen sometimes. Plug the phone into a wall outlet and leave it connected for eight hours, then try to boot into the bootloader using the power + volume down button combination. Don't do anything else yet though until you've answered the questions and we've ascertained exactly what's going on with your phone.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I told you what details I knew. I started this a month or two ago, and since then I have misplace where I put the ROM images. So I honestly don't remember. I am trying to get the phone fixed up now, cause now I have time to fix it. From what I remember, I tried flashing an image using either adb or fastboot onto the recovery. From there I haven't been able to get it into recovery or to boot normally. I could only get to the HBOOT screen. I really can't remember which one I tried to flash on there. And I can't get many more details on the hboot screen.
It's very difficult to help in that case. Try charging for an extended period of time like I suggested before and see if it'll power on.
Sent from my One X using XDA Premium 4 mobile app
timmaaa said:
It's very difficult to help in that case. Try charging for an extended period of time like I suggested before and see if it'll power on.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'll do that. I will also search through backups of my computer and see if I can find those files. I will post with any updates.
SRSroot
SerenadeX said:
I have tried rooting my HTC One X and I installed the wrong rom onto it after rooting it. I wasn't able to boot, but I could get to the fastboot screen by holding down the down button and the power button. I ran out of time to work on it, so I unplugged it before I had figured it out. Now I cannot get it to that screen, or even to show the charging indicator. Any ideas of how I can get it booted up again? Is there any other info you need to help me figure this out? I searched for a solution but I haven't been able to find one yet. Thanks in advance.
Click to expand...
Click to collapse
if you want to root your devices, i recommend you to use SRSroot, This app to make your devices rooted. you just click and tarrraaaaaa... your device is rooted... :laugh:
NB: you must have internet access to use this app
search "SRSroot" in google, click official web for SRSroot and download....
SRSroot only has a 50% success rate across all devices. Plus using that will only (maybe) allow root access on a stock ROM. It doesn't allow bootloader unlocking, or installing custom recovery, or installing custom ROMs. It's pretty much useless for this device because the whole unlocking process for the Evita is quite different. Maybe don't just post this in forums where you know absolutely nothing about the device.
Sent from my Evita
fresti said:
if you want to root your devices, i recommend you to use SRSroot, This app to make your devices rooted. you just click and tarrraaaaaa... your device is rooted... :laugh:
NB: you must have internet access to use this app
search "SRSroot" in google, click official web for SRSroot and download....
Click to expand...
Click to collapse
Not relevant to this thread, as its not lack of root method that is the OPs problem. Also, if you don't have this device and don't know if the root method you suggest will work on it, you shouldn't be suggesting it.
---------- Post added at 01:22 PM ---------- Previous post was at 01:15 PM ----------
SerenadeX said:
I'll do that.
Click to expand...
Click to collapse
If you weren't actively trying to do anything (flash any kind of file, etc.) when you unplugged the phone, I would have to think its just a matter of getting the phone charged again.
On the other hand, if it doesn't come back after charging overnight (use the wall charger, not charging via computer USB), and/or you get a message QHSUSB_DLOAD when connected to your computer, the phone is pretty much done and its either time to JTAG or a new phone.