Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Andrew10567 said:
Hey guys.....
I tried flashing IceColdJelly on my HTC One X ATT and i was rushing and i just remembered a notice before i rebooted the phone that it says there was no OS something something to this rom and i clicked OK and it attempted to reboot. Now its not turning on at all. Cannot get into download mode or ANYTHING. Don't tell me to try pressing any more buttons because i've been doing that for the past 3 hours. I know my way around phones and this is my biggest problem i've ever faced. I put in the phone to the computer and it recognizes it but has 3 beeps after basically cannot do anything to the phone. I have TWRP recovery on it btw. Basically, its a paperweight. Cannot turn on a single freaking thing. Please help. I cannot thank you guys enough if you can help in any way....
Thanks.
Click to expand...
Click to collapse
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Don't panic.right now there is no solution.There will be one soon.
GOOD LUCK
Wrong section ...... And not to be a **** the but hahaha people really need to Stop and read
Sent from my Nexus 7 using Tapatalk 2
Andrew10567 said:
Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Taking the time to research before flashing a ROM that is not even meant for your phone would have saved a lot of heartache:
http://forum.xda-developers.com/showthread.php?t=1974101
I thought the ICJ Bricking Crew was no more. I guess those clowns are trying to make a comeback.
tactical kitten said:
You can recover if you had anything less than hboot 1.14 so if you were on software 2.20 before you rooted your out of luck
Click to expand...
Click to collapse
I have downgraded using JET from 1.14 to 2.20. Process includes bricking your phone to get into special recovery mode that give RW access to hboot, but you do need TWRP at some point I think (not sure though) to get in bricked, before you start downgrade, so you might not be able to downgrade.
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
OP gives you there way to verify that device is connected and part of the steps is listing partitions. If you can get partitions listed on your PC, then I think you can just dd system image and it should come back to life... also have you tried 2.20 RUU? I had a corrupted system partition (bad sector causing reboot when I would try to access system - including booting phone or into twrp recovery). I ended up using RUU (which also failed from the same bug, but It actually reformatted my system partition giving me access to twrp and then I was able to restore).
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Andrew10567 said:
Yeah it was 2.20...... Wow. Are you serious? I wasted 270$ on the phone...... Just picked it up today too....
Click to expand...
Click to collapse
Lol. wow kid.
Sent from my HTC One XL
rpomponio said:
http://www.youtube.com/watch?v=wwleOote5M0&feature=youtube_gdata_player
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
It hurts to laugh so hard.
igagnidz said:
However, I don't think you are SOL. Look into manual steps of downgrading here: http://forum.xda-developers.com/showpost.php?p=32761598&postcount=107
Click to expand...
Click to collapse
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Sent from my One X using xda premium
Myrder said:
If there is no ROM loaded onto the phone, as in doing a full /system wipe, the asserts will not work.
The assert that's being flashed looks at the build.prop that's already loaded onto the phone.
Click to expand...
Click to collapse
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
iElvis said:
And of course, it's good practice to wipe /system when changing roms. I didn't think of that. That's obviously why people are still getting in trouble.
Click to expand...
Click to collapse
I don't ever wipe /system when flashing ROMs. It gets wiped when you flash anyway. I always wipe user data (factor reset), Dalvik and cache. But that's it.
iElvis said:
This method will not work because he's corrupted his extended partition table. All that's left is the write-protected hboot, which the processor can't find because the partition table is gone. So he can't boot into recovery.
People have been working on this issue for a long time and there is currently no solution if you're on 2.20.
To the OP, where did you get a copy of ICJ? The latest version is supposed to contain asserts to prevent flashing on this phone. You can get this repaired by HTC for $150 or something. Or, if your ethics allow it, people have played dumb and gotten warranty replacements.
Next time don't go rooting and romming the day you get your phone.
Click to expand...
Click to collapse
Yep, if you format /system, the build.prop is gone, and the assert looks to the build.prop.. why it flashes, I don't know.
The way its set up seems like it would only flash if "ro.device=endeavoru" or whatever the line is, is present. I guess there is no fail safe to stop the process if the build.prop isn't present
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They do and you're not the first to ask. I think they just swap up the motherboard.
Andrew10567 said:
Yeah, i'll skip the playing dumb idea. I prefer just going straight up to HTC about this. Would i be able to call in to HTC and ask them how much it costs? That is, if they accept these kinds of repairs.
Click to expand...
Click to collapse
They can fix any software corruption they have the tools too they know their phones front to back and can rewrite anything to them...just tell them what happened and they'll tell you the cost( maybe they'll feel bad and give a nice price) honesty can get you in good places sometimes
Thanks. Will send everyone who replied a thank button. Regardless of what type of comment...... I'll need to check the cost. Hopefully its below 100....
Related
I had a lunch TB4g and it just bricked today, I was running ShiftAOSP 1.2 (I believe unrelated) and the .802 radio (possible) but it will just go to the HTC screen and reset and keep trying to boot. I can get into HBOOT and FASTBOOT, I have tried to reflash a root friendly RUU but it didnt fix anything and still cant boot. Just giving you a heads up. I had it overclocked to 1.22, I had it in my car on the way home, sent one text, 23% battery and I plugged it into my CPU USB to charge for a little waiting for some friends to show up and that is when it went into bootloop. Heat was not an issue as I had used it minimally the whole day sending small texts. It did sustain a major G shock 2 days prior but no excessive G or roughness today. Since it can get into HBOOT it might be recoverable but thats to the devs to decide, I have the unlocked 1.04 hboot installed.
i doubt the radio caused it, but that sucks man. see if you can talk verizon into a bionic for a replacement.
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
JBO1018 said:
Does it bootloop in recovery?
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
fixxxer2008 said:
he wont be able to get to recovery, hes bricked. i had this sorta happen to me weeks ago but my phone recovered on its own. to say the least i put full insurance on it.
Click to expand...
Click to collapse
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
JBO1018 said:
He said it boots to the splash screen and he can get into hboot. So I'm confused why you would think he couldn't select recovery in hboot and see what happens. If he already flashed a full stock RUU custom recovery will be gone tho.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
it will boot to hboot and not reboot, but it will not boot to recovery
Have you tried flashing one of the recoveries that were modified to install through hboot? you can take your sd card out, and using a computer, place the PG05IMG.zip (search here @ XDA) and place it on the root of the card, flash through hboot. then using the computer again, remove the PG05IMG.zip from the sd card and go back into hboot and select recovery. i had to do this not too long ago and it worked for me, maybe it will help you.
I pulled the battery and wont plug it in all night to see if it resets some error it maybe had, my new phone is delivered tomorrow so its not a big deal.
fixxxer2008 said:
if i were him id just replace it. i just hope my tbolt lasts until the vigor ships.
Click to expand...
Click to collapse
I would agree. The whole reason I asked about recovery boot looping is because if it is thats pretty much identical symptoms everyone who had the boot loop of death "brick" thing had. If that is what the situation is I would get it s-on and get VZW to replace because I doubt he caused it.
Sent from my HTC Thunderbolt
fillyo said:
All you cheap ****ers trying to get something for free, if he bricked, his loss. Period.
Click to expand...
Click to collapse
Ditto. He probably told insurance he lost the phone and paid his $100 bucks.
People are so greedy these days. All for nothing and nothing for all.
Doesn't sound design like there was much effort to fix it either.
Questioned posted and shortly after a new one is on the the way?
Keep an extra phone around for instances like this.
Not everything is an insurance claim.
Sent from my A500 using XDA Premium App
You wonder why all the major companies are starting to hate people who root phones. Some people will flash a Rom everyday just to do it and if they miss up their phone they don't seem to care. Now do I think a thunderbolt is worth 700 bucks retail hell no it only cost about 125 to build. But people need to hit up these forums to try to fix their phones before they call Verizon. I read a few post of guys who buy bricks phone fix them and sell them so any bricked phone can be fixed as far as he said. Read up and don't be so quick to clear data as first sign of a problem. Always try what got me out of the bootloop of death.
1. Battery pull
2. Power and hold down volume button
3. Never and I mean never keep a radio stored on root of SD card after install this will cause Hboot to install radio and that is not what we want to do here.
4. Go to recovery
5. Under download folders in your SD card always keep a updated ROM of what ever ROM you are currently using or at least a stable build inside that folder if you are using AOSP keep a stable ROM that last worked for you so no data clear is needed if you are using Sense do the same.
6. I never flash a recovery at this point follow this it saved my phone. Clear cache, clear delvik, format system under mounts and storage.
7. Format is most important since it will not delete recovery if you need to try again. Go to install zip file, select zip file, and install your fresh ROM or a stable build I never have flashed a normal ROM or have I flashed back to a down graded GB ROM.
8. Reboot after ROM has flashed and your phone will boot correctly.
I hope this has helped it saved me a few times in boot loop of death. Stop clearing data you lose your recovery and stop flashing old GB ROMs thinking they will save you, it might but message me so I can say I told you so.
****NOTE also make sure you are updated to newest CWM there was a problem with bootlooping after flashing a kernel and maybe Rom. I had the problem with flashing a kernel sent me into a bootloop. Update or roll back.******
Sent from my ADR6300 using XDA App
The OP probably gets into recovery for a few seconds then bootloops randomly. If you are not bootlooping in hboot, you are not bricked. Find the stock ruu file and flash that through hboot. Although you will lose root, the phone should work again.
If it's bricked, throw it to the ground and stomp on it til it breaks and claim insurance..... That should piss some people off here
Seriously tho some guy mentioned something about a HBoot friendly RUU. You should look into it
Sent from my SICKLY INFECTED VirusBolt Synergy 3.0 using XDA Premium App
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
JBO1018 said:
As far as I have seen the random and sudden boot loop of death thing has happend to rooted and stock phones. Leading people much smarter than me to come to the conclusion it is most likely caused by some kind of hardware defect existent in a lot if not all Thunderbolts. If he bricked it trying to flash an hboot from an Incredible or a bad flash because of not taking 30 seconds to check MD5 sums then I would put the blame on him. I'm not trying to condone fraud but if the situation is what I was thinking it might be he shouldn't have to pay because HTC got cheap on some build lots or had some bad quality control. Bootlooping from a bad flash and being able to get into recovery and restore is NOT the same thing I'm talking about. In the situation I'm refering to the ROM and recovery both bootloop. You can still flash an RUU in hboot but even after that the phone still bootloops.
Sent from my HTC Thunderbolt
Click to expand...
Click to collapse
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
Sent from my ADR6400L using XDA App
Grnlantern79 said:
He could not get into recovery cause he cleared data, can't get there is there is not one. And it didn't seem to me like he tried to flashed CWM from HBoot either.
If he can't think of a way to fix it send it to me will have it running in a couple of google searches.
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Sent from my ADR6400L using XDA App
I tried to get into recovery a few times before doing anything, it would just go black and reboot to the HTC logo. As a last attempt I tried to load a rooted a ruu, it installed but didnt not boot. I have the 1.04 modded hboot so I dont think I can overwrite recovery. Either way, contrary to your beliefs I will not claim insurance on it, although this is a warranty issue, these phones are dropping left and right. I just moved to tmobile this week and my sensation 4g and G2x are supposed to be delivered today.
Thanks for your ideas but I tried to reflash recovery and it installed through hboot but it will just reset before it loads. I still have s-off and my emmc was the sem08g. I am going to plug it in and just let it boot loop all day while I am at work, maybe it will get out, maybe it wont, either way is it wont hurt anything.
I got my one x last week and rooted it a few days ago via the all in one method found here ( http://forum.xda-developers.com/showthread.php?t=1952426 ) and everything worked including superuser. After a few days of use I decided to try the icecoldjelly aokp rom found here ( http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/ ). The rom flash said successfull and so did the gaps zip. Then when I pressed reboot the phone never cam back on. I tired living it charging overnight in case it lost charge (even though it showed almost full before I flashed). I'm not sure but I think I may be out luck?
Is there anything I can try to get this thing to boot up?
Ezence01 said:
I got my one x last week and rooted it a few days ago via the all in one method found here ( http://forum.xda-developers.com/showthread.php?t=1952426 ) and everything worked including superuser. After a few days of use I decided to try the icecoldjelly aokp rom found here ( http://onexroot.com/one-x-roms/icecoldjelly-aokp-rom-for-rooted-one-x-android-4-1-2/ ). The rom flash said successfull and so did the gaps zip. Then when I pressed reboot the phone never cam back on. I tired living it charging overnight in case it lost charge (even though it showed almost full before I flashed). I'm not sure but I think I may be out luck?
Is there anything I can try to get this thing to boot up?
Click to expand...
Click to collapse
You flashed an international ROM, you now probably have an expensive paperweight. Sorry, please read the stickies next time
You may be able to dd a partition 4 to your phone if someone dumps one for you, and if you know how/someone is willing to help.
First go try this http://unlimited.io./qhsusbdload.htm
I hate seeing all these hard bricked phones I'm sorry but yeah u shoulda read:/
absolutelygrim said:
You flashed an international ROM, you now probably have an expensive paperweight. Sorry, please read the stickies next time
You may be able to dd a partition 4 to your phone if someone dumps one for you, and if you know how/someone is willing to help.
First go try this http://unlimited.io./qhsusbdload.htm
Click to expand...
Click to collapse
I figured as much. For some reason I mistook the international rom for the att one
If I tried to exchange it, would att be able to notice this?
I'll try your link first, thank you.
Ezence01 said:
I figured as much. For some reason I mistook the international rom for the att one
If I tried to exchange it, would att be able to notice this?
I'll try your link first, thank you.
Click to expand...
Click to collapse
Umm, yes they will notice it. Just don't run over it with your car and make an insurance claim :\
If you can install Ubuntu 12.04 and teamviewer i'd be willing to try and help you
absolutelygrim said:
Umm, yes they will notice it. Just don't run over it with your car and make an insurance claim :\
If you can install Ubuntu 12.04 and teamviewer i'd be willing to try and help you
Click to expand...
Click to collapse
lol, no definitely not insurance claim. I'm in the process now, I'll update with results. Thanks for the advice and help.
Ezence01 said:
lol, no definitely not insurance claim. I'm in the process now, I'll update with results. Thanks for the advice and help.
Click to expand...
Click to collapse
If it doesn't work and you still want help send me a PM
man that icecoldjelly rom is doing some damage....:crying:
Crappyvate said:
man that icecoldjelly rom is doing some damage....:crying:
Click to expand...
Click to collapse
Yea it is. But I think I have an idea that will help everyone.. Not that they will read the OP if I start a thread :beer:
absolutelygrim said:
Yea it is. But I think I have an idea that will help everyone.. Not that they will read the OP if I start a thread :beer:
Click to expand...
Click to collapse
don't tell me you want to start a tutorial on dd'ing to restore the partition that was overwritten by icecoldjelly that would be opening a big can of worms ? although maybe not since they are already bricked
Crappyvate said:
don't tell me you want to start a tutorial on dd'ing to restore the partition that was overwritten by icecoldjelly that would be opening a big can of worms ? although maybe not since they are already bricked
Click to expand...
Click to collapse
I will try that if I can't fix it.
They are already bricked so it won't hurt any more than it is right now
If I can fix this guy's phone, then i'll consider starting a tutorial.
I'm going to document everything as I do it, and make it noob proof. IF it works. BIG FAT IF
absolutelygrim said:
I will try that if I can't fix it.
They are already bricked so it won't hurt any more than it is right now
If I can fix this guy's phone, then i'll consider starting a tutorial.
I'm going to document everything as I do it, and make it noob proof. IF it works. BIG FAT IF
Click to expand...
Click to collapse
got a backup of my mmcblk0p4 if you want
Crappyvate said:
got a backup of my mmcblk0p4 if you want
Click to expand...
Click to collapse
Throw it to me
absolutelygrim said:
Throw it to me
Click to expand...
Click to collapse
just remove the .txt
Crappyvate said:
just remove the .txt
Click to expand...
Click to collapse
Right now we are trying to time it right and get his phone into emmc mode.. one that's done, I think we should have this problem fixed.
Windows recognizes it as QHSUSB_DLOAD (so its still alive), but when he holds down power, no lights flash, making this hard to time
---------- Post added 28th October 2012 at 12:22 AM ---------- Previous post was 27th October 2012 at 11:52 PM ----------
Crappyvate said:
just remove the .txt
Click to expand...
Click to collapse
Is your mmcblk0p4 from 2.20? I don't know if that would matter.
I think it's because we are using Ubuntu 12.10 and not 12.04, will report back eventually..
12.10 is not happening, if it's successful on 12.04, even just the unbrick method, I'm not concerned about the downgrade anymore, this could be good news for our little international rom lovers
Will try 12.04 sometime today
Sent from my HTC One XL using xda-developers app
absolutelygrim said:
12.10 is not happening, if it's successful on 12.04, even just the unbrick method, I'm not concerned about the downgrade anymore, this could be good news for our little international rom lovers
Will try 12.04 sometime today
Sent from my HTC One XL using xda-developers app
Click to expand...
Click to collapse
sorry i was out...no partition is from 1.85 or maybe even 1.73 don't remember,
any luck ?? have you tried to talk to beaups or 18th.abn ?
Unbricking has been a real pain in the butt using ubuntu, we found it to much easier and more successful using tinycore from a bootable USB. I don't know why, but it's been proven on several devices so try that. Also, p4 holds the device imei and cid, when it gets corrupted in may be causing the soft brick because p12 is dependent on its information since it also displays the device imei and phone info, so do p12, make sure your using a signed image and do p4, which can be any p4, the imei will just have to be repaired afterward. It will spring to life, I promise you
Sent from my HTC One XL using Tapatalk 2
Crappyvate said:
sorry i was out...no partition is from 1.85 or maybe even 1.73 don't remember,
any luck ?? have you tried to talk to beaups or 18th.abn ?
Click to expand...
Click to collapse
18th.abn said:
Unbricking has been a real pain in the butt using ubuntu, we found it to much easier and more successful using tinycore from a bootable USB. I don't know why, but it's been proven on several devices so try that. Also, p4 holds the device imei and cid, when it gets corrupted in may be causing the soft brick because p12 is dependent on its information since it also displays the device imei and phone info, so do p12, make sure your using a signed image and do p4, which can be any p4, the imei will just have to be repaired afterward. It will spring to life, I promise you
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
@crappy, nah we had to stop for the night cause I had to get up early and get senior pictures taken.
I had him install Ubuntu 12.04 rather than use a LiveCD, so we'll try it again later today.
@18th
We got to the point where it starts writing p4, but hangs and continuously sends the Reset, I posted in the thread over at the evo LTE forum asking about it, holding the power button for 30+ seconds as suggested prints an error cannot reset device
I am using mmcblk0p4 from crappy, and your hboot from dropbox.
On the hox, you only need to hold down the power button for about 10-12 seconds so 30 may be too long and sending a time out to the emmc recover tool
Sent from my HTC One XL using Tapatalk 2
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
XHaGGeNx said:
Phone was rooted using TWRP. I locked the bootloader and now I can't boot up into anything but the page with the TAMPERED RELOCKED screen, also has bootloader, reboot, reboot bootloader, power down. Am I screwed? I just wanted to revert my rooted phone back to the original OS and it's been a freaking NIGHTMARE ):
Click to expand...
Click to collapse
So you've relocked the bootloader, and then nothing else?
Run the RUU from the bootloader screen. Make sure the RUU is for YOUR phone
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
XHaGGeNx said:
That's the thing, I can't get into it! I can't get into that screen where I could access stuff to INSTALL, MOUNT, etc.. it keeps taking me to the white screen with bootloader,reboot, etc.
Click to expand...
Click to collapse
Seeing as though you have relocked the bootloader you can either a. unlock the phone again so you can install a custom rom or b. run a ruu to get it back to stock.
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
XHaGGeNx said:
Yeah because the problem is i have no OS to boot into. It just goes into recovery mode. Can you point me in the direction on how I can unlock the bootloader again?
Click to expand...
Click to collapse
No no no. You said you wanted to go back to stock correct?
Download your stock RUU, and run from that white menu that says RE-LOCKED at the top. That's your bootloader
Ok, when you mean run from that white menu that says RELOCKED, how can I run it from that menu if I cant get into anything from this menu? Do you mean just run the RUU program from my computer and have my phone connected to the PC? I used to be able to go into that TWRP screen when i was in bootloader but now I can't.
XHaGGeNx said:
Ok, that's what I am doing already. I am downloading the RUU for my phone. Hope to gawd this will save my phone. I am just worried because it's literally stuck at this bootloader menu screen. I can't do anything else.
Click to expand...
Click to collapse
Believe me, the fact your screen is on is a sign you are not bricked. Run the RUU (Make sure it's one that is easily rootable, like the 1.85 for ATT), and go through the process of bootloader and unlock and rooting. Hope this helped
I am glad to hear that. It's almost done downloading, about 4 minutes left. I really want to thank you for helping me out here. I am such a screw up with this stuff. Sigh. anyways, I'll let you know what happens here shortly. Thank you so much once again. Really..
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
It's working! It's updating and everything. Phew! No offense taken, I hear ya and agree. Just being a noob at all this can put me into a lot of trouble. I have learned a lot of stuff though lol. Anyways, thank you everyone for helping me! I should be good from here
Glad to hear its working
Cheers man, good to hear everything is fixed.
If you need anything else, contact me. There are a bunch of ways to.
As for rooting again? Just read up and you'll be set.
mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
mgutierrez87 said:
Honestly man once you get back to stock, don't worry about unlocking and rooting it. You have no business rooting your phone and flashing roms if you can accidentally delete your os, backup file, and the recovery partition. Not trying to be rude, but think about it, you could of destroyed your phone with one more bad flash
Click to expand...
Click to collapse
A simple "Be more careful next time because of ..." would have been just fine.
superchilpil said:
Hate to bump heads with ya dude but this isn't the way to be, I frown upon threads like this as well but I encourage others to root no matter who they are. Granted they do need to take the time to research what they are doing and how to get themselves out of a hole like this but someone has to help them learn
This is a community working towards a common goal, you never know maybe this dude will make his way towards development somewhere in the future. Or more likely since others helped him in his time in need he will turn around and try to do the same for someone else
Just my two cents
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
My apologies. We had been PMing for over an hour before this thread trying to get his phone back. I came off a little rude on that last post but he knows how hard I was trying to help him and that he can always come here for answers. Most forum guys would tell him to "search it"
please
how did you fix your phone i almost have same problem
He didn't delete ROM, recovery or anything. He relocked his bootloader. It just won't let you reboot unless you relock with a stock recovery flashed.
Sent from my One X using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1982968
Could u guys stop by my thread and help me out?
I kinda have the same problem, and RUU tells me phone is off, error 170.
Thanks
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
ryan9316 said:
Ladies and Gents,
I made sure I chose the correct RUU based on my CID (CWS__001)
I relocked my phone and attempted to install "RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_ 0.24p.32.09.06_10.130.32.34_release_signed.exe". After the RUU finished my phone seems to be hard bricked.
Won't Boot.
No power lights.
I knew this could happen when flashing an international version. AFTER getting owned I also found this post http://forum.xda-developers.com/showthread.php?t=2181929. Which was blatantly in the beginning of the forum. Has anyone found a fix for this issue, or is my only option JTAG repair?
Thanks,
Ryan
Click to expand...
Click to collapse
You could take your phone back and tell them it won't boot etc.
If you can't get it to boot neither can they, so no-one will know it's been unlocked/rooted.
Some people will say this is fraudulent, but hey, if you can live with yourself who cares what anyone else thinks?
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
exad said:
Pft I returned mine to Telus when the same thing happened to me. The way I see it, it was HTC's RUU that bricked my phone, not me. Like you, I did not have supercid and was S-ON.
You could try the unbrick Evita thread. If you make it past step 3 you can save your phone.
You'll need to boot to Linux.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
I saw this and will give it a try, thank you for the advice!
ryan9316 said:
I saw this and will give it a try, thank you for the advice!
Click to expand...
Click to collapse
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
mkalbarc said:
I bricked my phone trying to install elementalx and phone wouldn't boot at all and no lights. sent it in for jtag and they told me emmc controller was unresponsive and sent it back to me. looks like I may have to trash the phone... or make a few bucks on ebay.
Click to expand...
Click to collapse
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
If the emmc controller isn't responding, it's worth even less than that.
Sent from my One X using xda app-developers app
ryan9316 said:
Did they refund you? I was going to send it into mobiletechvideos for JTAG. I don't see the phones selling for more than 100$ on ebay.
Click to expand...
Click to collapse
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
mkalbarc said:
they did refund. minus the cost of shipping and something else, however. it was worth a try though... All I know though is I will never touch an elemental kernel again... not worth it that's for sure...
Click to expand...
Click to collapse
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
pside15 said:
Just curious about your situation. Did the kernel flash successfully and then just not boot? What ROM were you flashing it over? Tons of people, myself included, have flashed that kernel without issue so I'm interested in what exactly happened.
Click to expand...
Click to collapse
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. the rom that I had flashed was the latest cleanrom. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
mkalbarc said:
Sure, I too have used their kernels and have never had an issue until this time. So I started to install the kernel and it froze at I believe 60%? Then it sat... It said the flash could take awhile so to just wait so I did... For 2 hours. I knew something wasn't right because no elemental flash has taken my phone longer than a few minutes before this one so without thinking i'd hurt anything I held the buttons to hard power off the phone. After it shut off it's been completely dead since. No charge lights, no sign of any life at all other then the QHSUSB_DLOAD under device manager when plugged into my PC. super bummed but i'll get over it. the worst part about this was I had pics of my kids that I had not backed up that are now lost.
Click to expand...
Click to collapse
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
pside15 said:
That does suck about the pictures. That would upset me more than the phone as well. I went and looked at the thread after I saw your post and saw a couple of other bricks aside from yours in the last couple of hundred posts. Very unfortunate that flashing a kernel bricked it. I try to stay away from anything that uses the Aroma Installer unless there are no other options, not saying that was the problem, but I've had numerous issues with it previously. After seeing multiple bricks from a basic kernel flash I'm going to definitely be more cautious about what I flash from now on. I'd be totally screwed if I bricked this phone. Anyway, hope you end up with something better out of this, like the HTC One.
Click to expand...
Click to collapse
Funny thing about the One... I was thinking about getting it but after this issue I will never look at another phone that doesn't have a removable sd card...
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
3 words: Dropbox Camera Upload.
exad said:
I think a key thing to note here is that you are flashing software that has been altered by someone you don't know and you can never be sure that things will work out. There's huge risks associated with rooting/unlocking your phone. If there wasn't HTC would warrant your phone regardless of what you do.
If you don't have an answer to the question "What will I do when I brick my phone?" don't root. Whenever modding anything, consoles, phones, set top boxes, I always assume that I will render it unusable. If that doesn't sit well with me, I don't modify it. That should be the general rule of thumb to follow.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Very well said... I always get a little nervous when screwing with a new $500+ device.
Sent from my HTC One X using xda app-developers app
iElvis said:
3 words: Dropbox Camera Upload.
Click to expand...
Click to collapse
Thank you for the advice! I will remember that with my next phone.
I just use g+ to instantly upload my photos. Unlimited space is hard to argue with
Sent from my One X using xda app-developers app
phone not able to boot
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
anuj.sherawat said:
guys please help me out I flashed stock root JB ROM after that my device wont boot just white screen with HTC logo. The phone boots into recovery but I wiped the sd card SD card mount error is being returned.
Clockworkmod recovery v6.0.3.1 S off
Click to expand...
Click to collapse
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
31ken31 said:
Install twrp 2.3.3.1 and reformat sd card with a pc. Move Rom to sd and reflash. And also what hboot? I know you said s-off bit did you fastboot the boot.img and see is that helped?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
thanks first of all I was on CMW, formatted the drive as computer prompted, lost the data but was able to flash the ROM and fastboot the boot image to phone.
Now only one problem the phone restarts and then goes to boot loop everytime I have to fastboot the boot image file.
DO I need to change the recovery and is there any way to by pass the fastboot process? Sorry for noob question
I messed up bad. :crying: I have some idea what I'm doing but I just made a terrible mistake. I was running Viperxl with exernalx kernel and I wanted to try cyanogenmod 10.1. I had a back up of the factory version that was rooted and a back up of viperxl/externalx. I tried flashing the cyanogenmod rom and it was stuck in the loading screen. So I rebooted back into recovery then tried to flash the rooted factory backup I had. Same thing. It was stuck in the loading screen. Here's where I went wrong. I rebooted back into bootloader and tried factory reset without really knowing what it did. Now I have no back up. When I try to mount the sd card my computer says it has to format it first. And to format it, my computer has to clear it. And luckily I didn't just go for that. Any idea of what to do next? I'm stuck lol. Thanks for the help
Edit: Ok it's not really an sd card. All I can describe is it says drive G: and it has 10gb of internal storage(but it it has 16gb total it just says it will wipe about 10gb storage, can someone explain?) that I would have to all wipe out to format. I thought you would just call it an internal sd card but I don't think that's right. I just don't want to wipe anything important
Mr_Staples said:
I messed up bad. :crying: I have some idea what I'm doing but I just made a terrible mistake. I was running Viperxl with exernalx kernel and I wanted to try cyanogenmod 10.1. I had a back up of the factory version that was rooted and a back up of viperxl/externalx. I tried flashing the cyanogenmod rom and it was stuck in the loading screen. So I rebooted back into recovery then tried to flash the rooted factory backup I had. Same thing. It was stuck in the loading screen. Here's where I went wrong. I rebooted back into bootloader and tried factory reset without really knowing what it did. Now I have no back up. When I try to mount the sd card my computer says it has to format it first. And to format it, my computer has to clear it. And luckily I didn't just go for that. Any idea of what to do next? I'm stuck lol. Thanks for the help
Click to expand...
Click to collapse
You corrupted sd card doing factory reset from bootloader.. don't ever do that on this phone. After formatting on pc copy Rom to sd and flash. If your on hboot 1.14 or higher you need to flash boot.img from rom.zip you installed. Unless your s-off
Sent from my HTC One XL using xda premium
I made the same mistake a few months back. Just RUU back to stock and you're good.
31ken31 said:
You corrupted sd card doing factory reset from bootloader.. don't ever do that on this phone. After formatting on pc copy Rom to sd and flash. If your on hboot 1.14 or higher you need to flash boot.img from rom.zip you installed. Unless your s-off
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Yeah I learned that the hard way lol. I usually check before doing stuff like that but... no excuse, I just went stupid. I thought it would be bad to format the disk since it wipes everything off? Is the important software on the other drive and not the 10gb sd card? Noob question but I just want to make sure before I make this irreversible
Edit: Ok I put more thought into this and I don't think you would call it an sd card. Just internal storage. But I see you have the same phone so I hope your advice is good. I just need to be reassured before doing anything else
RollTribe said:
I made the same mistake a few months back. Just RUU back to stock and you're good.
Click to expand...
Click to collapse
I can't mount the sd card though since I factory reset it. Unless I format it on my computer and doing that will wipe everything off. And I'm not sure how that will turn out. So until then I'll keep searching around or hopefully get an answer. Person above said to format it but I'm just not sure yet and would hate to brick it. I'm kinda new to this so forgive my noobish questions on this stupid mistake
Mr_Staples said:
I can't mount the sd card though since I factory reset it. Unless I format it on my computer and doing that will wipe everything off. And I'm not sure how that will turn out. So until then I'll keep searching around or hopefully get an answer. Person above said to format it but I'm just not sure yet and would hate to brick it. I'm kinda new to this so forgive my noobish questions on this stupid mistake
Click to expand...
Click to collapse
It will only wipe the sd card photos, downloads, music s**t like that.if you want stock unrooted then ruu... If you want custom Rom follow my instructions..
Sent from my HTC One XL using xda premium
31ken31 said:
It will only wipe the sd card photos, downloads, music s**t like that.if you want stock unrooted then ruu... If you want custom Rom follow my instructions..
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
And chances are, since you've corrupted the memory, the data will be gone anyway unfortunately.
Sent from my Evita
timmaaa said:
And chances are, since you've corrupted the memory, the data will be gone anyway unfortunately.
Sent from my Evita
Click to expand...
Click to collapse
It's already gone.. I did it once, just to see what it did lost everything. And has anyone noticed the newbies posting strange answers around here lol. Guess u gotta get ur ten posts somehow
Sent from my HTC One XL using xda premium
31ken31 said:
It's already gone.. I did it once, just to see what it did lost everything. And has anyone noticed the newbies posting strange answers around here lol. Guess u gotta get ur ten posts somehow
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Oh yeah. My heart skips a beat when I see that lol.
Sent from my Evita
Just format it... If your that concerned you shouldn't be messing with the phone.. look at it this way it's corrupted and won't boot... No choice anymore..
You should read read read before doing stuff like this... It's easy to brick these phones. When I root and modify phones I'm prepared for something to screw up. But I personally spent days learning what to do before I started..
Sent from my HTC One XL using xda premium
31ken31 said:
It will only wipe the sd card photos, downloads, music s**t like that.if you want stock unrooted then ruu... If you want custom Rom follow my instructions..
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Thanks for the quick reply! That's what I thought. I just scared myself away from doing anything else. I don't always f up but when I do, I f up real bad lol. Most profound way to learn imo. And not to jack my own thread but can you run elementalx 6.7 with cyanogenmod 10.1? Can't seem to find answer and I'm not familiar enough with this stuff yet(obviously)
No you absolutely cannot use elemental kernel with aosp based ROMs. It's only for use with sense ROMs. It probably says that in the OP of the kernel thread. You really need to do some reading.
Sent from my Evita
Mr_Staples said:
Thanks for the quick reply! That's what I thought. I just scared myself away from doing anything else. I don't always f up but when I do, I f up real bad lol. Most profound way to learn imo. And not to jack my own thread but can you run elementalx 6.7 with cyanogenmod 10.1? Can't seem to find answer and I'm not familiar enough with this stuff yet(obviously)
Click to expand...
Click to collapse
Elemental x is for sense only
Sent from my HTC One XL using xda premium
Yeah, exactly like I said, it's the first line of the kernel thread.
Sent from my Evita
31ken31 said:
Just format it... If your that concerned you shouldn't be messing with the phone.. look at it this way it's corrupted and won't boot... No choice anymore..
You should read read read before doing stuff like this... It's easy to brick these phones. When I root and modify phones I'm prepared for something to screw up. But I personally spent days learning what to do before I started..
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Didn't see this till now. Is it that easy? I thought it took something more technical and risky than this. I read into this for two days straight before doing anything and everything went smooth. And I did back it up. Not sure what went wrong there when trying to flash it because it worked earlier. There's just a few things I'm not too familiar with like the factory reset. And for some reason I tried it assuming it just reset it back to how it came out of the factory. It's all a learning process
I guess you leaned the hard way huh, just remember never to factory reset in bootloader again, only in recovery. And do some more reading, your question about elemental kernel would have answered itself if you took the time to read properly.
Sent from my Evita
timmaaa said:
No you absolutely cannot use elemental kernel with aosp based ROMs. It's only for use with sense ROMs. It probably says that in the OP of the kernel thread. You really need to do some reading.
Sent from my Evita
Click to expand...
Click to collapse
31ken31 said:
Elemental x is for sense only
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Ok that makes sense. Idk why I didnt just check the kernel thread. I was just being lazy. Well.. you're definitely right. I got plenty of reading to do. I just always over analyze things and search stuff too specific which makes asking these questions on threads easier
There's nothing wrong with asking questions. But usually the same question has been asked and answered before, so be sure to search effectively first, it's part of xda rules.
Sent from my Evita
Yeah I understand that lol. I thought about that before asking. I was mostly just wondering if it was ok to wipe the memory to format it. And I explained everything just to check and make sure there was nothing else that could be done. Which I probably could've found the answers myself but it's a bit overwhelming making these mistakes without knowing what to do. Just want to cry out for help. Things always look so much easier retrospectively lol. And they usually are too
All in all I think you did the right thing, you have the right information we need to tackle the problem. You'll find xda to be a great place, it's full of like minded people that are willing to lend a hand when the **** hits the fan.
Sent from my Evita