Related
If anyone can help me and get this working, I will send you $5 via paypal.
Okay so I have fairly decent knowledge of roms/kernels/flashing etc. but I just don't know what to do to fix this problem.
It seems to have happened after I've;
Used the app - Network Speed Booster
Flashed a new rom
Changed the APN (Worked fine)
What I've Tried
- Flashing a new ROM
- Reflashing current ROM
- Flashing a different kernel
- Changing the radio band
- Resetting the APN to default
- A different SIM
Baseband - I9020XXJK8
Thanks to anyone who helps! If you tell me how to get it working, I will PM you saying that I will send you 5$ paypal.
Is the IMEI on the back of your phone (behind battery) the same as the one it shows you in settings -> about?
i had same issues
jh1997sa said:
If anyone can help me and get this working, I will send you $5 via paypal.
Okay so I have fairly decent knowledge of roms/kernels/flashing etc. but I just don't know what to do to fix this problem.
It seems to have happened after I've;
Used the app - Network Speed Booster
Flashed a new rom
Changed the APN (Worked fine)
What I've Tried
- Flashing a new ROM
- Reflashing current ROM
- Flashing a different kernel
- Changing the radio band
- Resetting the APN to default
- A different SIM
Baseband - I9020XXJK8
Thanks to anyone who helps! If you tell me how to get it working, I will PM you saying that I will send you 5$ paypal.
Click to expand...
Click to collapse
i had same issues with deferent roms,i had no idea what causing that.Now i am using KANGYU 2.2.1 Matrix kernel 19.5 , and radio XXKI1 and issue is solved.use radio flashing with caution.
Ihad dessent signal with cybergr rom thunderbolt too .cheers
btw my baseband is I9023
Harbb said:
Is the IMEI on the back of your phone (behind battery) the same as the one it shows you in settings -> about?
Click to expand...
Click to collapse
Yes it's the same IMEI
SpIRkA said:
i had same issues with deferent roms,i had no idea what causing that.Now i am using KANGYU 2.2.1 Matrix kernel 19.5 , and radio XXKI1 and issue is solved.use radio flashing with caution.
Ihad dessent signal with cybergr rom thunderbolt too .cheers
btw my baseband is I9023
Click to expand...
Click to collapse
Thanks for the reply, I will try that rom and kernel now and will post results later.
why don't you just use the stock rom without any changes???!!! i haven't encountred issues since the 4.0.4 is out..
In this case i wouldn't bother with custom ROMs. Grab yourself a stock ROM from the sticky, do your backups and wipes (data/factory reset, format /system, format /boot) and then flash the FULL ROM from the sticky.
This will require you to reroot. I would throw the latest superuser.zip on your sdcard and flash that immediately after flashing your new ROM to make it easier for you.
Can you try a stock rom?
Here's a list.
http://forum.xda-developers.com/showthread.php?t=1445570
huh
c'mon guys...i mean, he want to change his rom like all of 'us' and expiriense the "android dev. world" it is not the right point to use stock and only stock
SpIRkA said:
c'mon guys...i mean, he want to change his rom like all of 'us' and expiriense the "android dev. world" it is not the right point to use stock and only stock
Click to expand...
Click to collapse
When troubleshooting something like this, stock is by far the best option. He is free to do what he wants after the problem and cause are found and fixed.
SpIRkA said:
c'mon guys...i mean, he want to change his rom like all of 'us' and expiriense the "android dev. world" it is not the right point to use stock and only stock
Click to expand...
Click to collapse
Stock rom flash everthing again, bootloader, radio etc.if it works you can go further with custom roms
right one
bartjuhhbartyow said:
Stock rom flash everthing again, bootloader, radio etc.if it works you can go further with custom roms
Click to expand...
Click to collapse
i think you posted the correct help
Waiting for answer from TopicStarter
Thanks for all your help guys.
Anyway I've solved the problem
I just flashed a pretty much stock rom and now its working
Sent from my Nexus S using XDA
20C Baseband with 10D Radio
SMS Send Bug Fix
!!d800 Only!!
Edit (2015.05.12) - I have dumped and posted d80020y modem to my website. It seems that 20y might have fixed this issue. I have been using it for a day or so now and have not noticed this bug. You may wish to try that modem before this one.
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: ROMs that require the KK Modem (for rotation to work) cause SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
https://www.gregtwallace.com/lg-g2/d800-modems/
(It is the Modded One - Baseband: D80020C; Radio: D80010D)
Install:
1) Copy .zip and .md5 to the root of your sdcard.
2) Reboot into TWRP.
3) Install -> Select .zip File.
4) Check "Zip file signature verification." (File is properly signed.)
5) Swipe to install the zip. (MD5 and Signature should verify and modem should install.)
6) Wipe cache/dalvik (for good measure.)
7) Reboot System and Enjoy!
Note: In "System Settings" under "About Phone" -> "Software Information" the Baseband version will be listed as ending in ".190034". This is the 10D baseband.
10D & 10O Baseband Rev: M8974A-AAAANAZM-1.0.190034
Default KK Baseband (20c) Rev: M8974A-AAAANAZM-1.0.190082
This Patched KK Baseband Rev: M8974A-AAAANAZM-1.0.190034
Please respond with any issues, etc.
Shameless plug for donations:
Venmo Preferred (No Fee)
Zelle, send to [email protected]
Backup (Charges Fee)
Paypal
Reserved
So basically this is an all in one modem for stock KitKat ROMs (ex. CloudyG3,etc) and works on AOSP roms with working rotation,etc?
c_brown93 said:
So basically this is an all in one modem for stock KitKat ROMs (ex. CloudyG3,etc) and works on AOSP roms with working rotation,etc?
Click to expand...
Click to collapse
No, this will not work for ROMs based on the old source (e.g. CM11).
This only works for KK based ROMs. It allows KK based ROMs to be fully functional, while still using the old baseband (radio).
This looks promising, I'll provide feedback once I return from work tonight!
Besides fixing the stuck SMS sending bug, any other advantages to this modem? Battery life or signal strengths?
I'm running Lam Hoang G3 ROM on D800 but it should still be fine
Thanks for this man, I always had a better signal with the original radio and now I can use it with kk roms. You're the man.
bps119 said:
Thanks for this man, I always had a better signal with the original radio and now I can use it with kk roms. You're the man.
Click to expand...
Click to collapse
You're welcome.
XERO_Racer said:
Besides fixing the stuck SMS sending bug, any other advantages to this modem? Battery life or signal strengths?
Click to expand...
Click to collapse
This isn't anything fancy. It is exactly what it professes to be. All of the KK modem files, except the 10D radio files were swapped in. So if you had any other 'better' things on 10D vs. the KK modem, you might get them in this, but probably not.
Used this modem all day today. No issues. Didn't have the SMS issue at all.
blastagator said:
Used this modem all day today. No issues. Didn't have the SMS issue at all.
Click to expand...
Click to collapse
You think this will help with reboots caused by low LTE signal?
RenderBroken said:
You think this will help with reboots caused by low LTE signal?
Click to expand...
Click to collapse
I've never had that problem, so I have no idea.
blastagator said:
I've never had that problem, so I have no idea.
Click to expand...
Click to collapse
Thank you kindly for the reply. Now one last question. I am fairly new to the G2 still so I was not around during the new KK source days dealing with the KK modem and AOSP. This sounds like it should work for AOSP roms. Am I correct in that assumption? Thanks again!
The sending delay bug was very annoying, I just flashed it and will report back if there are any issues!
RenderBroken said:
Thank you kindly for the reply. Now one last question. I am fairly new to the G2 still so I was not around during the new KK source days dealing with the KK modem and AOSP. This sounds like it should work for AOSP roms. Am I correct in that assumption? Thanks again!
Click to expand...
Click to collapse
To be honest, I'm not 100% sure. It's easy enough to figure out though. Usually the ROM post says which to use. If not, you can just flash one of the modems, if your sensors work, you're using a modern that is compatible with your ROM. Easiest sensor to check is rotation. Open Maps and your gps blip will have an arrow showing your rotation orientation (compatible) or there won't be an arrow (wrong modem).
OMG Thank you SO much!
blastagator said:
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: Stock KK Modem (on KK based ROM) causes SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
Modem: https://drive.google.com/file/d/0B_5fX5B47GiwNTA4S1c3MG00M0k/edit?usp=sharing
MD5: https://drive.google.com/file/d/0B_5fX5B47GiwSXBGdnhxbnBadzA/edit?usp=sharing
(For people unfamiliar with Google Drive, click the download button at the top to download the flashable zip.)
Please respond with any issues, etc.
Click to expand...
Click to collapse
I have been waiting for a solution for this problem for so long. Downloading now. If this works I would be more than happy to donate. I love the CloudyG3 roms, but the issue with SMS getting stuck in "sending" has been a complete headache for me.
blastagator said:
I have tried multiple ROMs with the KK Modem as well as the KK-AOSP Modem. In all instances, when using the radio contained within the new KK Modem, my SMS messages would randomly get 'stuck' for lack of a better word. I posted a Q&A thread on this issue and had a couple of responses indicating the same issue, even on stock KK.
Therefore, in my quest to fix this, I contacted dr87 about how the AOSP patched modems were created. Based on his (very quick) response, I decided to create my own patched modem.
This modem is compatible with KK based ROM (e.g. CloudyPro II). However, instead of keeping the KK radio, which seems to cause issues, I patched the modem with the 10D radio.
This yields the best of both worlds. All sensors seem to be working correctly in KK. Also, I have not had any SMS messages get 'stuck' since this uses the old, good, radio.
I only created this last night! It flashed and works great on my phone. Flash at your own risk.
Also, I flashed with TWRP.
D800 ONLY
Major Thank You to dr87!
TL;DR:
Problem: Stock KK Modem (on KK based ROM) causes SMS messages to randomly get stuck, causing ~2 minute delay when sending.
Solution: Use this patched modem.
Download:
Modem: https://drive.google.com/file/d/0B_5fX5B47GiwNTA4S1c3MG00M0k/edit?usp=sharing
MD5: https://drive.google.com/file/d/0B_5fX5B47GiwSXBGdnhxbnBadzA/edit?usp=sharing
(For people unfamiliar with Google Drive, click the download button at the top to download the flashable zip.)
Please respond with any issues, etc.
Click to expand...
Click to collapse
is this a bug in the stock vanilla rom(like what came with the lgg2) that or just custom kk roms like ( optimus3g)? ive had this issue for a long time and i decided to leave stock and go with optimus 3g but my sms always get stuck, i reverted back to stock kk rom but have dori kernel installed. im jus tnot sure if i first noticed this while having a custom rom or if it was an issue on my stock kk rom. also can it be used with dori kernel?
I flashed this radio on the official CM 11 ROM. Rotation/compass doesn't work for anybody who wants to know. Everything else seems OK.
joeynox said:
is this a bug in the stock vanilla rom(like what came with the lgg2) that or just custom kk roms like ( optimus3g)? ive had this issue for a long time and i decided to leave stock and go with optimus 3g but my sms always get stuck, i reverted back to stock kk rom but have dori kernel installed. im jus tnot sure if i first noticed this while having a custom rom or if it was an issue on my stock kk rom. also can it be used with dori?
Click to expand...
Click to collapse
I believe the bug is a part of the KK radio and ROM independent. In my Q&A someone reported having the problem on the stock KK, completely untouched.
phatmanxxl said:
I flashed this radio on the official CM 11 ROM. Rotation/compass doesn't work for anybody who wants to know. Everything else seems OK.
Click to expand...
Click to collapse
This modem is not intended for CM11. CM11 is not stock KK based.
blastagator said:
I believe the bug is a part of the KK radio and ROM independent..
Click to expand...
Click to collapse
thanky you for responding. will i have any issue if i use this with dori kernel?
blastagator said:
I believe the bug is a part of the KK radio and ROM independent. In my Q&A someone reported having the problem on the stock KK, completely untouched.
This modem is not intended for CM11. CM11 is not KK based.
Click to expand...
Click to collapse
I like flashin' stuff....things
I just thought I'd give it a try and see what happens.
joeynox said:
thanky you for responding. will i have any issue if i use this with dori kernel?
Click to expand...
Click to collapse
Kernel and Modem should be independent and thus not cause a problem, but I don't know for sure since I haven't done it.
phatmanxxl said:
I like flashin' stuff....things
I just thought I'd give it a try and see what happens.
Click to expand...
Click to collapse
Oh, okay
Can someone please help me out with an issue I am having...?
I can't seem to get Service after installing an AOSP ROM. I have been messing around with this issue for several days now. When I install a 'NON AOSP' ROM such as 'the 'MOAR ROM' it works fine, but then I go to in recovery (Newest TWRP or Newest Philz Touch) and do all of the required 'Wipes' then Install an AOSP ROM like 'Fusion', 'PAC' or the most recent 'CM11 Nightly' and I do not get any Cellular Service (WiFi is fine) and I have been looking for answers for several days and I can't seem to find any.
Can someone please help me out and let me know what I need to do, or point me to the right direction?
Thanks in advance for any help and/or resources that anyone can provide me with. It will be greatly appreciated.
Phone:
Sprint Samsung Galaxy S5 NE5 (Rooted with Knox Tripped :crying
MOAR ROM Installed / Touchwiz Interface.
_________________________________
My Web Design Portfolio
Same was happening to me on philz recovery . so I install trwp for sprint/Verizon . then I installed trwp manager from play store . I install the PAC ROM from in the app and let it wipe it self . and that did the trick at least for me. I have tried many ways like your self. Nothing work that's the only way I got it working. Hope that help.
Sent from my unknown using Tapatalk
I'll give it a shot and see what happens. Thanks for the tip...
Has anyone else had this problem? If so, can you post anything you did to get it working...
My Phone Thanks You...
Im having the same problem on both TW and AOSP. If I mess around with the connection settings I can get a signal but when I reboot its lost.
Ive tried both recoveries and its the same on both. Ive tried flashing modems but that did nothing
EDIT: Seems that any kernel that I flash breaks my phones signal, I need to test further to see what part of the kernel flash is causing this.
Whenever I download klte roms I had that problem. I could receive data and text, but I couldn't send any. I used Google voice until I flash kltespr roms. once I flashed the specific roms for our device it worked. Though I had to install ktoonez's version of twrp to get them to flash. That file can be found on the AICP thread.
Shad Stang said:
Whenever I download klte roms I had that problem. I could receive data and text, but I couldn't send any. I used Google voice until I flash kltespr roms. once I flashed the specific roms for our device it worked. Though I had to install ktoonez's version of twrp to get them to flash. That file can be found on the AICP thread.
Click to expand...
Click to collapse
I think you guys need to flash an APN package with klte roms. Kltespr roms should not have this problem, but if you run into it flashing the APN package shouldn;t hurt there either. Not sure if there is still an APN zip floating around, you may have to manually fix your APN.
It turns out that the custom kernel I was using broke the signal for some reason. Other than that, I had no problems as long as I flashed a kltespr rom. Klte roms worked for data if i used a virgin mobile apn, but there was no texting or calling.
I attached the flashable zip I used to get the virgin mobile apn. I would recommend flashing it right after you flash your rom.
having this same issue also..
i have tried several things.. going back to complete stock and working forward
no matter what i do i get no service on any AOSP rom.. im going to try this apn fix. hopefully it doesnt further break anything lol
Anyone figure this out yet? I've tried about 4 aosp roms and no luck.
PacMan rom with PA Gapps and Ktoonsez kernel worked for me. None of the others did so it must be a ROM issue.
Part of the reason kltespr was de-unified was because of issues like this.
When I'd fix something it would break something else for T-mobile or international.
So I would recommend sticking to kltespr builds for the time being.
Hopefully some work I'll be putting in soon will help get this back in gear.
garwynn said:
Part of the reason kltespr was de-unified was because of issues like this.
When I'd fix something it would break something else for T-mobile or international.
So I would recommend sticking to kltespr builds for the time being.
Hopefully some work I'll be putting in soon will help get this back in gear.
Click to expand...
Click to collapse
I couldn't get data on any kltespr builds except Pac Man and even then I lost data the next day for some reason. The new lollipop build has data working for me even though it's "GSM only" so just hoping it stays that way haha Waiting on fixes for battery drainage and I'll run it daily
Hello.
My problem is that sometimes, when I receive a notification, ambient display turns screen on to show it (as it should do normally), but then, when it is supposed to turn screen off again, it only goes black, but the backlight is still on. It's hard to notice, but I don't want the backlight on, using battery, when I think it's off.
The only way to turn it off is by activating ambient display again (moving the phone, waving in front of proximity sensor, pressing power button), and then it would show my normal lock screen and then turn off, until "something" makes it leave the backlight on again.
Anyone have/had/knows this issue? I've used Mokee ROM, now I'm on RR and it happened on both, I don't remember if it happened in CM. Could it be something app related?
Thanks.
Yeah same happened with cm 12.1 latest nightly too.....just checked it now...
The Answer
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
That's strange! I guess it may be something like the drivers you said, because just one user said that have the same problem, but I'll have to wait until I have some free time to flash stock and root and flash CM and restore all apps and that again... I hate that part of installing another ROM.
therealduff1 said:
Hi there !
When you have installed the custom rom, you have probably flashed directly from another custom rom , is this correct?
If so, it may be your phones drivers slightly messed up at the moment seeing as it has different parts from other roms, depending on how you flashed it.
My solution would be to flash the stock firmware , which can easily be found in the forums, and then flash twrp, then your rom of choice. If that doesn't work, its likely a bug in that specific build of the rom you are installing , seeing as another person who has replied has had the same problem .
Click to expand...
Click to collapse
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Secuential said:
I flashed stock using fastboot and then RR but the problem persists... Any other ideas??
Click to expand...
Click to collapse
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
therealduff1 said:
Ok, I have spent some time thinking about this one for you, as I really want you to get this one fixed!
Although I need abit more information.
1) Does the issue occur on stock rom?
2)Are you sure it is not a problem with the build you are running?
3)What exact steps did you use to flash the rom?
To show that you appreciate my help so far, please click thanks
Click to expand...
Click to collapse
Thanks!
1)I can't tell if it occurs on stock, because on stock I use moto display (which doesn't have this issue).
2) I'm almost sure, because I've used 2 ROMs and both do the same. Maybe I'll have to try with CM nightlies?
3)I followed the guide in "general" section to flash stock using fastboot and android sdk. After that, I booted on stock, then rebooted to bootloader, flashed TWRP, entered to recovery, wiped data and then flashed RR ROM with it's gapps and then flashed moto camera and gallery. After that, wipe dalvik and cache and rebooted to system.
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
therealduff1 said:
Right , ok. I recommend trying one of the cm12 nightly builds, seeing as they worked on my phone fine in terms of ambient display
Click to expand...
Click to collapse
Well, the other user that commented on this post was also using latest CM nightly, so I'm not very positive about it, but I may try it when I have time.
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
therealduff1 said:
Well , looking at all of the information In this post , I think it is safe to say ambient display is not fully working on many roms :/
I installed a new build of cm12 earlier, and I found that sometimes the backlight will stay on , but other times it is fine.
If you want to work on this together, email me at [email protected] , and then we can look into it abit further ?
I will take a thorough look into the forums to see if others are recieving any problems as well .
Click to expand...
Click to collapse
Thanks! I have a lot of work right now, so I can't work with this now, but I'll email you when I have more free time!
Hi buddies,
I know maybe It is a wrong place to ask this, but I've got a strange problem regarding to speaker.
My speaker in my S6 gets some ticks and lags during the play. I mean constantly the music stops and plays over and over.
I have the issue frequently and at the moment when I check the hardware with *#0*# there is no problem with the speaker.
I have the problem in games softwares and music players, and just recently got it.
I've tested different ROMs and kernels, both stock and unofficial, in both Lollipop and marshmallow, but the problem is still keeping up.
Attachment I've uploaded you an instance to better understand the problem.
I really appreciate if you just give me a hand with this.
Thanks.
https://drive.google.com/file/d/0B684uiQkcfJZbVJGWXYzeXVxQkk/view?usp=docslist_api
What model S6 do you have?
Might have installed the wrong model, can you please try to flash an original stock rom and see if that works then go from there to see where you went wrong
Valkiry said:
What model S6 do you have?
Might have installed the wrong model, can you please try to flash an original stock rom and see if that works then go from there to see where you went wrong
Click to expand...
Click to collapse
I've got the international version (G920f).
I've flashed stock ROM bunch of times from different bases, and now I am on stock marshmallow ROM with stock kernel. Still have the issue.
If you've tried different stock roms I'd say your speaker is faulty? If you haven't triped Knox send it back?
Valkiry said:
If you've tried different stock roms I'd say your speaker is faulty? If you haven't triped Knox send it back?
Click to expand...
Click to collapse
But I test during the issue, the speaker is allright, (using *#0*#)
And also I don't enable the Knox at all.
When I use that code I goto imie viewer. Knox is always active on stock rom regardless, it sounds hardware related not software, since you've tried other roms and it's still the same issue it doesn't make sense that you broke your device speaker.
Valkiry said:
When I use that code I goto imie viewer. Knox is always active on stock rom regardless, it sounds hardware related not software, since you've tried other roms and it's still the same issue it doesn't make sense that you broke your device speaker.
Click to expand...
Click to collapse
Oh, I really sorry that was a blunder
I meant *#0*# ...
So How can I really make sure that It's a hardware issue?
Does flashing ROM with box helps?
Well if you keep flashing different roms and nothing is working to fix the problem, which is including kernel issues on stock and custom I'd say it's hardware related.