I opened this thread, because i had continous problem about LEAP driver on Jelly Bean (Samsung Galaxy S2).
I use WiFi in my work, and needs LEAP authentication.
The authentication software is LEAP WIFI Free.
Sympthom:
When i tried to connect to network it says Authentication Error.
The first leaked JB rom was xxLSJ for my beloved SII, and the leap was working like charm.
When i installed the first official JB rom, the authentication error occured.
I started to read whats happening, and the guilty one was the wifi driver error/bug(?!?!), so i replaced the wifi driver from leaked xxLSJ rom, and it was WORKING!
So every time when i change JB rom (doesnt matter how new it is), the wifi driver as leap connection not working properly, and i replace wifi driver (all files in directory wifi) manualy, and taraaaaam its working again. I use this method from the release of first Jelly Bean ROM
Couple of months ago, i tried exactly witch file(s) is the problem, and it is just one and only, the system\etc\wifi\bcmdhd_sta.bin
Enough of words... i made a flashable zip to replace the incorrect file, and Leap must working again!
I use it about almost a year without problem, but, flash/replace only it any Stock JB 4.1.2 rom, and always make nandroid backup!!!!!!! i am not responsible of any damage!!!!!
For manual install:
extract the system\etc\wifi\bcmdhd_sta.bin file from zip, and overwrite the file in your rom via root explorer.
If it was helpful to You, respond here in this thread to get notificaton.
Additional note only for Samsung Galaxy S3 users:
I changed my phone to S3, and the same error occured. I tried many many drivers, but only one(!!!) of them was working! To be honest i dont know from which ROM were i extracted that file, because there was many (10+)
For Samsung Galaxy S3 users ONLY with stock or custom rom based on leaked v4.2.2! the problem file is bcmdhd_sta.bin_b2! you can DL and replace.
https://android.googlecode.com/issu...ken=6Rxyg7sWrrOJ06I-1rBSjAPniz4:1388648928646
dont forget to set permissions and LEAP working again!
If you use v4.3 stock or custrom rom, you dont need Leap Wifi Free anymore, leap connection already included in the rom (just select leap when connecting).
Gonna try this monday, hope it will fix the Authentication errors when even not using Leap? :fingers-crossed:
empulse92 said:
Gonna try this monday, hope it will fix the Authentication errors when even not using Leap? :fingers-crossed:
Click to expand...
Click to collapse
:good:
I am only tested with Leap Wifi Free app, but who knows...please feedback here if it is working! Cheers
Related
Hello to all,
I've been looking on this forum, searched for everything I wanted, and always get an answer, but this time I need to ask some experts here. As the title says the gps don;t want to get fix even on clear sky and without any building around. I used many programs one of it is "gps status" where are shown 0/11 fix, basicaly there are 11 satelites available I believe. I have tried almost all the roms available in the development section but none of them worked, even the cm7. Used another firmware and there is fix to this. If I use the original samsung rom untouched the gps is working normaly. Please let me know what I doing wrong?
Thanks,
GPS Fix for Samsung ACE
Hi. this is a fix for the Samsung Galaxy Ace, this fix reprogram the GPS
this setting program the GPS and allows it to connect in seconds.
you must be root
to install first download the fix
copy Fix GPS ACE.zip to the SD
Reboot into recovery
Flash Fix GPS ACE.zip from recovery
Reboot your phone
GPS is always slow.
Problem not solved with the files I'm wondering if the darktremor's app2sd affects? My app and dalvik cache are on sdext
hello
did you try different modem, this post help me much
http://forum.xda-developers.com/showthread.php?t=1289830&highlight=modem
+ +
Yep many and none working with a custom rom, right now I'm using xwks2 which was installed with official 2.3.5 and working with it, but when I flash a custom rom something is wrong, have no clue what I think I will stick with the samsung rom
Allright instaled now on oficial samsung 2.3.5 rooted, working good, if someone can explain what is wrong when changing the on other rom will be nice
thanks,
Hello
there is little I installed Cyanogen 7.1, with S5830XWKS9 firmware and gps does not work at all, the icon did not appear at all in the status bar.
Then I flashed the modem with another (DXKPD) and everything is back to normal.
here is my experience.
+ +
Hi have 7.2 and mine is not working with aura.
Sent from my GT-S5830 using Tapatalk
try fasterfix from the market.maybe it would help
Well for some reason my gps is working now, what I've done is flashing with odin a multiple file (my chose was a froyo firmware) the I flash with odin the latest ks9 one package file, working great even with cm7.2, got fix in 19 sec for me is great (also using the gps config from http://forum.xda-developers.com/showthread.php?t=1320626
Thanks
Guys before you change the base band and all try Faster fix from the market.. worked for me.. now the gps gets locked in few seconds.. really useful app.. and also I recommend maps v5.8.. most of the time other versions gave me force closes when using navigation.. Hope this helps..
my gps always shoes "your current location is temporarily unavailable"
Hi,
We have 2 Vibrant phones. 1 is on Paranoid Android 2.54 (via stock eclair, ICS Passion, Slim Bean 2.9 & 3.0) and works perfectly.
The second one was on ICS Passion for a long time and I have finally got around to (trying LOL) to update it.
Here is where the weirdness begins - Flashed PA 2.54 no problems, flashed and booted up, but no wi-fi, well no wi-fi icon, and it can find a couple of wi-fi networks belonging to my neighbours, but won't find my network, 2 rooms away. The network is obviously all good, I am sending this from my laptop through said network.
Obviously I need an internet connection to get through the phone setup, so I power down, throw the SIM back in and boot up only to find no cell data either.
Skip the google account setup and get to the home screen to check things further and I find:
Calls in/out work, and most things are running, but wi-fi won't co-operate, and nothing in the APN list? Baseband and IMEI all look normal, too.
Try to flash Slim Bean 2.9 as I put the zip on the phone at the same time as a fallback and I get EXACTLY the same thing...
Anyone able to shed any light on what would cause this? Anything else worth trying? I'd like to avoid Odin as it honestly scares me reading all the problems people on here have with it...
At this point I've tried flashing both ROMs a few times with exactly the same results, I also can't go back to the ICS nandroid as the partition setup has changed and the restore doesn't work...
Thanks in advance for any help anyone can give.
Cheers...
I ended up flashing a 4.2 ROM (slim 4.2 beta 1) and it made the problem go away, I'm guessing something in the 4.1 base was broken and not getting overwritten on new installs?
ROM seems pretty sorted for a beta, few minor things not working, but hopefully it gives us a clean upgrade path...
Thanks.
I had the same issue with Slim 4.2 Beta 2. If anyone has a solution other than flashing the modem, please post.
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
I have installed slim and other ROMs but not had this issue. Currently on jellybam
Sent from my GT-I9300 using xda premium
wendleburger said:
Weird. The phone I was having this problem with now has that ROM on it and is working 100%.
I have a suspicion that flashing a ROM that uses a different kernel is what fixed it for us. I guess it just overwrites/replaces more stuff?
Maybe try hellybean 4.2 and see if it makes a difference, and if it does flash back to slim 4.2 and see if the problem comes back?
Click to expand...
Click to collapse
The weird part is that every other Slim Bean has worked great. I'll keep my fingers crossed for beta 3.
This might help someone having these no service/ no sim card no GPS fix issues with the galaxy SGSIII i9300, that might have to do with efs folder change and IMEI corruption.
Okay so i solved these no service issues and ill share my experience so maybe someone will find it helpful.
So the issue has to do with the famous efs folder conundrum, though tbh im not a developer so i cant say exactly what was the issue or even be a 100% sure it was the efs folder.
So I got me a used malfunctioning i9300 which i then repaired at a lab and proceeded to install a new TW based ROM, my first mistake was not backing up efs folder and creating a nandroid, but i havnt realized that yet. After flashing, I noticed that i have no GPS, but i didnt know if the GPS was working with original firmware because i neglected to check that or back it up, so i decided to put a pin in it for the time being and went on to check out some ROMs.
At first, I flashed couple of JB tw based roms, all was well (except for the gps), then i started to check out some KK roms, those didnt play well with my device, I got no service in every single rom i tried, You name it ive tried it, none fixed the service issue. Moreover i also tried a few JB AOSP based ROMs, among them the 4.3 JB PAC-man ROM, those had the same no service/no sim issues. Meanwhile whenever i un-root and flash with odin back to stock or restore a nandroid i made while on 4.3 foxhound ROM (with service working and a supposedly good copy of the efs folder) service is restored. I would also mention that I had more backups of the efs from the working “foxhound” i made with different tools and when i restored these folders when on a ROM with no service it didnt fix the issue.
Here are the solutions ive encountered and tried that didnt work:
-restoring efs with efs pro, samsung tool, efs backup -restore cmd tool.
-flashing latest firmware and flashing back to KK
-flashing all kinds of modems (those pre efs folder change (XXEMG4) and those after)
-flashing latest TWRP/CWM recovery
-flashing kernels
-trying to edit “nv_data.bin” with hex editor
-some more ways in trying to manipulate the efs folder.
-using samsung service codes on stock, which i found regarding this issue, except from the *#06# code, for imei, pretty much none worked for me.
Its important to mention that when on stock firmware or a JB TW based ROM i would see my baseband version in settings and when I tried the *#06# code for checking my imei it gave me a serial number with many digits that I assumed was indeed my correct IMEI number, and when i was on KK ROMs or non TW JB ROMs i would get the same popup with no numbers and in settings i would see “unknown baseband” .
To add to that, whenever i rooted and installed a KK ROM or a JB non TW ROM and tried to restore efs with efs professional i would get a message the device is not perm rooted (but thats neither here nor there).
This research took me about 5-6 days and the end of which i was ready to give up on having a KK rom or a non TW rom for that matter, NOTHING seemed to fix the problem. I just had some fight in me for one more hopeless attempt. I read somewhere that a flashing of cm 10.1 and then going to settings -> more and there change some network stuff from this to that would help -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
I said what the heck thats simple enough. I flashed CM 10.1.3 for i9300 and went into the settings but the options i read about werent the same as the settings i saw in my case,
so i did move one settings around in the settings-> more section, cant remember what it was and im on a different ROM by now,
it was nothing i knew about anyway (but you should give it a go and have a look, there are few options to choose from so you can eliminate your way to what makes sense).
I then went on to recovery to flash carbon rom 4.4 and to my enormous surprise i had service and connection and to my astonishment i also got back the GPS as a bonus ! yay ! I bet you forgot about that too by now…
This ends on a weird note though, though everything is at working order now and the IMEI number i get is the same as the one i get when on stock rom,
it does not match the number on the back of the phone under the battery. well mehh.. as long is its working.
Hope this helps someone.
You didnt mention that exact step. Changing "something from this to that" doesn't really count as being helpful.
Thanks for the post anyways.
~ RazorMC
RazorMC said:
You didnt mention that exact step. Changing "something from this to that" doesn't really count as being helpful.
Thanks for the post anyways.
~ RazorMC
Click to expand...
Click to collapse
Youre right, i couldnt find the thread that had the suggestion to install the 10.1 cm but my point was it didnt even apply to my situation because the options in "Setting -> more" werent compatible with what was suggested in the thread so i had to improvise and I just changed some setting i cant remember in "Settings -> More" but I realise that it would be more helpfull to say what i changed there exactly, but im not on cm 10.1 anymore and cant see what in there now.. the good news is that there werent many options to change there.
But i did went out and looked for the original comment that made me try this an it says -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
so in my case i didnt see these exact same options so i changed what seemed to me the most related to the issue at hand.
I dont think i had to touch the roaming, again i dont have CM 10.1 installed so i dont recall exactly what were my options.
is it a solution mostly for Qualcomm chipset based I9300 ? someone can say ? European providers use different frequencies I guess hence different chipsets and parameters.
Olek94 said:
is it a solution mostly for Qualcomm chipset based I9300 ? someone can say ? European providers use different frequencies I guess hence different chipsets and parameters.
Click to expand...
Click to collapse
mine is the international version but as i mentioned it didnt work like described but the end result was the same. I f you have the LTE version Im not sure which option youre going to get in CM 10.1 settings -> more , but if youre having trouble with service and GPS and stuff like that i do suggest you try flashing CM 10.1 (compatible with LTE - not sure how it goes with CM and LTE compatibility) and check if you got the same options to make the changes to, if not, try and improvise based on what makes even a little sense, thats what i did.
It might be that the flashing of CM 10.1 itself is what fixes the problem, so if you change nothing it might help still, anyway this is pretty simple and quick to do so better start here than starting with other messier solutions.
help
hi i was on stock 4.1.2 then i rooted flashed twrp recovery using toolkit and flashed revolutionary 5 4.3 straight away i didn't backup efs i know it was dump thing to do but i was new to galaxy s3 flashing so basically i f***k up. then i flashed official 4.3 firmware using odin.now i have a network reception but can't make or attend calls.i was thinking to go back to 4.1.2 in hope of getting things to work. please help n reply asap!! thanks
5668892 1021
jabirrockzzz said:
hi i was on stock 4.1.2 then i rooted flashed twrp recovery using toolkit and flashed revolutionary 5 4.3 straight away i didn't backup efs i know it was dump thing to do but i was new to galaxy s3 flashing so basically i f***k up. then i flashed official 4.3 firmware using odin.now i have a network reception but can't make or attend calls.i was thinking to go back to 4.1.2 in hope of getting things to work. please help n reply asap!! thanks
Click to expand...
Click to collapse
I believe I shared every bit of helpful information i can share with you about this issue and my process of handling it in the main message of the thread, Read the entire thing and the comments followed, then follow my suggestion, if you wish to do so.
samuelaviv said:
mine is the international version but as i mentioned it didnt work like described but the end result was the same. I f you have the LTE version Im not sure which option youre going to get in CM 10.1 settings -> more , but if youre having trouble with service and GPS and stuff like that i do suggest you try flashing CM 10.1 (compatible with LTE - not sure how it goes with CM and LTE compatibility) and check if you got the same options to make the changes to, if not, try and improvise based on what makes even a little sense, thats what i did.
It might be that the flashing of CM 10.1 itself is what fixes the problem, so if you change nothing it might help still, anyway this is pretty simple and quick to do so better start here than starting with other messier solutions.
Click to expand...
Click to collapse
Thank you, I was suspecting that you have a similar version than me. Well, in desperate cases anything can be tested (But some have told me not to mess with US versions as there is a risk of burning something )
Anyway the last version I could not flash , the CM 10.1 it was ejected with a file error soon despite 3 downlowd.
I will try with another more compatible version with Cyanogen.
Have a nice day
samuelaviv said:
This might help someone having these no service/ no sim card no gps fix issues with the galaxy s3 i9300, that might have to do with efs folder change and IMEI corruption.
Okay so i solved these no service issues and ill share my experience so maybe someone will find it helpful.
So the issue has to do with the famous efs folder conundrum, though tbh im not a developer so i cant say exactly what was the issue or even be a 100% sure it was the efs folder.
So I got me a used malfunctioning i9300 which i then repaired at a lab and proceeded to install a new TW based rom, my first mistake was not backing up efs folder and creating a nandroid, but i havnt realized that yet. After flashing, I noticed that i have no gps, but i didnt know if the gps was working with original firmware because i neglected to check that or back it up, so i decided to put a pin in it for the time being and went on to check out some roms.
At first, I flashed couple of JB tw based roms, all was well (except for the gps), then i started to check out some KK roms, those didnt play well with my device, I got no service in every single rom i tried, You name it ive tried it, none fixed the service issue. Moreover i also tried a few JB AOSP based roms, among them the 4.3 jb pac-man rom, those had the same no service/no sim issues. Meanwhile whenever i un-root and flash with odin back to stock or restore a nandroid i made while on 4.3 foxhound rom (with service working and a supposedly good copy of the efs folder) service is restored. I would also mention that I had more backups of the efs from the working “foxhound” i made with different tools and when i restored these folders when on a rom with no service it didnt fix the issue.
Here are the solutions ive encountered and tried that didnt work:
-restoring efs with efs pro, samsung tool, efs backup -restore cmd tool.
-flashing latest firmware and flashing back to kk
-flashing all kinds of modems (those pre efs folder change (xxemg4) and those after)
-flashing latest twrp/cwm recovery
-flashing kernels
-trying to edit “nv_data.bin” with hex editor
-some more ways in trying to manipulate the efs folder.
-using samsung service codes on stock, which i found regarding this issue, except from the *#06# code, for imei, pretty much none worked for me.
Its important to mention that when on stock firmware or a JB TW based rom i would see my baseband version in settings and when I tried the *#06# code for checking my imei it gave me a serial number with many digits that I assumed was indeed my correct IMEI number, and when i was on kk roms or non tw JB roms i would get the same popup with no numbers and in settings i would see “unknown baseband” .
To add to that, whenever i rooted and installed a kk rom or a jb non tw rom and tried to restore efs with efs professional i would get a message the device is not perm rooted (but thats neither here nor there).
This research took me about 5-6 days and the end of which i was ready to give up on having a KK rom or a non TW rom for that matter, NOTHING seemed to fix the problem. I just had some fight in me for one more hopeless attempt. I read somewhere that a flashing of cm 10.1 and then going to settings -> more and there change some network stuff from this to that would help -
(Originally Posted by Goose306 on s3forums.com)
"flash back to another AOSP 4.2 ROM (CM10.1, Liquid, etc.)
Got to Network settings. You need to change Roaming to automatic and CDMA settings to RUIM/SIM (I *think* that is the name of it, I'm actually on TW temporarily as I'm troubleshooting some SDcard issues of my own)
Reboot and you should be back in business. Touchwiz doesn't have a way of changing of those settings which is why ODIN/stock doesn't fix it"
I said what the heck thats simple enough. I flashed CM 10.1.3 for i9300 and went into the settings but the options i read about werent the same so i did move one settings around in the more section, cant remember what it was but it was nothing i knew about anyway, then went on to recovery to flash carbon rom 4.4 and to my enormous surprise i had service and connection and to my astonishment i also got back the GPS as a bonus ! yay ! I bet you forgot about that too by now…
This ends on a weird note though, though everything is at working order now and the IMEI number i get is the same as the one i get when on stock rom it does not match the number on the back of the phone under the battary.
Hope this helps someone.
Click to expand...
Click to collapse
:crying: :crying: :crying: :crying: :crying: Dude!!!!! I understand!!!!
I had a similar experience only I also tried flashing CM 10.1 and it did not work. Although I have another imei, I have all my services running on the Stock 4.3. Now the only problem is that if I change to any other rom, does not connect to the wifi network.
I found something like this: http://forum.xda-developers.com/showthread.php?t=839367&page=4
But neither worked. Yesterday I tried to repartition the phone and almost killed. I spent two weeks looking for a solution, and tried them all, but did not work, I think I will draw on the last and the only thing I think work ... The box.
The octopus box (or similar).
KK roms are beautiful ... but no matter what, I have no wifi in another rom than the stock 4.3 lol.
Thank you for your contribution! as you say: I hope you serve someone else.
VIOShero said:
:crying: :crying: :crying: :crying: :crying: Dude!!!!! I understand!!!!
I had a similar experience only I also tried flashing CM 10.1 and it did not work. Although I have another imei, I have all my services running on the Stock 4.3. Now the only problem is that if I change to any other rom, does not connect to the wifi network.
I found something like this: http://forum.xda-developers.com/showthread.php?t=839367&page=4
But neither worked. Yesterday I tried to repartition the phone and almost killed. I spent two weeks looking for a solution, and tried them all, but did not work, I think I will draw on the last and the only thing I think work ... The box.
The octopus box (or similar).
KK roms are beautiful ... but no matter what, I have no wifi in another rom than the stock 4.3 lol.
Thank you for your contribution! as you say: I hope you serve someone else.
Click to expand...
Click to collapse
yeah thats some BS those signal and issues on the i9300.. they really did a number on that one.
sorry my thing didnt help, i too tried everything and got nothing.
Maybe try flashing CM 10.1.3 and changing those options in settings-> more, Might be that just flashing CM 10.1 wont do it, I did change something ther but cant remember what it was, i wrote in my post what someone else had ther in the options but i had different ones but I still changed one option there ( what i thought might be connected to the issue ).
anyway dude i feel you its crying shame whole thing, and so many are posting about these issues all the time, im kinda hating on samsung cause they always seem to mess up like that.
Hope you solve this somehow..
Hi,
I have used XDA for a while now for useful info on rooting and customising my phones with custom roms.
I am looking for some help.
I own a Galaxy Mega I9205 and have just installed the Note 4/S5 rom by bevin.
Wasn't easy as there were 2 different threads and 2 different methods.
First way of flashing the rom followed by a fix for I9205 users didn't really work. The fix pretty much wiped the rom and phone wouldn't boot. The thread stated to flash a stock modem of which I can't find any (not that I'm 100% sure what I'm looking for).
Found a .bin file HLOS-BIIN and flashed this after flashing the rom but without the fix and pretty much had same issue.
I tried the method on the second thread of downloading his backup file and restoring that. Had to re-flash stock rom first before this to get everything working again but all is pretty much good. Rom is near perfect and looks great. I have mobile data working and seems pretty stable.
The issue I have now is that my WiFi will not switch on. I flick the switch and it immediately deactivates itself.
I have tried several ways mentioned on here to sort it out but nothing works.
I tried the vcore2 root but that pretty much wiped the rom so yet again had to go through the whole process.
I believe the kernel controls WiFi functionality.
Does anyone know of any decent kernels for this device or any ways of fixing this WiFi issue?
I don't want to go back to stock because I love the whole look and functionality of the note 4 / S5 rom and looks great on this big screen.
Any help would be greatly appreciated.
Karl
Karl Brunton said:
Hi,
I have used XDA for a while now for useful info on rooting and customising my phones with custom roms.
I am looking for some help.
I own a Galaxy Mega I9205 and have just installed the Note 4/S5 rom by bevin.
Wasn't easy as there were 2 different threads and 2 different methods.
First way of flashing the rom followed by a fix for I9205 users didn't really work. The fix pretty much wiped the rom and phone wouldn't boot. The thread stated to flash a stock modem of which I can't find any (not that I'm 100% sure what I'm looking for).
Found a .bin file HLOS-BIIN and flashed this after flashing the rom but without the fix and pretty much had same issue.
I tried the method on the second thread of downloading his backup file and restoring that. Had to re-flash stock rom first before this to get everything working again but all is pretty much good. Rom is near perfect and looks great. I have mobile data working and seems pretty stable.
The issue I have now is that my WiFi will not switch on. I flick the switch and it immediately deactivates itself.
I have tried several ways mentioned on here to sort it out but nothing works.
I tried the vcore2 root but that pretty much wiped the rom so yet again had to go through the whole process.
I believe the kernel controls WiFi functionality.
Does anyone know of any decent kernels for this device or any ways of fixing this WiFi issue?
I don't want to go back to stock because I love the whole look and functionality of the note 4 / S5 rom and looks great on this big screen.
Any help would be greatly appreciated.
Karl
Click to expand...
Click to collapse
Likely a rom/kernel incompatibility.
Did you see from http://forum.xda-developers.com/galaxy-mega/development/rom-t3023133
i9205 Users. Soon after you download and install the above ROM from the links, flash this fix
File Name : i9205_New_Fix_13FFeb
New Fix : https://www.mediafire.com/?6la12p1y9s3cr45
After you flash this Fix, flash a Stock Modem for i9205
Reboot to setup and then Update SU binary when it asks and reboot again.
Click to expand...
Click to collapse
only custom kernel I see is [KERNEL] [4.4] [Multiboot] GraKernel by Grarak
and may not be compatible with current rom.
This thread will be moved to Galaxy Mega Q&A, Help & Troubleshooting
Hi thanks for the reply.
I have already tried that fix but it just wipes the rom from the phone. When I reboot after flashing the fix it just boots into recovery mode so have to flash the rom all over again.
I'm sure there must be a way of manipulating the root files but just not sure how.
I compared the root files on my mega to those in my note 2 and it appears I have no binary files in my root wifi folder. This may be the cause.
I just need to somehow find the correct binary files for this particular phone.
Sent from my Galaxy Mega I9205
just install other rom.
i think thats kernel problem. kernel modification in build prop make crash and wifi annot turning on. i suggest u changing your rom
Hello,
I have an issue with making a tweaked, modified, etc TouchWiz ROM (aka BaconOS).
When I debloated, deodexed, deknoxed it with Assayed kitchen (and by flashing a debloat/deknox zip before that), the WiFi stopped working for some reason.
So I tried deodexing and only removing some apps (file manager, camera, samsung store, email, gapps), but that didn't fix the issue.
After that, I tried flashing stock ROM (Nothing changed, extracted using ext4unpacker) with assayed kitchen's updater-script, but still nothing.
Please let me know how to fix this issue.
maybe replace wifi folder from very stock rom..?
Naksuhd said:
maybe replace wifi folder from very stock rom..?
Click to expand...
Click to collapse
It has to do something with deodexing, because when I deodexed the stock rom, wifi stopped working. So the ROM will be odexed (a bit slower)
tried with odex system, problem is with debloating..
Hi, are you seriously making a ROM for this old device? Wow, finally something at last!
Had this device since christmas of 2014 and actively used it as my main device until january 2017.
During this time, I rooted it about 6 times. A couple of times I did it with Kingroot (or was it Kingoroot?) and all was well. But every time I tried to root using a SuperSU root that I found here, there was this glitch that would seemingly trigger out of nowhere, causing infinite "App has closed unexpectedly" messages to appear, along with a black screen behind those warnings, nothing worked until I did a factory reset. Yea, frustrating times...
I have always wondered why nobody bothered to port literally anything to this phone. Not even a (working) custom recovery was ever available for it. There was one that I tried, but was very unsuccessful in trying to boot it.
All that being said, my phone's battery has unfortunately "gone up in size", or "spicy pillow", so I can't really test anything right now.
My phone is the SM-G357FZ running TMZ firmware (Czech republic T-Mobile), and I always wanted to get rid of that and put an unbranded European CSC/firmware onto it.
I support you in your efforts OP and can't wait to test out your work!
Edit: I just discovered that there was an official update released by Samsung in 2021! Have you considered basing your ROM on that instead of the now ancient 2017 ROM?