Related
Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?
x_Jack_x said:
Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?
Click to expand...
Click to collapse
Possibly that app doesn't support being installed to the sd card? Just a guess.. Maybe you could try app to sd?
kylew1212 said:
Possibly that app doesn't support being installed to the sd card? Just a guess.. Maybe you could try app to sd?
Click to expand...
Click to collapse
It doesnt give me that option.I click on the app ( and its several that are having this issue)It doesnt even give a dload option.As soon as i click the app, it gives that message.Ive already tried changing the lcd resolution.Still same issue.IDK if it the market, the build im using, or my phone is just mad I put android on it..lol.Like the facebook that on it.Facebook works, and said theres a newer version, I click to update to newer. and get that error aswell.Makes no sence to me.
x_Jack_x said:
It doesnt give me that option.I click on the app ( and its several that are having this issue)It doesnt even give a dload option.As soon as i click the app, it gives that message.Ive already tried changing the lcd resolution.Still same issue.IDK if it the market, the build im using, or my phone is just mad I put android on it..lol.Like the facebook that on it.Facebook works, and said theres a newer version, I click to update to newer. and get that error aswell.Makes no sence to me.
Click to expand...
Click to collapse
Something is wrong (obviously) is this the first SD build you've used? Check to see if theirs a newer version and try it because their could have been a bug.. Honestly I would recommend nand install but I understand not everyone wants that. I would have to at least try reinstalling it and possibly a different rom...
Hope that helped some!
Sent from my NexusHD2 using xda premium
Fix Market problem: AmeriCanAndroid HD2 GB2.3.7 CM7.1
x_Jack_x said:
Im dual booting winmo and just installed AmeriCanAndroid ( via SD) .So Since my HD2 is finally runnig android, I went to get words with friends to play with my wife.And it said " Your Device is not compatible with this item".I didnt see anywhere on forums that had to do with this error on HD2.Any help?
Click to expand...
Click to collapse
Install File Expert (file explorer).
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage /system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
Hopefully this works! If not, try changing density to 240 (instead of 160) as many advise this is better. However a 240 density, makes display larger, while 160 is very much similar to what you now have.
(based on this thread: http://forum.xda-developers.com/showthread.php?t=1344334)
I run NAND builds and this is something that I have noticed. For example an app would work just fine with typhoon CM7, but when running Hyperdroid CM7 it would give me the compatibility error like you're getting. My guess is it has something to with how the ROM is cooked, but I could be wrong; I'm still kinda NEWB
Sysifos said:
Install File Expert (file explorer).
Browse to /sdcard/Android/
Click to edit "startup.txt" & chose an editor (I use TED text editor)
Edit the lcd_density=167 to lcd_density=160
Exit editor saving the file
Browse to Internal storage /system/
Long click on "build.prop" and change permissions to get full access to the file.
Long click on "build.prop" and Open as.. text (Using TED text editor)
Scroll all the way down till you find & edit the ro.sf.lcd_density=167 to ro.sf.lcd_density=160
Exit editor saving the file.
Exit File Expert
Open Application Manager and go to Market
Select "Details/Clear cache/Force stop"
Click "Force stop" & "OK"
Click "Clear data" & "OK"
Exit App Manager
Open the Rom Manager app.
Touch "Fix Permissions"
Re-boot
Hopefully this works! If not, try changing density to 240 (instead of 160) as many advise this is better. However a 240 density, makes display larger, while 160 is very much similar to what you now have.
(based on this thread: http://forum.xda-developers.com/showthread.php?t=1344334)
Click to expand...
Click to collapse
I have tried this already.When I try to save the build.prop it has an error, and says unable to save.But when I reboot and go back to build.prop its changed to 240.. go figure.I also tried the market thing by clearing cache and force stop.Also tried ROM manager and fixing the permissions.Still nodda.I guess I can try a diff build.Any suggestions? Wanna do it the SD way.Im kinda new to the phone stuff.So easier is better for me atm.
First of all, the guideline works on SD ROM installation. I never tried NAND cause I need to have dual boot option
As for the "File not saved" warning, before editing the boot.prop remember to change permissions (you've missed a step)! After all changes are done, save and close. Then restore permissions...
Sent from my HTC HD2 using XDA App
Sysifos said:
First of all, the guideline works on SD ROM installation. I never tried NAND cause I need to have dual boot option
As for the "File not saved" warning, before editing the boot.prop remember to change permissions (you've missed a step)! After all changes are done, save and close. Then restore permissions...
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thats probally my issue, the other tut like this i used didnt have the change permission thing.How do I change permission on such file?
After changing density to 160, you also have to change the phone model infos (search for adjusting build.prop to htc vision, but I'm not sure of this can be done in SD builds.
Also, you have to (after changing density) reboot and then force srop market and clear market data and cache.
Altogether, this should do it.
Edit: to be able to rewrite build.prop, get ES task explorer (it's free) and you have settings there, at their bottom is make system writable. Check that.
When I long click build.prop.. theres no option to change permissions.
x_Jack_x said:
When I long click build.prop.. theres no option to change permissions.
Click to expand...
Click to collapse
What file manager do u use?
I use 'File Expert' as file manager and by long press on the file, a pop-up menu appears. It has 'Permissions' at the mid-lower part of the menu. Open it and just enable all-you will fix permissioms at the end..
I don't know how other file managers handle this, but I'm sure they do it somehow!
Sent from my HTC HD2 using XDA App
matoflash said:
After changing density to 160, you also have to change the phone model infos (search for adjusting build.prop to htc vision, but I'm not sure of this can be done in SD builds.
Also, you have to (after changing density) reboot and then force srop market and clear market data and cache.
Altogether, this should do it.
Edit: to be able to rewrite build.prop, get ES task explorer (it's free) and you have settings there, at their bottom is make system writable. Check that.
Click to expand...
Click to collapse
I never changed model infos and works properly.. Can be done on SD builds though.
Sent from my HTC HD2 using XDA App
i use es file explorer.
x_Jack_x said:
i use es file explorer.
Click to expand...
Click to collapse
Go to settings, check root explorer and then check mount system as writable.
Save, reboot, and you should be there. It might ask for superuser permission, which you allow.
matoflash said:
Go to settings, check root explorer and then check mount system as writable.
Save, reboot, and you should be there. It might ask for superuser permission, which you allow.
Click to expand...
Click to collapse
On my es explorer, there is no setting that i can find.
x_Jack_x said:
On my es explorer, there is no setting that i can find.
Click to expand...
Click to collapse
When I click the middle, windows button on my HD2 when in ES explorer, it brings up menu and there is settings right there...
matoflash said:
When I click the middle, windows button on my HD2 when in ES explorer, it brings up menu and there is settings right there...
Click to expand...
Click to collapse
Well, it let me save the build.prop now.. did everything else. Still same error.
x_Jack_x said:
Well, it let me save the build.prop now.. did everything else. Still same error.
Click to expand...
Click to collapse
Here's how my part of my build.prop looks, maybe it will help, you should change it exactly to these:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
(then few lines lower)
ro.product.manufacturer=HTC
(Few more lines lower)
ro.build.product=vision
Plus of course the density to 160.
Save, reboot, clear market data and cache.
I have just checked my market and for me words with friends free is available for download.
So if THIS doesn't work, I give up.
matoflash said:
Here's how my part of my build.prop looks, maybe it will help, you should change it exactly to these:
ro.product.model=HTC Vision
ro.product.brand=tmobile
ro.product.name=vision
ro.product.device=vision
ro.product.board=vision
(then few lines lower)
ro.product.manufacturer=HTC
(Few more lines lower)
ro.build.product=vision
Plus of course the density to 160.
Save, reboot, clear market data and cache.
I have just checked my market and for me words with friends free is available for download.
So if THIS doesn't work, I give up.
Click to expand...
Click to collapse
That would be cool except I havd an HD2 not vision.And the board is leo not vision.Im not a phone DEV person, but somehow that doesnt look correct to me.If I changed my build.prop for htc hd leo to htc vision, it might corrupt my build.Maybe Im wrong, but I got this build out of the HTC HD2 leo android forums.
I'm just taking what txlibre wrote in http://forum.xda-developers.com/showthread.php?t=1715149 and re-displaying it in a format that I think is easier to understand for n00bs
This really isn't that hard TBH IMO
This worked for me on a GS3 locked to Orange UK, and another locked to Three UK. Your Mileage May Vary!!
-----I cannot be held responsible for anything that happens to you or your phone, from carrying out anything I have said!-----
Credits: txlibre, mskip, the person whoever originally wrote these instructions
----------------------------------
VIDEO GUIDE:
Part 1 (A-E) - http://youtu.be/P1H2yUyQ4J8
Part 2 (1-25) - http://youtu.be/uAVbYx68WI4
----------------------------------
Things to do before starting:
A - Make sure your S3 is rooted (http://forum.xda-developers.com/showthread.php?t=1703488).
B - Make a backup copy of the /efs folder on your PC.
C - Also backup your EFS using mskips ToolKit (http://forum.xda-developers.com/showthread.php?t=1703488).
D - Get a Hex Editor (I used Notepad++ with this plugin: http://sourceforge.net/projects/npp...n v0.9.5/HexEditor_0_9_5_UNI_dll.zip/download (just put the dll in the plugins folder of Notepad++)).
E - Install Root Explorer on your phone.
Now for the actual process:
1 - Using Root Explorer, copy the file nv_data.bin file from your phones /efs folder to your PC and open it in Notepad++.
2 - Scroll down and find address 00181460, modify the 01 to 00.
3 - Save the file.
4 - Copy the modified nv_data.bin from your computer back to your phones /efs folder using Root Explorer.
.....(Make sure you keep a copy of this modified file for step 15.)
5 - Once copied to the phone, open Root Explorer and long press on the nv_data.bin file till the menu pops up and select 'Permissions'.
6 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked, and press OK.
7 - Then again, long press on the nv_data.bin file till the menu pops up, and select 'Change owner'.
8 - Change Owner and Group to 1001-Radio and press OK.
9 - Restart your phone.
10 - Once restarted dial *#7465625#, check Network Lock is ON and press OK.
11 - Using Root Explorer, copy the file nv.log from your phones /efs folder to your PC and open it.
12 - You should see something like:
... ..Mon Jun 18 23:34:32 2012: MD5 fail. orignal md5 'e1493854d4d62ff4e123040855f8b2a9' computed md5 'd29d791b193de8b6711445231fb7d427' (rild)
.. ...Mon Jun 18 23:34:32 2012: backup NV restored.
... ..(Your numbers may differ).
13 - Copy the file nv_data.bin.md5 from your phones /efs folder to your PC and open it.
... ..You should see the first number listed in step 12 (in my case e1493854d4d62ff4e123040855f8b2a9).
14 - Copy the second number in step 12 (in my case d29d791b193de8b6711445231fb7d427) and put in the nv_data.bin.md5 file, so it is the only number in there. Now save the file.
15 - Now copy the modified nv_data.bin file (from step 4) and the modified nv_data.bin.md5 (from step 14) back to your /efs folder on your phone.
16 - Once copied, long press on the nv_data.bin file till the menu pops up and select 'Permissions'.
17 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked and press OK.
18 - Then again long press on the nv_data.bin file till the menu pops up and select 'Change owner'.
19 - Change Owner and Group to 1001-Radio and press OK.
20 - Now, long press on the nv_data.bin.md5 file till the menu pops up and select 'Permissions'.
21 - Make sure ONLY the Read, Write and Execute boxes for Owner are ticked and press OK.
22 - Then again long press on the nv_data.bin.md5 file till the menu pops up and select 'Change owner'.
23 - Change Owner and Group to 1001-Radio and press OK.
24 - Restart your phone.
25 - Once restarted dial *#7465625# and check Network Lock is OFF and press OK.
anyone tried this
This is the exact same process I used to unlock my gs2. Unless the address where you modify the the byte is off, I see no reason why this wouldn't work on a gs3.
Sent from my SGH-I897 using Tapatalk 2
any pictures for step 14 or is it pretty self explanatory when you do do it. can you paste it anywhere ?
mox123 said:
anyone tried this
Click to expand...
Click to collapse
I have tried this, and on the original thread, 3 others have used is successfully.
I used this on my wife's phone last night and I'll use it on mine this morning when I get it. Ill do a video
galaxy.S3 said:
any pictures for step 14 or is it pretty self explanatory when you do do it. can you paste it anywhere ?
Click to expand...
Click to collapse
I'll hopefully get a video up later today or tomorrow
can this be undone for warranty if a repair is required.
I'll wait till you post a video.
Sent from my SGH-T769 using XDA Premium App
reaths17 said:
can this be undone for warranty if a repair is required.
Click to expand...
Click to collapse
I would say all you would have to do is repeat the process but in step 2, just overwrite the 00 with a 01.
I will try it out when I get my own GS3 later.
Video guide is up guys
the second vid has been taken down
also, i can't get notepad++ to read the file, it just looks like a load of symbols and no actual text. Any help would be appreciated.
dumb donkey said:
the second vid has been taken down
also, i can't get notepad++ to read the file, it just looks like a load of symbols and no actual text. Any help would be appreciated.
Click to expand...
Click to collapse
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin
vinokirk said:
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin
Click to expand...
Click to collapse
Great...! was able to unlock the phone without the video; just followed the instruction and voila I'm now sim unlock...
vinokirk said:
Ill sort the video when i get home.
make sure the hex plugin .dll is in the right folder
Open the file in NotePad ++
Go to the plugins tab at the top and select the hex plugin
Click to expand...
Click to collapse
i've got notepad++ showing the dll file and also reinstalled it though plugin manager in notepad++ but still the same?
dumb donkey said:
i've got notepad++ showing the dll file and also reinstalled it though plugin manager in notepad++ but still the same?
Click to expand...
Click to collapse
You have to put the .DLL file you just download to this folder of your computer :
C:\Program Files (x86)\Notepad++\plugins...(If that is your installation folder of course)
And Go to:
1.Plugins
2.HEX editor
3.View in Plugin
In Notepad++ bar
armanderli said:
You have to put the .DLL file you just download to this folder of your computer :
C:\Program Files (x86)\Notepad++\plugins...(If that is your installation folder of course)
And Go to:
1.Plugins
2.HEX editor
3.View in Plugin
In Notepad++ bar
Click to expand...
Click to collapse
Thats done it! Thanks bud!
---------- Post added at 06:54 PM ---------- Previous post was at 06:14 PM ----------
Just putting my experience out there for anyone who comes across what i did.
Neither of my nv.log numbers matched the one from the nv_data.bin.md5, but i copied the second number anyway and put ONLY that one in the nv_data.bin.md5 file and follwed the rest of the instructions and it still worked!
I am now on a sim unlocked phone!
Thanx!
EDIT!! i'm currently having problems with 2 efs folders and tthe phone stuck in factory mode. i dont recoment changing if you come across what i did!
EDIT 2! Phone back to normal after i restored original efs folder.. but back to network lock on!
Thanks for taking the time to write this thread, as I have justed ordered a S3 which is locked to the 3 network. So will use your guide when I receive the phone, and save me £10 paying to get the code.
One quick question though, when you say download "root explorer" for a few pence, are you referring to the Root Explorer (File Manager) app at £3?
The other ones that come up are all free, so I assume these wont work with the below process?
dumb donkey said:
Neither of my nv.log numbers matched the one from the nv_data.bin.md5, but i copied the second number anyway and put ONLY that one in the nv_data.bin.md5 file and follwed the rest of the instructions and it still worked!
Click to expand...
Click to collapse
This is also what happened to me when I unlocked my phone. Once the video is up, you'll see
djglenn1337 said:
Thanks for taking the time to write this thread, as I have justed ordered a S3 which is locked to the 3 network. So will use your guide when I receive the phone, and save me £10 paying to get the code.
One quick question though, when you say download "root explorer" for a few pence, are you referring to the Root Explorer (File Manager) app at £3?
The other ones that come up are all free, so I assume these wont work with the below process?
Click to expand...
Click to collapse
I got it for 64p. It must've been a special offer.
dumb donkey said:
EDIT 2! Phone back to normal after i restored original efs folder.. but back to network lock on!
Click to expand...
Click to collapse
I'd try it from the top again.
Make sure you know which files you've modified already and which ones you haven't. The first time i did it, the phone didn't unlock. I found out it's because i copied across an unmodified bin file, doh!
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Hi,
Same thing for me with Root Explorer, instead I use build.prop Editor
EDIT: not fast enough :laugh:
qsec said:
I can do that above with RE, very strange problem you have.
Try a build.prop editor, i used this in the link. It sets correct permissions after editing and so on. Use the pencil icon in the bottom right to edit.
https://play.google.com/store/apps/details?id=com.jrummy.apps.build.prop.editor
Click to expand...
Click to collapse
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Maybe it's related to my root access? TB is showing I'm rooted, but check out my superuser app when I try to update an install new binaries...
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
EniGmA1987 said:
Get rid of Superuser and try SuperSu instead. Sometimes the old Superuser has issues on ROMs since ICS.
Click to expand...
Click to collapse
Downloaded and installed... Removed the old one. Still not letting me edit... Looks an feels like it is but won't enter any characters. At least RE isn't giving me the "too large" error anymore
in_dmand said:
I got it and tried exactly like you said, and while it does pull it up and my keyboard pulls up and I can feel the haptic feedback, no letters will be inserted in deleted...? Really weird.
Click to expand...
Click to collapse
i had the same issue, couldn't figure out why. try replacing a commented line with the code to disable the nav bar
How do I know if it's just a commented line and not necessary to the program?
in_dmand said:
I have rooted my phone and installed cwm recovery with the loki images built in. I am trying to modify my build.prop file so I can hide my soft keys manually and use lmt pie, but when I'm using Root Explorer (after I've mounted it as r/w) and when I open it with a text editor from RE it says "This file is too I large..." and displays a truncate version. It also won't let me save any edits. What am I doing wrong?
Click to expand...
Click to collapse
i had the same issue any help?
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
maxkanick said:
If you are in stock android 4.4.2 dont do it
You will stuck on bootloop
If you still wand to do let copy your build.prop to pc and edit with notebat++ or some program and recopy overwrite to your phone
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
You are right, I have tried to edit it on pc and stuck on a bootloop.
Use build.prop editor app from playstore
_____________________________________Read more write less and be smart
after updating to Kitkat 4.4.2 official I9505XXUFNBE everything working fine except that there is no LTE setting Under the "option>>Connection>>more networks>>mobile Network>>network mode" isn't there suppose to be LTE/WCDMA/GSM (auto connect).. but in my network mode there is only WCDMA/GSM, WCDMA Only and GSM only.. Is there anyone having these issue
Did u update by OTA or u used ODIN?
busylittlebee said:
after updating to Kitkat 4.4.2 official I9505XXUFNBE everything working fine except that there is no LTE setting Under the "option>>Connection>>more networks>>mobile Network>>network mode" isn't there suppose to be LTE/WCDMA/GSM (auto connect).. but in my network mode there is only WCDMA/GSM, WCDMA Only and GSM only.. Is there anyone having these issue
Click to expand...
Click to collapse
Is your phone rooted mate? well if your phone is rooted then do this to enable it Open root explorer then Data >property>persist.radio.lteon.xml open the file in Text Editor and change the value to true save then reboot.
I too have gone LTE
Same here... My menu only shows:
*3G/2G (auto connect)
*2G only
sorry for the late reply guys.. and thanx for the response..
Joku1981 said:
Did u update by OTA or u used ODIN?
Click to expand...
Click to collapse
no.. I Use ODIN
Repulsa said:
Is your phone rooted mate? well if your phone is rooted then do this to enable it Open root explorer then Data >property>persist.radio.lteon.xml open the file in Text Editor and change the value to true save then reboot.
Click to expand...
Click to collapse
yes it rooted.. I'll try your suggestion latter and let you know if it works.. thank you.. but now I just re-flash my phonei I use cf autoroot before and my phone become so sluggish and the rotating screen ,air gsture and air view is not working, dont know what I did wrong
busylittlebee said:
sorry for the late reply guys.. and thanx for the response..
no.. I Use ODIN
yes it rooted.. I'll try your suggestion latter and let you know if it works.. thank you.. but now I just re-flash my phonei I use cf autoroot before and my phone become so sluggish and the rotating screen ,air gsture and air view is not working, dont know what I did wrong
Click to expand...
Click to collapse
Try to reflash the rom once again man or do a factory reset/wipe cache in recovery if your having an issue.
Repulsa said:
Is your phone rooted mate? well if your phone is rooted then do this to enable it Open root explorer then Data >property>persist.radio.lteon.xml open the file in Text Editor and change the value to true save then reboot.
Click to expand...
Click to collapse
hi repulsa.. I've try your method.. but it I can't make it works..
"Root File manager >> home (logo) directory >> data/ >>property/ >> persist.radio.lteon" I try a couple of text editor that i can find on google play to open it but fail.. it say file canot be open (Jota, Jota+ text editor ,axel,920 text editor)
any suggestion for text editor to use..? thank you and sorry for the english?
busylittlebee said:
hi repulsa.. I've try your method.. but it I can't make it works..
"Root File manager >> home (logo) directory >> data/ >>property/ >> persist.radio.lteon" I try a couple of text editor that i can find on google play to open it but fail.. it say file canot be open (Jota, Jota+ text editor ,axel,920 text editor)
any suggestion for text editor to use..? thank you and sorry for the english?
Click to expand...
Click to collapse
Im using root explorer bro , Maybe your having this problem because your not Granting/Permission the SuperSu ?
Repulsa said:
Im using root explorer bro , Maybe your having this problem because your not Granting/Permission the SuperSu ?
Click to expand...
Click to collapse
I found a file explorer that have a root access and a text editor (FX root explorer) i've been granted root acces by SU and manage to open and edit the persist.radio.lteon and replace the existing file. do the restart but nothing happen on my lte setting.. still don't have LTE/WCDMA/GSM option..
busylittlebee said:
I found a file explorer that have a root access and a text editor (FX root explorer) i've been granted root acces by SU and manage to open and edit the persist.radio.lteon and replace the existing file. do the restart but nothing happen on my lte setting.. still don't have LTE/WCDMA/GSM option..
Click to expand...
Click to collapse
I hope you did save the file .. when you restart your Phone.. Anyways If you have a Custom recovery ie: Philz or TWRP try to download and flash this file Via recovery.. but if you dont have a custom recovery or the file doesnt work after flashing , I hope someone can help you with this issue mate .
I figured this out ... Go to more networks ...do search for netwoks ...when it finds networks do a select automaticly .. Dont choose your network ..For some reason it selects gsm/umts if you select it yourself
Im rooted using a i9505 rom using an ATT branded GS4 unlocked using tmobile Sim LOL
hi iam nikhil
i have not seen persist.radio.lteon.xml file in rootbrowser in samsung s4 i9500what should i do
After you have rooted the device completely, go to Google Play and install 'ES file explorer'. Open the app, and press the menu key on the device and you will get a panel to your left on the screen. Scroll down and enable Rootexplorer (you will ask to grant permission by the SuperSU app since you have rooted, so give permission). Now use the search function and find the file with this EXACT name 'persist.radio.lteon' and delete it. Please make sure you are deleting this exact file. Don't delete anything else and end up bricking your device. After deleting restart the phone and that's it! You will have the LTE/WCDMA/GSM option in the network mode once you are booted and you will receive 4G signals if you are in an area with LTE coverage.
nikhil.73 said:
hi iam nikhil
i have not seen persist.radio.lteon.xml file in rootbrowser in samsung s4 i9500what should i do
Click to expand...
Click to collapse
Get another device. The I9500 does not have LTE, and before you ask, you cannot enable it because the hardware is not present.
@chashmaa: Your advice works only if the device has a LTE radio. The I9500 nikhil has doesn't.
My post for busylittlebee(post 1).
@chashmaa: Why would you reply to a post that's nearly two years old? Besides, based upon the time stamps, it appeared you were replying to @nikhil.73.
Big sorry.
OK sir thank u
persist.radio.lteon.xml
I root my phon but there isn't this file in data>property
What i do??
First of all credit to pomeroythomas for his post which I am basically just relaying here.
This is for anyone who wishes to use the native call recorder but it is currently disabled for them. For example in the USA federal laws state that call recording is legal and it is legal in most states but because some states require two party consent Lineage OS has decided to disabled it by default so this "HOW TO" is needed to enable it. You are ultimately the one responsible to follow any laws where you live.
This requires you to have root access. You may be able to accomplish the same with adb without root though.
You will need APK Easy Tool. For more information on APK Easy Tool visit the original thread here. I personally just used the portable version.
You will also need to know your carriers MCC code which you can find here.
1. There are many different ways to get the Dialer.apk from your device. Personally I use Root Explorer. Copy your Dialer.apk located on your device at "/system/priv-app/Dialer" to your sdcard and then connect your device to your PC and copy the Dialer.apk to it.
2. Now open "apkeasytool.exe and click "Sel.APK/JAR" and open your Dialer.apk and select "Decompile".
3. Once it has finished decompiling open the folder "1-Decompiled APKs" located in the APK Easy Tool folder.
4. The file we are looking for is in "Dialer/res/" this is where you need your MCC code. Personally I am on T-Mobile so the folder I need is "values-mcc310" most US carriers also use this same MCC code ie. Sprint, Verizon, AT&T
5. Once inside your carriers MCC folder you want to open "Bools.xml" in notepad and change
Code:
<bool name="call_recording_enabled">false</bool>
to
Code:
<bool name="call_recording_enabled">true</bool>
and then save it.
6. Now go back to APK Easy Tool and click "Compile"
7. Once it has finished your new Dialer.apk will be located in "2-Recomiled APKs". Copy that back over to your device
8. Navigate to "/system/priv-app/Dialer" and rename your current Dialer.apk to "Dialer.apk.bak" and replace it with your modified one and change the permissions to "rw-r-r" or "0644". and then reboot.
Thats it. Now to test make a phone call and you should now have the record button available, the first time you press it you will be greeted with a message telling you that you are responsible for compliance with any laws, then you can hit "RECORD CALL" and then give Dialer the permissions it needs. Your recording will be saved to a folder named "CallRecordings".
This will not survive an update but you can keep the modified Dialer.apk on your SDcard and just repeat step 8 after an update.
Joe333x said:
4. The file we are looking for is in "Dialer/res/" this is where you need your MCC code. Personally I am on T-Mobile so the folder I need is "values-mcc310" most US carriers also use this same MCC code ie. Sprint, Verizon, AT&T
5. Once inside your carriers MCC folder you want to open "Bools.xml" in notepad and change
Code:
<bool name="call_recording_enabled">false</bool>
to
Code:
<bool name="call_recording_enabled">true</bool>
and then save it.
Click to expand...
Click to collapse
I'm in kccat6, official LineageOS - Samsung Galaxy S5 Plus (G901F).
This procedure seems simple, but I have my carrier in Spain, where recording is allowed, and there is no MCC folder with its number.
I've found related settings (and I changed them) in
Dialer/res/values/bools.xml (changed false to true)
Code:
<bool name="call_recording_enabled">true</bool>
and
Dialer/res/values/integers.xml (changed 1 to 4)
Code:
integer name="call_recording_audio_source">4</integer>
Compiled (signed), copied, checked permissions, wiped cache & dalvik, rebooted and there isn't a record button when calling.
Also there's a "Dialer/res/values-es" folder, but there isn't a "Dialer/res/values-mcc214-mnc4" folder. I created that folder and copied the files bools.xml and integers.xml, with only the above contents inside them. Compiled, copied, etc... and there isn't a record button.
Am I missing something?
Ochoceros, its worked for me. I am using Lowi, MCC 214. The only stick, that its needed to press "record" button with every call, its doesnt records automaticali. I have created the folder with MMC code in his name and only the bools.xml file, without integers.
LOS made changes to native call recording, the phone checks what country your in instead of the MCC code. Has anyone figured out how to enable call recording again?
I found the new file, where you can edit the call recording states.
Follow the instruction from the first post, except don't follow step 4 and 5.
Go to "Dialer/res/xml/call_record_states.xml" and set everything to true (easiest way).
Now continue on step 6.
Now how about auto recording
Nice work Vanta-Chan!
eric93se said:
Now how about auto recording
Nice work Vanta-Chan!
Click to expand...
Click to collapse
I wish I could program, but we either have to wait for the official developers of LOS, or hope for a kind soul who does that with a tutorial :angel:
Interestingly the version of dialer.apk from the first post (around early november 2019) had auto dialing. I'm pretty sure that dialer version doesn't work with the latest LOS roms (I could be wrong).
I have a screenshot of it since I was trying to sell my LG G3.
eric93se said:
Interestingly the version of dialer.apk from the first post (around early november 2019) had auto dialing. I'm pretty sure that dialer version doesn't work with the latest LOS roms (I could be wrong).
I have a screenshot of it since I was trying to sell my LG G3.
Click to expand...
Click to collapse
If you somehow could retrieve that Dialer.apk, which has the auto-record function, I could try to reimplement it to the newer versions.
can anyone upload the apk, i try recompiling but always get an exit code = 1 error.
n950 said:
can anyone upload the apk, i try recompiling but always get an exit code = 1 error.
Click to expand...
Click to collapse
Can't upload it directly to XDA, file is too big (~33Mb), but here's a link:
https://workupload.com/file/URfFtrAU
Mirror: https://anonfile.com/zd6eO0b4oa/Dialer_apk
Vanta-Chan said:
Can't upload it directly to XDA, file is too big (~33Mb), but here's a link:
https://workupload.com/file/URfFtrAU
Mirror: https://anonfile.com/zd6eO0b4oa/Dialer_apk
Click to expand...
Click to collapse
Thank u )
I can recommend the EdXposed Module XCallRecordingSettings.
https://github.com/iptux/XCallRecording-xposed
https://repo.xposed.info/module/net.iptux.xposed.callrecording
Version 1.0.14 supports LOS 16
Works great for me and easy to setup!
I know, it's not the native way to setup, but I guess this Module justs enables the call recording the natural way in LOS
textmarker007 said:
I can recommend the EdXposed Module XCallRecordingSettings.
https://github.com/iptux/XCallRecording-xposed
https://repo.xposed.info/module/net.iptux.xposed.callrecording
Version 1.0.14 supports LOS 16
Works great for me and easy to setup!
I know, it's not the native way to setup, but I guess this Module justs enables the call recording the natural way in LOS
Click to expand...
Click to collapse
This would mean not only have to install your mentioned app, but also edxposed etc.
Which, IMHO slows down the s5
andreoide said:
This would mean not only have to install your mentioned app, but also edxposed etc.
Which, IMHO slows down the s5
Click to expand...
Click to collapse
Add:
On my g900f sound is great, on g910f sound is very weak, uninstalled all exposed from g901f because like I said, sound is bad and edxposed slows down performance very much.
Add: (march 1)
Anyone know why sound is no good on g901f?
What might cause it, and how to fix (if any exists)?
I have tried all of these steps and it didn't work i still can't get record button i have also tried the solutions in the replies and nothing worked how can i enable the recording in lineage os 16
The phone is GT-I9505
the country i live in is Egypt so can anyone help me please
I'm using lineage 17.1 which uses Google dialer, this method doesn't work.
Can you please describe how to make it work on Google dialer.
Sent from my MI 9 using Tapatalk
Vanta-Chan said:
If you somehow could retrieve that Dialer.apk, which has the auto-record function, I could try to reimplement it to the newer versions.
Click to expand...
Click to collapse
Shouldn't it be on GitHub history?
You bet!
Thanks for the credit, man. Hope this helps y'all.
Joe333x said:
First of all credit to pomeroythomas for his post which I am basically just relaying here.
This is for anyone who wishes to use the native call recorder but it is currently disabled for them. For example in the USA federal laws state that call recording is legal and it is legal in most states but because some states require two party consent Lineage OS has decided to disabled it by default so this "HOW TO" is needed to enable it. You are ultimately the one responsible to follow any laws where you live.
This requires you to have root access. You may be able to accomplish the same with adb without root though.
You will need APK Easy Tool. For more information on APK Easy Tool visit the original thread here. I personally just used the portable version.
You will also need to know your carriers MCC code which you can find here.
1. There are many different ways to get the Dialer.apk from your device. Personally I use Root Explorer. Copy your Dialer.apk located on your device at "/system/priv-app/Dialer" to your sdcard and then connect your device to your PC and copy the Dialer.apk to it.
2. Now open "apkeasytool.exe and click "Sel.APK/JAR" and open your Dialer.apk and select "Decompile".
3. Once it has finished decompiling open the folder "1-Decompiled APKs" located in the APK Easy Tool folder.
4. The file we are looking for is in "Dialer/res/" this is where you need your MCC code. Personally I am on T-Mobile so the folder I need is "values-mcc310" most US carriers also use this same MCC code ie. Sprint, Verizon, AT&T
5. Once inside your carriers MCC folder you want to open "Bools.xml" in notepad and change
Code:
<bool name="call_recording_enabled">false</bool>
to
Code:
<bool name="call_recording_enabled">true</bool>
and then save it.
6. Now go back to APK Easy Tool and click "Compile"
7. Once it has finished your new Dialer.apk will be located in "2-Recomiled APKs". Copy that back over to your device
8. Navigate to "/system/priv-app/Dialer" and rename your current Dialer.apk to "Dialer.apk.bak" and replace it with your modified one and change the permissions to "rw-r-r" or "0644". and then reboot.
Thats it. Now to test make a phone call and you should now have the record button available, the first time you press it you will be greeted with a message telling you that you are responsible for compliance with any laws, then you can hit "RECORD CALL" and then give Dialer the permissions it needs. Your recording will be saved to a folder named "CallRecordings".
This will not survive an update but you can keep the modified Dialer.apk on your SDcard and just repeat step 8 after an update.
Click to expand...
Click to collapse
pomeroythomas said:
Thanks for the credit, man. Hope this helps y'all.
.
5. Once inside your carriers MCC folder you want to open "Bools.xml" in notepad and change to
Click to expand...
Click to collapse
The last code is given twice, but my guess is change that only once?
(Just to be sure...)
Thanks, I'll go try one of these days, and report back here later....
( phone: Samsung galaxy S5 plus, SM- G901F )
The dialer.apk, I don't think I have the original from lineage, I installed the dialer from google play a while ago. How to obtain the original? Or does it work withe google dialer also?