Develop Bugs

Is there a possibility to flash a new ROM without turning the phone on...?

Hello!I just bought myself a HTC Touch and I got a problem with it.At first the device worked fine didn`t had any problems but then one day begun to turn off just sudently without doing nothing on him and then this problem is happening increasingly often (and the signal degreases)one day suddently didn`t whant to turn on anymore,doesn`t want to charge,when i connect the charger the orange led doesn`t show up.So I was thinkin to flash it with another ROM but if the device doesn`t turn on not even in bootloader I do not know if it`s possible to do this..So please help me bringing back to life my elf
PS: Sorry for my bad english..:">

Profy_X said:
So please help me bringing back to life my elf
Click to expand...
Click to collapse
You should post in the elf forum right then . I'm not familiar with the elf at all, but as long as there isn't a JTAG interface, there is nothing you can do .

And how thoes the JTAG flashing works?Can you send me a short tutorial please?is there a possibility to brik the device forever?
PS: I allready post to the elf thread
Did anyone dealed with the same problem on a HTC device?

Desire doesn't start up and doesn't charge

I'm fairly new to the forum, and i've read all the related posts about this problem, but all of them sooner or later get to the same conclusion ... warranty.
I've tried to install an RUU (the wrong one it seems) and pulled the battery too soon (i think)... and it's dead, completely dead, no orange led, no recovery, nothing.
The big problem now is i've got no warranty, and i want to resolve the problem somehow maybe one of you found a solution, that would be greatly appreciated.
Thanks in advance.

The only way you can recover your phone now is to send it to HTC to fix it, or look into getting someone with a Riff box to do it for you.

Has anyone else experienced dead one x in APX Mode

Hi all, I've began to realise that no one can help get me out of APX mode on my one x but after reading stories about the Asus Transformer battery reset and LG optimus reboot from apx I am convinced there must be a way to get the device to reboot into bootloader or perhaps flash a boot.img to reboot the phone.
I am just wondering if anyone else has experienced apx and what they did about it......?
And if anyone can explain what may have happened to cause the phone to simply go dead and stay stuck in APX mode. A bad boot.img, overheating(although it didn't seem to be hot)ect....?
If I was to have the phone repaired where would I be able to do that in the uk apart from the network and HTC?
Does anyone think that removing and replacing the battery will allow the phone to boot normally?

My phone is also in APX mode after a strange crash during flashing a ROM and a strange kernel flash...

what is apx mod?

Dam how many people are in apx does it still boot into apx if you hold the power and volume down without letting go until bootloader
Sent from my HTC One X using xda premium

joewong1991 said:
Dam how many people are in apx does it still boot into apx if you hold the power and volume down without letting go until bootloader
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Muy phone does not boot at all, when I plug into the pc it says apx in device manager, what ever I try it will not boot

a friend of mine had the same after playing for an hour or so.
The Device won't boot up at all and only showed apx in device manager.
Send it to htc or wait till there's a solution for that.

APX mode == NVFlash recovery mode. A low-level recovery mode that allows you to flash the whole device. There's no known way of getting to this mode, but several people are reporting it and suggesting a faulty device is to blame.
You can try using NVFlash utility for Tegra 3 to find out more. Fetch partition table, download partition data, flash new data etc. Search forums for more info on nvflash.
But, chances are that your phone is just busted.

HOX in APX mode
I have HOX indicating APX in device manager. Just tu add one more sad story with short description of attempts to solve it.
I have two HOX one is ok. Both handesets diassembled fixed WIFI issue changed battery from good one to bad with no results, when replaced motherboard everything works well but that is half of the phone. APX is still appearing in device manager when only motherboard connected.
Tried all other methods nvflash, drivers etc as others with no results. Hope something will leak soon.

I also bought two, one for my son. His has the same problem. It won't boot but shows in devices as apx device on the pc.
Took it to my supplier four weeks ago and after many emails they tell me it is fixed but they wont send it for another week.
It took ages to get it delivered the first time. Last time I buy gadgets online. Any other Aussies get one from Topbuy or Kogan and had trouble with warranty?

Sadly mine got stuck in apx mode and I returned it to my carrier 3UK. They said it was due to me loading illegal software on it and demanded I pay them £76 to repair it. So I want my phone back now and agreed to pay it on my next bill, I will dispute it when I get it back. Looks more and more like hardware to me.

APX Mode is supposed to allow access to an nVidia based device if it is soft-bricked, but unlike other nVidia based devices such as the ASUS Transformer TF 101/201 or LG Optimus 2X, it is impossible to revive an HTC One X that is stuck in APX Mode. No-one has a guaranteed way of getting into APX mode, let alone getting out of it. As you may or may not know, the One X is very locked down and restricted. The bootloader is locked, and it's very hard to get updated stock ROMs as RUUs. Surprisingly, it is easier to get a custom ROM working through fastboot/recovery than it is to get a stock ROM working due to all the restrictions.
In fact, the One X is so locked down that even NVFlash cannot access it in APX Mode.
For example, if you try to send any commands to a One X using NVFlash, all you'll get in return is this error due to its heavy restriction:
Code:
Command send failed (usb write failed)
I have wasted 5 hours trying to revive a One X stuck in APX Mode, only to discover that it is impossible. Even HTC themselves can't fix a One X stuck in APX Mode - that is why they accuse you of installing illegal software, but in truth they have to replace the motherboard because they locked themselves out of their own hardware. This is a result of flawed internal hardware design.
So in short, don't think just because a computer can dectect the One X means that you can still save it. There is a barrier in the device itself that is above software-level.

Ah yes, this "news" is not new ...... its a known problem for several months already.
But thank you for sharing
A search would have come up with several threads, this is one of them

i am trying to fix a one x stucked at apx mode :/...are there any news about this issue?? probably a fix?

http://forum.xda-developers.com/showthread.php?t=2326009

Stock HOX - now in APX mode - help

Hi guys,
Some time ago, my HOX (everything stock) decided to loop boot and entering by itself in the bootloader menu. I tried to fiddle around with the options but the phone kept loop booting/[email protected]/enter bootloader. I left it discharge for some time (about 2 months I think). Now it won't power on (no LED, black screen). Connected to the PC, it shows up as 'APX' in device manager.
What are the steps to getting it working again?
Thanks in advance.

varzmaster said:
Hi guys,
Some time ago, my HOX (everything stock) decided to loop boot and entering by itself in the bootloader menu. I tried to fiddle around with the options but the phone kept loop booting/[email protected]/enter bootloader. I left it discharge for some time (about 2 months I think). Now it won't power on (no LED, black screen). Connected to the PC, it shows up as 'APX' in device manager.
What are the steps to getting it working again?
Thanks in advance.
Click to expand...
Click to collapse
Take a couple of deep breaths and follow the RUU-instructions you can find in several topics here. The empty battery shouldn't be a problem. After one of my misflashes (yep, test some and screw it up sometimes ) i leave my phone bootlooping when charging. Leave it so for a night and de the battery will be charged enough to pull you trough the RUU-process.

Htc one x apx
bazs2000 said:
Take a couple of deep breaths and follow the RUU-instructions you can find in several topics here. The empty battery shouldn't be a problem. After one of my misflashes (yep, test some and screw it up sometimes ) i leave my phone bootlooping when charging. Leave it so for a night and de the battery will be charged enough to pull you trough the RUU-process.
Click to expand...
Click to collapse
Probably you will wait until somebody find or some info leak about Tegra3 NVFLASH for HTC ONE X. I have two HTC ONE X one is in APX mode
i replaced motherboard from this good one to bad and it was working, but that is expensive solution.
Up to now it is not possible to NVFLASH new bootloader (hboot) without HTC service. Hope something will apear soon.
Anyway i suspect that due to overheating there is some hardware fault, mine unit was in the car during somertime and i noticed to late
that position is not good. And as other people reported several force close, and going to boot loader itself then all stops just APX appeared
in device manager, also when you take off motherboard and connnect it to computer (only motherboard it also indicate APX after some minutes.
Until good news . bye!

varzmaster said:
Hi guys,
Some time ago, my HOX (everything stock) decided to loop boot and entering by itself in the bootloader menu. I tried to fiddle around with the options but the phone kept loop booting/[email protected]/enter bootloader. I left it discharge for some time (about 2 months I think). Now it won't power on (no LED, black screen). Connected to the PC, it shows up as 'APX' in device manager.
What are the steps to getting it working again?
Thanks in advance.
Click to expand...
Click to collapse
If you phone boots into APX mode its because of a hardware failure that causes the firm/software to crash.
Theres no way to fix it yourself without replacing hardware stuff. Your Hoxis still under full warranty, send it for repair.

maybe this one will help you .. i manage to get out in apx mode by holding volume + button then plug charger .. ) then red light comes out .. leave for a full night .. then fry to open it . it will bootloop because you are in a bootloop state then try to access fastboot .. ) hit thanks if i helped you ...
Sent from my GT-I9100 using xda premium

HOX APX
I tried vol+ and power connect as suggested but no any indication, except APX disappear and unknown device appear, then on power on APX appear again. But tks anyway .

Htc locked apx mode, hence if you can access it either your board is fully discharged(rare cases) or something is burnt and it cannot be fixed without hardware replacement.
Sent from my HTC One X

j to the 4n said:
If you phone boots into APX mode its because of a hardware failure that causes the firm/software to crash.
Theres no way to fix it yourself without replacing hardware stuff. Your Hoxis still under full warranty, send it for repair.
Click to expand...
Click to collapse
No its not.
APX mode is the first mode the device will ever see, it is the first part of its life and the APX mode is used to flash software onto it. Its like flashing the boot.img etc but at the very start of the devices life. Hense why it can be flashed without an unlocked bootloader or rooted etc.
APX mode isnt well known with the HOX however, and HTC will not help at all, as they know this is a work around from unlocking the phone to flash, which voids their warranty.
If your in APX mode, I would try and get the RUU for your device and run that.

Wilks3y said:
No its not.
APX mode is the first mode the device will ever see, it is the first part of its life and the APX mode is used to flash software onto it. Its like flashing the boot.img etc but at the very start of the devices life. Hense why it can be flashed without an unlocked bootloader or rooted etc.
APX mode isnt well known with the HOX however, and HTC will not help at all, as they know this is a work around from unlocking the phone to flash, which voids their warranty.
If your in APX mode, I would try and get the RUU for your device and run that.
Click to expand...
Click to collapse
I know that the APX Mode is the lowest software level of our devices, its more or less the BIOS of Android/Linux...
But do you know why NO one managed to boot into APX Mode on the HOX so far...WITHOUT a broken device? (-:
If you're following the Hox forums you will notice that there are sevearl threads about hox that are stucking in apx mode and once you are in apx mode their isnt a way yet to bring it back to life again. Often you will read as well, that the Hox behaved werid before, it was dropped, battery complety drained, or whatever...so i'm 99% sure that the reason that the Hox booted into APX Mode is a hardware defect/bug that leads the firmware to crash and boots the device into APX Mode.
..and no just running a RUU wont work. Also installing the correct nvflash drivers for you desktop OS wont help.
Your Desktop PC wont recognize your Device anymore...at least not in the state that is required to falsh it. It will show that your device is in APX mode..and here you are definatly not able to run a RUU.

Bump. Having the exact same problem. Any help appreciated:crying:

coolsid1234 said:
Bump. Having the exact same problem. Any help appreciated:crying:
Click to expand...
Click to collapse
Bump what, have you read the thread ?
APX = dead hox ! Get it fixed. No other real solution available.

Mr Hofs said:
Bump what, have you read the thread ?
APX = dead hox ! Get it fixed. No other real solution available.
Click to expand...
Click to collapse
anyone knows what part of the motherboard or what chipset needs to be replaced to escape the apx problem/

All the mainboard should be replaced
Sent from my HTC One X using Tapatalk 4

How can you solder new processor on motherboard without dammiging board. I saw site where they sell processors for HOX . Be carefull when buying used motherboards on ebay or elsewere, I did 2 times and both useless.
Sent from my GT-I9500 using XDA Premium 4 mobile app

Hard bricked after update via SD card

Hello,
Let me give some information on fore hand.
A few months back my phone suddenly decided that it was funny to give me an error about "Settings has stopped working". This wouldnt go away. So i just downloaded this rom: 0PKVIMG.zip.
This way i was able to revive my phone whenever it decided to show that message again. So i kept it on my external SD Card. In case it would happen again.
Today, it decided to show the encrypted screen for no reason(Phone was in my pocket.). After i entered my Decryption key (It did accept my Screen lock pin) It showed me the error that the data was corrupted.
I went into recovery(Had 80% of battery left) reflashed that rom. After it said it was finished it was stuck on the bootloader for almost 2 hours.(Sometimes it took it an hour to show the begin screen.)
So i decided to reset it with the Power and Volume up keys. My screen went black and it didn't turn on anymore. So i came home and connected my charger just in case.
Then the battery charging light indicator started to blink. Then i knew there was something wrong. So i took out my ExSDCard just incase. Connected my phone to my PC.
My PC recognized it as: RELINK HS-USB QDLOADER 9008 (COM5)
After a long time spending on google i found out that this is the "Download Mode" for the Qualcomm chipset/processor.
I downloaded QFIL with some package i found on here in an other Thread for an other Device. It was for an other phone so i thought well, it's broken anyway lets try it. Ofcourse it said SaharaFail because the files didn't match with my phone.
I tried going into fastboot mode. Won't go in there. Bootloader/Recovery won't go in there either.
I was hoping before i send it in that i could fix it myself with a bit of help from you guys.
Thanks in advance, i hope i provided enough information and i am sorry for my English.
I am from The Netherlands and my English isn't that great.
Kind Regards,
FastE

Fast-E said:
Hello,
Let me give some information on fore hand.
A few months back my phone suddenly decided that it was funny to give me an error about "Settings has stopped working". This wouldnt go away. So i just downloaded this rom: 0PKVIMG.zip.
This way i was able to revive my phone whenever it decided to show that message again. So i kept it on my external SD Card. In case it would happen again.
Today, it decided to show the encrypted screen for no reason(Phone was in my pocket.). After i entered my Decryption key (It did accept my Screen lock pin) It showed me the error that the data was corrupted.
I went into recovery(Had 80% of battery left) reflashed that rom. After it said it was finished it was stuck on the bootloader for almost 2 hours.(Sometimes it took it an hour to show the begin screen.)
So i decided to reset it with the Power and Volume up keys. My screen went black and it didn't turn on anymore. So i came home and connected my charger just in case.
Then the battery charging light indicator started to blink. Then i knew there was something wrong. So i took out my ExSDCard just incase. Connected my phone to my PC.
My PC recognized it as: RELINK HS-USB QDLOADER 9008 (COM5)
After a long time spending on google i found out that this is the "Download Mode" for the Qualcomm chipset/processor.
I downloaded QFIL with some package i found on here in an other Thread for an other Device. It was for an other phone so i thought well, it's broken anyway lets try it. Ofcourse it said SaharaFail because the files didn't match with my phone.
I tried going into fastboot mode. Won't go in there. Bootloader/Recovery won't go in there either.
I was hoping before i send it in that i could fix it myself with a bit of help from you guys.
Thanks in advance, i hope i provided enough information and i am sorry for my English.
I am from The Netherlands and my English isn't that great.
Kind Regards,
FastE
Click to expand...
Click to collapse
Well Quallcom HSUSB mode is the mode where you can send direc commands to the cpu in hex speak... i remember that from another phone... so you will only be able to revive it if you find the correct msm8939.hex that can start the download of a partition table and partitions.... i will be honest to you... this whole process is only for very high experienced onces and you will need help from other m8s owners ( you need dumps of most partitions )
so if you find that mprg8939.hex anywhere we can try to revive it.... BUT in 90% of cases your IMEI can not be restored so you cant do calls.... in 40% your emmc is so hard damaged that you cant use it....
there is a second posibility wich is not possible on every phone.... on i9300 (sgs3) you can revive such a phone by creating a microsd card with a partitiontable like the phone and all coresponding partitions so you can boot straight from sdcard... but this case is really rare

SdtBarbarossa said:
Well Quallcom HSUSB mode is the mode where you can send direc commands to the cpu in hex speak... i remember that from another phone... so you will only be able to revive it if you find the correct msm8939.hex that can start the download of a partition table and partitions.... i will be honest to you... this whole process is only for very high experienced onces and you will need help from other m8s owners ( you need dumps of most partitions )
so if you find that mprg8939.hex anywhere we can try to revive it.... BUT in 90% of cases your IMEI can not be restored so you cant do calls.... in 40% your emmc is so hard damaged that you cant use it....
there is a second posibility wich is not possible on every phone.... on i9300 (sgs3) you can revive such a phone by creating a microsd card with a partitiontable like the phone and all coresponding partitions so you can boot straight from sdcard... but this case is really rare
Click to expand...
Click to collapse
Thanks for your quickreply. I hope someone can provide me these files. The first phone i own that i didn't root or mess about with fails on me. Lucky me!
I was hoping i could find something in a RUU but my internet speed is very slow. (600kb old telephone line..) I was afraid it was pretty bad. Still can't figure out why these "problems" happend. It just suddenly appeared. And the zip on the SD card was a good solution but i think the EMMC was already corrupted when the first error occurred months back. Will this fall under warranty? The device has some scratches on the back. A few dents on the sides. But the screen did never crack luckily.
Again thank you and i hope i can get it sort off working again because my subscription will end in April next year...
With kind regards,
Erwin

Fast-E said:
Thanks for your quickreply. I hope someone can provide me these files. The first phone i own that i didn't root or mess about with fails on me. Lucky me!
I was hoping i could find something in a RUU but my internet speed is very slow. (600kb old telephone line..) I was afraid it was pretty bad. Still can't figure out why these "problems" happend. It just suddenly appeared. And the zip on the SD card was a good solution but i think the EMMC was already corrupted when the first error occurred months back. Will this fall under warranty? The device has some scratches on the back. A few dents on the sides. But the screen did never crack luckily.
Again thank you and i hope i can get it sort off working again because my subscription will end in April next year...
With kind regards,
Erwin
Click to expand...
Click to collapse
if you never unlocked your bootloader and you are still in warranty send it in... i had a "sudden dead" emmc myself 2 weeks ago (never unlocked never rooted ) and send it in aswell ... they replaced it... but if you ever unlocked the bootloader the warranty is void

SdtBarbarossa said:
if you never unlocked your bootloader and you are still in warranty send it in... i had a "sudden dead" emmc myself 2 weeks ago (never unlocked never rooted ) and send it in aswell ... they replaced it... but if you ever unlocked the bootloader the warranty is void
Click to expand...
Click to collapse
Did it take long? I didn't even try like i said this the first phone i didn't temper with. It is fully stock expect those scratches then.

Fast-E said:
Did it take long? I didn't even try like i said this the first phone i didn't temper with. It is fully stock expect those scratches then.
Click to expand...
Click to collapse
im a german...my device repair needed 10 days (with sending) first time... but atm i resend it in because the cpu is not ok ( nothing they did wrong... just a bad replace mainboard i bet... can happen rare times )