Mediatek wifi driver NVRAM WARNING: Err - 0x01 - Android Q&A, Help & Troubleshooting

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.

Related

A13 Boxchip CM9/CM10 Development

I now know the Allwinner A13 is a stripped down version of the Allwinner A10, to be clearer the specifications of my Tablet (from UniFlash and AnTuTu Benchmark) are as follows:
Manufacturer: None
Brand: softwinners
CPU hardware: sun5i
CPU model: ARMv7 Processor (VFPv3, NEON)
CPU frequency: 60.0 ~ 1008.0 MHz
Screen resolution: 800 x 444
GPU vendor: Mali-400 MP
GPU version (OpenGL): OpenGL ES 2.0
RAM size: 512 MB DDR2 RAM
Knowing this, I used UniFlash to make a backup of the firmware bt after using UniFlash to try and load a CM9 Rom on to the Tablet, the Tablet died. After alot of googling I discovered AllWinner based chipsets use Live Suite (sometimes called LiveSuit) to flash firmwares on to the device.
To Flash firmware on to the device you need to follow the attached instructions ((http://dragondevs.com/viewtopic.php?f=159&t=390):
Download LiveSuite (http://www.softpedia.com/get/System/System-Miscellaneous/Live-Suit-Pack.shtml)
Install Live Suite
Start Live Suite
Select the Live Suite image file (folder icon
Turn device off (to be sure hold power button for 12 - 20 seconds)
Hold "Volume Up" button down
Connect the device to your PC (while still holding "Volume Up" down)
Start pressing the power button (you may need to do this once a second for 5/6 seconds)
If you haven't installed windows will ask to install a driver for a device (Dive Id will be something like Vf73465789123465435_Id, if the device is in the right mode, A13-MID, ADB-Interface indicates the tablet has connected in anouther mode).
Once this has finished LiveSuite will detect the device and a wizard will flash the firmware for you.
I have found a working firmware which according to AnTuTU Benchmark gives my tablet a rating of 3047 (see firmware section), this is on the higher end of reported A13-MID tablets
I have found out how to install CWM on to the device via SaussageMod (http://www.slatedroid.com/topic/29916-scriptmod-for-allwinner-a1x-platforms/). This solution is untested, further more it may be unnessary futher investigation has shown this website (https://www.miniand.com/forums/forums/2/topics/73) has developed a way of create Live Suite images. This is simplier than installing clockworkmod recovery,
I tried to load the following images on to my tablet and failed completely: http://forum.xda-developers.com/showthread.php?p=31043317 It didn't work and forced me to do a firmware refresh.
My other step for the day was to create Ubuntu 10.10 installation then I began following this guide to construct an Xperia Play CM9 Rom/Kernel. once I have created a working ROM (I own an Xperia Play). I'm hoping to be able to modify the kernel to include the relevent A13 drivers, but one step at a time.
TODO
Create Ubuntu Partition
Follow Xperia Play CM9 Rom/Kernel Guide and create working rom (test on my Xperia Play)
Download CT repository (https://github.com/christiantroy) and compare with Xperia Play CM9 rom
Find the relevent drivers from https://github.com/amery/linux-allwinner leaked source
Retrieve offical MALI 400 MP drivers (parts of it have been released) compare with leaked source
Use UniFlash backup of original Rom along with LiveSuite image creation to try and restore original firmware (see If I understand it properly)
Examine Build.prop find out why original firmware displayed ina phone layout and new one is in tablet mode (potentially reference CM supported Tablets).
Attempt to compile a A13 (Sun5i) based rom
Create a google code page to hold all of these thoughts properly.
Left blank will include rom/firmwares here for future reference
Firmware
https://www.dropbox.com/sh/bzjt7mzuftwz79f/nt7mRMPDj1 - My public Dropbox
http://www.azhuo.net/en/products_A13B_Allwinner-A13_7_inch_Android_4.0_Upgrade.html - password is: tabletpc
http://dragondevs.com/viewtopic.php?f=159&t=390 - McPad F1 firmware
Novo 7 Tools
https://dl.dropbox.com/u/74970692/Novotools_v1.0.apk
SausageMod
http://www.slatedroid.com/topic/29916-scriptmod-for-allwinner-a1x-platforms
Gapps - http://goo.im/gapps/
I have the same tablet and it would be very cool if you succeeded in your attempt to create a CM9 rom for it. I tried ROM made by Tragidy from this thread but there is a problem with touchscreen driver, ROM booted successfully but I could not even unlock the screen cause touchscreen did not work. I finaly flashed rom DCPAD2121.zip using livesuite which I belive is the original ROM that came with tablet and it worked.
I installed clockwordmod using sausagemod successfully, but there is a big problem - no hardware "back" key and only volume up works.
novo7tools.apk works OK for reboot, reboot to recovery or shutdown.
syncing
Thanks, it's slow going at the moment, I only spending ~1 hour each day on it and at the moment trying to sync the CM9 source is painful (it keeps timing out, due to "remote side corruption").
I figure I would start there as all the firmware images I can find are ICS roms (meaning the drivers must be ICS).
Hi, I have the same tablet but I cannot find the firwmare DCPAD2121.zip
Could you upload it please? From dropbox has been deleted
Thanks
You should check this topic:
http://forum.xda-developers.com/showthread.php?t=1861445
WillingMagic said:
You should check this topic:
http://forum.xda-developers.com/showthread.php?t=1861445
Click to expand...
Click to collapse
I tried that ROM, on my tablet after flashing the ROM it got stuck in a boot loop. It might be an idea to steal the config he created. The ROM is pre CM9 release. The A10 Flash kitchen software seems to work. I was hoping on producing a complete Live Suit image that people could flash (figuring our what CT has done on the A10 took a while).
Still having fun trying to sync the repositories, given up on trying to use a Debian VM, I'll will install full Ubuntu on a drive tomorrow, hopefully that will help fix things. It doesn't help most of the guides I can find are out of date and I keep having to make corrections.
I've also uploading all firmware I can find to my dropbox (at 200mb each they will take a while), I won't with tools simply because others ask you not too.
The Dropbox firmware was out of date when I tried to download it sun5i_android_a13-pfdq88_en_D06 firmware worked well for me, the firmwares are located at: https://www.dropbox.com/sh/bzjt7mzuftwz79f/nt7mRMPDj1
Cyanogenmod 9 in not working for you. Did you made data and cache wipe? Can you send me logcat and dmesg output?
You can`t steal my config, you have to remember about credits, and other stuff.
Creating a wiki is useless, there is already wiki for allwinner products, so better update info on it.
Github is better than google code to keep sources.
Using Livesuit=Windows, I hate dual booting just for flashing, Clockwork Recovery or modified SDcard with uboot is better solution.
Current kernel is not working well, with sun5i.
Using VM is stupid, because building rom takes a lot of time on quad core pc without it.
WillingMagic said:
Cyanogenmod 9 in not working for you. Did you made data and cache wipe? Can you send me logcat and dmesg output?
You can`t steal my config, you have to remember about credits, and other stuff.
Creating a wiki is useless, there is already wiki for allwinner products, so better update info on it.
Github is better than google code to keep sources.
Using Livesuit=Windows, I hate dual booting just for flashing, Clockwork Recovery or modified SDcard with uboot is better solution.
Current kernel is not working well, with sun5i.
Using VM is stupid, because building rom takes a lot of time on quad core pc without it.
Click to expand...
Click to collapse
I wiped the caches I couldn't send a logcat or dmesg as the device simply boot looped.
I've been providing links to threads whenever I come across others work, I'm new to android rom development for me this is a research effort which will hopefully produce something cool for my £50 tablet. Basically my day job has switched to developing UI's and I am looking for something new to learn (instead of why is Vaadin, Guice, SWT, Javascript, etc... is putting that button there).
Said dev career has also made me hate Git with a passion (not as bad as perforce but still) since Git integrates poorly with Visual Studio and Eclipse and you end up getting everyone overwriting each others changes. The idea of google code is simply because it makes a good platform for projects and you can use things like git with it. I didn't know about an Allwinner wiki, with all of my Googling I haven't come across it, where is it?
I don't care about build times I'm just researching, alas Debian has caused me enough problems so I've installed ubuntu on to a old disk I had lying around. Considering I've just tried to install Ubuntu via a Net install CD and it has screwed up the GRUB installation (nicely taking out my windows partition as well) can you blame me?
The reason for nabbing the config (and the Xperia Play and Christian Troys) is to understand how they work. Over the years I've found most Open Source software documentation is poor unless you have a set level of knowledge about it already.
Lastly I like automation, I want things to just work. Livesuit does that since I am normally a windows user, I as hoping in the distant future once I understand the build process to set up a Jenkins server to do it and create the whole lot automatically (via the Allwinner flash kitchen). In the even longer term I would like to update FlashTool to do what LiveSuit does. In the near term (next couple of months) I just want to be able to build a CM9 image.
All android and kernel source are keep on git, so changing it is stupid.
This is allwinner wiki: http://rhombus-tech.net/allwinner_a10 you can also update http://elinux.org/Hack_A10_devices
Everyone use CWM and it's standard for unofficial firmware/ROMS
brandonlee2 said:
Hi, I have the same tablet but I cannot find the firwmare DCPAD2121.zip
Could you upload it please? From dropbox has been deleted
Thanks
Click to expand...
Click to collapse
Here's my upload, I packed it in rar format: http://www.mediafire.com/?we4zhgop29bg3dj
I also found it here: https://docs.google.com/open?id=0BzQuMwoMQqvba1VtQ1p1ZWJkR2M
from this forum post: http://www.slatedroid.com/topic/35314-a13-generic-tablet/page__view__findpost__p__421128
I built a CM10 rom for A13 from sources. It boots fine but hangs either at the Android setup wizard or sometimes even at the CM animation.
myfluxi said:
I built a CM10 rom for A13 from sources. It boots fine but hangs either at the Android setup wizard or sometimes even at the CM animation.
Click to expand...
Click to collapse
Mind sharing your repo ?
Trying 4.1.2
Hi all,
So I've tried compiling from 4.1.2 source for my A13 Emgeton Consul 3
It boots up and gets to the CM10 boot animation but it doesn't get past it.
I can adb at first boot until adb stops.
logcat from boot attempt:
http://pastebin.com/gLTrieHm
My build.prop:
http://pastebin.com/Ap9M1tjW
Any pointers as to why it doesn't get past the boot animation?
Hello guys! I know it's not he proper place here to pose my question, but I am definitely at loss!
Do you happen to know if there is a way of rooting this tablet? And if so, does everything work properly after that?
phoivos86 said:
Hello guys! I know it's not he proper place here to pose my question, but I am definitely at loss!
Do you happen to know if there is a way of rooting this tablet? And if so, does everything work properly after that?
Click to expand...
Click to collapse
Mine came pre-rooted.
Just received my MID A13 Tablet. Is this thread dead?
koodiifin said:
Just received my MID A13 Tablet. Is this thread dead?
Click to expand...
Click to collapse
I've gone a bit quiet on the development front, setting up a file/media server & samba domain server to power my home network is eating up my time.
My dropbox contains every image I could find for the tablet, as mentioned previously you can root the device using saussage mod, although my device and every one of those images is already rooted. You can prove this by installing super user.
Sassage mod's clockworkmod recovery doesn't work for me and I was looking at the backup tool in order to generate my own one. If you are aimed at any development, let me know and I will update the main thread
Many have said that they have "lost" "forget" to take backup from original rom. So, i'd like to have backup from my original to go back if/when something goes wrong. How do i do that? What software i need. Do i need to root?
This is from my info sheet:
Model TWD_MID
android version 6.0.1 ?????
Baseband 1.5
Kernel 3.0.8+
Buildnumber: nuclear_evb-eng6.0.1 IMM76D 20120917 test keys
I am in a desperate need for some help:
My tablets specs are these:
Phone model: A13-MID
Brand: softwinners
CPU hardware: sun5i
CPU model: ARMv7 Processor (VFPv3.NEON)
CPU frequency: 60.0 - 1008.0 MHz
Screen Resolution: 800 x 444
GPU vendor: ARM
GPU render: Mali-400 MP
GPU version (OpenGL): OpenGL ES 2.0
Memory size: 353.5 MB
Android version: 4.0.4
Build number: nuclear_pfdq88c-eng 4.0.4 IMM76D 20120821 test-keys
Kernel: Linux version 3.0.8+
I just installed OpenVPN installer and installed the OpenVPN binary in the system/xbin
After that I tried to connect to my university's VPN but when it tried to connect, the tablet lost wifi connection and ever since it doesnt connect to any available wifi network!! I manually deleted the OpenVPN binary, but problem remains!
Do you know where could I find the stock ROM for this tablet in order to re-flash it?
Do you have any other proposals? Anything will help!
Thank you very much!!

device wasn't rooted and not set into usb debbug, I rescued .img files from another.

Well here I have a wonderful problem, I have two devices, according to the working one and the cpu z:
4x ARM cortex A9 @1.42 ghz
revision r3p0
Rockchip RK3066
Model rk3188
Manufacturer Zowee
Android version 4.4.2
bootloader unknown
java vm Dalvik 1.6.0
kernel 3.0.36+ (eng.candy.20150403.110733)
The device that has the problem is the exact same model and all, however, after plugging it to the AC current, it tries to boot up but enters into recovery mode, none of the options work at all, looking into youtube I found out that I can extract the firmware, so far so good, but, I can't use that method because RKROMDUMPER and RKAndroid_v1.29 need the tablet to be plugged and there is the problem, the faulty tablet does not load in that mode while plugged to the computer.
So I was left with the option of getting into recovery mode and attempt to update from external storage, so far the only "Firmware" or "ROM" I've got is the one I extracted from the working tablet, I have, backup.img, boot.img, kernel.img and so on, the biggest one is the system.img which is near 6GB size.
I really don't know how to proceed from this point, do I have anything usable with those .img files? I have tried downloading a 4.4 Android rom, the recovery tried to load the files contained in the zip folder yet the loader showed messages such as, bad footer, or invalid image or always a denial message of whatever sort you may imagine.
So, I am stuck, reading further more I discovered that there are other methods or even other roms that can be loaded, but the Zowee guys have near to nothing to work with.
Could you please help me with this? Are the .img parts usable or in some way "joinable" like merge them into a single file or directory?
The device was not rooted, so I am left with only the chance of fresh installing from sd card and nothing else.
Thanks in advance.

TVpad2

I have a chinese TVpad2 mini-pc running on custom linux (factory OS) with busybox.
I want to install Android or anything other than the factory OS but there's a lot of problems with this device:
-Filesystem is CRAMFS
-Can only access as root through telnet
-Can't access bootloader or put into FWDN (no info how this is done for this device)
What I have:
-Firmware update that contains the kernel
-Telnet root access
-Physical access to device (USB flashdrive only)
There is a forum dedicated to TVpad but they are also having trouble installing an OS on tvpad2...
What do I need to know that will help me accomplish this?
thanks
TVpad3
Hi,
I actually have TVpad3 which is very similar to your TVpad2, and Im very keen on having Android developed for these TVpads.
Theres probably thousands of these wasted devices around the world after the TVpad pirate network got shutdown.
Ive searched high and low, and so far have Not found any trace of any custom Android development anywhere.
So hopefully we can kick start something here !
This is what I know so far ....
Since the devices run on highly stripped-down Android OS, we know these devices can run android and should be a potential for custom Android development.
Unfortunately theres little hardware or development info out there for these devices.
But as far as I know, the hardware platform for these models are all based on Telechip TCC89xx chips.
https://www.telechips.com/eng/Product/consumer_pro13.asp
I have a TVpad3 personally, which I believe is based on a Telechips TCC8925.
Ive found that there are a few similar devices out there based on this platform, including the Pandawill CX-01 TV sticks which have very similar specs to TVpad3 (512mb RAM, 4gb Flash).
So we definitely know that the TVpad's hardware is capable of running full blown Android !
http://www.cnx-software.com/2012/06...v-box-powered-by-telechips-tcc8923-cortex-a5/
http://www.slatedroid.com/topic/36988-cx-01-cortex-a5/
Telechips has released platform sources here, with the latest being Android KitKat... its a bit old but could have potential for a starting point...
https://www.telechips.com/technical_support/kor/opensource/opensource_list.asp
I havent found anything about booting these devices into Recovery or ADB.
But there seems to be some mention of a "FWDN" mode here:
http://freaktab.com/forum/tv-player-support/other-tv-players/4695-cx-01-information-by-tatubias
http://tvpadtalk.ca/discussion/506/how-to-unbrick-your-tvpad1
http://androtab.info/arm/telechips/how-to-update/
http://auswitch.xyz/2012/08/16/how-to-upgrade-firmware-for-cx-01-mini-pc/
From what I can gather, FWDN works in conjunction with a Windows-based utility used to flash firmware over a USB cable.
And this poses the biggest problem for TVpads, they DONT have any peripheral USB port !
I've pulled my TVpad3 apart, and found what appears to be provision for a USB header, but im not sure if these are functional even if a USB socket was soldered in ?
If we can get a functional USB peripheral port working, then that would lead us to the Second problem, that is, HOW to activate FWDN mode on the TVpad ?
From what I can gather, different Telechip TCC89xx based devices seem to have different ways to enter FWDN mode.
Some devices require a certain key combo to be pressed during power up, while others need a hidden button pressed or certain pins on the circuit board to be shorted.
So before we can even think about developing Android, we need to figure out those two issues...
1 - USB connectivity, so that we can flash it with FWDN tool.
2 - How to enter FWDN mode, so that the FWDN tool can talk to the TVpad.
If we can overcome these two issues, then we can start building sources.
Or even flash ROMs from similar Telechip TCC89xx based devices.
Anyway, I hope this helps anyone out there.
And I hope we can really make some progress here
.
Unfortunately I've hard-bricked my TVpad2 playing around with fdisk command in telnet. I found out that if you repartition and then copied all the data back, changes will be persistent so you can store whatever onto the NAND flash. Just don't delete the partition containing linux which I idiotically did... oh well.
Anyway there's a command utility "tccbox" with various tools one of them having the ability to update firmware. Hopefully TVpad3 has it as well?
Sorry to hear you bricked your TVpad !
I guess your only way back is to FWDN flash it.
I wasnt even aware the TVpads had telnet enabled.
But that "tccbox" utility sounds very interesting.
I wonder if we can use it to flash firmwares from other TeleChips based devices ???
.... such as the Pandawill CX-01 TV sticks.
wildchill said:
Sorry to hear you bricked your TVpad !
I guess your only way back is to FWDN flash it.
I wasnt even aware the TVpads had telnet enabled.
But that "tccbox" utility sounds very interesting.
I wonder if we can use it to flash firmwares from other TeleChips based devices ???
.... such as the Pandawill CX-01 TV sticks.
Click to expand...
Click to collapse
Hi i have found my old TVpad3 but no working now, i want flash it for use to android device, you have any tutorial for this PLS
TY

T95Z Plus - with AP6255 WiFi Troubles

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?

WiFi and Bluetooth don't work anymore.

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.

Categories

Resources