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
Related
Ok I got overly excited with the news of the bootloader being unlocked. So I flashed the unsecure boot loader to my phone and everything went fine. So I decided to go ahead and extract the the kernel I was using from the zip so I didn't have to use kexec anymore. Anyway I read a post incorrectly and flashed the kernel to the wrong partition on my phone and got a hard brick. I can't get into odin or clockwork recovery, only a black screen. I saw another post I accidently flashed it to dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
If I plug it into my computer I get the popup to install the QHSUSB_DLOAD. If there is anyway to recover this please let me know!
Time to get your story straight.... "I just turned it off and it won't turn back on??? Maybe my chargers broken?"
Sent from my SCH-I535 using xda app-developers app
dushotgun said:
Ok I got overly excited with the news of the bootloader being unlocked. So I flashed the unsecure boot loader to my phone and everything went fine. So I decided to go ahead and extract the the kernel I was using from the zip so I didn't have to use kexec anymore. Anyway I read a post incorrectly and flashed the kernel to the wrong partition on my phone and got a hard brick. I can't get into odin or clockwork recovery, only a black screen. I saw another post I accidently flashed it to dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
If I plug it into my computer I get the popup to install the QHSUSB_DLOAD. If there is anyway to recover this please let me know!
Click to expand...
Click to collapse
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Wait you tried to unzip the kernel in your pc? For what exactly? How did you flashed it back unzipped?
VERIZON GALAXY S 3
jgrimberg1979 said:
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Click to expand...
Click to collapse
Yeah I effed up majorly. I was on a droid x for 2 years before so I'm new with kernel flashing. So jtag is the only option?
dushotgun said:
Yeah I effed up majorly. I was on a droid x for 2 years before so I'm new with kernel flashing. So jtag is the only option?
Click to expand...
Click to collapse
You can try a USB Jig to force your phone into Download mode, but if it's truly hardbricked then JTAG or getting a replacement are your only options.
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
we're only human if i had this phone and saw this unlocked bootloader i would get excited about it as well lol i feel for the man/woman
Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
Yeah thanks I realize I screwed up. I guess I was overconfident after two years of flashing stuff. I just need to know if there are any tools to reflash the aboot I effed up.
dushotgun said:
Yeah thanks I realize I screwed up. I guess I was overconfident after two years of flashing stuff. I just need to know if there are any tools to reflash the aboot I effed up.
Click to expand...
Click to collapse
Does pressing power home + vol down not do anything?
Contact Adam he might be able to help
jgrimberg1979 said:
Not to be a **** but damn dude WTF..Why would you do that. Anyways i think the only way to recovery is jtag since you are getting qhsusb_dload but i dont know. pm adam and ask him maybe he can help you out
Click to expand...
Click to collapse
Sucks, OP.
And don't even bother writing Adam. I don't know him, but I read his threads. He just had a major accomplishment (with help) and he will probably not even respond. Let him have his day/peace. He earned it. You admit that you jumped the gun.
Sent from my SCH-I535 using Tapatalk 2
Coderedpl said:
I hate to go off topic and say this but this could be one potential reason as to why the idiots at Verizon want to lock stuff.
Why not wait for things to settle down before trying it out without knowing?
Click to expand...
Click to collapse
Ohhh..c'monnnn- he/she was a Droid X user. As a fellow X2 encrypted bootloader ****ing never unlocked I was excited as **** about it being cracked too.
I'm not ****ing with my kernel or nothing.. but.. I couldn't resist. Been on lock down for 2 years- pre ordered the phone and come to find out they locked this ****er too.
Don't be so hard on the guy/gal.. :angel:
Coderedpl said:
Does pressing power home + vol down not do anything?
Contact Adam he might be able to help
Click to expand...
Click to collapse
I sent him a message but no response yet. I tried that and I still get nothing thanks though. I've read every page of the bootloader research by adam I saw this on his original post:
"op5= aboot
This block is signed by Samsung, we will not be able to modify it
This block contains HTML information. It would appear that it is possible to put the device into a mode where it will provide a webserver which displays state information.
This block appears to be a complete operating system
This block contains the Loke Daemon which communicates with Odin3."
I take this to mean there is no way for me to communicate with odin now and jig wouldn't be able to force it into odin either since I overwrote the 0p5 block. I guess thats it since I don't have a jtag set up.
Have you considered inquiring about JTAG rates from these folks?
http://www.youtube.com/watch?v=XnA8Djs55Ds&list=UUpntFTjw320ZgqHUEndzg0g&index=2&feature=plcp
- ooofest
You flashed the kernel to the aboot partition, most likely meaning no booty booty to get into a state (download mode) where you can ODIN to stock. That being said, looks like you'll be JTAGing in your near future. Curious about prices, if you do it!
ooofest said:
Have you considered inquiring about JTAG rates from these folks?
http://www.youtube.com/watch?v=XnA8Djs55Ds&list=UUpntFTjw320ZgqHUEndzg0g&index=2&feature=plcp
- ooofest
Click to expand...
Click to collapse
It's $60
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
ooofest said:
Have you considered inquiring about JTAG rates from these folks?
- ooofest
Click to expand...
Click to collapse
Thanks for the link, it looks like thats my only option for getting it fixed.
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
JBO1018 said:
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
Click to expand...
Click to collapse
It will and it will ENJOY it.
JBO1018 said:
This is why using dd to flash stuff can be dangerous. "I'm fairly certain it will flash Tetris.Apk to your bootloader partition if you tell it to" to quote one of the devs from my Thunderbolt days.
Click to expand...
Click to collapse
dd = disk destroyer :laugh:
Hey everyone,
I am looking to start an unbricking project, to help people that are bricked with QHSUSB_DLOAD message, seeing if the Sensation method will work, just with a One S HBOOT file instead of the Sensation HBOOT one.
So I'd like to ask if anyone knows where I can find the HBOOT.nb0 files starting from 1.06 to 1.13? If you have them, could you please upload any that you may have.
Thanks,
usaff22
Sent from pixels to more pixels
here are some
These are the hboots 1.06, 1.13 and 1.14, extracted them from the 1.53, 1.78 and 2.31 RUUs.
-Jobo
touch of jobo said:
These are the hboots 1.06, 1.13 and 1.14, extracted them from the 1.53, 1.78 and 2.31 RUUs.
-Jobo
Click to expand...
Click to collapse
Thanks. I'll start working on it.
Sent from pixels to more pixels
usaff22 said:
Thanks. I'll start working on it.
Sent from pixels to more pixels
Click to expand...
Click to collapse
Keep us updated
D3LTA said:
Keep us updated
Click to expand...
Click to collapse
No problem.
Sent from pixels to more pixels
Ok, I will be PM'ing people if they wish to try the method and report back to me.
I'm like HTC - I send OTA's out in batches, if something goes wrong, pull the update
Sending out a second batch of PMs
Project discontinued due to lack of interest.
Unfortunately no one replied or even sent a PM back saying they couldn't do it. If anyone wants to try it, fire me a PM and I might be able to do something.
Edit: Why the 1 star rating? This forum amazes me sometimes. I sent many PMs and no one was interested. That's not my fault.
usaff22 said:
Project discontinued due to lack of interest.
Unfortunately no one replied or even sent a PM back saying they couldn't do it. If anyone wants to try it, fire me a PM and I might be able to do something.
Edit: Why the 1 star rating? This forum amazes me sometimes. I sent many PMs and no one was interested. That's not my fault.
Click to expand...
Click to collapse
PM sent , hope this project will continue
What exactly are we testing? Ability to flash HBoot?
Ability to flash HBOOT, ability for the phone to be recognized via USB in EHostDL mode.
Sent from my locked, tampered ville
Hi,
can you please send me an update about whether you could manage to fulfill this project?
I have hard bricked my OneS's hboot image..
and stuck currently w/o getting any response from the phone, not even a charging flash
usaff22 said:
Ok, I will be PM'ing people if they wish to try the method and report back to me.
I'm like HTC - I send OTA's out in batches, if something goes wrong, pull the update
Click to expand...
Click to collapse
g.i. said:
Hi,
can you please send me an update about whether you could manage to fulfill this project?
I have hard bricked my OneS's hboot image..
and stuck currently w/o getting any response from the phone, not even a charging flash
Click to expand...
Click to collapse
http://unlimited.io/qhsusbdload.htm might help ya
thanks, but no. tried it.. its not good for my problem
who wants to help me save my brick? its along the same lines as what the op was looking at. i was in the middle of attempting to downgrade my hboot, my son whacked my laptop with a full bottle of water and caused my laptop to reboot. fortunatley, ive been able to somewhat get my one s back up and running. i need a good p4 (partition 4) from a one s to try. if i can get that, im pretty sure my phone will be back up and running, with a downgraded bootloader. if anyone could dump mmcblk0p4 for me i would be very grateful...
mikeyinid said:
who wants to help me save my brick? its along the same lines as what the op was looking at. i was in the middle of attempting to downgrade my hboot, my son whacked my laptop with a full bottle of water and caused my laptop to reboot. fortunatley, ive been able to somewhat get my one s back up and running. i need a good p4 (partition 4) from a one s to try. if i can get that, im pretty sure my phone will be back up and running, with a downgraded bootloader. if anyone could dump mmcblk0p4 for me i would be very grateful...
Click to expand...
Click to collapse
I've already tried what you're gonna try and it doesn't work. But here is my p4 anyways, I changed some digits from the IMEI so you're gonna have to edit it and put in your own.
https://dl.dropbox.com/s/ibb9cmo4y9j9x86/p4%20-%20Copy.img?dl=1
dc211 said:
I've already tried what you're gonna try and it doesn't work. But here is my p4 anyways, I changed some digits from the IMEI so you're gonna have to edit it and put in your own.
https://dl.dropbox.com/s/ibb9cmo4y9j9x86/p4%20-%20Copy.img?dl=1
Click to expand...
Click to collapse
no problem, thanks. what did you try?
mikeyinid said:
no problem, thanks. what did you try?
Click to expand...
Click to collapse
Can't quite recall off the top of my head, I do remember trying to get someone elses P4 to downgrade also. Are you gonna try to get a older RUU to work by changing the main version?
dc211 said:
Can't quite recall off the top of my head, I do remember trying to get someone elses P4 to downgrade also. Are you gonna try to get a older RUU to work by changing the main version?
Click to expand...
Click to collapse
no. im bricked right now, just trying to recover. but the one x and evo lte have a downgrade method that im almost positive will work on the one s also.
mikeyinid said:
no. im bricked right now, just trying to recover. but the one x and evo lte have a downgrade method that im almost positive will work on the one s also.
Click to expand...
Click to collapse
Good luck then. Hope it works for you.
I just obtaind root today and i flashed icecoldjelly and now my phone wont turn on. is there any way that i can fix this. i love this phone and just got it to my liking please help
We don't have an icecoldjelly ROM.
Please read before you flash.
Can you get to boot?
Sent from my One X using Tapatalk 2
superchilpil said:
We don't have an icecoldjelly ROM.
Please read before you flash.
Can you get to boot?
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
i got the rom from onex.com and they said the rom was for the one x, and no no boot
omarh3 said:
i got the rom from onex.com and they said the rom was for the one x, and no no boot
Click to expand...
Click to collapse
IceColdJelly is for the international One X, not the AT&T One XL.
Someone else managed to brick their phone doing this. Check this thread and do what I told the other guy:
http://forum.xda-developers.com/showthread.php?t=1953975
omarh3 said:
i got the rom from onex.com and they said the rom was for the one x, and no no boot
Click to expand...
Click to collapse
Goto - http://forum.xda-developers.com/showthread.php?p=33198089
User had similar issue and he solved
omarh3 said:
I just obtaind root today and i flashed icecoldjelly and now my phone wont turn on. is there any way that i can fix this. i love this phone and just got it to my liking please help
Click to expand...
Click to collapse
Do you have the 2.20 hboot? I imagine you do if you just rooted today. If that is the case you're lucky since hboot partition is read only and cannot be clobbered. Just re-flash TWRP recovery via fastboot and flash a ROM for the one XL and you should be good to go.
If you have pre-2.20 hboot you might be bricked.
denversc said:
Do you have the 2.20 hboot? I imagine you do if you just rooted today. If that is the case you're lucky since hboot partition is read only and cannot be clobbered. Just re-flash TWRP recovery via fastboot and flash a ROM for the one XL and you should be good to go.
If you have pre-2.20 hboot you might be bricked.
Click to expand...
Click to collapse
same thing happened to me and it was the same rom i think please help in any way you can
nvidia31337 said:
same thing happened to me and it was the same rom i think please help in any way you can
Click to expand...
Click to collapse
You flashed IceColdJelly? Your phone is completely dead?
iElvis said:
You flashed IceColdJelly? Your phone is completely dead?
Click to expand...
Click to collapse
yeah completely and says same message in device manager
nvidia31337 said:
yeah completely and says same message in device manager
Click to expand...
Click to collapse
You're bricked, sorry. There is a way out if you have access to a Linux computer; see that other thread.
yea same here cant even get into recovery, same error sound when connected to the pc. Dont have access to a linux computer, No effect when i try to put in recovery mode or anything. Looks like im going to have to get a new phone
Try the steps here:
http://unlimited.io/qhsusbdload.htm
Everyone has access to a linux computer, you download a live cd, burn it and then restart your computer to boot into linux
area51avenger said:
Try the steps here:
http://unlimited.io/qhsusbdload.htm
Everyone has access to a linux computer, you download a live cd, burn it and then restart your computer to boot into linux
Click to expand...
Click to collapse
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
redpoint73 said:
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
Click to expand...
Click to collapse
Cannot confirm if this can fix a corrupted hboot partition, but it's worth a shot. Haven't found any solid guides for pushing a new hboot partition to the phone while in this mode yet. Also do not want to brick my phone to test it
redpoint73 said:
Is this confirmed to work on One X's bricked from flashing international ROMs? I've seen it mentioned several times before that Qualcomm download mode can be recovered from using a Linux computer. But this is the first time I've actually seen the instructions. And it really doesn't look all that complicated.
Seems like quite a few people that have bricked (by flashing international ROMs) would benefit from this, and it deserves its own thread.
Click to expand...
Click to collapse
didn't beaups write something about this at some point, trying to find it again..
what commands do i run to un brick my phone? ive downloaded a linux based os please help. the phone is compleatley bricked but some one said i could unbrick it in this fashon
omarh3 said:
what commands do i run to un brick my phone? ive downloaded a linux based os please help. the phone is compleatley bricked but some one said i could unbrick it in this fashon
Click to expand...
Click to collapse
and ive run the commands that were in the link and it says command not found
Did you pay attention to: Type the following commands (note: linux is case sensitive)
Crappyvate said:
didn't beaups write something about this at some point, trying to find it again..
Click to expand...
Click to collapse
Totally possible. I don't recall, or haven't seen it. I've seen a few posts to the effect of "if you have Linux, it can be fixed, PM me" but that is all I've seen. Would be nice if there was a writeup we can point people to (and I can add to my index thread).
Go to Evo 4g LTE forum and go to original development. 1st page should have a thread by yarrimapirate about downgrade. He recently figured how to brick, downgrade hboot and get s-off from QHuSB. Mode. The guys is a genius. That thread may have some answers or at least some help or info for you. People in that thread are stepping over themselves trying to help people.
Good luck.
I'd post a link, but I know as soon as I step out of this thread I'll never find it again (xda app)
Edit: go here http://forum.xda-developers.com/showthread.php?t=1940512
[HBOOT][10/24/12] 1.15/1.19 downgrade tool (Linux)
hurled from my AOKP'd Evo LTE. Enjoy.
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....
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