Develop Bugs

Xperia S wont charge and boot.

I was listen to music until the battery drained.
When i try to charge my phone, Red Led is actually on but it cant boot.
I tried long press power+vol up button, no vibration.
I tried to charge this phone for 1 day full.
But sometimes the phone is boot automaticly. And the lets started to blink (it means no charging status) even the charger is pluged in.
and theeeeeeeen it off again.
My PC cant recognize my phone.
Im using PAC ROM.
Please help,
thanks

Odp: Xperia S wont charge and boot.
Wait while Phone turns on then try flashing stock Rom.
Sent from my Xperia S using xda app-developers app

mracer164 said:
Wait while Phone turns on then try flashing stock Rom.
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
My PC doesnt recognize my phone.
and its turns on only for 1minute.

Nova kernel?
Sent from my Android 4.2.1 Xperia S

Ben36 said:
Nova kernel?
Sent from my Android 4.2.1 Xperia S
Click to expand...
Click to collapse
yes but i already flash xtxperience and ics stock v.17
same thing happen

Same problem
Hey, i'm french and i've the same problem. Flash the FXP CM10 204 and flash Nova Kernel 1.51 after. Now, i've 0% battery and my phone won't charge. I've plug in my computer and sector but no change. I've the red led, after some minutes, led turn off and XS turn on. Boot and arrive on the PIN selector. Next, it's shutdown and the led turn on again...
Have you got an idea? I musn't use my phone and i must find a solution.
Thanks.

TesteurFull said:
Hey, i'm french and i've the same problem. Flash the FXP CM10 204 and flash Nova Kernel 1.51 after. Now, i've 0% battery and my phone won't charge. I've plug in my computer and sector but no change. I've the red led, after some minutes, led turn off and XS turn on. Boot and arrive on the PIN selector. Next, it's shutdown and the led turn on again...
Have you got an idea? I musn't use my phone and i must find a solution.
Thanks.
Click to expand...
Click to collapse
well im in progress now.
this is what i did:
waiting for jellybean boot (im using NovaKernel so i wait until ellybean boot picture show up) and enter CWM
wipe all, then i flash XTXperience 9 and stock kernel v.17
and now my phone charging but not turned on already.
so im waiting until the battery full.
hope everything fixed.
ORRRRR maybe any suggest?

Same problem. I am unhappy :crying::crying:

bradySVK said:
Same problem. I am unhappy :crying::crying:
Click to expand...
Click to collapse
its day 2 i have this problem

uDroid said:
its day 2 i have this problem
Click to expand...
Click to collapse
well u've flashed the new rom right? so is the phone working now?
i have this kinda problem awhile back. just put the charger. wait couple of minutes (for me it was about 10 minutes, there are reports that theirs need hours) then the sony's logo show's up. the i "unplugged the battery" (power+vol up till the phone's vibrating 3 times). then flash kernel via fastboot. i was using nova kernel back then.

Odp: Xperia S wont charge and boot.
Hey. I had this problem too. When phone automatically turns on, hold power plus vol up to reboot and put your phone to fastboot mode and flash advanced stock kernel 17. When you'll succeed reboot phone. (it won't boot) leave it charging for a few mins, fastboot flash your previous kernel back. Enjoy
Sent from my Xperia S using xda app-developers app

What will be the cause of this error?

skiba112 said:
Hey. I had this problem too. When phone automatically turns on, hold power plus vol up to reboot and put your phone to fastboot mode and flash advanced stock kernel 17. When you'll succeed reboot phone. (it won't boot) leave it charging for a few mins, fastboot flash your previous kernel back. Enjoy
Sent from my Xperia S using xda app-developers app
Click to expand...
Click to collapse
Yeah i already done that. THanks anyway
Just do like i did. It'll solve the problem.

Thanks a lot to all. I flash my kernel with fastboot and i have can charge it. Now, it's functionnal. Thanks a lot.
NB: ROM FXP CM10 204 + Nova Kernel 1.51 on Xperia S block charge.

It's because nova kernel doesn't heve offline charging function

Yes. I hope the dev add offline charge in it's kernel.
Sent from my Xperia S using xda premium

TesteurFull said:
Yes. I hope the dev add offline charge in it's kernel.
Sent from my Xperia S using xda premium
Click to expand...
Click to collapse
so its about offline charge kernel?
learned something to day heheeh
many thanks

Mine Too
I have an Acro S. Flashed the Nova Kernels... All of them.... my phone wouldn't charge. After reading these forums I went ahead and flashed the Xperia SS Speed V8 and V6 kernels, Advanced Stock ICS kernel for the S, I think another, in an attempt to get my battery to finally charge. It ultimately died. After dying, and letting it sit for days after quitting out of frustration, I read all these forums and tried so many things that worked for others, but not me.
Finally the 6.1.A.2.55 Stock Kernel based on Arakmar's ICS Kernel showed a sliver of hope. This is the only one that works for me, but it only charges up to about 8%, then steadily drops and dies again. I have also managed to use Flashtool to flash the original FTF (LT26w_1265-3909_6.1.A.2.55_GENERIC), returning it to nearly stock, but it still won't charge. I also managed to flash (from the sd card) CM10 and Gapps, but still no charge, even when I mix all those same kernels with it...... Any suggestions are greatly appreciated.

jnsanders said:
I have an Acro S. Flashed the Nova Kernels... All of them.... my phone wouldn't charge. After reading these forums I went ahead and flashed the Xperia SS Speed V8 and V6 kernels, Advanced Stock ICS kernel for the S, I think another, in an attempt to get my battery to finally charge. It ultimately died. After dying, and letting it sit for days after quitting out of frustration, I read all these forums and tried so many things that worked for others, but not me.
Finally the 6.1.A.2.55 Stock Kernel based on Arakmar's ICS Kernel showed a sliver of hope. This is the only one that works for me, but it only charges up to about 8%, then steadily drops and dies again. I have also managed to use Flashtool to flash the original FTF (LT26w_1265-3909_6.1.A.2.55_GENERIC), returning it to nearly stock, but it still won't charge. I also managed to flash (from the sd card) CM10 and Gapps, but still no charge, even when I mix all those same kernels with it...... Any suggestions are greatly appreciated.
Click to expand...
Click to collapse
If ur able to flash kernel like 1.32 it would definitely charge but if its not charging even then,then might be problem with usb or charger
Sent from my LT26i using xda app-developers app

It's definitely not the chargers. It does charge, but only when the phone wants to. I don't know why it worked this time, but I re-flashed the the FTF (still didn't charge), then the AcroS_Kernel_61A255 and now it magically charges!! This is probably my fourth time doing this exact same thing. It baffles me why it finally decided to start charging. These phones are so picky! But, first time charging in a couple months, I am happy right now :good:
Edit:
Stopped charging again. I put CM10 on it and it wouldn't charge again. Flashed back to the FTF and it still won't charge.. Anyone had this happen before?

an unseen before problem with HOX- phone dies when usb pulled off

Hi and firstly. thanks for your help!!
A friend gave me his hox for a repair after he tried putting in a new rom the wrong way...
so ive managed to put the rom he wanted (revolution hd 22) and the phone is now working ok...
calls, data, heavy apps... all works fine.
UNLESS- and thats the awkward part- unless you plug the usb data\charging cable out.
once the usb is out- the phone freezes for 30 seconds> reboots >than works fine for 30 seconds and than freezes whole over again
-this can happen until battery dies.
ive tried putting a new RUU
ive tried different kernels
ive tried wiping anything with fastboot or from the recovery
also tried TWRP and CWM- altough it dosnt even seems to be related
ive tried locking, unlocking, clearing fastboots cache... and NOTHING...
Now, the most weird thing, is when the phone is in recovery mode- it works on battery just fine!!
it can install my roms and kernels ok!
problem only occours when system goes up- than it will work only if its connected.
because of that- i can tell this isnt a hardware problem, and there must be a solution
does anyone has a clue with my issue please?

pazush said:
Hi and firstly. thanks for your help!!
A friend gave me his hox for a repair after he tried putting in a new rom the wrong way...
so ive managed to put the rom he wanted (revolution hd 22) and the phone is now working ok...
calls, data, heavy apps... all works fine.
UNLESS- and thats the awkward part- unless you plug the usb data\charging cable out.
once the usb is out- the phone freezes for 30 seconds> reboots >than works fine for 30 seconds and than freezes whole over again
-this can happen until battery dies.
ive tried putting a new RUU
ive tried different kernels
ive tried wiping anything with fastboot or from the recovery
also tried TWRP and CWM- altough it dosnt even seems to be related
ive tried locking, unlocking, clearing fastboots cache... and NOTHING...
Now, the most weird thing, is when the phone is in recovery mode- it works on battery just fine!!
it can install my roms and kernels ok!
problem only occours when system goes up- than it will work only if its connected.
because of that- i can tell this isnt a hardware problem, and there must be a solution
does anyone has a clue with my issue please?
Click to expand...
Click to collapse
try a custom kernel...if that doesn't wprk just go into a store or so and ask there what could the issue...if it wasn't there when he had the stock rom on it than he had a really bad flash and it is maybe rom or mainboard problem in some way

Sounds like a power issue. I think its hardware

Yep its maybe HW problem but why he can charge then in Recovery Mode
Solution:Your friend could charge in Recovery Mode and then boot up to the Rom
or you could try another ROM (your last hope ?)

Hey, thanks for helping,
There is no problem with charging it...
Problem is it cant work on battery
Only recovery works with bat power.
When using rom on bat- it freezes.
Edit: oh and one more thing, the phone is almost brand new, it has been used for only one week and worked ok. Until my friend took it to a store here for adding other lang...
Sent from my GT-I9300 using xda app-developers app

Recovery mode is taking less battery power then if you are using it with a rom booted up... Maybe the battery is now broken or the connectors are bad or so...
And what do you mean with adding other lang?
Gesendet von meinem HTC One X mit Tapatalk 2

One-X-master said:
Recovery mode is taking less battery power then if you are using it with a rom booted up... Maybe the battery is now broken or the connectors are bad or so...
And what do you mean with adding other lang?
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
i thought about it, but i think installing a new rom via recovery is taking more power
than just staring at the regular booted screen while its on idle
30 seconds of staring- freeze and than reboot...
i just cant figure how its a hardware issue, the device is almost new... how is it possible that im the first one meeting this issue?
and i ment my friend wanted to add another os language that didnt come stock (rom change)

pazush said:
i thought about it, but i think installing a new rom via recovery is taking more power
than just staring at the regular booted screen while its on idle
30 seconds of staring- freeze and than reboot...
i just cant figure how its a hardware issue, the device is almost new... how is it possible that im the first one meeting this issue?
and i ment my friend wanted to add another os language that didnt come stock (rom change)
Click to expand...
Click to collapse
try a complete full wipe ...wipe system, data, dalvik-cache and cache...and before maybe try factory reset from bootloader and be sure to save all content from sdcard to pc ...if that doesn't help try the complete full wipe ...if that doesn't help it's an hardware issue and he maybe pulled the caable wrong out or so or i really don't know...

One-X-master said:
try a complete full wipe ...wipe system, data, dalvik-cache and cache...and before maybe try factory reset from bootloader and be sure to save all content from sdcard to pc ...if that doesn't help try the complete full wipe ...if that doesn't help it's an hardware issue and he maybe pulled the caable wrong out or so or i really don't know...
Click to expand...
Click to collapse
hey, ive done that already.
whats the deepest way to rewrite the onex's software?
i tried ruu, is there anything other i dont know?

pazush said:
hey, ive done that already.
whats the deepest way to rewrite the onex's software?
i tried ruu, is there anything other i dont know?
Click to expand...
Click to collapse
Go into a store or ask and say you have this problem or your friend have to go and if he ask if you unlocked say yes but this problem was even on stock therefore you flashed a custom Rom because you thought it will fix it...
Gesendet von meinem HTC One X mit Tapatalk 2

Thank you for trying to help again,
But it isnt resonable to determine the phone mainboard is dead, all signs shows its software...
If it helps, the hox makes a long beep, or drawing stripes on the screen sometimes before it restarts, the other times it just freezes.
Sent from my GT-I9300 using xda app-developers app

pazush said:
Thank you for trying to help again,
But it isnt resonable to determine the phone mainboard is dead, all signs shows its software...
If it helps, the hox makes a long beep, or drawing stripes on the screen sometimes before it restarts, the other times it just freezes.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Flash completely another Rom...and also other kernel...some ppl had those issues too but it was problem with mainboard maybe its the mainboard problem...
Gesendet von meinem HTC One X mit Tapatalk 2

[Q] [Possible} Dead battery on New phone

So I got a new ZL from Newegg and I put CM 10.1.3 on it and it was working perfectly for 3 weeks.
Well this morning it started to act weird. Updating Apps prompt came up, random reboots. Then suddenly I wasn't able to boot into CM 10. It boots up to show the Clockworkmod android logo, but as soon as it starts to boot up CM, it shuts off.
I tried Factory Resetting it, wiping dalvik cache, wiping cache, wiping battery stats, everything. I even went back to the stock ROM, and nothing. I'm thinking it's a bad battery problem but.. I really hope that it isn't. It's a new phone.
Any help is very much appreciated!
*EDIT*
I also forgot to mention that I can power it on and it works perfectly fine only when plugged into a power source.

goldbolt said:
So I got a new ZL from Newegg and I put CM 10.1.3 on it and it was working perfectly for 3 weeks.
Well this morning it started to act weird. Updating Apps prompt came up, random reboots. Then suddenly I wasn't able to boot into CM 10. It boots up to show the Clockworkmod android logo, but as soon as it starts to boot up CM, it shuts off.
I tried Factory Resetting it, wiping dalvik cache, wiping cache, wiping battery stats, everything. I even went back to the stock ROM, and nothing. I'm thinking it's a bad battery problem but.. I really hope that it isn't. It's a new phone.
Any help is very much appreciated!
*EDIT*
I also forgot to mention that I can power it on and it works perfectly fine only when plugged into a power source.
Click to expand...
Click to collapse
Yes, it is possible and has happened to me in the same way, replace the battery and get perfect again

wanderson_tnt said:
Yes, it is possible and has happened to me in the same way, replace the battery and get perfect again
Click to expand...
Click to collapse
So even though it still works perfectly fine in Clockworkmod Recovery, it's totally the battery? If so then I dunno who to send it in to lol

goldbolt said:
So even though it still works perfectly fine in Clockworkmod Recovery, it's totally the battery? If so then I dunno who to send it in to lol
Click to expand...
Click to collapse
CWM don't use to many off battery power, that's why it didn't shut down on you...any other app or when it on, it uses battery more...so it will randomly reboot....if you don't know what to do, you can only send it to Sony servise center for repair....if you have warranty, you should relocked your bootloader and unroot your device...
Sent from my iPhone using Tapatalk Pro

Hey @goldbolt did you find out what the problem was? Because I have the exact same problem, it stays on when I'm in CWM but doesn't boot into CM but if I plug it in a power source it works fine. I'm really hoping you know what the problem is or if you found a way to solve it. Thanks in advance!

algebraik said:
Hey @goldbolt did you find out what the problem was? Because I have the exact same problem, it stays on when I'm in CWM but doesn't boot into CM but if I plug it in a power source it works fine. I'm really hoping you know what the problem is or if you found a way to solve it. Thanks in advance!
Click to expand...
Click to collapse
So I kind of did figure out the problem. I re-locked the bootloader and put the stock un-rooted ROM back on there and I called up a Sony representative (got the number from newegg reps) and we very painfully slowly walked through just trying to upgrade the system software with PC companion but alas, it was all in vain. So I was instead that I was still covered under warrenty and to just send it in and we would go from there. He also said that it's a larger than not chance that I won't have to pay anything for repairs. But basically... just send it in man. I'm very sad and bothered by this but oh well. Nothing much I can do now. I hope I helped you out.

Did you relocked it using flashtool? and where did you get the stock unrooted rom? sorry for bothering, but i really don't want to brick my useless phone lol
---------- Post added at 10:01 AM ---------- Previous post was at 09:40 AM ----------
Or a better question, how did you do it? ):

algebraik said:
Did you relocked it using flashtool? and where did you get the stock unrooted rom? sorry for bothering, but i really don't want to brick my useless phone lol
---------- Post added at 10:01 AM ---------- Previous post was at 09:40 AM ----------
Or a better question, how did you do it? ):
Click to expand...
Click to collapse
Yeah, I relocked using flashtool and I put the stock rom back on there via flashtool as well. I got the stock rom from http://www.xperiablog.net/forum/resources/categories/xperia-zl.9/ and just flashed it over when I connected it (by holding down the VOL Down button and plugging it into my computer).

goldbolt said:
Yeah, I relocked using flashtool and I put the stock rom back on there via flashtool as well. I got the stock rom from http://www.xperiablog.net/forum/resources/categories/xperia-zl.9/ and just flashed it over when I connected it (by holding down the VOL Down button and plugging it into my computer).
Click to expand...
Click to collapse
But did you change your kernel to stock in order to relock? or you just relocked and flashed the stock rom?

algebraik said:
But did you change your kernel to stock in order to relock? or you just relocked and flashed the stock rom?
Click to expand...
Click to collapse
I flashed over the stock rom and then relocked. That file and flash completely reverts to stock with the exception of bootloader lockingness

Bricked phone?

Hey Guys I really need your help.
I'm really worried as my phone just wont switch on. I was having issues with CM11, so I reverted back to ViperX 4.0.7, flashed the heartbleed patch, installed regular apps and the phone was working fine. With around 25% charge, I did a restart and the phone just won't switch ON again. Couple of times earlier when the phone wouldn't switch one I would hold the Power+Vol Down and it would start in the bootloader. But right now even that is not working. I tried keeping it under direct light and holding the buttons that too isn't working. Have charged it for nearly 18 hours now. Its out of warranty. Guys any help Whats wrong with it? How do I fix this ? Any help would be really appreciated.

xtr0ngrid said:
Hey Guys I really need your help.
I'm really worried as my phone just wont switch on. I was having issues with CM11, so I reverted back to ViperX 4.0.7, flashed the heartbleed patch, installed regular apps and the phone was working fine. With around 25% charge, I did a restart and the phone just won't switch ON again. Couple of times earlier when the phone wouldn't switch one I would hold the Power+Vol Down and it would start in the bootloader. But right now even that is not working. I tried keeping it under direct light and holding the buttons that too isn't working. Have charged it for nearly 18 hours now. Its out of warranty. Guys any help Whats wrong with it? How do I fix this ? Any help would be really appreciated.
Click to expand...
Click to collapse
Connect phone to pc and hold the power button...if you don't have luck your phone is stuck in apx mode so only HTC can fix it...if not then you may have luck and it will turn on the normally
Gesendet von meinem HTC One_M8 mit Tapatalk

One-M8-Master said:
Connect phone to pc and hold the power button...if you don't have luck your phone is stuck in apx mode so only HTC can fix it...if not then you may have luck and it will turn on the normally
Click to expand...
Click to collapse
Thanks One-m8-master. I connected the phone to the PC and in device manager under 'Other Devices' it showed up as APX. Then I tried pressing the Volume down key for 10 Seconds+ and then pressing the Power key for 10 seconds without the usb. And then after reconnecting it to the PC it displayed 'USB Device not recognized' and under 'USB controllers' shows Unknown device. Does it mean its still in APX mode?

xtr0ngrid said:
Thanks One-m8-master. I connected the phone to the PC and in device manager under 'Other Devices' it showed up as APX. Then I tried pressing the Volume down key for 10 Seconds+ and then pressing the Power key for 10 seconds without the usb. And then after reconnecting it to the PC it displayed 'USB Device not recognized' and under 'USB controllers' shows Unknown device. Does it mean its still in APX mode?
Click to expand...
Click to collapse
Yes, your phone is bricked....even if you get out of apx mode like I sometimes was able after a reboot or so you will stuck again and after a few times it will never turn on again....so send in
Gesendet von meinem HTC One_M8 mit Tapatalk

One-M8-Master said:
Yes, your phone is bricked....even if you get out of apx mode like I sometimes was able after a reboot or so you will stuck again and after a few times it will never turn on again....so send in
Click to expand...
Click to collapse
i was dreading those words
Just a recap. I was running CM11. Phone switched off at 50%. Dint Turn on for a long time. Turned it on by pressing Power+Vol Down (holding it for a while). Phone ran fine till it discharged completely and shut down. After charging it for a while, had to restart it again by Power+Vol Down. And apps started crashing. Next:
1) Booted into bootloader >fastboot USB>Flashed ViperX.4.0.7 boot img. included in full rom zip file.
2) In CWM recovery the The viper Installation failed. Back to Bootloader
3) Flashed the TWRP recovery.
4) Fastboot flash Viper boot.img again followed by fastboot erase cache.
5)Flashed the Viper Rom. Installed Apps. All went fine.
6) Did a restart it worked ok. After sometime I did a restart again and it Never came back.
Any idea what I screwed up with those steps so i dont mess it up again??

xtr0ngrid said:
i was dreading those words
Just a recap. I was running CM11. Phone switched off at 50%. Dint Turn on for a long time. Turned it on by pressing Power+Vol Down (holding it for a while). Phone ran fine till it discharged completely and shut down. After charging it for a while, had to restart it again by Power+Vol Down. And apps started crashing. Next:
1) Booted into bootloader >fastboot USB>Flashed ViperX.4.0.7 boot img. included in full rom zip file.
2) In CWM recovery the The viper Installation failed. Back to Bootloader
3) Flashed the TWRP recovery.
4) Fastboot flash Viper boot.img again followed by fastboot erase cache.
5)Flashed the Viper Rom. Installed Apps. All went fine.
6) Did a restart it worked ok. After sometime I did a restart again and it Never came back.
Any idea what I screwed up with those steps so i dont mess it up again??
Click to expand...
Click to collapse
You Should Use Phizl'recovery (5.19.5),do not Fullwipe in Aroma. I think it ll be OK.
Sent from my One X using XDA Free mobile app

Namautoenx said:
You Should Use Phizl'recovery (5.19.5),do not Fullwipe in Aroma. I think it ll be OK.
Click to expand...
Click to collapse
Thanks for the reply. But even to load Phizl'recovery, How do i get somewhere to install it without the phone turning on??

xtr0ngrid said:
Thanks for the reply. But even to load Phizl'recovery, How do i get somewhere to install it without the phone turning on??
Click to expand...
Click to collapse
Yeh, ị misunderstand your comment, I don't know your phone can not switch On.
Sent from my One X using XDA Free mobile app

Mr Hofs said:
As one M8 said, a APX is a bricked hox. No wrongs steps caused that it's just a hardware fault. Replacing the mainboard will solve it permanently.
Click to expand...
Click to collapse
Thank you Mr. Hofs. I guess Im out of luck then. I had purchased the phone from a different county and its been well more than 1.5 years. I love this phone too much

Does using aosp roms brick the device ? Or changing roms does that ?
My device is running aosp ROM and when it runs out of battery, i cant switch it on normally after putting it on charge. I have to keep pushing the power button to boot it (capacitive buttons flashes)
Is my phone also dying ?

a.broken.star said:
Does using aosp roms brick the device ? Or changing roms does that ?
My device is running aosp ROM and when it runs out of battery, i cant switch it on normally after putting it on charge. I have to keep pushing the power button to boot it (capacitive buttons flashes)
Is my phone also dying ?
Click to expand...
Click to collapse
Don't know, ask it in the Q&A section, maybe someone knows there about this issue. Or ask it in a AOSP rom thread if more people suffer from this matter. This should be the development thread for the Viper X rom

a.broken.star said:
Does using aosp roms brick the device ? Or changing roms does that ?
My device is running aosp ROM and when it runs out of battery, i cant switch it on normally after putting it on charge. I have to keep pushing the power button to boot it (capacitive buttons flashes)
Is my phone also dying ?
Click to expand...
Click to collapse
Guess that should Not be the reason. Many use AOSP Roms and even switch between sense and aosp roms often. My phone was working fine with both CM11 and Viper no problems absolutely until yesterday where apps started crashing and after a fresh install, its just not turning on.

xtr0ngrid said:
Guess that should Not be the reason. Many use AOSP Roms and even switch between sense and aosp roms often. My phone was working fine with both CM11 and Viper no problems absolutely until yesterday where apps started crashing and after a fresh install, its just not turning on.
Click to expand...
Click to collapse
I really hope somehow your phone starts ... Its sad to see someone's phone getting bricked...

a.broken.star said:
I really hope somehow your phone starts ... Its sad to see someone's phone getting bricked...
Click to expand...
Click to collapse
Thanks buddy. I took it to the HTC Centre today and they said motherboard needs to be replaced which would cost a bomb almost equal to buying a new phone. I just have one query, with the phone looking more or less hard bricked, is JTAG a good solution? Do the phones go the distance once they have been fixed via JTAG. Thanks for all the support guys.

xtr0ngrid said:
Thanks buddy. I took it to the HTC Centre today and they said motherboard needs to be replaced which would cost a bomb almost equal to buying a new phone. I just have one query, with the phone looking more or less hard bricked, is JTAG a good solution? Do the phones go the distance once they have been fixed via JTAG. Thanks for all the support guys.
Click to expand...
Click to collapse
It's a hardware issue... you didn't accidentally brick the device so it should not help.

xtr0ngrid said:
Thanks buddy. I took it to the HTC Centre today and they said motherboard needs to be replaced which would cost a bomb almost equal to buying a new phone. I just have one query, with the phone looking more or less hard bricked, is JTAG a good solution? Do the phones go the distance once they have been fixed via JTAG. Thanks for all the support guys.
Click to expand...
Click to collapse
Jtag could help but it's really hard or even impossible to do it with this phone...also the apx mode/bricked phone is due to some problems in system partitions which can't be modified by flashing roms or kernels without s-off...it's just a fault which earlier devices of one x are having...it can also happen if you flash too Many times different roms without wiping system or even wiping system too many times...but for now you can ether get a new device because buying new mainboard is stupid if it costs like a new device xD
Gesendet von meinem HTC One_M8 mit Tapatalk

One-M8-Master said:
Jtag could help but it's really hard or even impossible to do it with this phone...also the apx mode/bricked phone is due to some problems in system partitions which can't be modified by flashing roms or kernels without s-off...it's just a fault which earlier devices of one x are having...it can also happen if you flash too Many times different roms without wiping system or even wiping system too many times...but for now you can ether get a new device because buying new mainboard is stupid if it costs like a new device xD
Gesendet von meinem HTC One_M8 mit Tapatalk
Click to expand...
Click to collapse
a RUU won't help ? just a suggestion !

xeloni said:
a RUU won't help ? just a suggestion !
Click to expand...
Click to collapse
Ruu wud be helpful if the phone atleast booted to bootloader
So he can't do that
Sent from my HTC One X using Tapatalk

kantry123 said:
Ruu wud be helpful if the phone atleast booted to bootloader
So he can't do that
Sent from my HTC One X using Tapatalk
Click to expand...
Click to collapse
xeloni said:
a RUU won't help ? just a suggestion !
Click to expand...
Click to collapse
Nope even if the phone could boot by luck it won't help...there are damaged partitions which only can be fixed by replacing mainboard or use different hardware to repair them...a ruu just format and wipes them...if we had s-off we maybe could repartition whole phone...so only help is replacing majnboard or buying new phone
Gesendet von meinem HTC One_M8 mit Tapatalk

One-M8-Master said:
Nope even if the phone could boot by luck it won't help...there are damaged partitions which only can be fixed by replacing mainboard or use different hardware to repair them...a ruu just format and wipes them...if we had s-off we maybe could repartition whole phone...so only help is replacing majnboard or buying new phone
Gesendet von meinem HTC One_M8 mit Tapatalk
Click to expand...
Click to collapse
I will never buy a nvidia phone !!
Only Qualcomm !!

Problem with charging !!

Can someone please help.
I flush new rom everything working fine but it's one problem.
When I turn on my tablet on the screen is little line flicker .
Second problem is when I try charging battery and my tablet it's switch off and I plug the cable tablet switch on why ? Please some advice

Hi, screen goes allways on, if you plug a charging cable in, that`s normaly, and part of Android, you can`t trigger this off.....sorry, .....If yout urn on the tablet, there is a little flicker you say ? Just a short one, and then it`s ok? Maybe it can be part of a compatibility Problem with the wall paper, you have there and the screen orientation,, or other reasons.....if there are not more flickers, this should be not really a problem.....Maybe, you can try another Wallpaper.....
Gesendet von meinem SM-P600 mit Tapatalk

it happens to mine also, because of flashing the roms and what not. its at the boot up samsung screen right?

Hi how I can trigger this off ? Can you tell me please thanks anyway

atonal said:
Hi, screen goes allways on, if you plug a charging cable in, that`s normaly, and part of Android, you can`t trigger this off.....sorry, .....If yout urn on the tablet, there is a little flicker you say ? Just a short one, and then it`s ok? Maybe it can be part of a compatibility Problem with the wall paper, you have there and the screen orientation,, or other reasons.....if there are not more flickers, this should be not really a problem.....Maybe, you can try another Wallpaper.....
Gesendet von meinem SM-P600 mit Tapatalk
Click to expand...
Click to collapse
What he meant was that the tablet turns on when he plugs in a charger when the tablet is OFF... Not on with the screen off , but completely off. Mine does this too and it's really annoying cause it causes it to take longer to charge... This is NOT normal android behavior.

Known problem: You was on the android 4.3 rom and flashed a kikkat based rom. You should have flashed a kitkat based stock rom first and then reinstall twrp and then install your custom rom of choise.
So to fix your problem: download a stock kitkat rom from sammobile.com and flash it with odin. Flash TWRP and your custom rom after that. Problem fixed

That will solve the turning on when plugged in issue? Will the fix still work if we Odin a stock rom and reinstall twrp then restore a trwp backup of our current rom?
Update: Does it matter which stock rom? I didn't see any listed that said it was from the US for the SM-P600.
Sent from my SM-N900A using Tapatalk

ElAguila said:
That will solve the turning on when plugged in issue? Will the fix still work if we Odin a stock rom and reinstall twrp then restore a trwp backup of our current rom?
Update: Does it matter which stock rom? I didn't see any listed that said it was from the US for the SM-P600.
Sent from my SM-N900A using Tapatalk
Click to expand...
Click to collapse
Yes that will fix it. It does not matter if you are installing twrp after that. Search for "XAR" firmware / Cellular South.
That should be the right one from the US

Thanks a lot for the info! Found everything I need from a post in the general section
Sent from my SM-N900A using Tapatalk