Created myself a mess and I am at a loss on how to fix it. I was trying to run down the BT issue in AOSP and I remembered that BT works fine on the 915F. So I flashed the TWRP file for the 915F and flashed Mickey's RR ROM. The Bluetooth worked but the touch screen input was of the mark by a considerable margin. I reflashed the TWRP for our 910F, but the touchscreen is still messed up in TWRP. Tried flashing our RR thinking it might have been a kernel issue, still messed up. Tried a TW ROM, no dice. Odined a stock ROM, still messed up. Any suggestions?
May have found the solution...
https://forum.xda-developers.com/note-4/general/expanded-fix-touch-calibration-screen-t3617013
Related
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
nwsk said:
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
Click to expand...
Click to collapse
Basically yesterday I had the same problem, flash after flash didn't help. Can tell you exactly, what I did:
Found factory version of my firmware in my region (SEB Baltics for me, MGA). Then I reinstalled TWRP recovery through ODIN, wiped everything I could, after that flashed stock firmware 2 times consecutively (no reboot in odin, reboot manually after first flash and flash again).
After that everything went fine, and Wi-Fi started working again. MH1 custom ROM right now, going ok.
Googling seems to suggest having to reflash stuff multiple times (I've seen someone say they flashed their stock rom 11 times wtf), and there doesn't seem to be any set procedure that gets the flash to work... Did you also flash multiple times before this last run worked? Perhaps you just got lucky and it worked the last time? (I assume no one tries to bork their wifi and test if their last routine works again for them).
I'm asking mainly because I don't want to go through the hassle of reflashing the entire rom again; would it be correct to say that wifi is just contained in the modem/radio file, and I should try spam flashing that?
No. WiFi drivers are in the kernel, not the modem. If you were going to flash anything, you'd flash a kernel/rom.
nwsk said:
Hiya,
Using the international i9505 LTE, I tried flashing faux's kernel today, and everything appeared to be working. I also then flashed the xposed framework/some modules. Afterwards, I realised my wifi wasn't working anymore, and disabling the xposed framework didn't help. I also tried flashing the ausdim kernel which didn't work, as well as flashing my modem file, and the apparent wifi fix files multiple times, none of which solved the problem.
I have a nandroid backup, but would rather not restore it atm as it was made a while ago and I don't want to restore all the apps and stuff, so does anyone have any idea how to go about solving this problem?
Click to expand...
Click to collapse
I suggest you use titanium backup to bakup your apps, it's not a tough job as you thought. that might be the easiest way, although some data can't be backup.
nwsk said:
Googling seems to suggest having to reflash stuff multiple times (I've seen someone say they flashed their stock rom 11 times wtf), and there doesn't seem to be any set procedure that gets the flash to work... Did you also flash multiple times before this last run worked? Perhaps you just got lucky and it worked the last time? (I assume no one tries to bork their wifi and test if their last routine works again for them).
I'm asking mainly because I don't want to go through the hassle of reflashing the entire rom again; would it be correct to say that wifi is just contained in the modem/radio file, and I should try spam flashing that?
Click to expand...
Click to collapse
No, I did flash it 2 times straight away. Flashing correct modem didnt help me, dunno why.
Gh0stR1pp3r said:
No, I did flash it 2 times straight away. Flashing correct modem didnt help me, dunno why.
Click to expand...
Click to collapse
read this....
http://forum.xda-developers.com/showthread.php?p=45219995#post45219995
looks bit similar
bofff said:
read this....
http://forum.xda-developers.com/showthread.php?p=45219995#post45219995
looks bit similar
Click to expand...
Click to collapse
Welp, bluetooth had no problems whatsoever. It was only the wifi, which didn't want to turn on. Now everything is ok.
Well, finally got around to reflashing stock as Gh0stR1pp3r suggested, which worked. Thanks
Nandroid, kernel flashing, and modem flashing all didn't work. No clue why. I flashed the ausdim kernel again and it worked this time around, so it's just weird I guess? :S
And unfortunately I seem to have messed up the titanium backup somehow, I can't seem to find any of the stuff I thought I backed up Oh well
Hi!
I flashed a rom with MGG and got the same FC problems as everyone else. Flashed the stock MGG rom and cleared everything, factory reset etc. After that I didn't get any audio at all. Not ever during the samsung bootup animation.
I flashed another rom through cwm, same thing and no wifi. The wifi fix doesn't seems to work either.
Tried CM 10.2, there I'm getting wifi but instead no data trafic. Baseband says "unknown" even through I flash different modems. The wifi and data problems I can get around, its just that I can't flash older roms through odin until they unlock the new bootloader.
The audio problems in the other hand. Saw some guy having sound problems in the modem thread as well. Not to many have posted about this problem. Seems to be a pretty rare problem.
What could cause this, how to get around this?
Had to go to work with a non working phone so can't get any logs for you at the moment.
I'm concerned, please enlighten me!
Finally, flashed the latest CM 10.2. Got wifi and reception working!
Still no sound. What log would you like to see to find out what's wrong?
After flashing a few roms I have noticed sound has stopped working, at first youtube videos wouldn't load up or start to play and on first device boot all gapps installed would be in notification bar with an error installing. This is on both cm 10.2 and even the original stock 4.3 touchwiz rom, have I broken my device for good?I never had this issue before when I went back to touchwiz, I have the android 4.3 with knox installed currently....Thanks
Similar Problem!
Hi, I'm having similar problems I have no sound at all coming from the device, I've read every thread that seas sound on the heading for I9505 and for many people flashing I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar resolved the problem but not in my case.
Last night I tried flashing I9505XXUEMI8_I9505OXAEMI8_I9505XXUEMI8 and after I changed the kernel I got some sound when turning the volume up and down but the phone was running very slow.
Today I tried flashing Omega rom v15 flashing the right modem for the new bootloader before flashing the zip and no sound, I tried changing the kernel, still nothing.
So now I'm in build number XXUEMJ9 and baseband MJ5.
There has to be a solution for this as it is a software issue!!
PD: I can't get any signal either, WiFi is working though.
Ok this is a really strange Problem. I have two notes. On both I flashed the s5 port from Fahadali. Both had v6 on them and everything was awesome. He left development though so I continued the Project trying to make a "v7" Version, while doing that after I flashed the modified v6 many times but suddenly it softbricked. All I did Change though were some apks.
I've done this many times before with other roms without any Problems at all.
Then I reflashed stock NF4 through Odin and the newest twrp. Flashed v6 (the original non modded version) and it softbricked again...
I tried again, same result. I tried to Flash other recoveries, other bootloaders, other fw's through Odin and a lot more but: nothing.
Everytime I Flash v6 it breaks. I tried to Flash v5 and then suddenly: It worked! I tried to Flash other roms like Omega, and they work aswell. Only the v6 Version doesn't.
So if that's the case and the phone itself is clean (wiped 100 times Flashed stock even with a pit file) the Rom must be corrupted right? So I checked the md5 and well it was correct. I redownloaded and still: same md5. I checked the md5 on the note aswell. I tried using a sd Card instead and still: the same result.
In the meantime my other note worked perfectly, even with my modded Rom. So I continued to work on the v7 using that one. And then after like 14 flashes: the same Problem on that one aswell.
In detail:
I use twrp. And get into the Aroma installer of the Rom. It installs without any Errors whatsoever. Then I reboot.
And now the important part: the kernel has not been flashed cause it's not showing up in red (the rom's using a custom kernel).
This doesn't happen when I use the v5 Rom(still), and never happened before even with the v6. So I even tried flashing the kernel afterwards trough Odin and it gets successfully flashed. But the Rom still doesn't boot...
This means though that because of the kernel not being flashed (even though in Aroma it Shows that it does) even the rest might not get flashed. It only wiped the System Partition and that's it. But then the question remains why did it work before?? And why does it work for all the other People that have flashed it? And why did it work on mine until I flashed it more than 14 times?? And why does v5 and all the other roms still work fine?
I really don't get why this happens. Some v6 files have to still be on the device somehow, or idk. It's impossible cause I wiped but who knows. I've never seen anything like it, neither has the original dev of the Rom.
I Need to get v6 working, else I can't continue to build this Rom. Which is a big Problem for all who wants the s5 Rom.
I hope someone knows what to do. Thank you for your time.
Hey XDA peeps!
I recently got meself a G4 Plus (32/3 GB, XT1643), and everything has been totally fantastic, except for this: connecting to a Bluetooth device is almost impossible, and using any 7.1 ROM causes SIM errors.
I've been able to connect to my Android Wear watch, but that's about it. I got Motorola's VerveLoop+ headphones too, and it connects to everything but my G4+. I tried multiple things, reflashing the modem file (NON-HLOS.bin), flashing stock ROM, flashing multiple ROMs from the forums (CM, RR, BS, AOKP), none of them fixed the problem.
I'm currently using RR 5.7.4 (MM), and 5.8.0 (N) recently came out. I tried updating but it doesn't read my SIM after the process. I tried flashing the 7.0 "soak" ROM or whatever it is, but nothing, same issue over and over again. I tried a full format and flashing RR alone through TWRP but same thing.
So, what do? Any help on either would be very much appreciated.
themajod said:
Hey XDA peeps!
I recently got meself a G4 Plus (32/3 GB, XT1643), and everything has been totally fantastic, except for this: connecting to a Bluetooth device is almost impossible, and using any 7.1 ROM causes SIM errors.
I've been able to connect to my Android Wear watch, but that's about it. I got Motorola's VerveLoop+ headphones too, and it connects to everything but my G4+. I tried multiple things, reflashing the modem file (NON-HLOS.bin), flashing stock ROM, flashing multiple ROMs from the forums (CM, RR, BS, AOKP), none of them fixed the problem.
I'm currently using RR 5.7.4 (MM), and 5.8.0 (N) recently came out. I tried updating but it doesn't read my SIM after the process. I tried flashing the 7.0 "soak" ROM or whatever it is, but nothing, same issue over and over again. I tried a full format and flashing RR alone through TWRP but same thing.
So, what do? Any help on either would be very much appreciated.
Click to expand...
Click to collapse
I have multiple Bluetooth devices and connections all day long and I'm on RR 5.8.0 atm but no issues like you happened to me ever(XT1642, MM stock modem). Maybe with flashing you messed up the modem so sim detection etc. Is gone? Did you tried to separately flash the M modem?
strongst said:
I have multiple Bluetooth devices and connections all day long and I'm on RR 5.8.0 atm but no issues like you happened to me ever(XT1642, MM stock modem). Maybe with flashing you messed up the modem so sim detection etc. Is gone? Did you tried to separately flash the M modem?
Click to expand...
Click to collapse
Tried it before and tried it just now, and still nothing... Right now I'm more concerned about the Bluetooth thing, its bumming me out. I reverted back to RR 5.7.4 from a backup, but even on 5.8.0, Bluetooth wouldn't work.
Anyone know what to do?
So if I understand correctly Bluetooth has never worked properly for you ever since you bought the phone?
If that's the case and it doesn't work even with stock firmware you should consider hardware fault.
I would put stock back and try to get it serviced.
gabriwinter said:
So if I understand correctly Bluetooth has never worked properly for you ever since you bought the phone?
If that's the case and it doesn't work even with stock firmware you should consider hardware fault.
I would put stock back and try to get it serviced.
Click to expand...
Click to collapse
No what happened is that after flashing RR, the thing stopped working. I tried reverting back and it's the same. It's not that Bluetooth isn't functional, I can connect to my laptop and my Android Wear watch, but it won't connect to my Bluetooth headset (the VerveLoop+ as I mentioned)
themajod said:
No what happened is that after flashing RR, the thing stopped working. I tried reverting back and it's the same. It's not that Bluetooth isn't functional, I can connect to my laptop and my Android Wear watch, but it won't connect to my Bluetooth headset (the VerveLoop+ as I mentioned)
Click to expand...
Click to collapse
If it was working with stock, you should be able to get it back to work.
I would focus in making it work again in stock.
Make sure you flashed the right version for your model and so on.
STOCK
FLASH
gabriwinter said:
If it was working with stock, you should be able to get it back to work.
I would focus in making it work again in stock.
Make sure you flashed the right version for your model and so on.
STOCK
FLASH
Click to expand...
Click to collapse
Well thing is, I tried doing that before, after flashing RR the first time, Bluetooth stopped functioning properly, be it in CM or stock, same thing.
Note: I was able to fix the weird SIM thing with 7.1, but Bluetooth issues still persist.
themajod said:
Well thing is, I tried doing that before, after flashing RR the first time, Bluetooth stopped functioning properly, be it in CM or stock, same thing.
Note: I was able to fix the weird SIM thing with 7.1, but Bluetooth issues still persist.
Click to expand...
Click to collapse
A bit off-topic how did you fix the weird SIM thing with 7.1?
gabriwinter said:
A bit off-topic how did you fix the weird SIM thing with 7.1?
Click to expand...
Click to collapse
I don't really know, I was looking for a workaround and I backed up my RR 5.7.4 ROM, then when I hit restore it wouldn't work, so I flashed RR 5.8.0 just to see what will happen and it got fixed... Really odd how that worked...
Edit: Never mind it, it went back to how it was after restoring my backup properly. I tried updating but it didn't work. For 7.1 issues, I'll just wait until the official update and flash the modem file for it, I really hope it works.