Develop Bugs

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] Maguro rebooting radomly

Dear community,
i have a reboot problem with my gnex gsm for several weeks now. The phone seems to be rebooting randomly after freezing. The only situation where no reboot occurs is when it is attached to the pc via usb docking station in developer mode.
Ususally, i had cyanogenmod nightlies installed, but i also tried stock 4.2.2 and 4.3 images. Moreover i tried several full wipes using cwm and twp recovery. After the last wipe, I did not recover anything using titanium backup. At the moment i am running on 4.3 stock image and stock recovery with no root. Bootloader is still unlocked. The phone keeps rebooting...
Has anybody an idea where to locate the problem (probably some certain log files) ?

My GNex had that problem. It started with random reboots. Then got into a boot loop from which it never recovered.
Good luck. Hope you don't have the same fate that I had.
Try flashing back to stock and lock and unlock bootloader. If that doesn't stop the reboots, IMO, time to look for a new phone.
Edit : You might want to send it to Samsung for repair, if you are still under warranty.
Sent from my Micromax A116 using Tapatalk 2

Check battery connections, replace battery
Update us later

viskon said:
My GNex had that problem. It started with random reboots. Then got into a boot loop from which it never recovered.
Good luck. Hope you don't have the same fate that I had.
Try flashing back to stock and lock and unlock bootloader. If that doesn't stop the reboots, IMO, time to look for a new phone.
Edit : You might want to send it to Samsung for repair, if you are still under warranty.
Sent from my Micromax A116 using Tapatalk 2
Click to expand...
Click to collapse
I've already tried your suggestion, but it didn't help.
Actually, I'm still under warranty, but i was hoping to solve the problem by myself to avoid being without phone for a few weeks.
beekay201 said:
Check battery connections, replace battery
Update us later
Click to expand...
Click to collapse
Already tried that, i have a replacement battery. By the way, the reboot problem also occurs when charging from the normal power supply. Only the usb connection with debug mode avoids rebooting.
Thank you for your advice.

CStauch said:
Already tried that, i have a replacement battery. By the way, the reboot problem also occurs when charging from the normal power supply. Only the usb connection with debug mode avoids rebooting.
Thank you for your advice.
Click to expand...
Click to collapse
Okay, so what do you think you can do next? That replacement battery, is it a stock battery?

beekay201 said:
Okay, so what do you think you can do next? That replacement battery, is it a stock battery?
Click to expand...
Click to collapse
Yes, it is not distiguishable from the original one.
I was hoping, that there can be any hint in some sort of log file or something.

Have you tried booting into safe mode to see if it is an app issue?
http://www.talkandroid.com/guides/b...or-tablet-into-safe-mode-for-troubleshooting/
Sent from my Micromax A116 using Tapatalk 2

viskon said:
Have you tried booting into safe mode to see if it is an app issue?
Sent from my Micromax A116 using Tapatalk 2
Click to expand...
Click to collapse
Just tried that, also no difference

Are you using the original cable to charge it? I've had problems where using cheap ebay cables made the touchscreen all jumpy and needed a reboot to fix. I changed to the original cable and it never happened again. Dont know if you could have a similar problem but with random reboot.

AzNxJoHnNy said:
Are you using the original cable to charge it? I've had problems where using cheap ebay cables made the touchscreen all jumpy and needed a reboot to fix. I changed to the original cable and it never happened again. Dont know if you could have a similar problem but with random reboot.
Click to expand...
Click to collapse
I'm using both the original cable and two docking stations from amazon, one with ac/dc adaptor and one with usb. The phone always reboots no matter if it is charging or not. Only when connected to usb in debug mode, there is no reboot.

CStauch said:
Just tried that, also no difference
Click to expand...
Click to collapse
I strongly suspect a hardware issue. You might be better off sending it for warranty repair.
Sent from my Micromax A116 using Tapatalk 2

SAME PROBLEM!
Tried with several ROMs and Kernels, also stock, disabling proximity sensor (there is someone with this sensor issue...) but nothing changed.
Now I made a fuuuul hard deep wipe, and installed AOKP ROM with Nexus Toolkit. I have to check if it will be working, if not I'm going to restore phone to stock (locked unrooted etc) and then try...

Same problem here.

This happened also to me on August... was an hardware issue for me

TKPL said:
SAME PROBLEM!
Tried with several ROMs and Kernels, also stock, disabling proximity sensor (there is someone with this sensor issue...) but nothing changed.
Now I made a fuuuul hard deep wipe, and installed AOKP ROM with Nexus Toolkit. I have to check if it will be working, if not I'm going to restore phone to stock (locked unrooted etc) and then try...
Click to expand...
Click to collapse
Still not working... I wiped everything and restored phone to stock locked, and got, in one day, "only" one reboot and two super-lag (it's better than before but it's not good). I gonna send it back to assistance...

TKPL said:
Still not working... I wiped everything and restored phone to stock locked, and got, in one day, "only" one reboot and two super-lag (it's better than before but it's not good). I gonna send it back to assistance...
Click to expand...
Click to collapse
I had the same problems... i've tried to make a clean installation of the stock factory image ... sent to assistance.. it was an hardware issue...
Have You tried to use the flash-all.bat to restore the factory image, the executable inside the factory image archive that flash the stock image automatically... try it

enricocid said:
I had the same problems... i've tried to make a clean installation of the stock factory image ... sent to assistance.. it was an hardware issue...
Have You tried to use the flash-all.bat to restore the factory image, the executable inside the factory image archive that flash the stock image automatically... try it
Click to expand...
Click to collapse
I reflashed with the Nexus Root Toolkit the factory image, so I guess it made automatically the flash-all.bat.
Tomorrow I'm sending the phone to assistance

enricocid said:
This happened also to me on August... was an hardware issue for me
Click to expand...
Click to collapse
So What was the hardware issue because i have the same problem and out of warranty..... And I would like to repair the phone.
If the costs aren't to high.

It is happening to my gnex since yesterday.
I was on shiny Rom and all of a sudden it began rebooting randomly.
Looking at the last_kmsg I found a kernel panic related to I/o error of the ext4-fs (or something similar).
I performed several wipe, thinking of a kernel issue.
It continued rebooting randomly so I completely reset to stock 4.3 including format of sdcard.
I have the feeling that reboots began when the sdcard began to fill.
I also re_locked the bootloader, but reboots still occur.
It is probably a faulty Emmc chip, I will go to the store for warranty.
Lionhe
Inviato dal mio Galaxy Nexus utilizzando Tapatalk

need help with my bricked xperia play r800a

first, I will explain my phone condition.
from off power. If I try to turn on by holding power button, I can feel it vibrates as normal when it turn on to boot up. But for my xplay, its screen show nothing and it seem that the screen does not turn on at all. Then if I plug it to pc from this condition, the pc will ring detect device sound and unplug device sound and detect device sound and unplug device sound, repeat and repeat forever. So I have to pull off battery to turn the phone off. But flash mode and fastboot still work with flashtool.( as you all know plug usb with back button and search button)
what I have done so far to solve this is :
- I have tried to flash stock rom R800_4.0.2.A.0.79 and r800a_2.3.3_US Generic via flashtool in flash mode. flashing is complete but my xplay still remain unbootable.
- flash doomkernel via fastboot with flashtool. process complete but again, problem is not solved.
any help ?

So let me get this straight, you flashed a firmware and your phone is still unbootable and just has a black screen? hmm strange.. Have you tried Sony PC Companion?

Xplay21 said:
So let me get this straight, you flashed a firmware and your phone is still unbootable and just has a black screen? hmm strange.. Have you tried Sony PC Companion?
Click to expand...
Click to collapse
PC can not recognize my device just as I told on the thread that PC ring the sound of detect and remove, detect and remove on and on...........

still wait for solution.
so quiet.......

kokcona said:
still wait for solution.
so quiet.......
Click to expand...
Click to collapse
I'm sorry no one could help you out as of yet, this issue does seem quite rare so we can expect why you haven't gotten any help and sorry bout that. I would probably flash the different types of firmware and see if theres any hope there, or you can send your phone to repair and that should be your last to resort solution.

When did this happen and how? Such things do not happen without a history, we need to know what you did/tried before to see if we can fix it!
Gesendet von meinem D6503 mit Tapatalk

Remove phone and insert it then hold back button(or search button i dunno, but don't turn it on) until the power button shows blue light(or green) and insert the usb cable into the computer. You must tick the two box when flashing stock rom. Check No final verifications and Reset Customizations. Are you trying to use stock rom with doom kernel?
I had this problem too.

Have you tried flashing different Kernels and ROMs?

Bin4ry said:
When did this happen and how? Such things do not happen without a history, we need to know what you did/tried before to see if we can fix it!
Gesendet von meinem D6503 mit Tapatalk
Click to expand...
Click to collapse
I had used several custom rom before, the last custom rom is something with lupus kernel (sorry I cannot remember its name). At that time, I have many problem about performance such as when I got a call (the phone start to ring and vibrate) the screen won't show anything, I have to wait for several second before screen show up and I can recieve the call.
One day during on a trip, I designed to turn the phone off and pull out sim card. and used my friend's iphone4 during the trip. When I back home. I tried to start my xplay again. But the phone won't start anymore, it become the state as I mention in this thread.

ryanperez said:
Remove phone and insert it then hold back button(or search button i dunno, but don't turn it on) until the power button shows blue light(or green) and insert the usb cable into the computer. You must tick the two box when flashing stock rom. Check No final verifications and Reset Customizations. Are you trying to use stock rom with doom kernel?
I had this problem too.
Click to expand...
Click to collapse
I have not tried 'No final verifications and reset customizations' yet. So I will tried this when I got my phone back.
ps. I sent it to sony service center last week. Yesterday, they call me that it is hardware failure, and they don't have spare part. But I think they just cannot figture it out what is the problem and don't want to bother with old phone. So I call it back. still wait it to be back in my hand.

kokcona said:
I have not tried 'No final verifications and reset customizations' yet. So I will tried this when I got my phone back.
ps. I sent it to sony service center last week. Yesterday, they call me that it is hardware failure, and they don't have spare part. But I think they just cannot figture it out what is the problem and don't want to bother with old phone. So I call it back. still wait it to be back in my hand.
Click to expand...
Click to collapse
Atleast good news for you, i just read your answer and have to tell you that i have no idea too sorry ... Maybe it is really hardware failure.
Regards

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 !!

When Phone is off and plug usb cable, screen STUCK on "warranty bit kernel"

Hi everyone,
My problem is the following.
After installing CyanogenMod 10.2.1.3 I noticed a little problem. Whenever I plug the usb cable phone when it is off, screen stuck on "set warranty bit: kernel" with the empty battery icon.
The phone reboot normally after disconnecting the cable.
For information, I bought my phone with I9195XXUCNH5.
Is there a fix ?
Thanks

That "" set warranty bit "" means you have a custom kernel installed. To remove that you have to flash stock firmware which means you will lose root and recovery.

Hi,
Yes I know, I always have this message when I turn on my phone, its not a problem. I just describe the screen when it stuck.
I have this problem only when I turned off my phone and plug my usb cable.

maquille said:
Hi,
Yes I know, I always have this message when I turn on my phone, its not a problem. I just describe the screen when it stuck.
I have this problem only when I turned off my phone and plug my usb cable.
Click to expand...
Click to collapse
I did notice that on my phone. That is 'offline charging'. Charging while device is switched off.

sasank360 said:
I did notice that on my phone. That is 'offline charging'. Charging while device is switched off.
Click to expand...
Click to collapse
Ok, and what is your solution ? Because this notification don't desappear and phone stays alight indefinitely.
And I want to keep this version of cyanogen.
Thks

maquille said:
Ok, and what is your solution ? Because this notification don't desappear and phone stays alight indefinitely.
And I want to keep this version of cyanogen.
Thks
Click to expand...
Click to collapse
I noticed this while on stock rom. It is not possible to remove that sign without losing root and custom rom/recovery.

You don't understand. The probleme is not the message with "set wrranty bit : kernel"
Problem is the stuck on the battery icon

maquille said:
You don't understand. The probleme is not the message with "set wrranty bit : kernel"
Problem is the stuck on the battery icon
Click to expand...
Click to collapse
I know that. Can you tell me if the battery % is increasing or is it static while screen is stuck ??

sasank360 said:
I know that. Can you tell me if the battery % is increasing or is it static while screen is stuck ??
Click to expand...
Click to collapse
Battery is charging when screen is stuck but icon is still the same : empty battery

maquille said:
Battery is charging when screen is stuck
Click to expand...
Click to collapse
Then the screen is not stuck. That is called offline charging as i mentioned earlier. Once or twice I got out of that screen by pressing and holding power key until screen turns off.
Then I pressed power again and it booted back to system.

sasank360 said:
Then the screen is not stuck. That is called offline charging as i mentioned earlier. Once or twice I got out of that screen by pressing and holding power key until screen turns off.
Then I pressed power again and it booted back to system.
Click to expand...
Click to collapse
Yes, I can reboot my phone normally after unplug usb cable. I said it on my first post
But do you have solution for this "little" problem of stuck ?? I didnt have this probleme with my previous s4 mini under this rom

maquille said:
Yes, I can reboot my phone normally after unplug usb cable. I said it on my first post
But do you have solution for this "little" problem of stuck ?? I didnt have this probleme with my previous s4 mini under this rom
Click to expand...
Click to collapse
Ok you need to read please, he never mentioned unplugging the cable, while it is plugged in and "STUCK" as you describe, press and hold power button. That will turn it off, straight after screen goes black release and press and hold again until vibe is felt, it should boot then. If it doesnt work its a kernel issue with not being able to boot while plugged in. What kernel are you running? And is it official or unofficial cm10?
Sora.

Hi
Reboot is not the problem, i can reboot the phone when cable is plugged or unplugged when screen is stuck.
I just want to charge my phone when it is off without this animation. My only solution for the moment is to reboot my phone and continue charging
I think s4 mini "black edition" doesnt support off charging with CM 10.2.1.3 (official, and official kernel). Because I never had this problem with my previous s4 mini "normal" under CM 102.1.3
I tried CM12 with S4mini black edition and i dont have this problem.
So i think the problem is CM10.2.1.3 + s4 mini black edition
Is it more clear ? Sorry im french.

maquille said:
Hi
Reboot is not the problem, i can reboot the phone when cable is plugged or unplugged when screen is stuck.
I just want to charge my phone when it is off without this animation. My only solution for the moment is to reboot my phone and continue charging
I think s4 mini "black edition" doesnt support off charging with CM 10.2.1.3 (official, and official kernel). Because I never had this problem with my previous s4 mini "normal" under CM 102.1.3
I tried CM12 with S4mini black edition and i dont have this problem.
So i think the problem is CM10.2.1.3 + s4 mini black edition
Is it more clear ? Sorry im french.
Click to expand...
Click to collapse
Sorry so are you saying the screen stays on, on that screen with set warranty bit: kernel and battery logo? Hmm that is an issue.
By black edition do you just mean the colour or what because as far as im concerned the s4 mini lte's are all the same??
Edit: looked up the black edition: the only different is the case and color, iut is still the same hardware this has nothing to do with anything.
Sora.

For you fisrt question : yes
For the second, I mean black edition is most recent that my old s4 mini buy last year.
And I think new security norm included in new ROMS can create incompatibility with older versions of CM, like 10.2.
Result could be the same if you ugrade S4 mini normal with latest official firwire and put CM10.2
Im not sure to be clear in english...

maquille said:
For you fisrt question : yes
For the second, I mean black edition is most recent that my old s4 mini buy last year.
And I think new security norm included in new ROMS can create incompatibility with older versions of CM, like 10.2.
Result could be the same if you ugrade S4 mini normal with latest official firwire and put CM10.2
Im not sure to be clear in english...
Click to expand...
Click to collapse
Right, well thats a problem as I said mostlikely a kernel issue, maybe try a custom kernel for cm10 instead of stock cm10 kernel and see if that fixes your issue.
Yes only difference between black and norm is firmware is new with knox and the colour and back case with faux leather, so really no difference.
Let me know if custom kernel works or not for you.
Sora.

Problem is the same with f4ktion kernel. I didnt try an other one.
Wich one you advise me?
Envoyé de mon GT-I9195 en utilisant Tapatalk

maquille said:
Problem is the same with f4ktion kernel. I didnt try an other one.
Wich one you advise me?
Envoyé de mon GT-I9195 en utilisant Tapatalk
Click to expand...
Click to collapse
I don't use cm10 so I couldn't say sorry. Ask in the kernel thread to see if others have the same issue. Call it offline charging screen stays on.
Sora.
Sent from my Galaxy S4 Mini LTE using XDA Premium