Develop Bugs

[Q] Hard Bricked OneX (international version with Tegra 3)

Hi,
I have a OneX and yesterday totally bricked.
Maximus 4.1.1 JB, Unlocked Bootloader via htc developers and the phone is can't power on.
Befor this problem, i have other problems with charging and wifi.
Yesterday, the wifi is not turning on. Ok, restart. F*ck this s**it Bootloop. OK, stay calm, try to wipe data. Ok, the phone is booting after wipe data. "Change your language", ok, it set and click next. Here is the problem. Ok i lock the screen and lock off. I can't lock off the srceen. Ok, reboot with long pressed power button. The phone thence not booting and not chargeing,
Anyone knows what's the problem?
I can solve this problem or go to gsm service?

solution
I suggest you to pick you're self up,calm down,and slowly update you're HOX onto the lattest and grattes maximus v 6.o.
Before that,make sure that you're phone is fully charged,back up you're old/current rom and continue.
Don't panic,don't *itch and *oon,it's just a ****ing phone

demirisdemir said:
I suggest you to pick you're self up,calm down,and slowly update you're HOX onto the lattest and grattes maximus v 6.o.
Before that,make sure that you're phone is fully charged,back up you're old/current rom and continue.
Don't panic,don't *itch and *oon,it's just a ****ing phone
Click to expand...
Click to collapse
Thanks your letters, and the help, but the phone does not turn on :S

Turn it completely off and let it charge on the wall for a complete day^^ After that please STUDY THE INSTALL GUIDE OF YOUR CHOOSEN ROM PRECISELY AND READ IT AT LEAST 10 TIMES, this is very important. Now you're ready to flash a ROM. If it's still not wokring, you could've a serious problem with your One X. To have a working warranty claim you have to relock your bootloader!!

nitrous² said:
Turn it completely off and let it charge on the wall for a complete day^^ After that please STUDY THE INSTALL GUIDE OF YOUR CHOOSEN ROM PRECISELY AND READ IT AT LEAST 10 TIMES, this is very important. Now you're ready to flash a ROM. If it's still not wokring, you could've a serious problem with your One X. To have a working warranty claim you have to relock your bootloader!!
Click to expand...
Click to collapse
Hm... If i try to charge for a complete day, the phone turning on?
Read my first post... The phone is no charging. No charging from the wall and no charging from USB.
(Sooooorry my bad engilsh :S)

WinnerB0Y said:
Hm... If i try to charge for a complete day, the phone turning on?
Read my first post... The phone is no charging. No charging from the wall and no charging from USB.
(Sooooorry my bad engilsh :S)
Click to expand...
Click to collapse
I've read your first post. You won't see it if it's carging. Try the following; plug your phone to the wall charger for a couple hours and then try to turn it on. If it doesn't turn on, well, thats bad I remember there were some fixes for not charging ONE X's. I'll have a search if charging doesn't work for you.

nitrous² said:
I've read your first post. You won't see it if it's carging. Try the following; plug your phone to the wall charger for a couple hours and then try to turn it on. If it doesn't turn on, well, thats bad I remember there were some fixes for not charging ONE X's. I'll have a search if charging doesn't work for you.
Click to expand...
Click to collapse
Ok. I plugged in the charger isntant to the wall. Really, i won't see the charging led. But i stay on charger a couple of hours. If it doesn't work. It's soooo bad... Motherborad change...

allen175 said:
I had this problem the other day, the battery died before i went to bed, so i plugged it in over night and nothing happened, thought it was the charger, tried a different htc charger and nothing again. So i plugged it into my computer and a few minutes later the light started to flash. I let it flash for a few minutes and unplugged it from the computer and plugged it into a charger and turned it on and it charged up.
Long story short, plug it into your computer for a while then turn it on and charge it normally.
Click to expand...
Click to collapse
hutzdani said:
Happened to me also but when running bricked kernel.
If your not running the stock kernel you need to put the phone on the charger and just wait untill the red led starts to blink ( it can take 5mins for this to happen )
Then allow it to blink for a few mins then power on as normal and remove the charger.
It will boot and moan it has no charge so plug the charger back in once its booted fully, then leave it to charge.
once at 100% reboot and bam your back up and running as normal.
Click to expand...
Click to collapse
Here are some people facing the same problem as you do.

There is a file (script) that can override those stuff,it is meant for fastboot (usb) mode,and on adb you type the commands and the phone starts to charge (slowly) but it is getting the electricity.
Search the threads,and find it,I'm 99% possitive that you're phone is not fully bricked.
Best of luck

So lets give the guy some proper help. Tell me exactly where you are now ? Is the phone charged ? If you have enough power to boot in recovery ? It will charge within recovery so you can leave the phone on and in recovery !
Download a ics rom (like viper x) see if that works oke !
put the phone in fastboot USB mode
Bootloader unlocked - if yes continue
Flash the cwm recovery 5.8.4.0
Fastboot flash recovery recoveryname.img
Go into recovery and do a full wipe of everything. (Factory reset and wipe all caches)
Go to mounts & storage and mount as USB diskdrive
Copy the rom.zip to the phone sd card
Open the rom.zip and copy the boot.img to the fastbootfolder on pc
Put the phone back in fastboot USB mode
Fastboot flash boot boot.img
Fastboot erase cache
Boot back into recovery and flash the rom
After that reboot the phone and it should boot up !

Ahh...
Lesson, this phone IS NOT TURNING ON!
And... unfortunately despite charged few hour... The phone still bricked and i can't turn it on :S

WinnerB0Y said:
Ahh...
Lesson, this phone IS NOT TURNING ON!
And... unfortunately despite charged few hour... The phone still bricked and i can't turn it on :S
Click to expand...
Click to collapse
What you can try is to plug it into a pc .... i saw a post before that someone did that and that he could turn on the phone a few hours later. It's worth the try right !

MarcelHofs said:
What you can try is to plug it into a pc .... i saw a post before that someone did that and that he could turn on the phone a few hours later. It's worth the try right !
Click to expand...
Click to collapse
Thanks, i try it and i write later.

Not working :S
My PC is detecting only the APX hardware. And my phone keep dead.

It's rather hardware issue. Service maybe?
1x, xda premium hd

Apx hardware? I think your memory is corrupt.
Try plugging your phone into charger overnight, then into pc for charge and hold the Vol dwn + pwr for 15 seconds, if the phone doest turn on then you have dead hardware. You can go back to HTC and tell them it stopped working overnight ;D
The good thing in a bricked phone they can't find out whether your bootloader is unlocked or not.
However, some developers are interested in APX mode(because its not accessible in a working phone) and I THINK you can use nvflash (i have no idea how its used or whats its functions are)

APX Mode is when the phone detects very serious hardware damage. In short, you're ****ed.

XxVcVxX said:
APX Mode is when the phone detects very serious hardware damage. In short, you're ****ed.
Click to expand...
Click to collapse
What can I do?
Specifically, what kind of serious hadware damage?

WinnerB0Y said:
What can I do?
Specifically, what kind of serious hadware damage?
Click to expand...
Click to collapse
Go back to the store

MarcelHofs said:
Go back to the store
Click to expand...
Click to collapse
Khm.... I want to go, but, i bought the phone used...

[Q] Kindle Won't Turn On

So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?

philip1192 said:
So last night I was rooting a Kindle Fire 2. It's running 10.2.6. I was following a tutorial on this forum and I succeeded in rooting it. I flashed TWRP on it, but for some reason that didn't work. I tried booting to recovery and got a red triangle with an exclamation point inside it. It said it failed to boot. The device still worked at that point during the install. It was low on battery, though I had it plugged into my laptop. I was in fastboot and the device stopped receiving commands from it for some reason (I wasn't able to figure out why). Then the battery died. I guess a laptop usb port doesn't properly charge a tablet. But anyways, I plugged it into a wall charger for a couple hours and now it won't turn on. When I plugged it in, a charging light never came on. I used this same charger earlier in the evening and it charge the Kindle with no issues whatsoever, so I know it isn't the charger or cable failing to charge the device.
So here is where I stand:
When it died, it would still successfully boot
I was in fastboot when it died
Fastboot would not take commands from my laptop, whereas it had before I tried flashing TWRP (by that I mean when I try to send commands via the command line, it would simply say <waiting for device>)
The device is successfully rooted and bootloader unlocked
I've tried pulling the battery; I've tried holding the power button for 20 seconds, for 30 seconds and for short periods of time; I've tried any possible command from the computer. I haven't tried a factory cable because I don't have one. What do I do now?
Click to expand...
Click to collapse
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again

Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

persano said:
you dont have to do this if you dont have a factory cable man! try pressing it for 2 minutes and then release and press again
Click to expand...
Click to collapse
I'll try that and see if it'll help.
mindmajick said:
Pulled the battery!?!?
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Is that a problem?

Other than voiding the warranty since you opened the device... And removed a battery not meant to be removed? Naaaah
You should NEVER have to pull the battery on ANY android device.
Edit: couple more things
1. As long as you are USING the device it won't charge on USB to PC. Always better to charge off a wall outlet. MUCH faster charging too.
2. NEVER flash a ROM if your battery is low.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.

philip1192 said:
When the bootloader was unlocked, the warranty was voided. That's not an issue to me.
I've found that pulling a battery is a perfectly valid way to reboot a device, if nothing else will work, but I always consider it a last resort.
Ah ok. I didn't know that. I'm familiar with phones, so tablets are still new to me.
Click to expand...
Click to collapse
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1

mindmajick said:
But the bootloader wasn't technically unlocked AND you could restore back to stock or whatever for replacement if necessary.
Phones are the same way. You can always hold the power button for a hard shutdown or reboot. The only reason i don't recommend it on the kf is that its a sealed device. Sure, if the battery dies, replace it. But anyway.. Not trying to be argumentative bro lol. Sorry cant really help though.
--
Sent from my Kindle Fire 2, CM 10.1
Click to expand...
Click to collapse
How was it not actually unlocked?
Hopefully someone can...

philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163

philip1192 said:
How was it not actually unlocked?
Hopefully someone can...
Click to expand...
Click to collapse
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

soupmagnet said:
Not likely
http://forum.xda-developers.com/showthread.php?t=1887163
Click to expand...
Click to collapse
Well, they're lame. I like HTC better.
mindmajick said:
Well. I'm pretty sure the FFF boot loader is inserted AFTER the actual boot loader by using the stack exploit. If this isn't 100% correct, please correct me of I'm wrong.
I would try the factory cable though.. See if you can get one from SKORPN.
It sounds like your only option
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I guess I'll see if I can make that work. If not, I guess I have an expensive paperweight on my hands...

[Q] T-999 recently rooted, won't boot

Today I rooted my T-999, which had been running 4.3. Used saferoot to do so, then installed SuperSU, then flashed CWMR. All reported success, and there were no immediate indications of a problem.
After a couple hours, I manually commanded the phone to reboot. It shut down, but never rebooted. I let it go a few minutes, and then tried to boot it with the power button. No luck.
I've since played around with removing the battery, plugging it in without the battery, and a couple other combinations. In all cases, the phone won't boot. No light, no recovery/bootloader, nothing at all.
Any new ideas about how to restart, what order to remove the battery, plug in, etc. that might help? THANK YOU.
After some searching, I have not been able to find a situation quite like mine. I'm sure I've just missed it -- if the new post annoys you, sorry. I need help.

Can you get into Downloading mode ? Put the battery in and then hold Vol Down+Home+Power.

Perseus71 said:
Can you get into Downloading mode ? Put the battery in and then hold Vol Down+Home+Power.
Click to expand...
Click to collapse
Thanks for the reply - Haven't been able to get it to boot in DL or recovery mode unfortunately.

Does your computer recognize or say any kind of message when you plug it in? Sounds like it's hard bricked
Sent from my SGH-M919 using Tapatalk

serio22 said:
Does your computer recognize or say any kind of message when you plug it in? Sounds like it's hard bricked
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
No, nothing when I plug it in on USB. Can't get adb to recognize it either.

buzban said:
No, nothing when I plug it in on USB. Can't get adb to recognize it either.
Click to expand...
Click to collapse
Try the unbrick thread
Sent from my SGH-M919 using Tapatalk

PixelXL bricked

Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.

molletit said:
Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.
Click to expand...
Click to collapse
Try hold power and volume down for like 30 seconds ,to try to get into bootloader

cwalker0906 said:
Try hold power and volume down for like 30 seconds ,to try to get into bootloader
Click to expand...
Click to collapse
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.

molletit said:
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.
Click to expand...
Click to collapse
Try doing it while plugged into PC,if not you might have to wait for battery to die, then boot into bootloader

cwalker0906 said:
Try doing it while plugged into PC,if not you might have to wait for battery to die, then boot into bootloader
Click to expand...
Click to collapse
i tried while pluged, how else would i recognize the sounds in windows. Hmm i really dont know if the pixel is on or off, so this could take weeks... is it hard to open it and unplug battery ?

Have you tried holding the power button down for a long duration with it unplugged? It should after 30 seconds or so force the reboot
Sent from my Google Pixel XL using XDA Labs

DaveHTC200 said:
Have you tried holding the power button down for a long duration with it unplugged? It should after 30 seconds or so force the reboot
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
i just told you, ive holded it 60 seconds but the screen is black only, ive iam plugged or unplugged doesent matter at all..
it is just black, no display activity ...

molletit said:
i just told you, ive holded it 60 seconds but the screen is black only, ive iam plugged or unplugged doesent matter at all..
it is just black, no display activity ...
Click to expand...
Click to collapse
No you said you tried it plugged in, hence the sounds from the PC
Sent from my Google Pixel XL using XDA Labs

DaveHTC200 said:
No you said you tried it plugged in, hence the sounds from the PC
Sent from my Google Pixel XL using XDA Labs
Click to expand...
Click to collapse
tried it, doesent make any difference, screen is still black, no flicker, nothing.

molletit said:
tried it, doesent make any difference, screen is still black, no flicker, nothing.
Click to expand...
Click to collapse
You might have to wait until the battery runs out to see if when it's plugged in to charge to see if anything happens!
I've never had an issue with a force reboot unless it's just a screen issue, which could be addressed with Google or whom you got it from
Sent from my Google Pixel XL using XDA Labs

Try it on a different PC. Worked for me, when I bricked my Nexus 6, the same Way you did. Hope it works.

If you tried to boot slot b without first flashing a bootloader to slot b then you're screwed. That's a legit brick.

molletit said:
nope, nothing ;( even not after one minute, i can just hear connect and disconnect sound from windows, but nothing more. no screen, nothing.
Click to expand...
Click to collapse
this is called a softbrick if there is still some life with the phone...the sound u get when the computer recognizes it.

then iam screwd, normally fastboot should install it on both slots, or iam wrong ?

its a hard brick, not softbrick because i cant load bootloader

the_rooter said:
this is called a softbrick if there is still some life with the phone...the sound u get when the computer recognizes it.
Click to expand...
Click to collapse
Soft brick huh? He booted a slot with no bootloader. It's done unfortunately
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
molletit said:
then iam screwd, normally fastboot should install it on both slots, or iam wrong ?
Click to expand...
Click to collapse
you would have had to flash Imgs to your non active slot and you didn't do that correct?
molletit said:
its a hard brick, not softbrick because i cant load bootloader
Click to expand...
Click to collapse
yeah it's a hard brick I know someone personally that did the same thing you did.

Tigerstown said:
Soft brick huh? He booted a slot with no bootloader. It's done unfortunately
---------- Post added at 03:29 PM ---------- Previous post was at 03:27 PM ----------
you would have had to flash Imgs to your non active slot and you didn't do that correct?
yeah it's a hard brick I know someone personally that did the same thing you did.
Click to expand...
Click to collapse
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.

the_rooter said:
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.
Click to expand...
Click to collapse
I never heard of a soft brick being unfixable in my life period. I need to google it lol that's funny. Soft bricks are easy fixes. Why don't you fix it for him?

the_rooter said:
might have to research what the differences of brick are. If there is no sign of life...screen turning on, flickering, or sounds thats a true brick. If the phones makes a noise after plugged into computer it is not a true brick aka soft brick.
Click to expand...
Click to collapse
Maybe you should read more carefully. Hes not getting sounds from the phone itself. The computer makes a sound when he plugs it in cuz it recognizes a USB charging device. The phone can still recieve power from the computer regardless of the bootloader. However because he has no bootloader on his active slot he's toast.

molletit said:
Hi, sadly i just bricked my Pixel XL
ive installed newest system image trough fastboot, installed twrp rc1, super su, and after an reboot ive installed the ElementalX Kernel for 7.1.1., ive rebooted (all was fine).
Then ive remembered to see slot a and b in twrp restart,
ive loaded twrp, it was current Slot A, then ive hit Slot B and rebooted, since then my phone is just black, nothing on screen only sounds when on usb, like connected (dimdimdim).
tried already to hit different power + volume actions but still no luck.
Fastboot not recognizing an device, adb either.
Whats possible ?
thanks.
Click to expand...
Click to collapse
It sounds like you may be booting into a low level Qualcomm boot mode. It is possible to recover with Qualcomm tools, but you would almost certianly need Google's specially signed versions.

Twrp issue and can't even turn on phone

my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz

LumberjackZac said:
my device has been acting very funny since I finally wiped internal storage. Each time I boot into twrp it doesn't remember my preferences. acts like its the first time I've ever used it. Also, it wouldn't let me just reboot the phone. Usually had to pull the battery.
Well, now I can't get it to power on at all. tried several batteries and techniques with buttons and power cords. it's unresponsive. I cannot figure out why? my screen is blank but I hear my computer recognize the usb connection to a device. nothing shows in Odin
Was last running stockMM port from Paulpizz
Click to expand...
Click to collapse
Can you still boot into TWRP?

dhplap said:
Can you still boot into TWRP?
Click to expand...
Click to collapse
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available

LumberjackZac said:
I get nothing. No samsung screen, No twrp, No led, no charging. Nothing. Tried plugging it in and then the battery. I think the hardware is damaged where the battery connects.
When plugged into PC, I get an unrecognized device listed as QHSUSB_BULK. No driver available
Click to expand...
Click to collapse
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.

ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
That is awesome. Been looking at Note 4's on ebay because.... not looking good

ryanbg said:
I'll see if I can build you a T-FLASH image sometime today or tomorrow when I get the chance. Luckily we shouldn't have any problems fixing it.
Click to expand...
Click to collapse
Hey buddy. I've been reading that qhsusb_bulk is a hard brick, possible fried bootloader. But I guess if you can make this unbrick.img on to a sdcard it may work. I'm scratching my head on what files go into this unbrick.img and if I can make it myself. Any ideas