Related
Some poeple are the meaning, that the place for this thread will be better here: OK, lets following this issue here. Here is a copy from the previews one:
CM 4.2.1 / CM4.1.99x Exception with contact group
Exception with Contacts - so like as in 4.1.99x
I have the same problem as in 4.1.99x, that I can not add a contact in my group (there is still ony one, which was working after some crashes in 4.1.999) without a crashed application
If I look into the exception Monitor, I can found a lot of:
Quote:
java.lang.IllegalStateException: Failed to find the My Contacts group"
Click to expand...
Click to collapse
What can I do or must do ?
History: I have had the G1 not so long time, but modif. it via WIPE to the 4.0.x ( stable )
After this (2 days later I upgrade to 4.1.111)
from this status I was following the description with the 2 Step to 4.1.999, where I have see the error the first time. With 4.0.x / 4.1.111 I haven't recognize this problem, because I have add some friend in my contact-list. For my meaning, this one was coming in, during upgrade in the 3 steps: WIPE, Google-Recovery, CM-Update 4.1.999.
Hint: If I update the phone, I start the phone WITHOUT a Mobile-Card: because I have had one time a bill over 200€ for data connection, and nobody knows why. So I boot the phone after update without card, check APNdroid, if 3G etc. disabed, shut down the phone, insert the casrd and boot again.
Maybe this handling calls the error ?
......
......
YES, I have use the search function and didn't found any usefull infos.
>>> ( how does I love this answer! If you found time to write this one, than I think, you know the answer - pls give me this one )
YES. I have reflashed the 4.2.1 with the card inside the phone: No change
Btw.: I was falling also in the error with the ext2 and ext3, so I change this one on the PC via tune2fs. But normaly every program, which need a DB and did not found it, create one. Or isn't it ?
Push > because its still avail and a Java exception is not a handling error
Just to bump this a bit and to pretend like it is actually useful to post in this forum...
Have you tried backing up your contacts via the browser, deleting them, sync the phone and then restoring?
Have you tried backing up your contacts via the browser, deleting them, sync the phone and then restoring?
Click to expand...
Click to collapse
No I haven't, because I have not so much contacts... So I was starting with a brand-new phone, "root" them, wipe them and change to CM4.0.x (Stable), jump to CM 4.1.11 and after a few days following the instruction to move to 4.1.999 with WIPE, 1st paket and the CM-paket.
Here I see the problem and also in 4.2.1.
About a missing Backup, I try only to create a contact manual on the phone.
THe first time, if I want to add the contact, the phone ask me to syncronise - but I was offline at all. So I reject this message ( there are also no datas to sync online )
Push .... .....
Huge thanks to Hashcode for all his hard work thus far, what with the totally ingenious Safestrap and his latest victories with CM9. I hope this helps somebody out and that at least *someone* out there thinks this is as cool as I do.
Pushing OK+Backspace will force the console to kick you out back into the recovery, in case you get stuck. Keep in mind that the console is pretty powerful but also really dangerous if you don't know exactly what you're doing. Although, you'll never learn how to do anything awesome unless you get your hands dirty.
The Microphone button is now ESC, command history works, tab-autocompletion works via either the hardware Tab key or by pushing OK+i, and you can scroll back up through the text one line at at time with Alt+Up or Alt+Down or in chunks of 8 lines with Shift+Up and Shift+Down. Home is the home softkey, or the Search button on the keyboard, and End is the Power button. You could also push OK+A or OK+E for Home and End, respectively.
Make sure you uninstall Safestrap and then remove the application before you install this one. I just jacked Hashcode's .apk and stuffed my new binaries inside the .zips, if you don't want to bother with uninstalling and reinstalling the .apk, you can extract the recovery.zip and 2nd-init.zip from the archive and push them both to /system/etc/safestrap and reboot. Enjoy.
..............................................................
EDIT: I finally got my act together and put my modified sources on github:
http://github.com/buddyrich/android_bootable_recovery
............…………………………………………
EDIT: Just finished up my latest update to this branch of Hashcode/Koush's work. Added:
-Use numbers on the hardware keyboard to select menu entries. Got really tired of scrolling around and thought this would make things a bit quicker.
-Scrolling/repeating keys. Holding in for longer than about half a second will repeat even faster now, similar to a real terminal on a PC for instance.
-vim statically compiled to avoid the need for any external libs (ie: having /system or /systemorig mounted). Full color support and syntax is working great now; the only thing missing is background colors, which will be tricky to implement.
-a $HOME directory is now made at /emmc/safestrap/home. This is set up when the .apk is installed; it isn't necessary so it can be deleted if you want, but it is required if you want to have a persistent command history in bash as well as the ability to customize your .bashrc and .vimrc files. Most of you won't really know what this means, but if you do you'll probably appreciate it.
-Revamped all the menus and made everything look a little cooler. Let me know what you guys think! I got rid of the highlighting box that shows which menu entry is currently selected and changed it to simply highlight the text in white to distinguish from the green/yellow menus; I think it's a little easier on the eyes but some feedback would be cool. It wouldn't be very hard to allow the users to customize the menu colours themselves via external files placed on the sdcard/through a menu option.
-Fixed the issue some people were having with restoring to /systemorig; there aren't any more issues mounting/unmounting /systemorig or /system during a restore
-Probably many more things I've forgotten
-.bashrc tweaks, fixed a few aliases, nothing major
-You can flash updates from either safe or non-safe mode now, look in the advanced menu. Really though, be careful and remember to make backups of your /systemorig partitions. Don't say I didn't warn you! Guaranteed, someone out there will complain that they broke their phone so I was pretty hesitant to let that out in the wild, but I know I've found myself in the situation where I could've used it so there you have it.
Let me know if anyone finds any issues, I've done a pretty thorough job testing this over the last few weeks but there's always something to be missed. The new .apk is over the size limit to be posted in the forum due to the new bash and vim binaries and the vim runtime files, so you can download the new version from my dropbox here:
Safestrap (Tweaked) v1.08e for Droid 3
http://db.tt/CArenxr7
EDIT:
----------------------
Just finished thoroughly testing my latest release and think it's ready for human consumption! Another batch of sweet additions:
1) Proper implementation of /systemorig flashing while in non-safe mode... without any modifications needed to the updater-script present in any flashable zip. Even if the updater-script inside the. zip file you are flashing targets "/system", if you confirm it about three times in non-safe mode it will know to copy the files onto /systemorig to replace your stock system.
You can install Gingerbread-based ROMs such as MavROM 3.5 to the stock /system partition while in non-safe mode via the Advanced menu. Safestrap will backup and afterwards restore it's own files needed to ensure you can still get back in after a flash of the /systemorig partition. Note that flashing your original /system partition with an ICS ROM won't work yet because they need custom init.*.rc scripts in place during the 2nd-init process; this isn't hard to do but I was getting anxious to get something out so it'll have to wait until next time.
2) Redesign of the layout for the menus, much more organized
/* 3) Allow for rebooting directly into the recovery, either via the shell command "reboot recovery" or through the Reboot Menu */
// EDIT: Seemed to be causing some users to persistently boot straight into the recovery so on the backburner for now
4) Allow for custom colors for either safe or non-safe mode; to change the colors for now you have to execute a few little shell commands. Here's an example to change safe mode colors to a blue-grey and then non-safe mode colors to maroon:
Code:
s_rgb 139 137 137
ns_rgb 127 34 10
cc
Basically, "s_rgb" sets the colors for safe-mode and the three arguments (139 137 137 in the above example) are the codes for the red, green and blue components of the end result; you can look up rgb color codes for your own custom colors. "ns_rgb" is the command for non-safe colors. "cc" just tells the recovery to update the colors to whatever they've been changed to. If you don't like what you've done and just want to revert back to the stock ones, you can just wipe your /cache partition and they'll go back to normal.
Eventually I thought it'd be cool to be able to do this via the recovery UI but I haven't been able to envision how it would work yet.
5) Added background colors/highlighting in the console now, makes vim look a lot prettier. If there's anyone out there who cares, I preinstalled a few plugins (MiniBufExplorer, MRU (most recently used files), bash-style path completion, etc.)
Also, changed the cursor from the big ol' ugly white block to an easier-on-the-eyes one-character underline.
Yeah, it's overboard.
6) Much faster backups and somewhat quicker restores now. I clocked full backups (including /systemorig and ~350mb /data partition) at around 2 mins and full restores at around 7 minutes. Also fixed up the progress bars so they give a more accurate representation of how much longer the backup/restore will be.
7) Moved $HOME and other misc. Safestrap files to /cache instead of the /sdcard
8) Probably half a dozen other OCD details that I've already forgotten.
Test it out and let me know what you guys think!
As always, sources are posted on my github:
https://github.com/buddyrich/android_bootable_recovery
You can get the new .apk here:
Safestrap (Tweaked) 1.08f for Droid 3
http://db.tt/u4vAwv2u
i need this about 6 hrs ago lol.
Quite useful mate cheers.
=smc
Thank you so much for sharing this file. Your work is greatly appreciated.
This is a nice little(big)addition to safestrap! Thanks for adding it in!
I can't think of any better use for Christmas Eve than coding a bash console into recovery! Merry Christmas to the D3! Thank You!
Sounds good. I haven't grabbed it yet (as I need to keep my own customised Safestrap for ME863 nandroid support) but one thing I'd note is that the "OK" button (i.e. trackball click) is used for "Control" in Console+, and the console in Amon_RA's HTC Dream recovery. That saves you losing the @^ key.
Edit: Also: Source? Sounds like something that could be pushed upstream. I always found the console in Amon_RA's recovery very useful, missed it on my current device, when I didn't have a computer with ADB handy.
TBBIe,
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
I'll commit my sources to github shortly so you have take a look.
I am trying to get through the preinstall problem myself after flahing xt883 and I was wondering if I could fix it with this?
Sent from my DROID3 using xda premium
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
redsox985 said:
Hey there guys, Village Idiot here...I've been successfully using Hash's SafeStrap for a while now and wanted to try this one out. What's the difference here? Just by looking at it, I can't tell. It seems better from what everyone is saying, but I have no idea how to utilize it. Would you mind dumbing it down for Simple Jack over here? Thanks.
Click to expand...
Click to collapse
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Endoroid said:
It has a console option included, allowing you to run shell commands, which could potentially save your butt if used right.
Otherwise it the same
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
ovelayer said:
Which it just did lmao..hash really needs to include this in his release!
Once again thanks for this mod it is PERFECT!
Click to expand...
Click to collapse
Oh I'm sure I'll be damn thankful at some point. Made a point of installinng it
Sent from my XT860 using xda premium
Rick#2 said:
I have an XT860, so I'm curious to see if this would work on your ME863. I remember seeing a post of yours a few months ago mentioning issues with the preinstall and data partitions (I think it seemed that the data partition was extended into the first bytes of the preinstall partition, rendering it unmountable during init) that should also have affected the XT860, but I have never experienced any issues with the partitions since Hashcode released v1.06.
Click to expand...
Click to collapse
The difference is the other way 'round. The /data partition is extended backwards over the end of the /preinstall partition.
It doesn't cause problems during init, it was causing nandroid to fail mounting /system, and presumably would make switching to safe-mode fail (although I never tried)
My patch to fix this for nandroid was based on 1.06. The only way this could be 'fixed completely' in safestrap was if safestrap had had repartitioning code added at some point to resize /data back down and grow /preinstall to be large enough to hold a safe system. And Hashcode'd said he didn't have time or real inclination to do that, I thought.
I'm fairly strapped for time at the moment, so I don't know when I'll have a chance to look at the source and/or try out your build. But it's definitely somewhere in my TODO list. ^_^
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
@rick#2
I'm running CM9 for daily use, but it's a bit wobbly at times, so I run 7.1 as the "non-safe" system. The big limitation to this is that I can't maintain the 7.1 fallback properly as hashcode deliberately disabled installing zips in non-safe mode.
If the wife has forgiven you by now - any chance of adding the ability to install .zips when in non-safe mode?
The alternative is to keep swapping bootstraps all the time, and all it takes is one late night sleepy mistake to stop the device booting one system or both.
I'm in favor of this as well, and have even mentioned it in the main SS thread. Could you add flashing to non-safe, but say with like 3 layers of warnings saying something like "THIS IS YOUR NON-SAFE, MAIN SYSTEM. FLASHING HERE CAN BRICK YOU."
This would be really nice because it's a PITA to keep switching strappers, albeit it easy, just a burden.
This is a great hack! I was considering doing this myself but you beat me to it! BTW, is your modified source code on github or somewhere like that, or can you send it to me if not? Thanks again!
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Rick#2 said:
Hey guys, sorry for the lack of updates to this thread. Been buuuusy.
I made an account on github about two weeks ago, but still haven't gotten the chance to upload the sources there, for those of you who are interested. I'll do that shortly.
I've got a new version I'll put up pretty soon, just need to do some more testing. I've enabled scrolling (ie: holding a key down to repeat it as opposed to requiring you to push it each time) but have to iron a few things out, and I'd like to add another menu enabling some of the (somewhat dangerous although useful if you know what you're doing) features some of you have requested.
Click to expand...
Click to collapse
Dude you rock!
Sence you introduced your mod i have used nothing else..
The scrolling feature would be a HUGE improvement i agree ..
Also it would be nice if you could flash on the non-safe system as well..
Hope you can get er done..
I allways seem to watch this thread for updated..i really hope you can continue this adventure without the wife killing you lol..stay real!
---------- Post added at 12:45 PM ---------- Previous post was at 12:41 PM ----------
denpad2010 said:
orry for dumb question...ok, i wanr root my friends drodi 3,i think i know how to do it using the one click software the same i used to root my bionic,now to order to go into custom recovery i need install this apk file am i right,i mean is the same as in bionics bootstrap???? sorr y for noob qustion ,just that i dont speak english very well so i need be 100% sure what am doing thanks again,,btw do u know if the last wifi tethering works on this droid 3???
Click to expand...
Click to collapse
Hey bro if you want wifi teather look up android-wifi-teather..it works!
Please find at the URL below my copy of the stock ROM (Version C) for the D415, with my modifications included.
The D415 is a great phone for the price, and it came with many cool features. However, the phone still has an amateur streak running the stock ROM. Some of LG's apps are great on this phone, but some of them are downright useless for most of us. T-Mobile added their own pushy bloatware to the mix as well. The end result, as we all know, is a usually fluid, but at times clunky and awkward experience using the device. I was impressed the first day I had it, but I wanted to make it better that first day as well. I wanted to get rid of all the useless stuff, and polish it into something I wouldn't be embarrassed to pull out in front of a client. I liked a lot of what LG did here, and wanted to hold on to that, but I also wanted a few changes:
Root:
FOTAkill
SuperSU installed on first boot
Polish:
Small UI sounds changes
Boot Animation
Replaced Flashlight App (thanks to xbmi, consider a donation in the app)
Added Heads Up
Removed foo foo themes
Added Bookmarks Sync
Replaced Stock Messenger with AOSP MMS
Debloat:
LG Memo & Widget moved to user apps
LG Music & Widget moved to user apps
Visual Voicemail moved to user apps
Weather widget moved to user apps
Apps removed completely:
LG Contacts widget
TMobile TV
Lookout
CarrierIQ
Maps
Mobile Life
Streetview
Talkback
T-Mobile My Account
T-Mobile Name ID
Voice Dialer
Youtube
Amazon
Chrome
Cloud Print
Drive
Easy Home
Gmail
Google Plus
Google Calendar
Play News Stand
Play Books
Play Game
Play Movies & TV
Play Music
Google Search
Google TTS
Hangouts
Stock Calendar
To do:
AOSP Keyboard (IDK what I'm doing here yet. It's crashing when I put it in now).
Version E (need to learn how to extract KDZ)
Instructions:
Download zip to SD
Reboot to Recovery
Wipe Dalvik, cache, data, system.
Install zip
Reboot and enjoy
Thanks to @Daisuke1988 for the original flashable stock rom.
Feedback welcome in replies!
I just got this phone today. I hate it but this should make it much better. Thanks guys!!
Sent from my SGH-M919 using XDA Free mobile app
Keep poking around with it. There are a lot of hidden gems sprinkled in by lg that will really cause you to like this phone. I came off of a nexus 5 to this. I chose it for the price tag, you can't beat $7 a month and get the build quality and battery life. I would buy again. The only thing I miss is a decent camera. But the stock camera app helps with auto focus mode.
Will it work on d405?
catbro said:
Will it work on d405?
Click to expand...
Click to collapse
Good question, it would be nice
Sent from my LG-D405 using XDA Free mobile app
I guess I have to try this evening, if nobody's trying till then I will report back
If the pure stock ROM works in the 405, this one should as well. I'm not sure myself without looking it up.
I have a D41510c and when I tried to install this rom, it failed. I'm restoring a backup, but I will try again in a while.
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
jb3p76 said:
Sorry to hear that, I tried very hard to make the cuts fine in this. Without further info I'm gonna guess the download got corrupted. The zip itself is really straightforward (simple script, boot and system imgs.) The only part I would have thought would have failed the installer was that I repacked the system IMG (saved a few hundred MBs) instead of simply unmounting it after my changes. Otherwise, if its going to break, it should be upon first boot. Let me know what happened if it doesn't work again.
Click to expand...
Click to collapse
I'm re-downloading, hopefully this will work!
I can deodex this but you will have to wait till Tuesday for me to upload it. or is it already deodexed?
I had thought about it but honestly haven't learned how to yet. Was I mistaken to think the payoff would not have been that great? Either way, I can wait til Tue, I know others will want it deodexed. Thanks!
I tried again, but it failed...
E:Error executing updater binary in zip
E:Unable to mount '/system'
EDIT: I was able to boot into the rom, but it's extremely slow
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Before I get too far down the rabbit hole can anyone confirm they have successfully flashed this and its working out for them?
jb3p76 said:
Wondering if it has to do with first botched install now that it went. Were you able to format /system again? My other thought was repairing permissions. When it failed the first time, was it before "Setting permissions for root" was displayed? If so it was in the middle of flashing /system. I flashed this on mine using twrp. IDK that I will be much help but I think if we can figure out the variables Google should at least point us in the right direction...
Click to expand...
Click to collapse
Well, I rebooted and it's faster now. I used towelroot to get root. Nohing appeared about the permissions. I was able to update the binaries using TWRP.
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
jb3p76 said:
It's should have already had root and SuperSU installs on first boot. Did that not happen? I'm glad your phone is doing better! So many weird things going on there!
Click to expand...
Click to collapse
I use ROM Toolbox Pro, and when I went to start it the first time, it said root check had failed. That's why I used towelroot. I'll continue to test things and report back to you. So far, it's pretty smooth.
Weird. Can you tell me if the SuperSU apk is to be found in /system/apps/bootup?
I'm doing a backup so i can wipe and install fresh again. I'd like to mess around with the root stuff and see if I can figure that out. Did you happen to get a listing of which files are missing?
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.
The first tweak/fix is for a GPS update/change.
Starting with Android 5.0, GPS has been flaky for a lot of people. The device picks up satellites, gets a lock, but then loses the lock. Sometimes it then gets a lock again and holds it, sometimes it just drops it again.
This was not fixed with 5.0.1, 6.0, or 6.0.1. It took Google over a year to even acknowledge it was an issue.
A user suggested a fix in the official bug report thread:
https://code.google.com/p/android/issues/detail?id=81140#c695
They suggest telling the device to not attempt a Mobile Station Based update of GPS information.
This can be done by changing the "CAPABILITIES" value in /system/etc/gps.conf.
I've made a file to automate this. It can be flashed from TWRP.
Nexus_5_GPS_Update_0.1.zip changes /system/etc/gps.conf to not use "MSB" updates.
Nexus_5_GPS_Restore_0.1.zip changes /system/etc/gps.conf back to the default of using "MSB" updates.
-----
The second tweak/fix is for CDMA users. I use my Nexus 5 on FreedomPop (a Sprint MVNO), and on almost every boot I'm greeted with this lovely message:
"Unfortunately, Update Device has stopped."
Its crash message mentions this:
java.lang.IllegalArgumentException: You cannot keep your settings in the secure settings.
From what I've read, moving an app from /system/app to /system/priv-app is supposed to fix this. The two problem files (OmaClient.apk and UpdateSetting.apk) are both located in /system/app, not /system/priv-app.
I figured, "why not move them to priv-app?"
So I've made a file to automate this. It can be flashed from TWRP.
Nexus_5_Sprint_Update_0.1.zip moves the apps from /system/app to /system/priv-app
Nexus_5_Sprint_Restore_0.1.zip moves the apps back from /system/priv-app to /system/app
-----
I tested these on CyanogenMod 13 (May 10th nightly build). There is no binary in the zip, each just contains a script to update the system, so you can easily view them in plain-text. Since both of the issues experienced seem to be impossible to purposely reproduce, I cannot say for sure if these fix the issue.
That's why I wanted to see if the files work or help others.
You can boot to TWRP and flash the zip files there. If you use something like CM Downloader, you can add them as additional zips to flash after any ROM update.
Let me know!
My GPS has been really useless these days. I guess I have to root my phone to try this out..
If I want to do it manually, what do I have to change it to?
ashirviskas said:
If I want to do it manually, what do I have to change it to?
Click to expand...
Click to collapse
Open /system/etc/gps.conf
Change this:
CAPABILITIES=0x33
To this:
CAPABILITIES=0x31