hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
salissimo said:
hey guys, i would really appreciate if someone has a minute to help me, cause i am lost in terminology and forums, and am working too much these days so cannot really read thousands of posts right now, and your experience could probably help.
so i installed rom manager , did i dont know what, went to work, my phone went battery dead, came back home, plugged it, but it wont recharge, nor go to boot loader, nor but normally, the light flashes randomly here and there when unplugging or pressing pwr button.
when connected to pc, the pc bips ta ta ta, or ti da, or ta di, but phone doesnt show anywhere, but the pc runs the device driver installation.
any clues?
it is an htc one x from rogers canada
thank you!
Click to expand...
Click to collapse
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
exad said:
Thanks for starting your own thread.
Screen stays black, power button stays black, can't get HTC screen or reovery up? If that's the case, it's bricked. You can try the Unbricking thread, you'll need a linux boot disk if you don't run linux and some time and patience. I'll brb to post helpful links.
Create bootable linux USB: http://forum.xda-developers.com/showthread.php?t=2223669&highlight=boot*+linux+usb
Unbrick thread: http://forum.xda-developers.com/showthread.php?t=1966850 If you make it past step 3 you may be able to save it. Otherwise, needs Jtag or warranty repair.
Good luck.
Click to expand...
Click to collapse
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
i guess i deserve it
thanks
iElvis said:
Did you flash anything with ROM Manager? I'm not sure it's supported for the One XL, but that could have changed. In the early days, a lot of people bricked because it was flashing things for the quad-core phone, which uses a different partition layout.
Was it functioning correctly, but then the battery went dead and it never revived? That sounds like the power management bug. Some people, unfortunately, have had their phones just die like this, like it just decides the battery is dead and won't recharge. If that's the case, you're due for a warranty replacement.
Click to expand...
Click to collapse
Charge it overnight and see if it turns on at all afterwards.
Sent from my One X using xda app-developers app
Delete.
Sent from my HTC One X using xda premium
salissimo said:
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
Click to expand...
Click to collapse
There's bit of etiquette involved. If the thread is "mature" in the sense that the OP's issue has been resolved, or multiple discussion threads have evolved, then popping in with a related question is fine. It's just not polite to pop in on the second page of someone else's query when people are still trying to help him, unless you have the identical problem.
salissimo said:
well, the problem is it dint let me to do a lot of things trhough rom manager because it wasnt the premium version but it did let me change a bootable setting and i do not remember which. the phone after that worket normally. but my stupid self forgot i have changed that in rom manager, went to work, my battery emptied during the day and the phone went off. when i plugged it when i came home it would not charge or turn on. so my guess is it is trying to boot something i set up but doesnt have enough power to finish it and cannot recharge further because it is stuck in that booting... if I understood anything about this things in these few hours i was trying to be smart and jerked off around the phone
Click to expand...
Click to collapse
It's possible, but sounds unlikely. I don't think that just changing some setting would stop it from at least powering on. ROM Manager would have had to overwrite something critical that would prevent the CPU from even finding hboot. Had you merely messed up some boot setting, you should still be able to get the boot screen, which would then start looping.
Plug your phone into your PC and see what pops up in Device Manager. I expect you'll get QHUSB_DLOAD, which means you're bricked.
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
salissimo said:
thanks.
i thought opening new threads with similar topics was considered kinda spamming, thats why i posted there. sorry.
ihave googled jtag but it is still unclear what that would be...
uhh, linux tralalaaaa a long night in front of me ha?
can you please explain in a few words?
thanks
Click to expand...
Click to collapse
salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
I've never used that unbrick tool but I'm assuming you would need to be able to get to the bootloader to get it to work. Correct me if I'm wrong.
Sent from my HTC One X using xda app-developers app
salissimo said:
guyz. what about this line?
quote
rerequisites: Ubuntu 12.04 or higher. 32/64 bit
unbrick package: http://dl.dropbox.com/u/40181085/unbrick_evita.zip
A null p4: included in the unbrick package.. you will need to hex edit your IMEI into this file. the offset is 0x21c, it's after 11111111, which is the SuperCID
end quote
what does it mean an null p4 ? is it a file? i have a file called killp4 in the unbrick evita folder i downloaded. should i type my imei into it and save it? where in the file? any specific syntax? thanks!
Click to expand...
Click to collapse
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
exad said:
bakp4 is the null p4
I think killp4 is the same but I used bakp4 when i did it.
Click to expand...
Click to collapse
salissimo said:
can you please try to answer my question? do i have to edit the file? which file? what and where to write in? can i skipo this step maybe?
thanks
Click to expand...
Click to collapse
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
exad said:
Hex edit your imei into bakp4 You cannot skip any steps. Did step 3 bring up your emmc partitions? if not you can't move any further. It's a full brick.
Click to expand...
Click to collapse
salissimo said:
thanks,
i think i got ack something like sda1 sda2 sda3 so i am still hoping.
i have just opened my phone to find out there is no imei code printed anywhere in it.
so i am digging through my **** to find that little sticker which i think no longer exists.
heh, am i lucky.
is there an imei printed somwhere within the phone to your knowledge?
thanks a lot man
Click to expand...
Click to collapse
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
If you got it from AT&T, contact them and ask for bit. Whenever they activate a phone, we store it in the system and keeps track of what phone the customer is using.
Sent from my Carbon-ize Evita using xda-developers app
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
exad said:
Needs to be the same amount of partitions as shown in the picture.. I think it's 32? if I'm not mistaken. If not, then you cannot recover.
no, it's not printed on the phone anywhere. It's in the Hboot or in the box the phone came with. that's it.
Click to expand...
Click to collapse
do you think mz phone is still under warranty considering it was tampered, and i cracked it open?
thanks!
salissimo said:
in the screenshot there are dev/sda dev/sda1 dev/sda2 dev/sda3 dev/sda5 dev/sda6
i have dev/sda dev/sda1 dev/sda2 dev/sda3 i think
but i havent done that with imei when i tried
so no chance ha?
what if i dont find the imei?
thank you!
Click to expand...
Click to collapse
I doubt AT&T can tell you unlocked it. They'll assume it's a power issue like Telus did for me. HTC may or may not warrant it. Mixed results from xda members
Sent from my One X using xda app-developers app
It should be in the EFS nv_data.bin. folder.
Sent from my HTC One X using xda premium
Related
I was one of the unlucky testers before Steve0007 closed the thread. Did anyone figure out how to save our Sensation after the bad flash? My phone does not light up or respond to any button presses but when plugged into the computer it is recognized as an "unrecognized device."
I guess this is the risk we run being early testers. Hopefully someone figures it out otherwise I've got myself very expensive paper weight.
I assume no two button rescue? And this should be in q/a or general
Can you get to the bootloader?
Sent from my Sensation using xda premium
what did he brick people's phones with what was it supposed to be?
Wrong section. And that happened to me when i got an hd2 and i bricked it. Luckily it was 2 days after i bought it so tmobile gave me another because they thought something was wrong with it. But next time please post in the right section. Thanks.
nba1341 said:
what did he brick people's phones with what was it supposed to be?
Click to expand...
Click to collapse
Its probably only a soft brick
Sent from my Sensation using xda premium
Thank god I didn't flash it, I just finished downloading it when people started reporting issues.
Anyway, I'm sure he didn't mean for it to happen. If you have a spare battery, have you tried putting that one in?
These things are usually flash at your own risk.
I would never flash a ruu, unless it's official it could cause problems.
Sent from my Sensation using Tapatalk
Also, if it doesnt work and if you have tmo. Tell them bs and they will get you one. Just some advice and please dont flame me.
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Yes as I said, this happened to me exactly when i had a tmo HD2 and flashed a european ruu and it was dead. I tried everything. You will have better luck to talk to your insurance company.
Have you got ADB installed on your pc? If not start downloading and installing it. I will find some links, in just a sec.
Edit:
New to ADB CLICK HER
More to set up path CLICK HERE
http://www.mediafire.com/?rrwi4f258lie1r7
Extract to system 32 or sysWOW64 (64bit)
Try 3 finger salute (VOL UP,VOL DOWN + POWER) with your phone plugged into pc and pc volume up see if it makes a sound like a device has connected.
Whats was this RUU anyway?
if you just need ADB you dont need all of the stuff above or to set up a path if its extracted to those folders
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
This is excatly what happened to me.Computer wont see the phone though,so no adb fix can be applied.Mnn i'm so pissed as i dont have insurance.
usually blagging HTC will do the trick for a repair,dont mention XDA, ROOT, ICS or basically anything except your phone said update was available and the battery died
Click to expand...
Click to collapse
roflcopter is 10chars
duychau said:
tried spare battery. same result. And i'm sure he didn't do it maliciously I've flashed many of his things before with no problem. Just hoping to get some help. Phone doesn't respond. Can't get to bootloader. Only sign of life is windows recognizing that i plugged something into the usb slot.
Click to expand...
Click to collapse
What does it recognize it as?
unrecognized usb device
Ok guys, it looks like the firmware that I posted to another thread from 3.06 bricked few devices. I have flashed it and it worked fine, so i tried again with the package i posted and indeed it is corrupted as it bricked also mine
My device does not respond, so I would think it is dead
I feel sorry for those who have bricked also theirs based on the package i posted.
I am closing my Rom thread and starting now my Rom developments will be for my own use. I will not publish anymore my work.
Again I feel sorry for those who have lost their devices.
Steve
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Arrrggghhhh,This could not have come at a worse time
nba1341 said:
ok so now his rom thread is closed. Why not keep it open and work together to help those with bricked devices attempt to restore them to a working state?
That way you keep your reputation rather than running away after bricking devices?
Click to expand...
Click to collapse
Because as far as I know no way to get them back
Well looks like I HARD Bricked my phone when I ran SuperOneClick v2.3.1 to Root my phone.. "its only 2 days old" the phone will not even power up now.. and when I plug it into my pc It just shows up as "qhsusb_dload" in my device manager.. rogers is going to send me a new phone overnight and I have to send back my bricked one.. do you think they will find out I was rooting the phone? they are just replace it as a power issue.
http://forum.xda-developers.com/attachment.php?attachmentid=631288&d=1308601930
See if these drivers will work for ya. If not, probably nothing you can do about it.
Sent from my SGH-I727 using Tapatalk
Yep tryed the drivers.. Odin will now see the phone but just sits a setting up connection... also the phone can been see with the battery in or out... Rogers is sending me a new one tomorrow or Monday.. .from what I seen there is no way for them to tell if I have rooted the phone or not since they will have to do a jtag flash.
They will probably just say it was a hardware failure of some sort. You should be fine.
Sent from my SGH-I727 using Tapatalk
well I got QPST to see my phone now I just need a hex file to flash to it... looks like its been wiped clean my phone... odin will not see it but qpst will.
Haven't played with qpst since I tried to "unlock" a cdma phone. What a joke that was. CDMA sucks so bad. Sorry for spamming your thread..
Sent from my SGH-I727R using XDA App
I saw your post in the dev thread that you got scolded for. Not sure if it's locked yet so I'm posting here.
I'm hard bricked as well, with a replacement on the way. I'd rather fix my phone if possible with QPST. Please report back if you're able to get that hex image or find another way to make the phone work again. (although I'd be looking for the AT&T image--not the Rogers version)
Thanks and good luck!
Yes I have been looking for both images AT&T and rogers but none to be found.. the good thing is if we hard brick our phones and it will not even power up. We can still access it with Qualcomm Product Support Tools (QPST).. Now I can't find an image but if someone would be nice enough to upload a hex image of their low level boot.. but then they have to know how to use qpst. and its not a very nice tool to use.
TriC_101 said:
Yes I have been looking for both images AT&T and rogers but none to be found.. the good thing is if we hard brick our phones and it will not even power up. We can still access it with Qualcomm Product Support Tools (QPST).. Now I can't find an image but if someone would be nice enough to upload a hex image of their low level boot.. but then they have to know how to use qpst. and its not a very nice tool to use.
Click to expand...
Click to collapse
Can you link me to QPST? I've got a similar situation to yours.
By the way,
Does your phone do anything at all to indicate it's been plugged in?
Have you tried opening ADB to see if it is recognized there?
Ya the phone will not power on at all, nothing on the screen but when I plug it into the PC it sees Qhsusb_dload. in the Device mannager and QPST will see the phone.. but its stuck in a mode waiting to download a hex or bin file from Qpst.. but the phone will not power up at all. so ADB will not work.. the phone is stuck in a very low programming level.. here is a link to the software
http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051.html
so what do we do now, my phone is bricked too :[
Does it power on?
Wow thats alot of bricks. Most ive ever seen in one forum. What did you all do. Try and flash something from a different device?
what i did was i'm trying to flash the rom from galaxy s2 tmobile with the conversion zip but it bootloop on me, so i went to odin, it gave me error failed, i make mistake at this step is that i took out the battery the download mode to goes away, which i should have press volume up or down to get out of the screen after i did some research but everything was to late, i only have the phone working for less than 24 hours
---------- Post added at 06:10 AM ---------- Previous post was at 06:09 AM ----------
JimmyStale said:
Does it power on?
Click to expand...
Click to collapse
no but i plug in my computer in does try to install the driver thou
silver03wrx said:
Wow thats alot of bricks. Most ive ever seen in one forum.
Click to expand...
Click to collapse
Perhaps we should build a house...
silver03wrx said:
. What did you all do. Try and flash something from a different device?
Click to expand...
Click to collapse
My phone got washed in the laundry and I'm trying to resurrect it.
even my skyrocket bricked any help please
silver03wrx said:
Wow thats alot of bricks. Most ive ever seen in one forum. What did you all do. Try and flash something from a different device?
Click to expand...
Click to collapse
Tried to flash a "rom" I made in dsixda's Android Kitchen http://forum.xda-developers.com/showthread.php?t=1390903
I'm pretty sure I followed the instructions completely, not sure where I went wrong. Maybe trying to flash a 2.3.5 over Alien 4 (which is 2.3.6)?
At any rate, not blaming the kitchen. I probably did something I shouldn't have.
Got a replacement yesterday, so I'm good now with a hard lesson learned. First hard brick ever!
One more....
i was chatting with whats app and then the phone reboots and black screen....
the important thing is that a friend purchased the phone in Canada and i have no invoice and also no HTC service in México...
bad way to start the year.
TriC_101 said:
well I got QPST to see my phone now I just need a hex file to flash to it... looks like its been wiped clean my phone... odin will not see it but qpst will.
Click to expand...
Click to collapse
you are right, i also can see my phone on QPST and it seems to be clean. I think we just need someone to backup their phone and boot image in hex to unbrick the phones....
Someone that want to help us to test this???
Greetings
xuvert said:
you are right, i also can see my phone on QPST and it seems to be clean. I think we just need someone to backup their phone and boot image in hex to unbrick the phones....
Someone that want to help us to test this???
Greetings
Click to expand...
Click to collapse
I wouldn't mind helping as it would possibly benefit me as well. I can't seem to get QPST to read my working 727. I can get it to recognize the device but it says "no phone".
If someone wants to point me in the right direction I'd be glad to help.
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
Hello, I just got my new GS3 yesterday. Eager to root and ROM and all the fun stuff. I rooted and unlocked, and used Odin to flash CWM Recovery. Flashed the latest version of Android Revolution HD 16. I wiped cache, dalvik, the whole 9 yards. I did not WIPE boot.img though. Flashed Android Revolution 16, it all went good. Clicked Reboot Phone in CWM Recovery and nothing. No LED light on when plugged into USB or via wall charger. No Download mode, or recovery. Nothing, like nothing at all. Anything you guys suggest?
EDIT: I am not sure if it is Hard Bricked. When I plug it into my PC, it makes a sound. Also tries to install a driver and fails every time.
EDIT2: Okay guys, my fault. Downloaded a ROM that was meant for a different model/type GS3 forum when I have a Verizon GS3 (SCH-1535). Anyone know how to fix this problem? Please disregard this incorrect forum post.
If you flashed anything related to the international S3, Google search J-tag! Or return the device and play dumb...
droidstyle said:
Google search J-tag! Or return the device and play dumb...
Click to expand...
Click to collapse
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
T Greezy said:
I am paying for full coverage every month too, and okay, couldn't I also get a Usb JIG to force download mode?
Click to expand...
Click to collapse
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
droidstyle said:
No read my edited post. You most likely hardbricked your device, meaning you no longer have download mode.
Click to expand...
Click to collapse
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
T Greezy said:
Well, I NOW have a red LED on my phone when it is plugged into the PC without battery, sd card, or sim card. Is that a good sign?
Click to expand...
Click to collapse
No that verifies what i previously posted.
droidstyle said:
No that verifies what i previously posted.
Click to expand...
Click to collapse
I have faith, thought. I can maybe push something using ADB you think?
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
josh995 said:
You need J-tag.
If there was a way to fix it yourself, nobody on here would worry about bricked phones.
Gotta be super careful and read every single word of a ROM thread and if you aren't sure if it will work for your phone or not, just ask and someone will say either yes or no
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
T Greezy said:
I guess so. I read something about plugging the phone into the pc without the battery so the red light would come on. Then, you would hold a combination of buttons, and while you're still holding them, put the battery back in while you're still holding them. I guess J-Tag is the only way? Where can I get this? Someone link me. Thanks!
Click to expand...
Click to collapse
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
No one is going to stop you. You flashed an international ROM on an s3. This is a known method of hard bricking your s3.
Sent from my SCH-I535 using xda app-developers app
T Greezy said:
Look like I'm going to drop 60 bucks for a JTAG service? Anyone please stop me if this is not the only way to fix this
email me at [email protected]!
Click to expand...
Click to collapse
That sounds about right. Luckily it's $60 and not $600 for a new phone
Sent from my SCH-I535 using xda app-developers app
Same thing happened to me. Needed a j-tag but risked calling Verizon told them my phone wouldn't come on all they asked me was if I damaged it with water or heat. (Either Verizon doesn't care or actually they just scrap the phone) I was rooted and unlocked but flashed the wrong carrier rom. Now I have a replacement phone that cost me $0.
They sent me the 16g and not the 32g by mistake I figured I've pushed my luck enough
Sent from my SCH-I535 using Tapatalk 2
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
ericerk said:
First go to Get.cm download a d2vzw rom. Put it on your sd card. Put the sd card into phone
If you have ADB on your computer do
Code:
adb reboot recovery
You should boot in Clockwork Recovery.
From there flash the D2VZW Rom, Wipe Data,
That should save you.
Click to expand...
Click to collapse
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
I do have a question for the op and the other guy who flashed an international ROM. Were did you get them and how did you find then ( like was it a site you googled?) I've noticed a lot of these lately and am wondering if it's something that can be avoided (besides the obvious read what you're flashing)
To the adb guy there us no recovery on his phone it was overwritten by part of the international ROM. he needs to JTAG his phone, don't call Verizon. You did this to your own phone, pay the 60 and learn your lesson.
Sent from my SGS3 running Eclipse 2.1
droidstyle said:
How do you figure? How can you adb recovery when the device wont turn on? The device is hardbricked plain and simple...your advice is simply false hope.
Click to expand...
Click to collapse
One day someone is going to find a way to unbrick the hard brick, lol. Eventually. Anyways, if it was "dead" then why would it show my S3 as "QHSUSB_DLOAD"? and attempts to install a driver. I'm gonna try to find the right driver to manually install, and troubleshoot from there. I mean come on guys, be optimistic. How great if this problem was RESOLVED? Also, the download mode got wiped/overwritten from a different ROM for a different model of the GS3. What about the Recovery? CWM? If I can just magically, somehow, maybe even push some type of command. Even maybe ADB? Or something in the terminal. I'm really trying to find a solution. So in the future, we will have a SOLUTION.
Anyways, I'm going to be shipping my GS3 Monday or Tuesday for Samsung to repair (If they can) or replace for no charge!
Wish me luck guys, gonna be really thinking out of the box.
Hope you can figure it out. But someone had a way to fix a hard brick.... The JTAG
Sent from my SGS3 running Eclipse 2.1
Okay guys, I've actually have gotten some good progress, I hope! I came across a thread that a guy named (therockk) he also, hard bricked his S3. Sent him a PM, and he told me he got ODIN to recognize his hard bricked S3 "WITHOUT" download mode. He said he found a driver for QHSUSB_DLOAD and manually applied the driver update. His PC, then recognized his S3 as a ID CODE: COM10 - I do not know what that means, I asked around. Some people say that it is the code for when your phone is connected in Download Mode? Nevertheless, this is good in my eyes. The phone as now, recognized as COM10 in ODIN, in its hard-bricked stage. This could be that also, maybe, the phone will be recognized in ADB/Fastboot commands. Maybe we can get something going here guys! I'm trying to look on the bright side. I'll keep you posted.
EDIT: Okay guys, was looking at some screenshots of the CODE ID's. Like I said, my buddy "therockk" said he got ODIN to recognize his phone as a COM10, while being hard-bricked. I am guessing there are different CODE ID's for each model/version of the S3. I did make an observation that he, has a different model S3 ( i747 ) and he got his to see COM10. Which means it was Added!! - My Verizon S3 (SCH-1525) should come up as COM4 when the PC recognizes it. When I do get my PC to recognize my S3, I will confirm that my SCH-1535 phone comes up as COM4, if not, I will confirm the correct CODE ID. therockk's i747 came up as a COM10, that is confirmed.
EDIT 2: Okay guys! Updated the driver successfully! QSHUSB_DLOAD is now Qualcomm HS-USB QDLoader 9008 (COM8). I feel like we're getting closer. Now to see if Odin will pick it up!
I can probably help you through this problem after work tonight if you are still having trouble. Just pm me around 10pm est
Sent from my SCH-I535 using xda app-developers app
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