My phone so far:
SM-A320FL with the current stock Android 8.0 DBT. Flashed with Odin3.
Magisk 18.1 thx topjohnwu
[*]Xposed 90 beta 3 thx rovo89
Xposed systemless over Magisk module "Xposed Framework"
TWRP 3.2.3 for SM-A320 thx McFy
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
I also encountered the following problem which I found a solution for:
After every reboot all of the paired Bluetooth devices are lost. I had to pair them again. Pretty annoying, especially the pairing with my car.
After searching around I found the solution within a Xposed thread, which I adapted to my phone.
There are two ways to solve this problem.
You lose all of your saved Wifi passwords and you need to pair all Bluetooth devices again.
First Method:
Go into Magisk and look for the module:
libsecure_storage companion for rooted Samsung devices
Follow the instructions that are given with the module. It works fine with my SM-A320FL.
Second Method:
First of all you need ROOT access and a root explorer (e.g. ES File Explorer) on your phone. You also lose all of your saved Wifi passwords.
Every time you do something on your phone make a BACKUP
Download the file at the bottom
Extract the Zip file to your hard drive
Copy the extracted system folder to your SD card
Copy the four files (2x libsecure_storage.so and 2x libsecure_storage_jni.so) within the subfolders (lib and lib64) to their respectable positions. The folders lib and lib64 are found in the systems folder on your phone. I didn't need to override any files.
Add the following line at the bottom of the build.prop file (system folder):
Code:
ro.securestorage.support=false
Reboot
Now the paired Bluetooth devices should stay paired.
I had to delete all Wifi connections and enter the password again to get them going. That's because the Wifi passwords are stored encrypted.
simple_s said:
My phone so far:
SM-A320FL with the current stock Android 8.0 DBT rom. Flashed with Odin3.
Magisk 16.4 thx topjohnwu
Xposed 90 beta 3 thx rovo89
TWRP 3.2.1 for SM-A320 thx McFy
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
I also encountered the following problem which I found a solution for:
After every reboot all of the paired Bluetooth devices are lost. I had to pair them again. Pretty annoying, especially the pairing with my car.
After searching around I found the solution within a Xposed thread, which I adapted to my phone.
To solve the problem I did the following steps:
First of all you need ROOT access to your phone. You also lose all of your saved Wifi passwords.
Every time you do something on your phone make a BACKUP
Download the file at the bottom
Extract the Zip file to your hard drive
Copy the extracted system folder to your SD card
Copy the four files (2x libsecure_storage.so and 2x libsecure_storage_jni.so) within the subfolders (lib and lib64) to their respectable positions. The folders lib and lib64 are found in the systems folder on your phone. I didn't need to override any files.
Add the following line at the bottom of the build.prop file (system folder):
Code:
ro.securestorage.support=false
Reboot
Now the paired Bluetooth devices should stay paired.
I had to delete all Wifi connections and enter the password again to get them going. This is because the Wifi passwords are stored encrypted.
Click to expand...
Click to collapse
cool, i mean nice fix...working also on s9+
thx for this
Working here too!
Galaxy S9 with Magisk root.
Installed Xposed v90-beta3 yesterday, problem that BT connections were gone. Also WIFI passwords were incorrect. Not a problem that I had to re-enter WIFI passwords, but BT connections were gone each (re)boot.
This fixed the problem.
Thnx!
Deleted
Thanks works for my S9
Ok, I noticed that you said \system\lib and \system\lib64
And no overwrite is required because they don't exist...
That's because the files are actually in \system\vendor\lib and \system\vendor\lib64
The question is...
As you mentioned, no overwrite while on github says place them in their respective location... Which path is the right path...
I used Vendor, before I found this thread...
Because I simply searched for the file name...
Dante63 said:
Ok, I noticed that you said \system\lib and \system\lib64
And no overwrite is required because they don't exist...
That's because the files are actually in \system\vendor\lib and \system\vendor\lib64
The question is...
As you mentioned, no overwrite while on github says place them in their respective location... Which path is the right path...
I used Vendor, before I found this thread...
Because I simply searched for the file name...
Click to expand...
Click to collapse
I put the files in system / lib
And but pairing stays now
Alex-V said:
I put the files in system / lib
And but pairing stays now
Click to expand...
Click to collapse
Same, pairings stay for system vendor lib...
Maybe as long it's lib, doesn't matter which one ?
Deleting WIFI Passwords is not mandatory (at least for me). I had to reinstall Xposed and clear Cache (not Dalvik/ART) in order to get it working again. Without reinstalling Xposed and clearing cache the lib files got deleted every reboot.
Thanks.
For S7e with Oreo, beside forgetting paired devices on every bluetooth off/on, enabling bluetooth took noticeably longer time.
Placing libs in /system/lib and /system/lib64 did not work (build.prop edited, of course), placing them in /system/vendor/lib and /system/vendor/lib64 helped.
Is there a way to avoid replacing the files? On the xposed issue page (https://github.com/rovo89/Xposed/issues/294) ahronshor mentions backing up /data/system/secure_storage/com.android.bluetooth/, and then copying it back in place. Maybe that's the way to go, provided you are before rooting a freshly installed original firmware.
Another thing. I have flashed a new firmware (G935FXXS3ERKE), then flashed TWRP back even before rebooting. Then booted to TWRP and installed "remove encryption.zip", SuperSU and xposed, and finally booted the system (for the first time after update).
Bluetooth works now, on new firmware's original libraries and build.prop (btw, .so files are identical with previous G935FXXS3ERJ2, build.prop has just dates and versions changed). Off/on, restart - paired devices stay where they should, bluetooth enable time as usual.
Maybe the libsecure_storage.so patch (jnl was not modified at all) was to stop trying to read encrypted bluetooth data and to create an unencrypted container. It seems once the Bluetooth data file on /data is unencrypted, original code manages it correctly.
Thanks! Works on Note 9 Oreo 8.1
Reporting this solved my problems on J7 2017 with Oreo 8.1. Magisk 18 and Xposed. Thanks.
simple_s said:
First of all I am not able to make a backup within TWRP. Seems to be a problem of Magisk.
Click to expand...
Click to collapse
How did you solve the backup problem? I also can't make backup. It gives me some error.
The BT problem is solved. Note 9.
There is a magisk module that can do the trick without need to xposed.
Sent from my SM-N960F using Tapatalk
is there a way to fix the issue on stock 8.0 (last update december 2018 patch) without rooting?
It happens to me during last month...
thanks!
Ninolina said:
How did you solve the backup problem? I also can't make backup. It gives me some error.
The BT problem is solved. Note 9.
Click to expand...
Click to collapse
I couldn't solve it.
iltoffa said:
is there a way to fix the issue on stock 8.0 (last update december 2018 patch) without rooting?
It happens to me during last month...
thanks!
Click to expand...
Click to collapse
I don't think so.
I added new informations to the guide.
Apparently there is a Magisk module for some phones who does the same thing. You find it in Magisk under
libsecure_storage companion for rooted Samsung devices
It works perfect on my SM-A320FL.
My personal solution has been to remove IFTTT which was installed. From that, no disconnections found at all
Related
Hi there, i've been trying to make some changes to my build.prop (mainly enable miracast...can't believe they would disable it!) and i've had a rather challenging time.
I am now stuck on how to pull the actual build.prop...when i enter the command i get a long list of ADB definitions but no file - at least not that i could find. I tried a few times, including directing the file to be saved on an empty drive in case i could not see it.
I have unlocked my boatloader and installed TWRP. Mounted the system then gone back and entered the commands in ADB....and i don't seem to be having any success. Any help would be appreciated.
thanks
m
Why not just edit it within the built in editors in most file explorers? I use Solid Explorer and it allows me to edit at will within the app itself, no pushing or pulling. Of course I back up my current one before doing anything to it
Tower1972 said:
Why not just edit it within the built in editors in most file explorers? I use Solid Explorer and it allows me to edit at will within the app itself, no pushing or pulling. Of course I back up my current one before doing anything to it
Click to expand...
Click to collapse
i'm not rooted...and i've read that you don't get OTA updates...and it's happened to me more than once that i have an issue with the phone, and i can't get service because it's rooted...
and i guess i thought it was too much trouble to get rooted, make the changes, and then unroot...but i could be wrong at this point?!
You won't get OTA with twrp either. You need stock recovery.
so i bit the bullet and rooted my phone...i was able to get the build.prop editor to work (at first i did not have busybox which it seems helps apps to realize you have root). So now when i go to unable Casting, i can turn it on from the top right of the cast screen, and my tv appears. I can select it and it starts to sync up...then the mircosoft display adapter shows that it's also trying to sync...and then it times out it seems. I've checked it with my tablet and my wife's phone...both work.
any suggestions?
I understand Miracast no longer works in Nougat. I'm still on MM with my 6P and it works, but if you're on 7, you may have lost that feature.
What about WUGS toolkit? Do you need to re rooted for that...ifnot thats what I always use to edit the prop. So much easier as it has most edits you'll make and you just choose.
you never needed to root i edit build.prop like this all the time
1. boot to twrp recovery
2. go to mounts and select system
3. adb pull /system/build.prop
4. make edits
5. adb push build.prop /system/
idk if your edit will work but thats how to do it without root and for some of the other things said in this topic you can ota in twrp but it will fail if modify anything like you just did
Hi Everyone,
I have a phone, the Huawei Ascend P7 -L10.
Some weeks earlier I tried to install Spotify in my phone, but I didn't manage to install it. After several attempts I end up crocking my phone.
It happened when I found some app that had apparent solution to solve Spotify installation problem. I don't remember the name of the app. Anyway, I found it effective so I tried to follow the instructions given. I made it, then the changes were effective. What the app does is to change the phone model and respective carrier.
All the dilemmas started when I decided to restart the phone.
Here goes what I've done so far after the incident.
1. I tried by myself to restore/upgrade the system. I've experience doing this.
2. I took the phone to the 1st Repair Agency - they did not fix it
3. I took to the 2nd Repair Agency - the same thing, they fail to fix it
Note: When you try to restore the phone it gives the following information “update failed!"
and when you normally try to switch the phone on it stop on black screen and nothing else, I've also tried wipe cache, wipe data everything but nothing. Please help!!
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
es0tericcha0s said:
Sounds like it might have modified your build.prop (general explanation of build.prop is here: http://forum.xda-developers.com/android/general/explanation-build-prop-values-t3069341). Basically this file found in /system dictates a lot of settings and modes for the phone to do and be in. If you are rooted, then you can view the build.prop with a build.prop editor, text editor, or root enabled file manager. If you aren't rooted, then you will have to see if there is a way to install TWRP recovery or you might be able to use adb if you can still get into your phone's settings. With adb, you should be able to pull the file to your PC then edit it back to the correct info. You might need to see if you can download a rom that will have this info or get someone in the forum for your phone to post it so you can verify that everything is the way it should be. Once that is done then updates should work again. Reason being is that most updates reference the build.prop to make sure it is installing to the correct device to avoid major issues.
Click to expand...
Click to collapse
Thanks for your replay. My device is rooted one, but the problem is, I can't login not even connect it via cable (using e.g. HiSuite). So, how can I pick up the file from phone?
**does not yet work for 7.1.1**
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Excellent! This works perfectly! Thank you so much for posting this.
J320A PC9 worked perfectly!
March security patch
Hi man, this method support the march security patch, or are still in january security patch
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
I tested on AQD2 so it'll work on AQC1 too.
I assume it'll work for all 6.0 updates we get.
This works perfectly. Thank you!
I suggest you put 'root' in the tile, otherwise google cannot find it.
I googled 'j320a root', google only links to ashyx's post which doesn't... well maybe only mine phone.
I am new to this root bit.
Possibly I have done something wrong. I read your instructions carefully and quit didn't understand where the unzipped files should go. Do any of these have to be placed in the phone's directory?
Failed on my AT&T SM-J320A
I wonder if it has anything to do with the new update pushed out recently
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
DamienMc said:
@JeffF73
Run Odin and Click ap.
Navigate to the directory where you unzipped root_j320a.zip.
In that folder you'll see a bin folder, inside that is sm-j320a_Engroot_601PJ2.tar, which needs flashed to the phone.
Once that's complete, let it boot and wait.
Then run root.bat
Click to expand...
Click to collapse
Hello DamienMc Thank you for your reply and help. I figured it out. I had to put my phone in "Download Mode" by holding down Volume Down, Home Button and Power button while booting. Then I was able to use Odin without failing. This solved all my problems thank you
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
sonic0504 said:
Is it safe to flash this after doing this?
https://mega.nz/#!D8hSzLaa!pDugFwQ0NyGBLy36j1643bI3e4f9xog7US8UTTkZ8SU
Click to expand...
Click to collapse
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are noticable tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Ragheb Alama said:
Hi man, this method support the march security patch, or are still in january security patch
Click to expand...
Click to collapse
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
DamienMc said:
Yes, that has selinux set to permissive as well, although there's no real difference. The build.prop differences are "noticeable" tho...I plan on doing an update to this, just have to figure out how to tell if it's A or AZ from adb
Click to expand...
Click to collapse
Thanks, I just needed to install this to use adb to uninstall an update I did to System UI because it would continuously crash.
SBCarr said:
Yes, it works for QC1. However, you may need to replace build.prop in /bin from QC1 with WiFi fix before root.
I did notice that after root, the contents of /Android/data folders in both internal storage and external sd card are hidden from PC. Before root, both are visible from PC. Any thoughts about what cause the changes?
Will this work on July security patch?
Click to expand...
Click to collapse
Probably the eng_boot we use, it breaks the flashlight and wifi passwords too... it does work on j320a July update, so I assume it'll work on j320az update too
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
ScSoluciones said:
@DamienMc Dude, thanks for ur post, but i tried 2 times and fail, i got stuck at logo, i had to reflash to stock but now my build.prop is gone or corrupted, my phone says model unknow, i cant even use hidden menus like *#06, etc, i need the original file to fix it please. model SM-J320A RUNING QC1
Click to expand...
Click to collapse
Reflash CSC as well, that'll wipe your device but fix your problem.
Are you sure you waited long enough after the phone booted before rooting?
If at any time during the script you see it say "adb server out of date. Killing..." something is wrong. You can x the command prompt and do root.bat again.
DamienMc said:
Using a PC to root seems like moving backwards compaired to a 'one click' apk. but we're already at the PC to flash eng_boot, plus this new method is so much faster...so here we go
Features:
SuperSU 2.82
Init.d
Wifi fix
Flashlight fix
Issues:
For the wifi fix I just copied an edited J320a build.prop
So J320AZ users will see J320A in about device, and will have to reassign notification sounds. (Hope to fix it in the future)
Needed Files:
Odin
Root_J320A.zip
Procedure:
1. Unzip both files.
2. Run Odin click the 'AP' button.
3. Navigate to Root_J320A/bin and select sm-j320a_Engroot_601PJ2.tar and press "Start" (make sure NOT to check re-partition)
4. After it completes sucessfully, leave the phone hooked to the pc... and then wait, wait a good 2 or 3 minutes after its booted.
5. Once 2 or 3 minutes has gone by you can navigate to the Root_J320A folder.
6. There you'll see root.bat, double click that let it do its thing.
6a. If at any time during the script you see "adb out of date. killing..." hit the x to close the window and restart the script.
*This may work on J320AG models but make sure you check oem unlock from dev settings first... and let us know how it goes
Enjoy
- D
Credits:
@ashyx - eng_boot
@Sh$llNinjA - eng_root
@sjowns - flashlight fix
@Chainfire - SuperSU
@Ryuinferno - init.d script
Click to expand...
Click to collapse
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
james2ya said:
This was the first time i ever tried to root my phone and i followed the instructions located here:
https://forum.xda-developers.com/galaxy-j3-2016/how-to/root-samsung-sm-j320a-galaxy-express-t3573628
Well my wifi wouldnt save any passwords , flashlight was broken and my ATT J320A would always want to boot in to recovery mode. I thought i was screwed!!!! Then i seen one link in the thread to this thread where Kingroot was not needed.
I opened Odin and gave a shot and then ran Root.bat file, and the device rebooted wifi and flashlight were fixed and best of all my J3 was now rooted!!!!!
Still working on getting rid of that annoying pop up but all is good, thanks so much for this root and fix from the other thread.
Click to expand...
Click to collapse
@james2ya If you are talking about the pop that either says something in the order of "Unathorized activities where made" go to the play store, download and install SecurityLogAgent Fix, Open it up and click "Disable Securitylogagent" then restart phone when it asks. This should help get rid of that popup.
works great for me! now i just need a custom rom. is it possible to install trwp on j320a?
Hello.
I was forced to reinstall firmware due to phone issues.
Now I'm again with root and TWRP.
Firmware is on nougat, version c900b300 but many files are missing.
In particular, themes cannot be applied even if I can download them.
I followed a procedure suggested for the Mate 8 but with no results.
Is someone able to help me?
I think this is not a post for q&a section.
Otherwise please move it.
Thanks.
Ah, even the ringtones folder is empty, but this is not a big issue...
Try these 2 methods
1 - https://forum.xda-developers.com/honor-6x/help/solved-huawei-gr5-2017-honor-6x-problem-t3606037
2 - https://forum.xda-developers.com/honor-6x/help/theme-issue-5-0-upgrade-t3579812/page2
First method pushed FM spk in data folder, I rebooted but no FM radio app shows up.
Regarding second method, Google drive file doesn't exist.
I hope to be able to install Oreo when available through TWRP.
Now I don't have the updater and I'm not receiving ota update from Huawei. Unfortunately I'm stuck with March security updates
Dammit, I'm out of ideas at the moment. Plus, i didn't knew that even updater was missing... You wanna try with an apk of mine extracted?
of course mate.
Now I'm more relaxed, as I understand that is better just playing with this phone. I'm not gonna put job related files anymore in, so if something happens, I can recover easily.
Baaaaaaaaad phone...
Ah, sorry if I forgot to mention that I miss A LOT of file. Basically all the crapware like Health or Huawei related bullshits, updater, ringtones, themes are not installing. Cannot even load a different wallpaper.
But I have nougat base and patches till March.
Better than nothing!
Ringtones= thank you Zedge to exist!
Themes= amen, I can live with it
Diamantes said:
Ah, sorry if I forgot to mention that I miss A LOT of file. Basically all the crapware like Health or Huawei related bullshits, updater, ringtones, themes are not installing. Cannot even load a different wallpaper.
But I have nougat base and patches till March.
Better than nothing!
Ringtones= thank you Zedge to exist!
Themes= amen, I can live with it
Click to expand...
Click to collapse
For Huawei bloatware it's surely a positive thing if you don't care, since that those results "well" radicated into system and aren't easy to remove. For all the rest, looks like you are on a firmware build that was created to another build, and so causes various incompatibilities... But it's the worst case that i saw, except bricking related cases maybe a rebranding to an other variant, with the flash of another firmware could solve at least the missing apps issue. Anyway, i uploaded the updater apk; after all i don't think it'll works sincerely neither making it a system app with apps or modules like systemizer, if all those issues are present already... But in the worst case here, you'll just get an install failure due to an apk version that doesn't match your first, initial build. Try for fun, i would say.
Thank you for the tips.
Even if I read on this forum (honor in general) many different opinions regarding how to flash a Rom with twrp...and sometimes even with dload method.
I mean: it seems to me that with twrp is compulsory to flash the zip with "PV" only, even if many disagree
With dload, unzip the folder and better to put all the files, not only the .app one inside...
Am I right?
By the way, the updater apk should be put inside what folder? Of course it cannot be installed normally (file corrupted)
You can use apps like Link2SD, but if the file looks corrupt (had this problem too when i accidentally deleted compass app time ago) it means that doesn't matches your build number. You could try by installing a version that matches your actual build.
Diamantes said:
Thank you for the tips.
Even if I read on this forum (honor in general) many different opinions regarding how to flash a Rom with twrp...and sometimes even with dload method.
I mean: it seems to me that with twrp is compulsory to flash the zip with "PV" only, even if many disagree
With dload, unzip the folder and better to put all the files, not only the .app one inside...
Am I right?
By the way, the updater apk should be put inside what folder? Of course it cannot be installed normally (file corrupted)
Click to expand...
Click to collapse
Yes, with dload method, you need to flash all files available in zip to get everything working, i tries this and everything worked for me without anything missing.
For flashing zip, yes it is PV files that can be flashed via Twrp
The problem, as far as I know, is that now Huawei stopped releasing ROM files and even the .ru website now will have problems to collect files...
Diamantes said:
The problem, as far as I know, is that now Huawei stopped releasing ROM files and even the .ru website now will have problems to collect files...
Click to expand...
Click to collapse
They are still getting it. Not sure how
Solution
Hey, i have had the same Problem with the theme changer - found this solution which just take 1 minute
Themes:
- I downloaded the Huawei Tool from here:
https://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
- enable USB-Debugging connect your phone to the PC and start the tool
- choose "7" for utilities
- after that choose "12. Install /data/hw_init (Mate8,P9,P9 Plus)" and confirm
- after reboot the theme change will work again!
Will it work on honor 6x? The hw data is only for p9 ,isnt it?
starkeeper2018 said:
Hey, i have had the same Problem with the theme changer - found this solution which just take 1 minute
Themes:
- I downloaded the Huawei Tool from here:
https://forum.xda-developers.com/honor-8/development/tool-srk-tool-huawei-bootloader-root-t3470823
- enable USB-Debugging connect your phone to the PC and start the tool
- choose "7" for utilities
- after that choose "12. Install /data/hw_init (Mate8,P9,P9 Plus)" and confirm
- after reboot the theme change will work again!
Click to expand...
Click to collapse
Will it work on honor 6x..the hw data is showing only for honor p9 ,etc but not 6x
(I posted this on the Android Mods Thread on accedent)I have a LG Nexus 5 HammerHead and tried to flash the newest Kali NetHunter using TWRP 3.5.2. After I flashed the ROM successfully, I have notice that the phone itself says no wifi networks found when swipe down to look at the wifi connections. I go to the wifi settings it says "Searching for wifi networks" with a spinning wheel of death(the loading icon). I've tried configuring it to use 2.4 Mhrz and didn't work, set it up to where it would only find good connections and still didn't work, I even did a factory reset and actually made it worse. I even reflashed it and see if that fixed it, nope. I connected it to the internet using a Ethernet adapter that is made for phones using a micro USB connection, updated the apps, updated and upgraded Kali NetHunter itself in the terminal and wifi connections is still not finding any connections at all. Could It be that Kali NetHunter doesn't support the internal wifi card that is built into my phone, could it be that twrp is having some errors on their end, or is it a bug that Offensive Security is not aware about? Please Help?
This may happen cos of wi-fi firmware. These files are called fw_bcmdhd.bin and fw_bcmdhd_apsta.bin. There are two versions of firmware:
1. https://github.com/LineageOS/androi...c531cd30abd21d93c5a04/bcmdhd/firmware/bcm4339
2. https://github.com/LineageOS/androi...5f8949fe77780d922c973/bcmdhd/firmware/bcm4339
You need to find where these files are stored in your rom, replace them with files from version 1 or version 2, restore permissions for these files if necessary and reboot your phone.
z3DD3r said:
This may happen cos of wi-fi firmware. These files are called fw_bcmdhd.bin and fw_bcmdhd_apsta.bin. There are two versions of firmware:
1. https://github.com/LineageOS/androi...c531cd30abd21d93c5a04/bcmdhd/firmware/bcm4339
2. https://github.com/LineageOS/androi...5f8949fe77780d922c973/bcmdhd/firmware/bcm4339
You need to find where these files are stored in your rom, replace them with files from version 1 or version 2, restore permissions for these files if necessary and reboot your phone.
Click to expand...
Click to collapse
Honestly, I have been trying to find these files and can't seem to find them. I even put the file name on the search bar of my windows 10 and it can't find them either. I think its just missing firmware on Offensive Security's end in this situation. I've had a troublesome experience with their kali linux products such as kali linux itself on having missing firmware after installation. Thank you for helping me out and hopefully these files should do the trick after I re-flash NetHunter with the firmware you have provided. As a matter of fact would the files belong in the firmware folder?
Martisabolt said:
Honestly, I have been trying to find these files and can't seem to find them. I even put the file name on the search bar of my windows 10 and it can't find them either. I think its just missing firmware on Offensive Security's end in this situation. I've had a troublesome experience with their kali linux products such as kali linux itself on having missing firmware after installation. Thank you for helping me out and hopefully these files should do the trick after I re-flash NetHunter with the firmware you have provided. As a matter of fact would the files belong in the firmware folder?
Click to expand...
Click to collapse
You will not find them in the search bar of your windows)
And no, firmware is not missed. Without wi-fi firmware you will be unable to enable Wi-Fi at all. In your case Wi-Fi can be enabled but you didn't see any networks.
Also /firmware - is incorrect place. It is a mount point of the /modem partition.
Wi-Fi firmware can be located at /system/firmware or /system/vendor/firmware/. Try to find them in TWRP. Boot into TWRP, mount System partition, open File Manager and review all the paths i've listed here. But i can't be sure cos i've never used Kali NetHunter.
z3DD3r said:
You will not find them in the search bar of your windows)
And no, firmware is not missed. Without wi-fi firmware you will be unable to enable Wi-Fi at all. In your case Wi-Fi can be enabled but you didn't see any networks.
Also /firmware - is incorrect place. It is a mount point of the /modem partition.
Wi-Fi firmware can be located at /system/firmware or /system/vendor/firmware/. Try to find them in TWRP. Boot into TWRP, mount System partition, open File Manager and review all the paths i've listed here. But i can't be sure cos i've never used Kali NetHunter.
Click to expand...
Click to collapse
Ok, I've been to those locations and in the system's folder, no firmware folder. However, in the sys folder, there is and does not show any firmware files in TWRP.
Give me the links to ROM files u flashed
This came directly from kali.org.
What was your base ROM before installing Kali? Stock Android 6.0.1?
yes
Well, Wi-Fi firmware in stock android 6.0.1 is located at /system/vendor/firmware/ folder. I've looked in the kali installer script and didn't find any scripts which can modify or delete this firmware. So we can try to install different firmwares into stock folders. I've attached 2 flashable zips for you. Try the -DHD version first. Flash it in TWRP and reboot your phone. If it doesn't help, then try -STOCK version.
It this will not help then i'm out of options
z3DD3r said:
Well, Wi-Fi firmware in stock android 6.0.1 is located at /system/vendor/firmware/ folder. I've looked in the kali installer script and didn't find any scripts which can modify or delete this firmware. So we can try to install different firmwares into stock folders. I've attached 2 flashable zips for you. Try the -DHD version first. Flash it in TWRP and reboot your phone. If it doesn't help, then try -STOCK version.
It this will not help then i'm out of options
Click to expand...
Click to collapse
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Martisabolt said:
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Click to expand...
Click to collapse
Don't hurry to kill your phone) Try to revert to complete stock 6.0.1 and re-lock bootloader by this instruction:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
And if your wi-fi will not work then yes, something bad happened with hardware
z3DD3r said:
Don't hurry to kill your phone
Click to expand...
Click to collapse
I tried both packages and thery didn't break my ROM. Unhappily they did not help.
I use the Re4son Kernel and can set wlan0 to monitor mode. But airodump is blind then.
@r.mutt @Martisabolt
Hammerhead kernel source (Marshmallow)
These are the complete Nexmon files seperately arranged.
Either you use a proper file manager with root permission, or just use the TWRP fiile manager and insert/copy them into the according sections.Maybe set the correct permission, while you're there and of course know your stuff. :>
Martisabolt said:
Ok, I have tried both. Sadly I guess I'm out of luck and this is now nothing but a bricked phone in my hand. None of these files worked and actually made my phone crash when I tried to load the first file. I tried the second file as well and now I can't turn wifi on. I might as well have to build my own rom or junk this phone
Click to expand...
Click to collapse
Hi Mate, Sorry for the delayed reply. Now i can afford nexus 5. Faced same issue as you. Thanks @z3DD3r for the hint.
Follow below instruction If you want wifi.
*Boot to Twrp
*locate /advanced/filemanager/vendor/firmware
You are there
(Note: 100% you can't see the files as discussed in above thread. But those are hidden(while installing nexmon from nethunter store i have seen those already exists in same folder))
*At bottom you see permisson blue box
*Click the same-select chmod 755-swipe to confirm
Now reboot to system. Here you go.