Hello,
Whatever the kernel with root I flash in my SGS2, I can't connect any bluetooth keyboard any more. When I press a key, the connection is very brief.
This is a very annoying bug.
Are you sure it isn't the keyboard at fault?
More info needed.
What rom
What kernel
What keyboard
I'm using right now the official stock ROM, XWKL1 version, with an official kernel. If I flash the Speedmod kernel (r19 test 1), I can't connect any bluetooth keyboard any more, and I must flash the official kernel if I want this feature back.
The pairing works well, but if I press a key on the bluetooth keyboard, the phone asks me for authorizing the connection. From there, as soon as it connects to the device, the connection ceases immediately. I can barely read "Connection to HID Device" as it appears very briefly, and that's all I can get if I have the root permissions.
My keyboards are the Beewi BBK200 and the Halterrego HWrite. They have been tested under Windows without any flaws. They also have been tested with the official kernel from a freash flash, and they also work flawlessly as long as I don't flash a custom kernel.
The same problem happened with an official XWKK2 ROM and Siyah kernel.
bumppity bump?
Yeah..bumpy. Only CF Root works, all the rest don't.
Known issue. Only the original kernel can use Bluetooth hid. Cf root kernel works because it repacks the original kernel as is.
Sent from my GT-I9100 using Tapatalk
Hello everyone,
I have received a HOLDS NJ-N81S Spreadtrum SC6820 based android phone ( a Samsung Galaxy S4 Clone). During a failed root attempt via VROOT software, the phone no longer boots. I did howerver before even using VROOT make a copy of the local files via ftp, I do not have a real backup ROM etc.
I have been stiching FDL1/2 files and nvitem files from various other chinese phones to make a frankenstein ROM for my phone and have succeeded somewhat. The phone now boots correctly and I have sound and LCD screen is no longer grabbled.
My main roadblock is the touchscreen panel, I do not have the correct drivers for driving the panel, my original kernel modules are not compatible with my stiched ROM. I'm in need of help if anyone is able to assist me, I've attached below the original peripheral drivers before the failed VROOT app
Original drivers: www dropbox com / s / moj2upchd2x6xos / Spec_NJ-N81s-drivers.rar
the ko versions are: 2.6.35.7 mod_unload ARMv7
the version I need is:2.6.35.7 preempt mod_unload ARMv7
the touchpanel driver is the mxc622x.ko which is needed in order for the ft5206_ts.ko to work, flashing the ft5206_fw.bin to the chip I think isn't necessary as the focaltech panel controller chip wasn't touched.
Hello everyone, I have made some progress on the phone since I last posted the problem.
As I did not have a ROM backup of the phone before proceeding to ROOT it, I had to scavange the kernel modules to handle the display, touch, sound, and the modem around the net. I have succeeded in getting the phone to properly boot and touch is working. My first problem was the screen being flipped upside down, but I got around the problem by patching the build.prop to rotate 180.
The biggest problem I have right now is that I get a corrupt display everytime the phone wakes up from standby, I press the power button and the phone goes to standby fine, but I don't see an image when I wake i up again, I can hear the sound working, the touch still works etc. I need help fixing the problem I don't know if it's the MALI gfx that has trouble waking up or something else is at play here.
Hi i posted on here a day or so ago, because i couldn't get a ROM to fix a RK3066 based chinese tablet that started freezing at the boot logo.
Anyway after trying some suggested ROMS elsewhere, the tablet is working again. We had to use a mixture of the boot.img from one ROM and the kernel/system from another to get it running because the propper ROM isn't available anywhere.
However, WiFI and BT do not work now.
After some research and delving into the terminal, dmesg was saying that it "couldn't open FW: WIFI_RAM_CODE". Apparently this is the firmware for Mediatek branded wifi chips (which this tablet uses). The only ROM that works on this tablet seems to only support realtek/broadcom wifi modules and not Mediatek.
After reading a little about porting wifi drivers, I downloaded a ROM from another device that uses the same Mediatek model of wifi chip as this tablet, and used adb to push the WIFI_RAM_CODE file from that ROM onto the /etc/firmware directory of the tablet. The FW error is now gone in dmesg when the wifi is turned on, but in the list of wifi networks all i see is:
NVRAM WARNING: Err - 0x01
No other networks are found. Only this error.
Any input you can provide would be much appreciated. I'm not too bothered about bluetooth but to get wifi back would be great.
Thanks,
James.
Hi again,
I have a friends T95Z and trying to fix it up. It won't connect on WiFi. When you go to network settings - WiFi is switched off. If you switch it on - it "pretends" to search for about 40 seconds - finds no AP nearby and switches "Off".
I have wrenched on a number of these T95Z. boxes and always seem to get them working.*
Hats off to Superceleron and his ROM -* His ROM really cleaned up the first couple of these I worked on. They had the LTM8830 chipset I think.
Then I worked on a couple newer T95Z's and that ROM didn't work. If I recall - same thing where you can try and turn the WiFi on but it just turns off. I think they turned out to have the 9377 chipset. Found a workable ROM for them and all is well.
Okay so here are some pics of the insides of this one:**https://imgur.com/a/Kd2M1Ta
I flashed a bunch of ROMs - Here is like a list of some of the file names etc:
Poison ROM - https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720
T95ZPLUS_q200_9377_customV3.2
atvXperience_v2F_s912
s912_atvXperience_v2FF
T95U PRO_S912_02012017_
v1016-EB-AGCF-LPDDR3-2G
Sorry that I didn't keep great notes on what I flashed but hey - once you start flashing - it is just so easy to try another one.*
Anyway - Several of the ROM's said they were for the AP6255 chipset and ALL of the ROM's do the same thing where the WiFi just won't turn on.*
Now I am not an expert on this - so I don't know:
Can you confirm - Is this a Sunvell?
Is the wifi chipset an AP6255?
What else should I try?* I wandered into a T95U ROM... should I wander further and look for Beelink or other manuf ROM's that show the AP6255?
Is there any other tool or APK that can be flashed after ROM install to query the hardware config or add chipset support?
Open to ideas.*
Thanks!
wantpizza said:
Hi again,
I have a friends T95Z and trying to fix it up. It won't connect on WiFi. When you go to network settings - WiFi is switched off. If you switch it on - it "pretends" to search for about 40 seconds - finds no AP nearby and switches "Off".
I have wrenched on a number of these T95Z. boxes and always seem to get them working.*
Hats off to Superceleron and his ROM -* His ROM really cleaned up the first couple of these I worked on. They had the LTM8830 chipset I think.
Then I worked on a couple newer T95Z's and that ROM didn't work. If I recall - same thing where you can try and turn the WiFi on but it just turns off. I think they turned out to have the 9377 chipset. Found a workable ROM for them and all is well.
Okay so here are some pics of the insides of this one:**https://imgur.com/a/Kd2M1Ta
I flashed a bunch of ROMs - Here is like a list of some of the file names etc:
Poison ROM - https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720
T95ZPLUS_q200_9377_customV3.2
atvXperience_v2F_s912
s912_atvXperience_v2FF
T95U PRO_S912_02012017_
v1016-EB-AGCF-LPDDR3-2G
Sorry that I didn't keep great notes on what I flashed but hey - once you start flashing - it is just so easy to try another one.*
Anyway - Several of the ROM's said they were for the AP6255 chipset and ALL of the ROM's do the same thing where the WiFi just won't turn on.*
Now I am not an expert on this - so I don't know:
Can you confirm - Is this a Sunvell?
Is the wifi chipset an AP6255?
What else should I try?* I wandered into a T95U ROM... should I wander further and look for Beelink or other manuf ROM's that show the AP6255?
Is there any other tool or APK that can be flashed after ROM install to query the hardware config or add chipset support?
Open to ideas.*
Thanks!
Click to expand...
Click to collapse
The problem is that flashing multiple ROM's can sometimes leave remnants behind and mess things up. Or, you flashed an incompatible ROM that hosed up the EEPROM. The first thing I'd suggest trying, is to go back to square one by flashing the proper stock ROM back on the device again using the USB Flash Tool and be sure to select "Force Erase All" when doing it. I've ran into the same problem on multiple occasions and flashing stock always seems to get me back up and running again.
If that doesn't work, then you'll probably need to crack it open and reset the EEPROM by shorting out the pins in order to get it into a state where it'll overwrite the incorrect code. To do that, make sure the USB Burning tool is running and the USB cable it plugged in so you know when it's been triggered. Then run a paperclip along the pins of the chip until it trips and shows back up in the tool. That will put it into programming mode so you can re-flash the ROM again completely.
Link to 2/16 STOCK FW: https://mega.nz/#F!YJ0nTC4Z!qBz6gmJCjwHn0HtlVe2apw
Link to 3/32 STOCK FW: https://goo.gl/RG92GR
Good luck!
Thanks for the reply.
I am downloading the 2G version now. I will try a force flash as suggested.
A couple of questions - when a ROM leaves remnants - what are the other symptoms? I thought that lots of problems appear when the flash is "dirty"?
Anyway - I will flash this version when Mega lets me finish the download.
If I have to move on to step two and short the eeprom - which chip in my pictures is that?
Thanks again!
AthieN said:
. . . .If that doesn't work, then you'll probably need to crack it open and reset the EEPROM by shorting out the pins in order to get it into a state where it'll overwrite the incorrect code. To do that, make sure the USB Burning tool is running and the USB cable it plugged in so you know when it's been triggered. Then run a paperclip along the pins of the chip until it trips and shows back up in the tool. That will put it into programming mode so you can re-flash the ROM again completely.
. . . .
Good luck!
Click to expand...
Click to collapse
....
Okay - well force flashed the referenced ROM and even another "Factory" ROM supposedly for the 6255 wifi chipset. No go.
They both still work it seems fine - but no wifi.
So any hints on reseting the EEPROM?
Thanks again,
wantpizza said:
....
Okay - well force flashed the referenced ROM and even another "Factory" ROM supposedly for the 6255 wifi chipset. No go.
They both still work it seems fine - but no wifi.
So any hints on reseting the EEPROM?
Thanks again,
Click to expand...
Click to collapse
Very strange. It almost sounds like your WiFi radio is malfunctioning. If that's the case, then there's really not much you'll be able to do to fix it unfortunately...
One thing you can do to verify, is to grab a file manager like FX, go into /system/etc/wifi and verify that the 6255 directory exists. If it does, then it's probably just the radio. You'll need to be rooted to do the above though. Also, grab a terminal emulator, 'su -' to root, and run a 'dmesg |grep eth' and 'dmesg |grep wifi' and see what it says. You might be able to figure some stuff out based on the output... Are you 100% sure you have the 6255 radio?
As for the EEPROM, it's pretty dangerous to do that, but if you really want to try, just do what I mentioned earlier. Crack open the device, plug it in to power and the USB, and then run a paperclip along the posts, shorting them out until the device resets and shows back up in the USB burning tool...
Okay - flashed just about as many variations I could find. I tried your trick of looking for a folder inside /system/etc/wifi and did confirm there is a directory labeled 6255 and it has some files in it. I will try to run a couple of grep commands too and post what I find. But I am starting to feel that the actual chip is faulty.
After further thought - I am not really wanting to do a dangerous step to reset an EEPROM when it might turn this from a device without wifi to a device that does nothing.
Still curious - looking at the pictures I posted to begin with - is anyone sure that the chipset is the AP6255? Does this chipset do both the cat5 and wifi networking? Or is there yet another chip that does the cat5 networking? (I know there are better words for this - just can't think of them right now)
Anyway - anyone have any other thoughts? I already explained to my friend that this one looks like a hardwire only device so I am putting it back together.
Thanks again,
You're beating a dead horse thinking some magic ROM you flash will fix it when it's clear the source of the problem is the common denominator of wifi being hosed on all of them. Especially since you said you installed roms that supported your AP6255 (as your board pic makes clear) wifi chip where everything else worked except the wifi.
You need to grep for the wifi network errors as AthieN spelled out how to do in his initial reply.
wantpizza said:
Hi again,
I have a friends T95Z and trying to fix it up. It won't connect on WiFi. When you go to network settings - WiFi is switched off. If you switch it on - it "pretends" to search for about 40 seconds - finds no AP nearby and switches "Off".
I have wrenched on a number of these T95Z. boxes and always seem to get them working.*
Hats off to Superceleron and his ROM -* His ROM really cleaned up the first couple of these I worked on. They had the LTM8830 chipset I think.
Then I worked on a couple newer T95Z's and that ROM didn't work. If I recall - same thing where you can try and turn the WiFi on but it just turns off. I think they turned out to have the 9377 chipset. Found a workable ROM for them and all is well.
Okay so here are some pics of the insides of this one:**https://imgur.com/a/Kd2M1Ta
I flashed a bunch of ROMs - Here is like a list of some of the file names etc:
Poison ROM - https://forum.xda-developers.com/an...mputers/amlogic/t95z-plus-poison-rom-t3751720
T95ZPLUS_q200_9377_customV3.2
atvXperience_v2F_s912
s912_atvXperience_v2FF
T95U PRO_S912_02012017_
v1016-EB-AGCF-LPDDR3-2G
Sorry that I didn't keep great notes on what I flashed but hey - once you start flashing - it is just so easy to try another one.*
Anyway - Several of the ROM's said they were for the AP6255 chipset and ALL of the ROM's do the same thing where the WiFi just won't turn on.*
Now I am not an expert on this - so I don't know:
Can you confirm - Is this a Sunvell?
Is the wifi chipset an AP6255?
What else should I try?* I wandered into a T95U ROM... should I wander further and look for Beelink or other manuf ROM's that show the AP6255?
Is there any other tool or APK that can be flashed after ROM install to query the hardware config or add chipset support?
Open to ideas.*
Thanks!
Click to expand...
Click to collapse
Thanks for the other hint on running the grep command.
I tried and tried to copy this a better way - but short of retyping word for word - a picture was the best I could do.
https://imgur.com/a/oZxojmU
I don't read many reports from a grep command but it is interesting - on one of the lines it reports that "No power on pin 2"
Not sure if it simply is that the chip wasn't soldered in correctly?
Anyway - that is the update. Any thoughts or things to try before I give up are appreciated.
Regards,
el80ne said:
You're beating a dead horse thinking some magic ROM you flash will fix it when it's clear the source of the problem is the common denominator of wifi being hosed on all of them. Especially since you said you installed roms that supported your AP6255 (as your board pic makes clear) wifi chip where everything else worked except the wifi.
You need to grep for the wifi network errors as AthieN spelled out how to do in his initial reply.
Click to expand...
Click to collapse
Sorry - didn't read this before my post but don't worry - I am with ya. I had a suspicion from the start. But - there is lots of "Wizardry" in these forums so worth a post.
Thanks everyone.
The good news is that it looks like your kernel isn't finding the right wifi driver on boot which is why it's shutting down. That means there actually might be a ROM version out there that supports your device. But maybe it just doesn't know where to look.
The name of your modular driver is for the AP6255 is dhd.ko.
Try loading it manually from command line as root.
# modprobe dhd
See if you can find dhd.ko in your filesystem somewhere under /lib/modules.
If you can't then try and find a rom that has your wifi driver module on it called dhd.ko.
Update: Just saw there's a more updated qualcomm driver called qca9377.ko so try to load that module or see if the file qca9377.ko exists under /lib/modules.
# modprobe qca9377
wantpizza said:
Thanks for the other hint on running the grep command.
I tried and tried to copy this a better way - but short of retyping word for word - a picture was the best I could do.
https://imgur.com/a/oZxojmU
I don't read many reports from a grep command but it is interesting - on one of the lines it reports that "No power on pin 2"
Not sure if it simply is that the chip wasn't soldered in correctly?
Anyway - that is the update. Any thoughts or things to try before I give up are appreciated.
Regards,
Click to expand...
Click to collapse
Okay - well good news bad news?
I tried to load each of those other drivers
Code:
# modprobe qca9377
modprobe: can't change directory to '/system/lib/modules': No such file or directory
# modprobe dhd
modprobe: can't change directory to '/system/lib/modules': No such file or directory
Now I need to find some other rom that has those drivers?
Or can I just find those files and place them in that file directory? Anywhere I can just get the driver?
Thanks again,
Okay - newest update
I searched and there was no folder named 'modules' in system/lib
So I created that folder and I copied dhd.ko into that folder. (I searched for the newer qca9377 but i couldn't find it)
Now if I type modprobe dhd in terminal as su I get
Code:
#modprobe dhd
modprobe: can't open 'modules.dep': No such file or directory
Oh and - newest wrinkle - somehow I installed something that pops a durex condom ad ontop of everything about every 45 seconds. What is the easy way to find the offending apk? I tried to long click so I could find the properties or something but nothing working. The only thing open is this terminal emulator??
Anyway- that is the latest.
Thanks again,
i have the same issue did you ever resolve?
me too, anyone resolve it?
I have downloaded an android 13 GSI on my infinix zero 8i and after installing magisk the wifi and bluetooth completely stopped and I figured the reason is the driver got wiped some how since when I try to view the certificate for the WiFi or Bluetooth it gives me unavailable, I got a stock rom on my PC and its got a file called md1img.img and I am pretty sure it is the modem driver because on the product info txt file in the firmware file it says modem a couple times under md1img, I tried to flash it by typing fastboot flash md1img md1img.img and I keep getting the error that the directory does not exist, how do I flash the driver?
also the UI becomes really slow sometimes after the device has been on for a little, its not that important but is there a fix for that too?
also also not so important, the camera notch is obstructing a lot of the notifications and time, is there a fix for that?
PS. I do not want to flash the stock ROM I have already wasted an entire weekend trying to get the GSI installed so please don't suggest that
PS PS. I understand close to nothing on the subject matter so if you have a soloution please type it out step by step so I don't brick my phone again.