Related
Hello.
Since this is the first phone I actually trying learn and modify myself I have no experience with possible side effects and such, however what I've read somewhere else, SystemUI.apk as well as framework-res.apk should NOT cause boot loops or no boot at all.
On Nitro however it does both: first it boot loops then after battery pull it doesn't boot at all, hanging at second LG logo.
Then booting into CWM and replacing SystemUI.apk with the original one does not bring phone back to life, in fact restoring whole system partition doesn't do a damn thing. Only restoring full backup brings it back.
So the question is, what the __ is wrong with this phone?
P.S.
I've tried replacing files with Root Explorer as well with adb push. After any .apk files replaced I do chmod 644 and also chown root.root to make sure.
[email protected] said:
Hello.
Since this is the first phone I actually trying learn and modify myself I have no experience with possible side effects and such, however what I've read somewhere else, SystemUI.apk as well as framework-res.apk should NOT cause boot loops or no boot at all.
On Nitro however it does both: first it boot loops then after battery pull it doesn't boot at all, hanging at second LG logo.
Then booting into CWM and replacing SystemUI.apk with the original one does not bring phone back to life, in fact restoring whole system partition doesn't do a damn thing. Only restoring full backup brings it back.
So the question is, what the __ is wrong with this phone?
P.S.
I've tried replacing files with Root Explorer as well with adb push. After any .apk files replaced I do chmod 644 and also chown root.root to make sure.
Click to expand...
Click to collapse
[email protected], I replaced both those files, if im not mistaken, when I applied the percentage battery mod and no carrier mod, but i never went into boot loops or soft brick. What, if i may ask, were you attempting to do replacing those two files?
Ok, here is my observations so far:
It can boot loop if used any android based software to copy files (Root Explorer, ES File Explorer, etc), unless you somehow manage properly chmod and chown the replaced file, otherwise you'll end up with ridiculous ---rw-r-- permissions (0064 - owner can't read write or execute).
In my tests it's pretty much impossible change chmod on replaced SystemUI.apk because of FC on everything.
Next, when something went wrong and SystemUI.apk that was replaced via adb push didn't work resulting in boot animation loop, it can get to the point, that even restoring unmodified file won't bring the system back. Something happening during that loop that destroys/corrupts other stuff in the data partition. When that happens even restoring system partition doesn't work, only restore data or factory reset can help.
As of what I'm doing with SystemUI.apk, I'm trying figure out why the space in the taskbar where clock is, is not dynamic, when you change to 24H mode it wastes so much space. I already tried use the same data from SU640 rom, it didn't change a thing.
And also trying get the CRT ON effect, which will be a beautiful with already implemented CRT OFF
[email protected] said:
Ok, here is my observations so far:
It can boot loop if used any android based software to copy files (Root Explorer, ES File Explorer, etc), unless you somehow manage properly chmod and chown the replaced file, otherwise you'll end up with ridiculous ---rw-r-- permissions (0064 - owner can't read write or execute).
In my tests it's pretty much impossible change chmod on replaced SystemUI.apk because of FC on everything.
Next, when something went wrong and SystemUI.apk that was replaced via adb push didn't work resulting in boot animation loop, it can get to the point, that even restoring unmodified file won't bring the system back. Something happening during that loop that destroys/corrupts other stuff in the data partition. When that happens even restoring system partition doesn't work, only restore data or factory reset can help.
As of what I'm doing with SystemUI.apk, I'm trying figure out why the space in the taskbar where clock is, is not dynamic, when you change to 24H mode it wastes so much space. I already tried use the same data from SU640 rom, it didn't change a thing.
And also trying get the CRT ON effect, which will be a beautiful with already implemented CRT OFF
Click to expand...
Click to collapse
LOL! Now I remember you were the one so anal about that extra space by the clock when you convert to 24h setup haha.
Also, what do you mean get the CRT ON effect? I dont understand what that is
Okay, maybe I'm missing something, but I've been replacing framework-res.apk and SystemUI.apk more than once a day on average every day, and have never had a problem while using root explorer with any bootloops/not booting, etc. You should not have any problems at all changing SystemUI.apk or framework-res.apk as long as you are properly changing their permissions after you have put them in /system/ but BEFORE you have put them in /system/app and /system/framework, respectively. If you are trying to change permissions "after the file has been replaced" that's too late. It's probably corrupt. Must be changed before.
itiskonrad said:
Okay, maybe I'm missing something, but I've been replacing framework-res.apk and SystemUI.apk more than once a day on average every day, and have never had a problem while using root explorer with any bootloops/not booting, etc. You should not have any problems at all changing SystemUI.apk or framework-res.apk as long as you are properly changing their permissions after you have put them in /system/ but BEFORE you have put them in /system/app and /system/framework, respectively. If you are trying to change permissions "after the file has been replaced" that's too late. It's probably corrupt. Must be changed before.
Click to expand...
Click to collapse
You can't change permissions on the file that is not there yet.
The bootloops I'm experiencing is when for example I decompile SystemUI.apk, don't change anything and recompile it back. It worked before but not anymore, and I yet to figure out why. Using apktool v1.4.3
All I could think of is this started happening after I attempted install xUltimate-v2.3.3 to deodex files. It's probably just coincidence though...cause I also tried do recompilling on fresh virtual windows on just unbricked phone files.
It's weird.
[email protected] said:
You can't change permissions on the file that is not there yet.
Click to expand...
Click to collapse
You put the file in /system/ so it IS there. Then you change the permissions. Now that the file has correct permissions, you put it in /system/app or /system/framework and let it overwrite the original, so the INSTANT it replaces the original one it already has the correct permissions. You HAVE to put it into /system/, otherwise you can't change to those permissions, but you need to do it before you overwrite the originals.
Nice, I never thought of that. Thanks!
LG optimus LTE Won't turn on after install CWM
hi, my lg optimus LTE won't turn of after i try to install CWM and try to boot it. Phone is dead now and every time i try turn it on, only the 3 touch button is flashing for couples seconds and went off. Any one can help?? When i try plug it it in the computer it only recognize it as QHUSB_LG (can't get the correct name, don't have my PC with me). PLease help!!
Remove battery, put it back in, then plug the phone into wall charger. Let it charge.
yea i did all that, still only the touch screen button is flashing. Gonna try a different battery and see what happen. Just got this phone less than 2 weeks. Let hope it is a better problem.
[email protected] said:
Nice, I never thought of that. Thanks!
Click to expand...
Click to collapse
[email protected], I made the same mistake but with the framework-res.apk and now my phone is stuck in a bootloop. Were you able to fix the permissions for the file? Or did you have to do a factory reset?
Thanks
Yes, but I had original file at the same directory just renamed and also I had to re-do root while it was boot looping, sometimes I had to repeat the root process 50 times before it succeeded, like killing half a day.
I removed Album as the default picture launcher like done by venkat kamesh (link to original thread is at the end) for other Xperia models following his nice tutorial , after installing you can choose which app will be used for opening your pictures out of the camera.
Updated 27/03/16
Instructions for MM (use the attached file SemcCameraUI-generic-xhdpi-release.apk)
device needs to be rooted
make a backup of your original "/system/priv-app/SemcCameraUI-generic-xhdpi-release/" folder so you can restore the original behaviour if needed.
copy my SemcCameraUI-generic-xhdpi-release.apk to "/system/priv-app/SemcCameraUI-generic-xhdpi-release/" folder to override the original file
change the permissions of SemcCameraUI.apk to the ones the original app has (rw-r--r--):
Code:
chmod 644 SemcCameraUI-generic-xhdpi-release.apk
delete oat folder
reboot - enjoy!
Instructions for LP (use the attached file SemcCameraUI.apk)
device needs to be rooted
make a backup of your original "/system/priv-app/SemcCameraUI" folder so you can restore the original behaviour if needed.
copy my SemcCameraUI.apk to "/system/priv-app/SemcCameraUI/" folder to override the original file
change the permissions of SemcCameraUI.apk to the ones the original app has (rw-r--r--):
Code:
chmod 644 SemcCameraUI.apk
reboot - enjoy!
Big thanks to venkat kamesh!!!
Original threads
http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/mod-camera-album-default-app-t3139667
http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/tut-how-to-remove-album-default-xperia-t3219268
will it work with marshmallow?
No, this version is only working for Lollipop.
I will make a MM version in the following days and post it here.
I'm.using this xposed module to accomplish the same thing.
http://forum.xda-developers.com/xposed/modules/mod-xperia-camera-enhancements-t3260643
I managed to modify the apk, unfortunately it doesn't start any longer, no idea why ... Any hints what could go wrong after recompiling the apk with apktool and cause the app to crash? I did it the same way as with LP ...
civicsr2cool said:
I'm.using this xposed module to accomplish the same thing.
http://forum.xda-developers.com/xposed/modules/mod-xperia-camera-enhancements-t3260643
Click to expand...
Click to collapse
This doesn't work on my MM system, I guess its only for LP ...
Thorstenk said:
This doesn't work on my MM system, I guess its only for LP ...
Click to expand...
Click to collapse
Yeah, I haven't made the jump to mm for a lot of reasons, xposed modules being a big one
Should work by now with MM, see first post for instructions!
Happy Easter
didn't work on mm (32.1.A.A.163), didn't appear in drawer and oat folder didn't recreate himself after reboot, permissions are correctly set, even wiped cache and dalvik/art cache through recovery. is there a problem with the apk ? could you post md5 of SemcCameraUI-generic-xhdpi-release.apk plz
sheraro said:
didn't work on mm (32.1.A.A.163), didn't appear in drawer and oat folder didn't recreate himself after reboot, permissions are correctly set, even wiped cache and dalvik/art cache through recovery. is there a problem with the apk ? could you post md5 of SemcCameraUI-generic-xhdpi-release.apk plz
Click to expand...
Click to collapse
On my device it works without having the oat-folder and as far as I know the oat-folder won't be created again, because the apk is deodexed ...
I just downloaded my file again and did the whole process again and it still works .
Did you do it (copy the file and set the permissions) via adb?
Could you try it again?
md5 is: 43774a75b358b255ca629c0bfd56e289
md5 is correct, I set permissions with total commander, I did it with root explorer too, the permissions are correctly set (rw-,r--,r--) but camera app is nowhere to be found ... I will try with adb and see
The camera is missing after I did this.
Tried it on Marshmallow, can you help bro?
Followed the instructions carefully. Thank you
Tried via adb, doesn't work as well.
Upon checking the file SemcCameraUI-generic-xhdpi-release.apk its still my default apk and not the one i pushed with adb (the one i downloaded here), the oat folder was still there as well. Pretty sure I deleted it via adb as well and no error showed up.
Update: Tried it again via adb, this time SemcCameraUI-generic-xhdpi-release.apk pushed properly with correct permissions and oat folder deleted as well. But the camera is now missing again. Any ideas? Thank you
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Thorstenk said:
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Click to expand...
Click to collapse
Thanks but tried it like 3 times already, no luck still.
Not working for me either on 6.0.1 -.-
Seems like .apk is broken or something (when opening .apk get parsing error )
and when replacing original .apk Camera disappears like the other ones said
Thorstenk said:
I had somehow similar problems that I can't explain ... just copy back your original files including the oat folder and check if its working again (it should) and afterwards try it again. For me it works ...
Click to expand...
Click to collapse
Hello, what about using Xposed to create a module like the one working for Lollipop?
it would be a lot easier for people instead of replacing files, messing with odex files and It could probably support all the MM releases. If i have some time i could try to do it, but i'm not as skilled as you.
Apart from that, thank you a lot for the work! I've been searching this since ever.
modified camera for MM 6.0.1
Herewith modified camera file from 32.2.A.0.224
For me it works like a charm.
Enjoy!!
bruno.trudo said:
Herewith modified camera file from 32.2.A.0.224
For me it works like a charm.
Enjoy!!
Click to expand...
Click to collapse
can you make a new one with .253 plz ?
Sure, I can. Please send me appropriate SemcCameraUI-generic-xhdpi-release.apk file.
I am still on .224
Thanks! Here it is : https://drive.google.com/file/d/0B9nyD39hGfrkTWxOczkwdXZZcnc/view?usp=drivesdk
My device was fine before Rooting importantly the Bluetooth stack was was also fine. However, after rooting all BT Pairings are lost across reboots etc. Just turning BT off then on again causes the issue making it necessary to delete and re-pair every time the device starts. over the last week i've ran various tests, and concluded the issue lies with either the hardware or the stock image i got from Sammobile.com. Being a noob, during my experimentation i have had to flashback to the stock image on several occasions. Only discovering the Bluetooth issue when putting my work to good use and using the device.
Yesterday i tested the theory. Flashed it to stock, booted to OS and skipped all the config disabled WI-FI and DATA so it couldn't pull updates. Tested Bluetooth and the issue is present. The Bluetooth did work correctly before i started rooting it. This is unlikely a hardware issue so can only assume its an issue in the build i have from Sammobile. If any of you have access to a stock pre-installed rom that works that they could give me access to, so i can do some testing or indeed any advice it would be very much appreciated.
Device = Samsung Galaxy Tab S4 (SM-T835 on EE)
PDA = T835XXU2ARJ3
CSC = T835OXM2ARJ3
Many thanks
Colin
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
cbb77 said:
This is known issue once rooted, however it has already been fixed. There is a module that you need to load via Magisk. Search for: libsecure_storage companion for rooted Samsung devices. Load that up and you'll be good to go.
Click to expand...
Click to collapse
thanks for the info, i saw a few threads a few days ago about secure storage and did it manually which didn't help with the issue. similarly neither does the module for Majisk . a case of keep looking i guess. any other suggestions will be very much appreciated
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
cbb77 said:
Hmm, I would try uninstalling and reinstalling again via Magisk to confirm. I have rebooted multiple times and the bluetooth pairings stick for me. I do have T830 vs. the T835 that you have but I wouldn't think that it should matter. Worth another shot anyway.
Click to expand...
Click to collapse
Cheers will give it a go - at this point i have nothing to lose, just taken a fresh backup so nothing ventured nothing gained
its stuck no boot while removing secure_storrage module from majisk
Oddly having tried the suggestion above of removing the majisk module the device no longer boots it gets stuck on the Samsung logo. For some reason the vendor partition is no longer able to mount.. Completed a restore eventually to get it to boot. Disabling the module yields the same result. no vendor partition and no boot. Going back to an earlier backup prior to the module being installed
The plot thickens
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
c6pea said:
Today i'm still trying to find a fix for disappearing Bluetooth devices. Using the Magisc module cases my Tab to stall during boot on the Samsung logo similarly trying to replace the /vendor/lib and /vendor/lib64 binaries manually also causes the system to freeze on the Samsung logo. looking at the binaries and some path file references there in. It would appear as though my tablet is missing some key files or folder so far the following are missing
/data/system/secure_storage/ls_data.db
/dev/.ashem.secure_storage_ashem
/dev/.secure_storage/sd_socket.ro
any of you have any thoughts
Click to expand...
Click to collapse
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Boot failure when LIbs replaced
ashyx said:
You actually only need to replace the libsecure_storage.so libs and set the correct permissions.
Add the following to the build.prop:
ro.securestorage.support=false
Click to expand...
Click to collapse
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
c6pea said:
No matter how i do this, the device failes to boot and gets stuck on the samsung logo.
Install the majsik module through majisk reoot when prompted = device brick
making all the changes manually including the changes to the build.prop in the /vendor partition = device brick on reboot.
Tried Using instructions and librarys from the following post
https://forum.xda-developers.com/sa.../guide-fix-bluetooth-losing-pairings-t3798262
Although, the above post says to replaces the libs in the system folder which serves no purpose but replacing them in the vendor partition causes the device to brick at next boot.
Thanks far the suggestions, Still looking
Click to expand...
Click to collapse
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
ashyx said:
Is this happening with only the storage libs or does it happen if you make any other changes to vendor?
Click to expand...
Click to collapse
Thanks for the assist
It occurs only when the Libs are changed.
Originally using the majsic module to install the libs it couldn't overwrite the files as they are in use. modifying the build.prop seemed to resolve that but as soon as those libs are change either manually through terminal or via the installer i end up with a soft brick LOL
its Bugging me!!!
Interestingly
Once the device hangs.
Simply restoring the vendor partition doesn't fix the boot issue.
In order to get the device to boot I have to restore /data (you don't need to restore /vendor just /data)
oddly restoring the /data partition restores the 2 library files in /vendor to their respective originals
Majisk zip extraction issue
so I have resolved the Bluetooth issue, Rather having majisk install the module i just downloaded it and extracted the contents and discovered that upon zip extraction the contents of each file were appended to themselves. see screenshot "confused.jpg" of the readme.md - so in relation to the library files, the files being installed were double in size hence corrupt.
ie /vendor/lib/secure_storage.so should =308kb the file being insatalled in my /vendor/lib partition was 616kb the 64 bit library was also double the size it should have been.
infarct all the files within the Zip had the same issue.
so i extracted the Zip contents on my pc and transferred the library files via usb. made the relevant changes to build.prop and stopped the secure_storage deamon. Machine now boots and Bluetooth pairings are retained across reboots.
Small Wins
Any one have a clue why the files would double up on content??????
built in zip extractor
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
c6pea said:
the issue i have is with the stock zip extraction tool.
extracting the zip file content on the tablet with winzip. the files are as they should be
Click to expand...
Click to collapse
7zip is the extraction utility you want. Winzip is pants.
ashyx said:
7zip is the extraction utility you want. Winzip is pants.
Click to expand...
Click to collapse
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
c6pea said:
Use winrar on the PC used it for a 15 year haha
only installed winzip to test another extraction tool on the tablet, low and behold the extracted content of the file is as it should be. Unlike the tablets stock zip extractor utility
Click to expand...
Click to collapse
Same for winrar, closed source bloated rubbish.
7zip supports practically every format and totally ad free.
I've tried over 5+ different treble ROMs and the mobile data will not work. My friend @Spaceminer had helped me try to solve it by finding an apns-conf.xml as well as a flashable zip but no luck.
I'm using the Moto G6 Play XT1922-7 Boost Mobile Variant.
I'm sorry I haven't provided much detail to the issue but this basically sums it up.
Thank you for any help.
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Alphita said:
Same problem here with 1922-4 retail variant, i have tried to flash the vendor.img over gsi's via fastboot but it just get stuck in a bootloop. The only option i have is stay in stock pie
Click to expand...
Click to collapse
Did you try to flash the vendor.img on TWRP?
sinkoo1979 said:
Did you try to flash the vendor.img on TWRP?
Click to expand...
Click to collapse
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Alphita said:
Yes and got another bootloop and the 'failed to mount /vendor' message when you try to flash anything. Idk if there's a possible fix for mobile networks
Click to expand...
Click to collapse
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Spaceminer said:
You have to find your correct apns-config.xml, place it in /system/etc and set permissions to 0644. Then reboot, open your mobile network settings and reset your apn.
If you ever want to go from Pie to Oreo, grab your very last Oreo firmware and flash everything like normal. Some things won't flash, and that's okay. If that happens, just skip it and flash the next items in line. When you're done, reboot it normally and let it encrypt at least once. If you don't let it encrypt first it can cause a recovery bootloop and you'll have to flash everything again.
Click to expand...
Click to collapse
How do i set those permissions? Thanks in advance
Alphita said:
How do i set those permissions? Thanks in advance
Click to expand...
Click to collapse
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Spaceminer said:
Use a root explorer, navigate to the file, long press it and select permissions and set them to rw-r--r--. It should prompt you to mount the system automatically to make the changes. Mine does anyhow. (See sceenshot)
Or;
In TWRP, select mount > system. Then select advanced > file manager > navigate to and select the apn file, and you'll have an option to change permissions. Select it, delete the 0000 and enter 0644 then swipe to confirm. Reboot.
Or;
Using an Android Terminal enter;
su
mount -o rw,remount /system
chmod 0644 /system/etc/apns-config.xml
reboot
Click to expand...
Click to collapse
Thanks! I will try this the next time i flash a rom
Would someone be so kind enough to share their BOOST apn.config.xml that the replaced the one on with that does NOT work on these GSI's?? If you do I'll follow you and hit thanks all day. ??
Here's (see screenshot) the closest I've ever gotten far as having data on a gsi. I must have the wrong xml file. I am fully aware of the process described above and have even done it multiple ways after I knew the way described and how I was adding the apn xml was correct and I have zero data.
If someone will attach their apn.config.xml, the one that they acquired data from using the boost Mobile network I'll be extremely thrilled and forever greatful to add it to the thread I made over in guides section so that in the future people can solve this issue fast and get her running and have a jolly day. ? I made that thread (I'll change the name later today) initially to consolidate as much info as I could and put it all in the op so we can be a bit more organized. I just haven't figured out anything else so I can't add to it just yet. ? This would be a great addition if someone would be so cool enough to kick me down some knowledge far as what's the correct apn.config.xml to replace the og one in gsi to get data working. I've deleted the current apn xml and replaced it with the one I have, I've overwritten it, I've tried countless times messing with the telephony.db and I obviously can't do it. Please pleeeaasee post the proper apn xml so I can get this phone going and add to op over there. @Starkiller2
I hope everyone is having a good day. It hot as **** where I'm at today. ??
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Starkiller2 said:
I got nothing on xml. I only ever found one way to get it to work on boost, that was with the sqlite editor.
https://play.google.com/store/apps/details?id=com.dundastech.sqlitemasterlight
Click to expand...
Click to collapse
Vague and unhelpful. Need better directions on that I messed with sqlite editor for days on end swapping out telephony.db things and never did get it going.
Did you swap both of them??
Did you swap other files in telephony.db too?
Details...?
What files exactly did you extract in telephony.db?
Vague comments never help anyone. Better to not post at all then post some two word comment with a link.
I apologise, I'm driving across country and was making an effort to help in the little time I had, but you're right, better to not try at all. Which may be why you aren't getting any answers to your questions. Some info is usually better than none and can sometimes lead you in the right direction, but you won't even get that much snapping at everyone who doesn't immediately solve the problem you have and then rage quitting when you can't do it yourself. It makes people not want to put in any effort. You have 4000 posts I assumed you could figure out how to edit apns with an app from the play store. You're right. I should absolutely stop offering any input at all, but rather I should just start *****ing and whining when I'm not spoon fed like I see so much here.
And as I have posted directions in multiple other threads, I assumed you had done at least a cursory search for your answer(as per forum rules) which would've found those posts but I was apparently wrong there as well.
---------- Post added at 07:00 PM ---------- Previous post was at 06:45 PM ----------
Spaceminer said:
Next time you're running a custom rom and you get data working, you can just copy /system/etc/apns-conf.xml and save it for later. You won't have to mess with any apps after that.
Click to expand...
Click to collapse
Thank you. That's good to know
hi, there is in the web a file apns-conf.xml to download? or sombody take us a backup? Thanks
Hey gang, I too am having issues trying to simply get mobile data working on GSI's. I have a Pixel 3a, and have tried multiple Android 10 GSI's, all of them don't allow me to use mobile data. I have not tried the apns-conf.xml trick yet, as I am unsure if that's the answer if it hasn't worked for others. Android 11 does not use an apns-conf.xml in system/etc/ so I couldn't extract it from my current setup unfortunately. Wish you all luck, post back if you get something working.
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
doid1 said:
not working, moist do you have rooted phone? because only on rooted phones you can do this trick
Click to expand...
Click to collapse
I'll probably flash a ROM this weekend and pull my xml to test this. I have Telus so I unfortunately can't help with the Boost users, but can at least help confirm whether this method works or not.
ok thanks i wait, my phone seems to be dead on 4g.. says: no registration..
I tried everything imaginable and perhaps even the unimaginable .. heheheh .. but the result is always the same: no recording on the 4g, so I'm more and more inclined that it is a hardware failure or even a damage to the eeprom memory because 'I have formatted everything and the mobile phone has recharged everything correctly but it was useless ..
I tried to see that maybe it has a sim locked, but I didn't manage to enter meta mode and try to force it also because only with miracle box there is a guide ... umh ... and I do not stop until I succeed in the objective, and then the next step will be to take a complete image of another mobile phone identical to mine and copy it over it (but it is almost impractical because I cannot find anyone who gives me a full backup of this phone) and then I will brutally try to put another image of another working smartphone on it, leaving only the crucial sectors intact (system, boot, vendor, recovery, preloader, everything else I format it hehehehh) I will know..
Well I have a ROM flashed and found the apns-conf.xml, which is not included on my stock ROMs (10 or 11). Now going to flash a GSI or two and do some tests to see if I can get any data working.
Edit: Couldn't get the apns-conf.xml to work. However, I did find out the some GSI's work right out of the box for my Pixel 3A, those included AOSP 10 / 11 by Phh, and the CAOS R build. Bless, qidroid, havoc booted fine but did not have mobile data working.
New video guide below
VIDEO GUIDE
1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. We will need this later. Do not leave the backup on the device as the next step will wipe the device.
*IF YOU LOOSE THIS PERSIST.IMG BEFORE WE MODIFY IT WITH A CALIBRATION, YOU LOOSE ALL CHANCE OF FIXING THIS YOURSELF*
*IT HOLDS IMPORTANT FP CALIBRATION DATA THAT WE WILL BE OVERWRITTEN IN THE NEXT FEW STEPS*
Note: This requires root
Type this into terminal or ADB shell with root privileges.
Code:
dd if=/dev/block/bootdevice/by-name/persist of=/sdcard/persist.img
Backup the partition to another device. Preferably a PC as you may need one in the later steps.
2. Next we have to restore our OS to an earlier OOS. (10.5.4 is what I used and recomended)
Use the MSMTool to restore your device to 10.5.4.Note: You will loose your unlocked bootloader and will be required to unlock your bootloader once more.
Guide and Source for MSMTool
MSMTool 10.5.4 Download
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
[GUIDE] Unlock Factory Mode *root*
4. Now we need to perform a FP calibration. We want to fail.
Enter Factory Mode as shown in the previous guide. (*#808# in the stock dialer)
Swipe over to "Device Debugging"
Select "Finger print test"
Select "Finger print calibration test(Pure White - 90% Blue)
Select "Start Test"
Keep on going through the tests (You must hold an object or your finger over sensor on all BUT THE BLACK RUBBER TEST of these test for it to work!)
The test will fail and this is what we want. There should be a lot of red lines, if you only have one or two try again.
5. We need to extract the the old broken persist.img
NOTE: It is important that we extract the backed up persist.img as it has been unmodified by our recent calibration. This persist.img although broken still has all our working calibrations on it including Finger Print calibrations.
The way I did this is by opening it extracting it via 7-ZIP on my PC
Once extracted move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.
6. Download a root explorer. I highly recommend 'Solid Explorer' from the Play Store.
Open 'DATA' folder and delete 'gf_persist.so'
Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and place them at /mnt/vendor/persist/
It should ask you if you want to keep the old or new files. Select to keep the new.
Reboot.
7. If you followed all my steps correctly this you should be able to go into settings and add your fingerprints.
Why does this work?
Good question... I think what is happening is something in the persist partition breaks which causes the device to think that the sensor is not calibrated when in fact it still is.
When we start and fail a new calibration this fixes whatever was broken in our partition. But now we have a failed calibration.
So what we do is take the files from our backed up persist partition and move over all the necessary files that have our original calibration. But now our partition has the part of it that wasn't working fixed.
I spent a good many days working on this fix (1-2 hundred hours or so). I hope you can be respectful if you have issues. Please kindly ask below and I'll do my best to help.
Thank you for this!
Absolutely fantastic that you solved it, I RMA,'d mine, but for others this is Highly beneficial......?
I will also thank you for your many hours placed so that others now don't have to RMA.
Well done ......?
antnyhills said:
1. *VERY IMPORTANT* We need to back up your broken persist.img and store it in a safe place. PC preferred. Do not leave the backup on the device as the next step will wipe the device.
Note: This requires root
Type this into terminal or ADB shell with root privileges.
Backup the partition to another device. Preferably a PC as you may need one in the later steps.
2. Next we have to restore our OS to an earlier OOS. (10.5.4 is what I used and recomended)
Use the MSMTool to restore your device to 10.5.4.
Note: You will loose your unlocked bootloader and will be required to unlock your bootloader once more.
Guide and Source for MSMTool
MSMTool 10.5.4 Download
3. Next step is to unlock the built in 'Factory Mode' I have a guide on how to do this below.
[GUIDE] Unlock Factory Mode *root*
4. Now we need to perform a FP calibration. We want to fail.
Enter Factory Mode as shown in the previous guide. (*#801# in the stock dialer)
Swipe over to "Device Debugging"
Select "Finger print test"
Select "Finger print calibration test(Pure White - 90% Blue)
Select "Start Test"
Keep on going through the tests (Do not touch or cover the sensor during any of these tests)
The test will fail and this is what we want.
Reboot.
5. We need to extract the the old broken persist.img
NOTE: It is important that we extract the backed up persist.img as it has been unmodified by our recent calibration. This persist.img although broken still has all our working calibrations on it including Finger Print calibrations.
The way I did this is by opening it extracting it via 7-ZIP on my PC
Once extracted move the 'DATA' folder and the 'ENGINEERMODE' folder to the root of your sdcard.
6. Download a root explorer. I highly recommend 'Solid Explorer' from the Play Store.
Select the 'DATA' and 'ENGINEERMODE' folders you just put on the device and place them at /mnt/vendor/persist/
It should ask you if you want to keep the old or new files. Select to keep the new.
Reboot.
7. If you followed all my steps correctly this you should be able to go into settings and add your fingerprints.
Why does this work?
Good question... I think what is happening is something in the persist partition breaks which causes the device to think that the sensor is not calibrated when in fact it still is.
When we start and fail a new calibration this fixes whatever was broken in our partition. But now we have a failed calibration.
So what we do is take the files from our backed up persist partition and move over all the necessary files that have our original calibration. But now our partition has the part of it that wasn't working fixed.
I spent a good many days working on this fix (1-2 hundred hours or so). I hope you can be respectful if you have issues. Please kindly ask below and I'll do my best to help.
Click to expand...
Click to collapse
Gteat job
Won't be able to try for a few hours but a huge thank you to the op for putting in the work!! You are a hero!!
You linked the MSM tool for the EU variant. I have the international. Does it matter which one we use?
Oops, fixed. Thank you
antnyhills said:
Oops, fixed. Thank you
Click to expand...
Click to collapse
So I went back to 10.5.4 as instructed. Previously on 10.5.10 and backed up persist.img before rolling back. Followed all steps correctly. Fingerprint still gets an enrollment error. I am honestly so confused what I did wrong.
Fischer1234 said:
So I went back to 10.5.4 as instructed. Previously on 10.5.10 and backed up persist.img before rolling back. Followed all steps correctly. Fingerprint still gets an enrollment error. I am honestly so confused what I did wrong.
Click to expand...
Click to collapse
And you made you you replaced all the files in the Data and Engineermode folder?
Will you also take a screenshot of the '"Passed" fingerprint test for me?
No go for me also
antnyhills said:
And you made you you replaced all the files in the Data and Engineermode folder?
Will you also take a screenshot of the '"Passed" fingerprint test for me?
Click to expand...
Click to collapse
Yes, I copied both data and engineer mode folders as instructed. Also, I was dumb and only did one fingerprint test. After going through all of them it did end up failing at the end.
Still wanted to give this a go before sending my phone back to OnePlus for repair.
Edit: Thought maybe upgrading from 10.5.4 to 10.5.10 would fix it after following all instructions, still have a fp enrollment error.
Fischer1234 said:
Yes, I copied both data and engineer mode folders as instructed. Also, I was dumb and only did one fingerprint test. After going through all of them it did end up failing at the end.
Still wanted to give this a go before sending my phone back to OnePlus for repair.
Edit: Thought maybe upgrading from 10.5.4 to 10.5.10 would fix it after following all instructions, still have a fp enrollment error.
Click to expand...
Click to collapse
I'm currently working on a much easier to follow video. Should have that out in a few hours hopefully.
antnyhills said:
I'm currently working on a much easier to follow video. Should have that out in a few hours hopefully.
Click to expand...
Click to collapse
I appreciate the time and effort that went into this. Looking forward to the video!
Post # 1 appears to be missing steps 5&6 (thankfully original is quoted later.
I found mistakes in my guide and have corrected them. Hopefully now it should work for everyone who follows the updated instructions exactly...
Negative for me as well
flick36 said:
Negative for me as well
Click to expand...
Click to collapse
Try my updated guide
antnyhills said:
Try my updated guide
Click to expand...
Click to collapse
already tried, it's a negative again, the only mistake was to delete de ff_persist.so, right?
antnyhills said:
I'm currently working on a much easier to follow video. Should have that out in a few hours hopefully.
Click to expand...
Click to collapse
Ya video will be helpful, coz this is a very specific process and hard to follow ?
flick36 said:
already tried, it's a negative again, the only mistake was to delete de ff_persist.so, right?
Click to expand...
Click to collapse
Old guide said not to touch the sensor during calibration. New one is touch touch on all tests but the black rubber test.
Make sure you see a bunch of red lines after you run the calibration and it fails. Not just one.