Develop Bugs

WiFi - bcm4329.ko file?

Hey I have a desire Z and my logcat says that the Wifi driver isnt loading. I want to replace it with one that works so my wifi actually turns on.
If you have a bcm4329.ko for the desire z could you please let me know?
Thanks

Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?

KCRic said:
Isn't that file subject to the kernel you're running? Or are you stock and just looking for the stock bcm file also?
Click to expand...
Click to collapse
Yeah I think it is normally part of a kernel but I cant seem to get this damn wifi to work no matter what I do, so I was thinking if anyone had one of the files kicking around I would just ADB overwrite the old one and see if it works.

Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.

theSpam said:
Try flashing one of the kernels in my signature -- they both include a corresponding WiFi driver.
Click to expand...
Click to collapse
Still doesn't work
Really have no more ideas to fix my wifi.

you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one

ilostchild said:
you can always jus download a rom and go to the folder where its located and take it out and push it in your phone instead of waiting for some one
Click to expand...
Click to collapse
I tried that too and it didn't do anything. Im really pulling at straws. Is there a program to test to make sure the hardware is actually good?

Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,

ilostchild said:
Im sure you done this already but some one is bound to ask, so ask now.
have you tried to wipe
and reflash the rom your using and try it again,
Click to expand...
Click to collapse
Yep, tried that twice. I even went back to stock between the reload.
One time I flashed it using the PC10IMG method and the other I used Clockwork (rom manager).
I really have no idea where to go at this point. I think I've exhausted all my ideas. Ive tried reflashing roms, kernels, and radios.
Was hoping someone had some diagnostic software that would test the hardware of the phone or something so at least then I would know if my actual hardware for the WiFi and Bluetooth was shot or not.
Thanks anyways.

Wow, I forgot about this thread over the weekend
Anyway, have you tried changing the permissions for the file? You can use 'fix permissions' in ROM Manager or clockwork or use Root Explorer to change the permissions. Of course if you're a terminal kind of guy you can chmod it.
Sometimes the permissions don't set correctly or, on some systems running linux, the permissions get changed for some reason. Maybe that's what's going no here, sounds like it anyway. Btw, make sure to reboot after changing the permissions because it won't work until you do.

has anyone fixed this issue where wifi stops working?

wifi not turning ON
Hello Everyone,
During the process of getting IP address from WiFi network, I received a "Error Massage" on my Alcatel OT-990. After this massage, WiFi started behaving abnormally. Sometimes it turned ON another time it did not. Now after a few weeks later, WiFi is not turning ON at all.
I have Tried following Solutions but nothing worked:
1. Did factory reset, erased system, cache etc and Flashed different ROMs (JB ot 990, ICS QME, QLTsar, 2.3.4, Telenor One touch 4.0.04) using Recovery many a times(From different Sources).>>Problem not solved
2. Updated my phone using alcatel update manager to 2.3.4>>> Problem not solved
3. Tried by changing permissions of BCM4329.KO, wpa_supplicant.confg etc every file related to wifi/wlan>>Problem not solved
4. Used WiFix Manager>>>Problem not solved.
Bluetooth and FM radio working all right.
If anybody knows about its solution ..please help me out.

A100 Build Prop Issue

Hello,
I have searched and haven't found anything to assist. I am assisting my buddy with his A100 to make it useful again instead of a paperweight. He heard rumors you can edit the build.prop without rooting the device so it will act like a A500 to play other games. He used Astro File Manager and another File Manager program and edited the build.prop, but now his device is not booting up correctly. It gets stuck at the loading screen.
Anyone have any way of helping. I dont own a A100 and I tried a hard reset.
Also, dumb question, but can others verify this will not work without rooting the device...obviously this one time of bricking the device is not enough to convince otherwise.
Thank you for your help.

no you need root access to modify the build.prop
whatever he changed it wasnt good lol.
your best bet is to put one of the update zips of the ics leaks on his sdcard and flash it by holding "vol down & power"
volume down is the left most volume rocker while holding the device in landscape with home button on the right. (volume up if your holding it portrait)
best of luck !
the build.prop resides in /system which without root you cannot access..
Sent from my SGH-I897 using xda premium

thank you
Thank you for the info ptesmoke.
I knew you had to root the item first, but he did it anyway. I will help with this tonight and see how it goes. I found the ICS software within the forum, so lets see if this works.
I think I also found the root information as well, so going to see if works to change his build.prop. If not, i will continue to do more research through this forum.
Again, thanks for the information.

tbuser said:
Thank you for the info ptesmoke.
I knew you had to root the item first, but he did it anyway. I will help with this tonight and see how it goes. I found the ICS software within the forum, so lets see if this works.
I think I also found the root information as well, so going to see if works to change his build.prop. If not, i will continue to do more research through this forum.
Again, thanks for the information.
Click to expand...
Click to collapse
Keep in mind that even with root access and a build.prop not configured properly will still result in a bootloop. Also, the build.prop could not have been edited without root access.

[Q] How To Add Root How A Custom Rom?

Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!

ik4evr said:
Hello Everyone,
I'm ik4evr. (Making the SM-T520 rom) =)
Anyway, i'm trying to add root to my custom rom. However, every time I do it using the kitchen, and flash the rom and try to open SuperSU it says binary not installed. I tried manually putting the root files in my room too. Can anyone out there help me with this. Thanks!
Click to expand...
Click to collapse
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since

THEDEVIOUS1 said:
welcome to my world...it took me about a week of research before i found anything that helped & dont even remember where i read it at now. Long story short....there seems to be an issue with the binaries that the kitchen uses so in the end i finally just copied the su/busybox/init.d files from cleanrom for the T320 & havent had a problem since
Click to expand...
Click to collapse
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?

ik4evr said:
Thanks for the reply. Unfortunately, that didn't work still =(
Anything else?
Click to expand...
Click to collapse
If that didnt work then it might be your updater-script...once again just copy the one from a known working deice with an exynos cpu & 4.4.2 (N9000 MAYBE?) then u should be ok. Also...did u swap the daemonsu file in xbin as well? Another thing...delete the su located in "bin" & make sure its in "xbin". The last thing i can think of...did u unpack the boot.img & change the value in the dfault.prop to make it non-secure?
edit: I was just thinking...i noticed u said "supersu" but every guide ive seen added "superuser" instead so swap that too. U should be able to include either but mine didnt work either until i switched them although it could have been coincidence since i also made all of the rest of the alterations around the same time...if u notice in my thread i told users to go download supersu AFTER they flash just to be safe but now that i have it working i'll probably try changing apps again for the next version to eliminate a step

where do I dl twrp for tab pro 10.1 wifi?
I only see 10.1 tab pro lte ...not wifi?
Thanks

[Q] Slightly messed up my firmware

Hello there,
I'm very new, so apologies if I'm posting in the wrong forum, or if there's a more appropriate place for this quesion!
Here's the thing... In an attempt to root my Sony Xperia C1905, I was trying to revert my firmware to a previous version of Android (4.2, I think). Anyway, something happened and things didn't work out, so I re-flashed it with a version of 4.3 that I downloaded from somewhere (I don't know where, but the default language was set to German!)... Thing is, when I turn my phone on, I get stuck in a boot-loop (pretty Xperia colous) for about 3-5 minutes until it gets to the main screen.
I have tried things like using the Sony PC Companion to repair it, but to no avail. Is there some other way I can fix this, or revert it to its original firmware, without this stupid boot-loop?
Thanks for reading!

TheStudent said:
Hello there,
I'm very new, so apologies if I'm posting in the wrong forum, or if there's a more appropriate place for this quesion!
Here's the thing... In an attempt to root my Sony Xperia C1905, I was trying to revert my firmware to a previous version of Android (4.2, I think). Anyway, something happened and things didn't work out, so I re-flashed it with a version of 4.3 that I downloaded from somewhere (I don't know where, but the default language was set to German!)... Thing is, when I turn my phone on, I get stuck in a boot-loop (pretty Xperia colous) for about 3-5 minutes until it gets to the main screen.
I have tried things like using the Sony PC Companion to repair it, but to no avail. Is there some other way I can fix this, or revert it to its original firmware, without this stupid boot-loop?
Thanks for reading!
Click to expand...
Click to collapse
Please refer to this thread as it will tell you how to flash .ftf files manually. Also, make sure that you tick wipe data and wipe cache. This is probably the source of your bootloop problems. Have a good day, feel free to PM me if you need more help.

Wait, buddy i might be wrong here but did you say that it goes to the min screen after the bootanimation ( pretty colours). If so, then that isnt a bootloop. A bootloop is when your phone stays on that bootanimation and never loads up, it's also called a soft brick. As gamer649 above me said, you might wanna check out that thread to know how to flash ftfs manually.

Thank you both so much for responding so quickly! I shall indeed check out that thread posted by gamer649 and hope that solves the problem (If not I shall report back.)
Thanks again!

paper13579 said:
Wait, buddy i might be wrong here but did you say that it goes to the min screen after the bootanimation ( pretty colours). If so, then that isnt a bootloop. A bootloop is when your phone stays on that bootanimation and never loads up, it's also called a soft brick. As gamer649 above me said, you might wanna check out that thread to know how to flash ftfs manually.
Click to expand...
Click to collapse
Ah yeah, you're right, it's not a boot-loop in that case because it does indeed load up after a while, my mistake!

Professional help

Ok let me be really specific i have flashed stock firmware through odin, i have done clean wipes, i have done every possible thing in my power but still experience horrible tablet preformance i get app stops and restarts everytime even after i have flashed on odin no one here has been able to help me they tell me to do the same thing over and over download stock firmware and flash, do a clean wipe iv'e done it all please help i know someone can i think its a file in the screenshots i enclosed that is corrupted but i have no idea which one is it. its not the system or the kernel it is something deeper please help i am begging you developers

k,
no offense, but your post is wildly disrespectful. [frowny face]
you are basically putting the proper ownership of your error off on others.
to be fair, in your ignorance you flashed a firmware without first doing some research on the topic.
a noobish mistake, it happens, i've done it.
there were plenty of threads created prior to your experience warning of new samsung releases
overwriting bootloaders and how to navigate the issue.
from my interaction with you, i think i am accurate in saying you did not do the aforementioned research.
i for one took time to describe a way to "fix" your issue. You chose not to attempt it, which is fair. It is risky.
Cool.
However, lots of the users you've interacted with on xda have a fair to expert handle on how to get things done.
they do what they can to help, they cannot be expected to compensate for another's impatience, lack of attention
to detail and/or incompetence/ineptitude.
m

What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago

kgalv419 said:
What are you talking about i am not blaming a single soul for anything, i have been flashing roms and firmwares for years now. Somehow something went wrong and i am asking for help. I flashed the official firmware from sammobile for the sm t210r i booted into stock recovery and factory reset. And still i get the same results don't take pleading for direspect i am just frustrated not with anyone but with the tablet believe me it wasn't like this a month ago
Click to expand...
Click to collapse
hmm,
okay, different approach.
http://m.youtube.com/watch?v=JmvCpR45LKA
just a refresher.
now,
screenshots of directories are next to useless.
what's needed is , at the very least a logcat.
to get that or anything else moving you need,
custom recovery installed.
root.
busybox.
adb setup properly on pc.
the ability to describe you problem in words other than my thing doesn't work.
the sense not to keep creating thread after thread concerning the same issue.
if you are that insistent on undoing what you have done, my previous suggestion to you is probably the best bet.
if you want "Professional" help then seek a repair service.
Savvy?
m

Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer

kgalv419 said:
Gee thanks for the video very eye opening. Will post a logcat then i have all the things u mentioned recovery,adb etc all i require is clear steps to follow into fixing this lil issue and i will b a happy camper. N yes bro i savy don't be so serious i can see that your an intellectual an i respect that and apreciate any help u can offer
Click to expand...
Click to collapse
k,
okay, cool. sorry for being so rough on you.
i am downloading a copy of 4.4.2 firmware though linking me to the firmware
you initially flashed would be good.
what would be better is if you still have the firmware file crack it open with 7zip and get me a list
of the files [.img, .bin] inside.
run logcat after you boot up. attach to post as text file
then run your routine to where you get your issue, fc's etc and run logcat again and post as text [2]
m
okay it looks like i am not going to be downloading the 4.4.2 firmware.
downloads break from the one source i found
and i have no interest in joining the other site. that's bull****.
so if you can get me the list of files contained in the realease that would be helpful.

OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.

kgalv419 said:
OK bro I narrowed it down to it not being a ROM or firmware issue here is my log, the firmware that I flashed was from sammobile its a tar file and 7zip can't open it. Currently i am on tranchikat 1.8 the " unfortunately app stops" still persist its not really force closes its stops hope you can deduce something off the log and again thanks very much bro it doesnt matter how long it takes.
Click to expand...
Click to collapse
k,
dude, where's my car ? [log ?] :silly:
m

Here bro

kgalv419 said:
Here bro
Click to expand...
Click to collapse
k,
i am going to guess you are trying to run a battery/governor tweaker ?
i am going to guess when you type getenforce in terminal
your output will be enforcing.
i am guessing when you resend your logcat you will do so after
typing su
and then
logcat -d > /sdcard/logcat.txt
if my guesses as to the app and selinux are correct you;
a- need to let the app go into the dustbin of history
b- need to look for a tutorial on dumping/unpacking/customizing/repacking/reflashing your boot.img
in order to disable selinux and make it stick.
if my guesses are wrong it is because;
the log you posted is super-lame [sorry] use your terminal, not a catlog app.
you have yet to tell me what app are giving you your headache. in which event is an issue between you
and the app's developer.
lastly you should be question the developer of the rom.
m

Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.

kgalv419 said:
Bro its not any specific app I'll give you an example. Say I am going to settings doing whatever all of a sudden boom "unfortunately settings have stopped". Say I am on my browser browsing a way I go to my bookmarks boom " unfortunately internet has stop". It does it randomly not evrytime but at random "unfortunately touchwiz has stopped" etc the apps will close an I can start them again and they will run normally until another random stop. I have tried all costom Roms on here and still have the issue so I know its not a ROM problem, I have flashed my stock firmware both 4.1.2 and 4.4.2 and it persist so that rules out it being those either. But I will do what u said and use terminal to get the log. So far what I can tell its not the apps nor the ROM nor the kernel that is causing the stops and random reboots.
Click to expand...
Click to collapse
k,
okay, this ---> android.permission.INTERACT_ACROSS_USERS_FULL is the ballbuster.
it's connected to , from what i've read so far , a maybe faulty root and multiuser.
what version supersu are you using ? unroot and then reroot trying from version 1.97 maybe to 1.99.
kill multiuser and clear out any suspect accounts in settings. will post back if i find something more conclusive.
you can jump in as well by searching the error i mentioned.
android.permission.INTERACT_ACROSS_USERS_FULL
m
@kgalv419
edit after rooting set actions to auto grant permission and trust system
EDIT - disable xposed modules - xprivacy if you're running it.
QUESTION - THIS IS A JELLYBEAN ROM ? seems to be a jellybean issue...
EDIT-EDIT i found this... http://forum.xda-developers.com/gal...card-app-data-to-extsdcard-tw-t2178863/page16
read that page looking specifically at the portion concerning /system/etc/permissions/platform.xml
you may need to add/edit the line for
android.permission.INTERACT_ACROSS_USERS_FULL
with the proper uid [user identification] meaning the right number/symbol for root,shell,ewok, etc.
the entry looks something like this;
<assign-permission name="android.permission.INTERACT_ACROSS_USERS_FULL" uid="shell" />
and remember to reset the file's permissions correctly - 644

Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.

kgalv419 said:
Nah it happens on both jellybean and KitKat for me I don't think its the root because when I flash the official samsung firmware through Odin it is basically unrooted and the problems persist
iI tell you when it first started. I was on jellybean then the kitkat update for the sm-t210r came out, I flashed it via Odin and from then it started
So naturally I downgraded back to jellybean but the issue it stayed, so that's basically the history of the random app stops and random reboots.
Click to expand...
Click to collapse
In a situation like this thinking is guessing = no good.
re-read previous post. search, test, verify. Don't guess [think].
m

Yes bro trust me I'm trying

Are you able to flash CWM and root your device ?
I will advise what is next to be done....
Sent from my SM-T211 using XDA Free mobile app

Yes I already have it rooted with philz touch recovery

Wipe format every single partition that you see remove 1st your ext sd card this will empty all folders then redo tne Odin part
Sent from my SM-T211 using XDA Free mobile app

By every single partition you mean including those folders like acc, and others in the device?