Related
Hey all,
Loving my nice shiny new O2X but having some problems using the LG On-Screen Phone software, the one that lets you control your phone from your PC. I have it all installed and followed the user guide but when I attempt to connect to the phone after putting the password in (still 0000 as default), I press next to connect and can see that it causes the phone to wake up and a screen icon appear in its notification bar but then I get an error on the software saying "An error occurred while creating the OSP window after downloading the skin file from the mobile phone" this messages times out then it shows "Failed to connect to phone" and I'm back to the password screen.
Obviously some communication must be occurring for the phone to wake up and try to start the appropriate app but it just isn't working.
So far I have tried it with USB debugging on and off and have also tried reinstalling the USB drivers on the PC, no luck.
Has anyone else experienced this or have any advice?
Thanks
Russ
Hmph, tried this on 3 PCs now with the same results
I‘m only able to get it run for once, the other times are having problem like yours.
Sent from my LG-P990 using XDA App
Slightly better off than me but glad I'm not alone!
I emailed LG support but I got a cut and paste template response telling me how to download the LG Suite in the first place, which I have obviously already done!
Hi, I just tried again now and it worked... here I attached a screen shot..
then after quitting, it's back to normal (i.e. can't connect again!).. it's weird
Hmph, just tried flashing ROM to MCR Fr11 and still have the same issue
Just discovered a log file in My Documents saying this...
13:39:39 - -----------------------
13:39:39 - OSP_ConnectService
13:39:39 - type:1, param:8
13:39:39 - OnOspEvent::OSP_CONTEXT_UPDATE_EVT
13:39:39 - OnOspEvent::OSP_CONTEXT_TYPE_EDIT_MODE
13:39:39 - Edit Mode : True
13:39:39 - OnOspEvent::OSP_CONTEXT_UPDATE_EVT
13:39:40 - OnOspEvent::OSP_AUTHENTICATE_RESULT_EVT
13:39:40 - OnOspEvent::OSP_CONNECTED_EVT
13:39:40 - connect value : 0
13:39:40 - OnOspEvent::OSP_GET_MODEL_EVT
13:39:40 - COSPScreenWnd:arsingPhoneXML - File not found(\\boxserver\Russell Oakes\LG OSP\Phone_skin\P990\P990.xml)
13:39:40 - OnOspEvent::OSP_FTP_PROGRESS_EVT
13:39:40 - OnOspEvent::OSP_FTP_PROGRESS_EVT
13:39:40 - OnOspEvent::OSP_FTP_PROGRESS_EVT
13:39:40 - OnOspEvent::OSP_FTP_PROGRESS_EVT
13:39:40 - OnOspEvent::OSP_FTP_PROGRESS_EVT
13:39:40 - OnOspEvent::OSP_FTP_GET_EVT (SUCCESS!)
13:39:40 - COSPScreenWnd:arsingPhoneXML - File not found(\\boxserver\Russell Oakes\LG OSP\Phone_skin\P990\P990.xml)
13:39:43 - OnOspEvent::OSP_DISCONNECTED_EVT
13:39:43 - OSP_Connect : Fail
Which would suggest that a file isn't being successfully copied to the PC, could someone upload the contents of their "LG OSP\Phone_skin\P990" folder from My Documents?
Thanks
Woohooo got it working!
I had to go to /system/media and copy off the file osp_skin_p990.zip to my PC and extract it to the "LG OSP\Phone_skin\P990" folder in My Documents and then it worked!
So it looks like the program was unable to automatically download and extract this file for some reason, just needed a little manual intervention. Strange that it happened on 3 PCs though, which would suggest that maybe the file is located somewhere unexpected on my handset?
There is another thing that is not really user friendly.
On the connexion Assistant, if the model of the phone is not selected on the bottom right corner combo box, the connexion is not working but the error is not really usefull.
I had to copy the files in "My Documents\LG OSP\Phone_skin\P990" (thank you roakes ) and then had to select the model P990 in the combo box and then it worked.
It is working in USB and Bluetooth
Hello guys!
Im also having this problem, but my system/media is empty! And my "My Documents/LG OSP/Phone_skin" does not contains P990 Can anyone upload or tell me where I can get the contents?
same here... i've copied P970 phone skin, installed all LG drivers... no luck. still cannot connect phone to OSP. really suck!
I have a worse situation here, even if all my drivers are installed i still get a failed to connect to mobile phone message everytime I try on the computer
lws803 said:
I have a worse situation here, even if all my drivers are installed i still get a failed to connect to mobile phone message everytime I try on the computer
Click to expand...
Click to collapse
Same problem
Any news ??? did you solve it ?
Edit:
ok with unistall lg programs and reinstall lg pc suite and from that install OSP
Edit :
There is no way to fix it now...
This is the error in the OSP log :
16:39:00 - OSP_ConnectService
16:39:00 - type:1, param:27
16:39:04 - OnOspEvent::OSP_DISCONNECTED_EVT
16:39:04 - connect value : 1
16:39:04 - OSP_Connect : Fail
16:39:17 - OSP Start : Setup version 0.4.27.20110628
16:39:19 - LGBTCON_IPC_IsInitialized() or LGBTCON_IPC_InitializePCBT() function fail
Try rebooting your phone, works for me every time
Sent from my Optimus 2X using XDA App
try to disable usb debuging if it is enabled
In my case both on froyo & gb it wont give me any prob, I think u can try to install updated version of osp & USB drivers.
Sent from my Optimus 2X using XDA App
I have found a way around this.
I own a LGP930 and also got this "skin error" problem. I noticed in the
My Documents\LG OSP\Phone_skin directory, there were other skins already present. Now these are simply image files that will "contour" your phone's screen.
I looked up the images in a folder labeled "720x1280" and they seemed pretty similar. Along with these images there is an xml file that (I am only assuming here) manages the logic of the image names and placement on the display. My folder, labeled "P930" (my phone, in other cases, your own model) was empty .
The solution:
1. Copy the files from the models available that represent the best your phone and paste them into your model's folder. If it does not exist, create it.
2. Rename the xml file to your model's name, in my case it was P930, which is also the folders name (not sure if this is critical, but to be safe just do so).
3. Open the file with notepad (notepad>open or right-click then edit).
you should see these tags:
Code:
<on-screen-phone id="P930" version="2.0">
<model>LG-P930</model>
<name>P930</name>
I renamed all these (there were named "720X1280"). Fill these tags with the model of your phone, again.
4. Run the software. It should now be working. This is all model-specific, so it will be different everytime and if you do not have the exact name it won't load.
5. Optional: Edit the images to whatever you like as long as they have the same name and have fun.
Hope this helps out anyone who will find this topic.
Cheers,
Sphero09
Sphero09 said:
I have found a way around this.
I own a LGP930 and also got this "skin error" problem. I noticed in the
My Documents\LG OSP\Phone_skin directory, there were other skins already present. Now these are simply image files that will "contour" your phone's screen.
I looked up the images in a folder labeled "720x1280" and they seemed pretty similar. Along with these images there is an xml file that (I am only assuming here) manages the logic of the image names and placement on the display. My folder, labeled "P930" (my phone, in other cases, your own model) was empty .
The solution:
1. Copy the files from the models available that represent the best your phone and paste them into your model's folder. If it does not exist, create it.
2. Rename the xml file to your model's name, in my case it was P930, which is also the folders name (not sure if this is critical, but to be safe just do so).
3. Open the file with notepad (notepad>open or right-click then edit).
you should see these tags:
Code:
<on-screen-phone id="P930" version="2.0">
<model>LG-P930</model>
<name>P930</name>
I renamed all these (there were named "720X1280"). Fill these tags with the model of your phone, again.
4. Run the software. It should now be working. This is all model-specific, so it will be different everytime and if you do not have the exact name it won't load.
5. Optional: Edit the images to whatever you like as long as they have the same name and have fun.
Hope this helps out anyone who will find this topic.
Cheers,
Sphero09
Click to expand...
Click to collapse
Good job , my lg f320K work finel
F120L
keilien said:
Hello guys!
Im also having this problem, but my system/media is empty! And my "My Documents/LG OSP/Phone_skin" does not contains P990 Can anyone upload or tell me where I can get the contents?
Click to expand...
Click to collapse
In my case, just delete the folder LG OSP and then run the software again. A new one will be created automatically.
I just got an LG K7 MS330 from metro to upgrade from my LG F6 and I can no longer use On screen phone. I attempted what I interpreted this process to be and had no results. If you know a way please tell me.
The usual "LG Software" option in the connection type menu is not on the newer K7 as it was on the older F6, it only allows Charge only, MTP and PTP.
Please help
Hi there !
Maybe is too soon to ask, but 2 days after I rooted my XT860 (oneclick way), it reboot itself (while in stand-by !) and now I am stuck in a boot loop . Unfortunately, USB Debug is not enabled and already tried factory reset with no success ("recover" type included :-/). So I think that the only way fix it now will be SBF.
I didn´t remove anything from /system (but install tons of applications via androidmarket), so I´m no really sure if it is really a software problem. During de boot loop I see some color lines/retangles/patterns over "M logo pulsing" and then, the phone freezes and reboot again (Is this behavior common when the phone is bootlooping ? )
If anybody have Bell XT860 SPF around, please, let me know. Suggestions will be also welcome.
Regards !
Claudio Cuqui
My XT860 took the root process fine, guess you didn't have such good luck.
May I ask what your Build version is for the Canadian phone?
Blur_Version.#.#.#.Bell.en.CA
Something like that.
Sure !
5.1.544.XT860.BellMobility.en.CA
If you need any further informations, let me know.
Thanks for your time,
Claudio
Thank you. I'm just trying to see which phone versions are out there at the moment.
cuqui said:
Sure !
5.1.544.XT860.BellMobility.en.CA
If you need any further informations, let me know.
Thanks for your time,
Claudio
Click to expand...
Click to collapse
I would also love an SBF for Bell Mobillity's XT860. I created an annoying glitch when I removed some of the system apps and would love to start from scratch -- simply freezing apps I don't want rather than deleting...
I'd settle for an appliable update, the leaked one wont verify the sig for me because it's not from bell I assume
Willis111 said:
I'd settle for an appliable update, the leaked one wont verify the sig for me because it's not from bell I assume
Click to expand...
Click to collapse
I'm worried that an update might have issues with my modified/rooted phone and would love to restore it to it's original state PRIOR to the update that is coming from Bell.
AFAIK, when you update your phone, unless you change A LOT in /system, in the end of day, an updated follow by a factory restore (menu option) will have almost the same effect that a SBF. My biggest concern is, if I can still be able to root it after the update (100% sure that it will be lost after update) and, for me, this is a big problem since I need it for openvpn :-/ Really don´t know why google don´t put it built in as it does with other vpns......
Regards !
Claudio
I read in a thread here that there were a few root methods for the droid 3 that weren't made public so they wouldn't be patched even if the current one is. Only rumor though, no one has said for sure that they have another working root method, just a guy who thinks he knows a guy who said ....
Good to know that they have a plan B in the case of current root method be patched by a new release ;-)
Regards !
Claudio
Same version on mine. I guess there is only one version available (that one.)
I am very much hoping there will be an SBF released for our phones soon. I am reluctant of hacking/altering stuff, because there is no secure way back and I don't want to be stuck with crappy working camera, or car dock battery drain issues. Hopefully our "safety net" will arrive soon!
Sent from my XT860 using Tapatalk
In the meantime, we have a system dump provided here:
http://forum.xda-developers.com/showthread.php?t=1255647
UnhappyDroid3User said:
I'm worried that an update might have issues with my modified/rooted phone and would love to restore it to it's original state PRIOR to the update that is coming from Bell.
Click to expand...
Click to collapse
Do you know of an update coming from bell? I tried to find information on it as I know Verizon is releasing one soon(apparently soak test starts tomorrow). I would love to have the cell standby battery issue fixed.
Sent from my rooted xt860
Don't hold your breath.. Motorola tends to update Verizon's models first, then the rest of the world. I guess due to Verizon being their 'biggest customer'. Maybe in 3-4 months we'll see something (trying to remember how long it took them to release some fixes for Milestone 1... if I remember right we saw Froyo on Milestone 1 about 6 months after OG Droid or wasn't it longer?)
leobg said:
Don't hold your breath.. Motorola tends to update Verizon's models first, then the rest of the world. I guess due to Verizon being their 'biggest customer'. Maybe in 3-4 months we'll see something (trying to remember how long it took them to release some fixes for Milestone 1... if I remember right we saw Froyo on Milestone 1 about 6 months after OG Droid or wasn't it longer?)
Click to expand...
Click to collapse
I think it's actually because providers (verizon, bell etc) buy the updated software off of manufacturers (motorola, htc etc). That's exactly why I'm not holding my breath either, I've got a bell phone and although they've made a huge leap in getting new phones recently I'm reluctant to say the same about software updates.
Well, since developers are busy cooking some new roms from verizon´s droid3 , and we hear only silence from Bell Canada about a possible update for our XT860 until now, I decide to try somethings in my already bricked phone (since I have nothing to loose). I have experience with linux and take some time studying the images available from verizon. The idea here is the following:
Get backups from the following directories (and all sub-directories) from a WORKING / ROOTED / *BELL* XT860:
- app
- bin
- etc
- fonts
- framework
- lib
- media
- preinstall
- tts
- usr
- xbin
- build.prop (this is a file - a VERY IMPORTANT ONE - not a directory)
preinstall partition should have only the 2 games and some videos explaining how the phone works (and they take a considerable amount of space, so I think we can work on it latter). One important thing to note is that the backup should be made using a software that is capable to keep permissions/ownership of the files and handle symlinks properly. Since I´m new to android I don´t know which software would meet these requirements (tar definitely will do - so, if you rooted your phone you should trying something like busybox tar -cpzf /pathofyoursdcard/dump.tgz /app /bin /build.prop /etc /fonts /framework /lib /media /preinstall /tts /usr /xbin - will work - maybe titanium do this as well (?). This will take a while. After that, I will use system.img and preinstall.img structure available for verizon to rebuild one similar for XT860 using the files from dump.tgz.
Once I have build these 2 files, I intent to flash them using fastboot on linux (already available here in XDA forum).
Assuming that I just messed with files in those 2 partitions (like, I think, most of XT860´s owners), they should suffice for bring the phones back from the death (hopefully !).
Here is the problem: since my XT860 is bricked, I don´t have how to backup those files on my own. So, I, if any good soul could create it and make it available in some place (dropbox, megaupload, etc), I will be very grateful and, of course, promise if that idea works (and don´t make my phone crash and burn , I will make those images available for everyone brave enough to try them
Regards !
Claudio
PS: if anyone see something terrible wrong with this strategy, please, let me know
cuqui said:
Well, since developers are busy cooking some new roms from verizon´s droid3 , and we hear only silence from Bell Canada about a possible update for our XT860 until now, I decide to try somethings in my already bricked phone (since I have nothing to loose). I have experience with linux and take some time studying the images available from verizon. The idea here is the following:
Get backups from the following directories (and all sub-directories) from a WORKING / ROOTED / *BELL* XT860:
- app
- bin
- etc
- fonts
- framework
- lib
- media
- preinstall
- tts
- usr
- xbin
- build.prop (this is a file - a VERY IMPORTANT ONE - not a directory)
preinstall partition should have only the 2 games and some videos explaining how the phone works (and they take a considerable amount of space, so I think we can work on it latter). One important thing to note is that the backup should be made using a software that is capable to keep permissions/ownership of the files and handle symlinks properly. Since I´m new to android I don´t know which software would meet these requirements (tar definitely will do - so, if you rooted your phone you should trying something like busybox tar -cpzf /pathofyoursdcard/dump.tgz /app /bin /build.prop /etc /fonts /framework /lib /media /preinstall /tts /usr /xbin - will work - maybe titanium do this as well (?). This will take a while. After that, I will use system.img and preinstall.img structure available for verizon to rebuild one similar for XT860 using the files from dump.tgz.
Once I have build these 2 files, I intent to flash them using fastboot on linux (already available here in XDA forum).
Assuming that I just messed with files in those 2 partitions (like, I think, most of XT860´s owners), they should suffice for bring the phones back from the death (hopefully !).
Here is the problem: since my XT860 is bricked, I don´t have how to backup those files on my own. So, I, if any good soul could create it and make it available in some place (dropbox, megaupload, etc), I will be very grateful and, of course, promise if that idea works (and don´t make my phone crash and burn , I will make those images available for everyone brave enough to try them
Regards !
Claudio
PS: if anyone see something terrible wrong with this strategy, please, let me know
Click to expand...
Click to collapse
I would be willing to help you on this. I'm fairly new to android and even newer to Linux but would love to see a reliable method of saving bricks for our device. It might spark some ROM development too. If you can help me with some directions we could make this happen. I assume I would have to restore to stock in order to make a reliable recovery.
Sent from my rooted xt860
First at all, thanks for your time and help !
You will need:
- a sd card (1Gb will be fine - to save the tar file - it is not show stopper if you don´t have it, but it will make things a lot easier;
- rooted Bell XT860 device - as far as I can see by your signature, you already have it ;-)
- access to a root shell - and for that you need a terminal - connectbot from android market will work - it´s free application;
- after install it, you should try to connect as root to ip 127.0.0.1 (ou choose local conection from connectbot) - you will probably see an warning requesting authorization from connectbot to allow it run as root - you should allow it;
- if everything works as expected, you will see a terminal waiting for commands. Then you should navigate (using cd /; and then, running ls -l (will show all files) on directory to see if you can see all the files/directories that I listed in last post:
- app
- bin
- etc
- fonts
- framework
- lib
- media
- preinstall
- tts
- usr
- xbin
- build.prop (this is a file - a VERY IMPORTANT ONE - not a directory)
and if you can see your sdcard (you should see its contents by running cd /sd-ext; ls;
- if you find all files you should run this command (and assuming that your sdcard is mounted on /sd-ext:
busybox tar -cpzvf /sd-ext/dump.tgz /app /bin /build.prop /etc /fonts /framework /lib /media /preinstall /tts /usr /xbin
- after that it will create a tar file keeping all file properties below /sd-ext (your sdcard) called dump.tgz with all content need. There are LOTS of files, so, it will take some time to finish.
- If everything ends fine, I will need this file (dump.tgz). Please, upload it where you like most (dropbox, rapidshare, megaupload, whatever) and send me the link to download.
You don´t need to restore your phone to stock. The only side effect would be a bigger image if you have installed some applications.
Again, thanks for your time and help !
Best Regards !
Claudio
PS: Let me know if you need further information/help.
PS2: Sorry if some part of my instructions are not pretty accurate (I´m trying to remember the commands/sequence since I don´t have my phone working right now :-/)
cuqui said:
First at all, thanks for your time and help !
You will need:
- a sd card (1Gb will be fine - to save the tar file - it is not show stopper if you don´t have it, but it will make things a lot easier;
- rooted Bell XT860 device - as far as I can see by your signature, you already have it ;-)
- access to a root shell - and for that you need a terminal - connectbot from android market will work - it´s free application;
- after install it, you should try to connect as root to ip 127.0.0.1 (ou choose local conection from connectbot) - you will probably see an warning requesting authorization from connectbot to allow it run as root - you should allow it;
- if everything works as expected, you will see a terminal waiting for commands. Then you should navigate (using cd /; and then, running ls -l (will show all files) on directory to see if you can see all the files/directories that I listed in last post:
- app
- bin
- etc
- fonts
- framework
- lib
- media
- preinstall
- tts
- usr
- xbin
- build.prop (this is a file - a VERY IMPORTANT ONE - not a directory)
and if you can see your sdcard (you should see its contents by running cd /sd-ext; ls;
- if you find all files you should run this command (and assuming that your sdcard is mounted on /sd-ext:
busybox tar -cpzvf /sd-ext/dump.tgz /app /bin /build.prop /etc /fonts /framework /lib /media /preinstall /tts /usr /xbin
- after that it will create a tar file keeping all file properties below /sd-ext (your sdcard) called dump.tgz with all content need. There are LOTS of files, so, it will take some time to finish.
- If everything ends fine, I will need this file (dump.tgz). Please, upload it where you like most (dropbox, rapidshare, megaupload, whatever) and send me the link to download.
You don´t need to restore your phone to stock. The only side effect would be a bigger image if you have installed some applications.
Again, thanks for your time and help !
Best Regards !
Claudio
PS: Let me know if you need further information/help.
PS2: Sorry if some part of my instructions are not pretty accurate (I´m trying to remember the commands/sequence since I don´t have my phone working right now :-/)
Click to expand...
Click to collapse
Seems straightforward enough. Do I need to unfreeze/rebloat? And I'm running update 9 beta of the supercharge which makes changes to build.prop. unsupercharge first? Also I've done theming in uot kitchen. I do have backups of the original framework-res. Also are any of my personal info stored in these folders(name/phone number/website login info)
I'm out and about right now but I'll try it out when I get home
Sent from my rooted xt860
So, I installed PA 4.6 Beta 2 for locked bootloaders on my Xperia SP yesterday. To install the rom I performed all necessary wipes via recovery twice. Now there's this big problem. After I opened my gallery I noticed mutliple similar folders, after checking details of individual images and going to the directories mentioned in image details using root explorer I noticed the following -
1) storage/emulated/0 leads to the current internal storage directory being used by the PA rom
2) There's another 0 directory this directory i.e. storage/emulated/0/0 which contains empty DCIM/pictures/ringtones folders
3) Same as 2, storage/emulated/0/0/0
4) Finally going to storage/emulated/0/0/0/0 leads to the old interal storage which is used to be on the stock rom. All files are intact.
This is quite weird. Can someone please explain what's going on and how can I fix this? This never happened on nexus 4 after installing new roms.
EDIT- Nevermind. Fixed it myself. Although an explanation on why this is happening will be appreciated.
Hello,
I'm a beginner lost in reading all the useful information on this forum.
I started with the idea to reduce the permissions of applications of my Razr I.
Google pointed to this http://www.xda-developers.com/protecting-your-privacy-app-ops-privacy-guard-and-xprivacy/
And I'm really happy and surprised about all information I can find here, thank you that much for
making this possible to all of you!
As today I feel ready to start playing around with my phone I wanted to ensure I understood the items right.
May be for you it takes only some seconds to verify my guess and can give a short notice
about Step 2 or 3 is easier to become implemented.
Step 1.) I wanted to do a full backup before I start, following this thread:
So I'll install ADB on my PC and run "adb backup -f FullBackup.ab -apk -all"
This works on a Razr I with 990.43.74.xt890.Retail.en.EU - of the shelf and is not risky at all - or?
Could you pls. tell whether it is really true I can switch back to my backup if I'm not happy with my System?
Step 2.) My first intention was to root my device and install Xposed framework
http://forum.xda-developers.com/showthread.php?t=2299428
http://repo.xposed.info/module/de.robv.android.xposed.installer
And to use Permission Master out from google play store
First of all I wanted to ask you whether this is feasible technicaly and esp. for a beginner?
Alternative to Step 2 Step 3?
Step 3.) In general I'm happy with my Razr I Android 4.4.2 (990.43.74.xt890.Retail.en.EU)
But I'm wondering whether it would be easier or has less risk to use a custom ROM instead of implementing Step 2.
By reading in this forum I found out there is a planty of features FM-Radio, enhanced stand-by current ,
to get rid of preinstalled aps and so on.
I'm an embedded developer but do not have the overview about the architecture of Android devices, what I got so far is:
There is a bootloader which needs to be changed from OEM closed to open.
There is a boot partition I flash ROMs in.
I need some tools on my PC combined with SDK and Motorola drivers to allow a USB-Debuging and flashing.
And sure as always once your bootloader is damaged you are lost, so I understand even backup will not help here.
So I'll keep my fingers crossed.
Thanking you in anticipation and pls accept my excuses about my english and stupid beginners questions.
Best Regards
gonso
PS:
As I main entry point I used the
http://forum.xda-developers.com/razr-i/general/index-razr-t2832722
from there I'll try to get ADB, drivers etc.
Hi GonsoXDA,
Step 1: I have never used it. Didn't even know that it existed. On the internet there are numerous people who uses it and it seems to work. Maybe someone else can give some info about this or just try it. U can try it with a non-important app and see if it works. Just backup it, delete it and restore it.
Step 2: This works just fine. But do know 3 things:
1. First root: To get root on stock rom, u need to use kingsdroot methode afaik. And that one sends your IMEI to some rare ip adress. I personnaly don't trust this and stay away from it, but there are many people who use it.
2. Xposed requires a recovery to install the framework. It can be done mannually or by the app i suppose. With only root u don't have a recovery on your device that can perform such action.
3. If something goes wrong only a full restore with RSD-Lite can most of the time help u out. Because u don't have a recovery that works than.
Step 3: We only have 2 full roms. 1 for JB (stock) and a working CM11 rom (kitkat).
Only the Jellybean roms support fm-radio, on every newer rom fm-radio is cut out of the audio firmwares. The risk of going to this is even less as Step 2, because u can do a full backup and restore of ur phone. ( I would chose for this if u want to play a bit with the phone and ur warranty is already out of years)
The gereneral idea about the android architecture is this (it is different for almost every device and the Razr I has many more thing to hold into account, but if u are here only for the roms and xposed, there is no more to know):
Bootloader: Is like an uefi bios for PC, but then for android. It also contains fastboot
Bootimage(boot): Has all the info like kernel and ramdisk to boot the system
Recovery: Is like 'boot', but boots into the recovery partition that lets u change every aspect of the device if u know how. Its mainly used to flash a custom recovery to, backup and restore a nandroid backup and flash/wipe roms, mods, (all/specific) data and packages.
Systempartition: Is the system the boot boots into. It's android.
Datapartition: Where all the user data is stored.
Cachepartition(dalvik): Where all cache is stored and in earlier android versions also dalvik. But not now anymore.
Fastboot: To flash/wipe the above partitions and many more (needs drivers)
Adb: To push, pull, command things in system or recovery (needs drivers)
Sdk: contain the abd and fastboot packages, but aren't needed for adb and fastboot because with the right drivers can work on there own (see the internet)
If u have a custom recovery and only change things on the system, data and cache partition there is almost no way to damage the phone. There is always a backup through recovery. As long as u stick to the things u can do in recovery.
The only thing tha can mesh up your phone beyond repair is doing wrong stuff withint the bootloader and other inner parts in the phone(like i did to get newer kernel working) or u are in bad luck and you internal memory blocks. See 'Super brick samsung phones' (emmc error).
I suggest:
- Unlock your bootloader
- Install custom recovery
- Make a backup with the recovery
- Do what u want, xposed on stock rom, try CM11?
- If things won't boot, restore through recovery
And always, read up before doing anything. There are thousands of articles about android, flashing things, repairing android, using adb and fastboot. AND ALWAYS HAVE A BACKUP PLAN!
Hello,
always having a backup seems not to be that easy.
So I unlocked my boot loader and tried to install twrp2850 and twrp2860 via mfastboot.
The mfastboot with 533.353kB caused the following "(bootloader) Variable not supported!"
I rebooted into bootloader and tried recovery -> horizontal Android man with a red !-rectangle
After reboot to normal power up my phone seems to be in factory reset, all my data is gone :crying:
ok crying dosn't help so I looked around and tried with another mfastboot 186.178kB and recoverycwm6.0.5.1.4.img.zip
http://forum.xda-developers.com/showthread.php?t=2441224
The twrp I tooked from here: http://forum.xda-developers.com/showthread.php?t=2278483 seems not to work.
I did a backup with cwm is there a change to get back my data? I think I know the answer.
In the meanwhile I installed
http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855
And will try to install
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Thank you for the help, work and excuse the stupid beginner posts.
Regards
gonso
gonsoXDA said:
Hello,
always having a backup seems not to be that easy.
So I unlocked my boot loader and tried to install twrp2850 and twrp2860 via mfastboot.
The mfastboot with 533.353kB caused the following "(bootloader) Variable not supported!"
I rebooted into bootloader and tried recovery -> horizontal Android man with a red !-rectangle
After reboot to normal power up my phone seems to be in factory reset, all my data is gone :crying:
ok crying dosn't help so I looked around and tried with another mfastboot 186.178kB and recoverycwm6.0.5.1.4.img.zip
http://forum.xda-developers.com/showthread.php?t=2441224
The twrp I tooked from here: http://forum.xda-developers.com/showthread.php?t=2278483 seems not to work.
I did a backup with cwm is there a change to get back my data? I think I know the answer.
In the meanwhile I installed
http://forum.xda-developers.com/razr-i/development/rom-unofficial-cyanogenmod-11-t2966855
And will try to install
http://forum.xda-developers.com/xposed/modules/tool-installer-xposed-installer-zenfones-t2983589
Thank you for the help, work and excuse the stupid beginner posts.
Regards
gonso
Click to expand...
Click to collapse
Than u know the answer, it is no I think.
Both twrp images should work just fine, but always chose the latest. The message "(bootloader) Variable not supported!" doesn't do anything So don't worry about that one. There should be a lot more in you log that the message if twrp didn't install. U did extract it and flash it with the command: mFastboot flash recovery <recovery-image>. Where <recovery-image> could be C:/users/*/Downloads/recovery.img.
Hello,
yes sure "The secret of health for both mind and body is not to mourn for the past, worry about the future"
So I use CM11 now for about 2 days and I'm really impressed, so far everything works :good: THANK YOU!!!
As I asked already I installed XPosed and Permission Manager, but I found XPrivacy might be the better solution and switched to this.
(Today I do not have all the technical background to judge whether it is technically equivalent, but I'll investigate on it)
Esp. one thing I'm wondering, why XPrivacy is reading my Contacts once I check the permissions of an app?
But the more important thing I recognized differences between CM11 and the Stock ROM. One is the Entry
"Privacy" in the settings. It seems to be more or less the XPosed and XPrivacy, or?
But it seems the Restrictions are not shared, so I can restrict in the one and do not see the restriction in the other tool.
So first is there a risk to use both, is it useful or just doing the same twice.
Thank you
Gonso
gonsoXDA said:
Hello,
yes sure "The secret of health for both mind and body is not to mourn for the past, worry about the future"
So I use CM11 now for about 2 days and I'm really impressed, so far everything works :good: THANK YOU!!!
As I asked already I installed XPosed and Permission Manager, but I found XPrivacy might be the better solution and switched to this.
(Today I do not have all the technical background to judge whether it is technically equivalent, but I'll investigate on it)
Esp. one thing I'm wondering, why XPrivacy is reading my Contacts once I check the permissions of an app?
But the more important thing I recognized differences between CM11 and the Stock ROM. One is the Entry
"Privacy" in the settings. It seems to be more or less the XPosed and XPrivacy, or?
But it seems the Restrictions are not shared, so I can restrict in the one and do not see the restriction in the other tool.
So first is there a risk to use both, is it useful or just doing the same twice.
Thank you
Gonso
Click to expand...
Click to collapse
That's a sentence.
Why XPrivacy needs it i don't have a clue. For that sort of things u need to be by the dev of the app.
CM has a lot of features out of the box compared to stock, but stock is most of the time a bit more optimized in terms of proprietary stuff like camera.
So as u noticed, CM had an inbuilt security app. This app (CM) and XPrivacy don't share there settings, so that's the difference u see. But most likely if u disable something in one of the apps it is disabled even tho the other doesn't say it because it doesn't know of it.
I don't think it will be a risk. They both do the same thing, but they don't know about it. To be on the safe side, just use one and restore the other to default. U can always search on the web if they don't get along.
U can now make a full backup, so everything can be reverted and your data should be relative safe.
Hello,
thank you again - I now find the answer by reading in the development part of the forum. For me as a beginner it is sometimes not easy to interpret the discussions there.
If accepted I will use the thread now as a kind of diary, may be some other users will have similar destinations and my learn from my mistakes.
So to answer my question a little more detailed, but with less background know how than Hazou. Pls. do not trust me I'm a beginner, I have not analyzed the code just the behavior - feel free to correct or contradict my words!
The XPosed is in the area of permissions just a framework which allow other modules to put some code between an app requesting permissions and the Android core granting this permissions. The Xposed it self doesn't handle settings or permissions you did in modules like the CM Privacy, Permission Manager or XPrivacy.
As a result I came to the same conclusion it is not a risk, but an overhead to have more than one pice of code between the app requesting permissions and the Android core. -> My proposal: Do not use more than one of this Permission control apps in parallel.
From the privacy perspective the Permission is just a starting point, it allows you to hide your private information from the app. On the other side many apps will need access to the data to work and most of them are able to connect to the internet.
So I realized the next step would be the restriction of internet usage of apps. Here permissions are sword but we need a scalpel, to separate the necessary from the unwanted connections. This scalpel could be AFWall+ and "Netzwerk Log", this is a firewall and a sniffer.
What I can say to day the apps run on CM11 installed on my Razr I.
So it looks like I see my destination raising on the horizon and I will try to formulate it in the following order:
1.) Hide Contacts, Calls and SMS from Apps who do not need this to work -> XPrivacy
2.) Disable some Android features I think I don't need.
(e.g. Captive Portal Check - settings put global captive_portal_detection_enabled 0)
3.) Restrict the internet access of some apps to servers they need to connect. ( e.g. E-Mail client is restricted to connect to the mail server)
4.) Limit the access to my pictures, stored on SD card. [I have not found a solution so far]
If you read this I think 1 is reasonable for most of you, even if you do not have deep Android or Network know how (as I have), you just restrict the permissions - if app crashes or doesn't do the job you expect you may permit access or uninstall the app. (XPrivacy allows you also to fake data)
3 is a usual task of a network administrator, if you are used with iptables it is just work. I'll try to find out whether there is somewhere a source of "Templates". Usually the network admins share there common settings based on services, once I find out I'll post.
To restrict the access to SD Card I only see the change to extend the sandbox of Android to the SD and to hide files which does not belong to the app. As I would store my pictures on SD as I would store my Navi Data, but neither the Navi app should see my pictures nor the Cam and Gallery my Navi Data. ...
I don't know whether there is an app out there but It should be possible the same way like XPrivacy fakes the other data.
Thank you
Gonso
Hello,
Most of the time I used the numbers to just put in the extension, so if I want to call 0049 9876 54 321 I put the numbers 321 the Motorola dialer will show a list of all contacts where the number contains 321.
Some Numbers of contacts are not shown as well, seems if a contact has more numbers only one or two are shown.
The CM11 dialer doesn't show the number, is there a setting to get this feature?
I tried to get my Stock dialer back, so I copied dialer.apk from stock into the /system/sec-app/ directory of the CM11 and restarted the phone -> doesn't change the dialer ....
Any proposals? I'm terrible sorry for my stupid questions, I read several threads and still no idea about a possible solution
Gonso
PS: CM11 file manager shows a secure storage /storage/emulated/0/storage/secure - what is the algorithm used for the encryption.
gonsoXDA said:
Hello,
Most of the time I used the numbers to just put in the extension, so if I want to call 0049 9876 54 321 I put the numbers 321 the Motorola dialer will show a list of all contacts where the number contains 321.
Some Numbers of contacts are not shown as well, seems if a contact has more numbers only one or two are shown.
The CM11 dialer doesn't show the number, is there a setting to get this feature?
I tried to get my Stock dialer back, so I copied dialer.apk from stock into the /system/sec-app/ directory of the CM11 and restarted the phone -> doesn't change the dialer ....
Any proposals? I'm terrible sorry for my stupid questions, I read several threads and still no idea about a possible solution
Gonso
PS: CM11 file manager shows a secure storage /storage/emulated/0/storage/secure - what is the algorithm used for the encryption.
Click to expand...
Click to collapse
Stock CM dialer doesn't have that function afaik. The moto one doesn't work because it needs the Moto framework to work. Just download a dialer U trust from the playstore.
I don't have any clue about the secure storage, sorry.
workaround found - downgrade to stock Froy 2.2.1 - IMEI back - still no idea how to use backed up efs file(s)
(c&p or s.th. else)
Still open: where to download and which version of TWRP for stock? did not find any:cyclops:
Btw.: it is my own smartphone (o-bill) and should be not a solution of all those telling stories of the mobile of a friend of a friend
It took me hours to find the wright files and I had 5x soft bricks with boot loops...
BETTER would have been a solution how to reinstall efs (write protected) if you don't have TWRP or if you copied efs file obviously wrong like me (just c&p to desktop); edit single file(s) or rename or what ever
------------------------------------------------------------------------------------------------------------------------------------------------
Hi forum,
I'm hesitated: IMEI was replaced
Backed up my efs file and installed really good roms (Omni 5.1.1., Lineage OS 11 (=4.4.4), CM12, and others)
Then I tried to exchange the small 512 MB RAM with a 32GB micro SD. Card was actually recognized as a 8GB one.
So I took it away to use it somewhere else and formatted it therefore.
Since then my IMEI has been replaced with the general one for developers - however, I need my S1 back fully.
This is the assumed root cause - maybe also it just happens sometimes if triying different roms...
Back to the facts:
I do know my IMEI
I have 5 copies of the efs file since 2013
when tried to restore from backup TWRP did do but showed failure with the efs file
Tried mobileuncle and others - failed because MTK engineer mode cannot be used (not supporten cause of other chip maybe) AND therefor
this quick win actions via dialer (#*#....) also do not work for me
root rights? Yes
SU? YES
Hex editor? YES
Must I really go back to stock (Froyo) with Odin and this stuff I forgot how to deal with it?
Or does anybody here has a proper solution how to fix this IMEI-RE-ENTRY-issue that is not too much time consuming and save? I searched for hours here and in other forums as well as in the internet...
I appreciate smart solutions and thank you all in advance
KC