[ROM][KK][4.4.4][KTU84P] CyanogenMod 11 20140714-UNOFFICIAL - Samsung Galaxy Exhibit 4G

CyanogenMod is a free, community built after-market firmware distribution of Android 4.4 (KitKat), which is designed to increase performance and reliability over stock Android for your device.
Downloads
Read install directions before downloading or use ^C^V
Latest ROM md5sum: c821ebacaa5c969c55b0a511be8a3933
Current GApps 4.4.4 :: PA
CWM 6.0.5.0 md5sum: 4bfb28bcf29dc04243df246860f24940
Recovery for flashing in Odin CWM 6.0.5.0 md5sum: b5856bd395248af1c74dac8b92cd258e
For Odin: select the ops file, enable one package in options, then load the md5 file with the One Package button[1]
Installation
Install at your own risk
- First time flashing CM11 to your Galaxy Exhibit (or coming from another ROM)?
Boot into existing recovery and create a Nandroid Backup!
Install at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
Reboot recovery into at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
CWM: WIPE dalvik-cache, format: data, system, and cache. TWRP: WIPE dalvik-cache, data, system, and cache.
** Optionally back-up sdcard0 before install and format it in recovery if experiencing install issues **
Install the ROM (without gapps)
Reboot system
After system boots, boot back into recovery and install KK Google Apps.
Wipe dalvik-cache and cache. Reboot.
- Upgrading from CM11
Boot into existing recovery and create a Nandroid Backup!
CWM: WIPE dalvik-cache and format cache. TWRP: WIPE dalvik-cache and cache.
Install the ROM
Reboot
Known Issues
ART takes ~15 minutes to install and some apps may not be compatible.
Display remains on while device is powered off and charging
Kernel Source
Credits
arco68, jocala, Christopher83,
pawitp, davidteri, mikeNG,
AriesVE DevConnection Team

Changelog
20140714
Sync with CM sources
Add center clock option
Add Xposed fix
Remove KSM
Disable LPA
416 MB userspace memory
md5sum: c821ebacaa5c969c55b0a511be8a3933
20140710
Sync with CM sources
Kernel 3.4.98 compiled with Christopher83's 2014.06 4.9.1 toolchain
406 MB userspace memory
Remove zram
md5sum: 7b0c0d8abf63adfa267b1f8f2c72b269
20140415
Sync with CM sources
Kernel compiled with Christopher83's 2014.04 toolchain
md5sum: bc9b6c5403d94a7e63f69aba7f1ec194
20140414
Sync with CM sources
Kernel v3.4.87
Enable LPA (credit arco)
md5sum: 23b1e4fb4b6f863eae2a5ac447f6dafb
20140402
Sync with CM sources
Kernel v3.4.85 (credit Christopher83)
Use older Adreno blobs
Netflix confirmed working
Add Performance Control (credit h0rn3t)
md5sum: d6dbb5bbeb4758657e9c74ad50c16ac8
20131125
Initial release
md5sum: 4fa0b6dd64730f4139d54375555dd91

Basebands & Misc.
Basebands
Flash in CWM recovery. Wipe cache and Dalvik-cache before installing.
T679UVLG3 2012 July
md5sum 61efc2e31fd0885dc0f948f84f94574f
T679UVLK2 2012 November
md5sum 0c0175d46e3fc4c9f11ee3352af85442
Odin 4.43 and USB driver
Placeholder for Odin 4.43, ancora.ops, and Samsung USB v1.3.2410 driver here in rar format.
Newer drivers will not connect with device in download mode.
Works with XP and will not work with win 8.

nice one didn't realize anyone else was deving for our phones. I'll test it out later after i get initial release up for AOIP CE.

Fantastic! I'll let you know if GPS doesn't work. I use it everyday during my runs.
edit*
GPS does work for me. The ROM does boot and works, but it's somewhat slow at times. The browser crashes. I tried clicking the news tab on the google main page. AND... everything is tiny. I'm not sure if that's how kit kat is suppose to look or not. Wow, they weren't kidding when they said kit kat uses little ram. Bluetooth also works... I paired my phone to my Windows 8.1 laptop successfully. I was able to play music on my phone through my laptop speakers, view files stored on my phone and send and receive files.

Thanks for the hard work and bringing us 4.4. Going to give it a whirl and see what happens!

I have heard of some issues with the stock browser on some other devices, due to webviewapi but everyone says chrome works fine. Don't know if that's helpful or the case here. Downloading now, eager to try some Kit Kat.
Sent from my SGH-T679 using xda app-developers app

I use chrome and it performs well enough that I never tested stock browser. chromewebview takes forever to compile, but I'll look at it later.

TripFX said:
nice one didn't realize anyone else was deving for our phones. I'll test it out later after i get initial release up for AOIP CE.
Click to expand...
Click to collapse
Let us know how camera works with ion, I think that's why arco switched back to pmem, but I'll try helping when you're there.

DPI
I went into the build.prop and changed the DPI to 240, I'm sure most folks know how to do that but thought I'd mention it for those who are wondering so all apps will be compatible & such.
On another note Titanium Backup is not showing all apps in batch restore mode that I have backed up, but when I view the Backup/Restore list they are all there. Might be a 4.4 bug.

Thanks for the effort to bring Kit Kat to our phone, hope you'll feel welcome to our community!

ArtfulDodger said:
I went into the build.prop and changed the DPI to 240, I'm sure most folks know how to do that but thought I'd mention it for those who are wondering so all apps will be compatible & such.
On another note Titanium Backup is not showing all apps in batch restore mode that I have backed up, but when I view the Backup/Restore list they are all there. Might be a 4.4 bug.
Click to expand...
Click to collapse
Might be st with the storage mounting points. I know usbdisk is logging a fit and sdcard1 doesn't seem mounted properly, so sdswap may be a temp issue.

jfbs said:
Might be st with the storage mounting points. I know usbdisk is logging a fit and sdcard1 doesn't seem mounted properly, so sdswap may be a temp issue.
Click to expand...
Click to collapse
Well when I try to restore most of those apps, the restore button is missing? Hmmmm...

ArtfulDodger said:
Well when I try to restore most of those apps, the restore button is missing? Hmmmm...
Click to expand...
Click to collapse
It could be caused by selinux permissions, or within TB itself regarding 4.4's API.

jfbs said:
It could be caused by selinux permissions, or within TB itself regarding 4.4's API.
Click to expand...
Click to collapse
Yeah because any system apps can be restored, and just a handful of user apps. 90% of the apps are being read as data only backups. Not sure what else to do at this point. Going to restore my nandroid, backup again and re-flash the ROM. Oddly enough the Play store didn't give the option of just downloading all of them again like it normally does. At any rate if I can't get my apps restored in bulk I won't be able to do this. Manually it would take forever and a day.
I have to tell you however your ROM is very light and smooth with zero tweaks. I'd really like to get this going if I can!

It could be superuser. Try supersu?

jfbs said:
It could be superuser. Try supersu?
Click to expand...
Click to collapse
I did, no luck. If I can get Play to just re-download the apps, I will do that and then restore data.

jfbs said:
Let us know how camera works with ion, I think that's why arco switched back to pmem, but I'll try helping when you're there.
Click to expand...
Click to collapse
Thanks since you are deving roms I can skip making my own rom then and focus more on ION :highfive:. Ya acro switched back because the cam driver has to be rewritten from scratch to work with it. It's not a biggie for me just mostly time consuming but it will be well worth the effort to keep our phones going longer and break the 3000 mark on quadrant :fingers-crossed: You should check out AOIP CE when it's up if ya like the installer I can mod/make one for you :angel:

some questionable advice
ArtfulDodger said:
Yeah because any system apps can be restored, and just a handful of user apps. 90% of the apps are being read as data only backups. Not sure what else to do at this point. Going to restore my nandroid, backup again and re-flash the ROM. Oddly enough the Play store didn't give the option of just downloading all of them again like it normally does. At any rate if I can't get my apps restored in bulk I won't be able to do this. Manually it would take forever and a day.
I have to tell you however your ROM is very light and smooth with zero tweaks. I'd really like to get this going if I can!
Click to expand...
Click to collapse
Don't tell anyone I suggested this, but as long as you have enough nandroids I suspect it can't hurt to try restoring just data from the backup and seeing if KitKat can cope with updating your JB-based data. Worst case nothing works and you have to go back to this unfortunate plan, but you might get away with it. Despite everyone's advice I haven't started from scratch since CM10 -- when moving to AOIP I just wiped ROM and cache but not data. When I briefly tried AOIP 2.0 I saw a message on the screen about "upgrading contacts database". So the bottom line is that Android knows how to handle version upgrades -- which makes sense, because the manufacturer OTA updates don't usually wipe your data.
With AOIP 1.5 the only trouble I had after my unorthodox migration was a crash in the calculator app and it went away when I performed "clear data" on just that app. So it might be worth a try.
[I didn't try asking Android to downgrade data when I switched back from AOIP 2.0 to 1.5 though... I restored the data from my last 1.5 nandroid at that point.]

aaopt said:
Don't tell anyone I suggested this, but as long as you have enough nandroids I suspect it can't hurt to try restoring just data from the backup and seeing if KitKat can cope with updating your JB-based data. Worst case nothing works and you have to go back to this unfortunate plan, but you might get away with it. Despite everyone's advice I haven't started from scratch since CM10 -- when moving to AOIP I just wiped ROM and cache but not data. When I briefly tried AOIP 2.0 I saw a message on the screen about "upgrading contacts database". So the bottom line is that Android knows how to handle version upgrades -- which makes sense, because the manufacturer OTA updates don't usually wipe your data.
With AOIP 1.5 the only trouble I had after my unorthodox migration was a crash in the calculator app and it went away when I performed "clear data" on just that app. So it might be worth a try.
[I didn't try asking Android to downgrade data when I switched back from AOIP 2.0 to 1.5 though... I restored the data from my last 1.5 nandroid at that point.]
Click to expand...
Click to collapse
I was a little skeptical I might get FCs out the wazoo but this actually works, for the most part. It breaks system settings however (no surprise). Only problem is now RAM Expander can no longer use the swap file, even if recreated. Get the "invalid argument" error after creation, although the file is there.
This was a great tip though as most all apps work just fine with no FCs. If I can get Expander working and Viper all will be well.
Edit: Swap files will not work with this ROM. Probably has something to do with path issues, IDK. Viper does not work either but that is a common issue among 4.3 and 4.4 ROMs. Oh well. Still this is nicely done, very lightweight and functional. 4.4 is going to have issues until app devs can catch up.
Great work and first effort @jfbs. I have a feeling I'll be back to try future updates.

Related

[RECOVERY] TWRP 2.6.3.0 touch recovery [2013-09-16]

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Great to have a second choice! I'm still using RomRacer though.
A great clockwork alternative!
Flashed it and it looks great! Haven't tested it out fully but i wish I could use the internal partition because my sdcard is pretty full and the battery percentage would show. Unless i find a reason to switch back to cwm, Ill keep this.
Any plans on adding support for CM7 based roms? Only /sdcard is being recognized, /emmc isn't available at all.
*Edit* Also wanted to include webtop (/osh) in the above question.
I also flashed it, but didn't spend much time in it (got work to do ).
Can the backup restore location be changed to point to backups that were made with other recoveries?
Download link is dead for me
rozzco said:
I also flashed it, but didn't spend much time in it (got work to do ).
Can the backup restore location be changed to point to backups that were made with other recoveries?
Click to expand...
Click to collapse
I don't think other recovery backups will be compatible. The test backup I did yesterday looks like this:
boot.emmc.win
data.ext4.win
system.ext4.win
And none of my CWM backups were showing up when navigating through my sdcard contents.
no more power button + volume down? wow. i need to slow down now
thanks for this.
anyone wana make a zip of this? im sure you will get 3x more users downloading ur recovery than before.
slojko said:
anyone wana make a zip of this? im sure you will get 3x more users downloading ur recovery than before.
Click to expand...
Click to collapse
I did yesterday. See this post from my thread in General.
ive actually been running this for a few days now and found it really awesome!
backup and restores are lightning fast and everyhting ive tried works perfectly
i found that in cm7 based ROMs only the external gets mounted. which is fine because thats what I use
Great work Team Win
Wow, this looks awesome. I just downloaded it and will load it up on my phone in a few minutes. Thanks for the awesome work TeamWin!
Great work, but i'm getting a few issues:
Everytime i try to install something,at the end of process it gives me:
E: cannot load volume /misc.
Also when i mount usb and unmount, later on i try to install something and recovery restarts itself showing homescreen, fixed by going back to usb mount screen and unchecking "unmount cache" although it's weird to see this checked, when actually i didn't check anything( i see only "unmount sd-card" checked when i leave the panel).
Hope this can be addressed soon,cause it's a very nice recovery UI
ATT Atrix 4G
Darkside 4.2
Kernel Faux 0.23 1.45Ghz @stock
Teamwin Recovery 2.0
its possible to use this on locked atrix ?
and..we have any recovery to use with an locked atrix ? i need to wipe my battery and dont know how without a custom recovery....
many tks
There are no recovery for a locked atrix(real ones at least)
Search the market for battery calibration
sent from my Atrix via XDA premium
flaviocc said:
its possible to use this on locked atrix ?
and..we have any recovery to use with an locked atrix ? i need to wipe my battery and dont know how without a custom recovery....
many tks
Click to expand...
Click to collapse
Just unlock it. Its definatley worth it. Then you can get cwm or this and wipe whatever and flash whatever.
And I have to say the recovery is very nice. Kinda weird not using volume buttons but very nice. I am also getting the can't load volume thing error.
Sent from my MB860 with ICS using xda premium
ghost_og said:
I did yesterday. See this post from my thread in General.
Click to expand...
Click to collapse
This works for me One question: can i install .zip file from internal memory,cant find internal sdcard anywhere?
dulexetina said:
This works for me One question: can i install .zip file from internal memory,cant find internal sdcard anywhere?
Click to expand...
Click to collapse
I'm guessing you're on a CM7 based ROM? Currently it only supports motoblur naming (sdcard, sd-ext). They plan on adding support for /emmc at some point. Keep a backup .zip of CWM on your sdcard just in case.
Can you guys take Rom Racer's recovery and just add the tweaks from this CWM to it? Pretty much make a touch version of Rom Racer's...
ghost_og said:
I'm guessing you're on a CM7 based ROM? Currently it only supports motoblur naming (sdcard, sd-ext). They plan on adding support for /emmc at some point. Keep a backup .zip of CWM on your sdcard just in case.
Click to expand...
Click to collapse
I am on blured rom,and even restore did not worked for me-tried many times (to restore full,just data,just system...but no succes) i am back on old recovery until this one gets fixed. This recovery is so simple to use and realy nice,just waiting for full working version now.
Sent from my MB860 using XDA App

[MOD] EXT4All Continued + Now with TWRP 2.3 Support

The purpose of this thread is to host a location and continue support for a really neat ext4 mod.
IMPORTANT: If you flash the no data limit mod you need to do it after every update or your data, which won't be lost will be hidden by the contents of the data data partition.
I'm going to keep this brief. The original thread was closed so I wanted to have a new location where everyone can find the files. But this is a new thread for Jermaine151's and my EXT4all mod.
Below is the original thread which already has a lot of useful information:
http://forum.xda-developers.com/showthread.php?t=1315372
Here is where you can find most of if not all the EXT4All files:
http://dinc.does-it.net/EXT4_Mods/
Sorry this thread isn't too organized but I threw one together so people could post on it with their comments.
This mod should work on all AOSP ROMs including ICS ROMs and MIUI. It's been confirmed on CM7 and MIUI but I've also tested on CM9. It should also work on all Sense ROMs and does work on every Sense ROM I've tested. Be sure to flash a newer version of the gingertiny kernel if you use a Sense ROM as the kernel version flashed to add ext4 compatibility is out of date.
V2 Mods with TWRP 2.3+ support and proper support for filesystem tweaks for ROMs that are already set to use ext4 found below:
V2 EXT4All Mods
FAQ
Q. How do I know if the ext4 mod(s) worked?
A. The best way is to do the following from terminal:
su
mount | grep /data
It should show a line with /data and ext4 and, if it has the no data limit, also a line with /data/data and ext4. If you're on an ICS/JB ROM it will show ext4 anyways. The best way to tell with the new version of the mod is to see if noauto_da_alloc shows in the results of the above commands.
Hey tiny, thanks for opening this btw. Wasn't sure if I should post here or on ur kernal thread but my girls dinc was having the data limit problem so I wiped cache and dalvic, flashed ext4 no data limit normal dalvic then flashed ur newest kernal (3/11 date). And I have been having the hardest time keeping her phone stable. I've tried every governor sav2, interactivex, ondemand, even sa, tried deadline, sio schedulers, even tried raising the voltages to a post u had on ur kernal thread, page 85 or something (wasn't sure if I should set the min and max of the voltages for the same thing, but that's wat I did). But she still says its very unstable. She's running stock+ 3.01 and she DOES have a cheap ebay battery in her phone, not quite sure how much that plays a role in the problem. She's at work right now so I can't pull any logs, but I know ull probably need a logcat? Or I dunno. If u could gimme directions on anything I should post to assist u. And I'm not overclocking at all for the record. On stock kernal she never had any stability issues, uptime of 200 hours+. But urs is definitely snappier and that damned data limit is the main reason y I even switched her over to begin with. Thanks tiny in advanced for everything u do!!!
Sent from my ADR6400L using xda premium
I'd prefer the kernel thread.
And I'll need a last_kmsg. Just copy /proc/last_kmsg with root explorer or another file explorer and attach it to a post on the kernel thread. Since you most likely eliminated undervolting by using the voltages on page 85 of the kernel thread, then it's possible the battery has an effect. I've heard that poorly made batteries can cause issues that stock batteries don't have so further deviation from stock may have an influence. Either way, I'll look at that log once you get it. Make sure not to battery pull until you can copy that log and try to do it within 24 hours of the last reboot to be safe.
the following thread contains very simple and plain english directions for using this MOD. it helped me, and it was my first time rooting. Thanks also to tiny4579 for posting this new thread.
http://forum.xda-developers.com/showthread.php?t=1488351
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
funkpod said:
Question about this mod, I am running CM7.2, RC2, and onto rc3 soon.
I am having random resets, problems w/ my phone freezing, a mysterious message "sorry, process system is not responding", and other various issues. Could it be that the mod is causing some problems for my phone, or more about something that wasn't cleaned out when i flashed over a nightly?
Click to expand...
Click to collapse
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
I've been running various ICS roms and switched back to Warm rev 58. Upon installing the latest kernel and the Ext4 mod. I am unable to install apps. Any idea what may be causing this. I wasn't sure if it was the rom or not do I did an update with SVN and installed that with the same results. I have a nandroid with just the rom and all the apps I want, but would like to overclock and the stock kernel won't allow. And would also like to be able to install a new app should one arise.
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks, how do I generate the logcat?
Sent from my Incredible.
Aw yeah.
Ok. It's not the kernel. Installed the most recent and everything is fine. Installed the ext4 with dalvik moved before that and rebooted and apps were missing and it wouldn't let me install new apps and some of my previously installed apps were missing. When I tried to install them it said it was going to replace an existing app and then said app not installed.
Any ideas???
Sent from my HTC Droid Incredible using xda premium
tiny4579 said:
Try a logcat before wiping which i would suggest in the end or else we won't know. I don't think the mod would cause that though.
Also pull /proc/last_kmsg.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
funkpod said:
also, i can't see the file /proc/last_kmsg
i see /proc , and i see "kmsg" but i don't see "last_kmsg"
is that the same thing?
and for some reason, the android sdk doesn't work now, that i have uninstalled and reinstalled it...
Click to expand...
Click to collapse
Sorry I just dont have time tonight to explain. Maybe tomorrow.
Sent from my Galaxy Nexus using Tapatalk 2
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
funkpod said:
hELLO!
I HAVE A LOGCAT!
and it captures 2 errors.
First, it captures the "sorry, system process not responding" error, and then it captures this weird thing where it restarts. it doesn't go all the way back to the "htc incredible" screen, however, it goes to the cyanogenmod animation, starts up, and THEN goes right back to the cyanogenmod animation, again!
finally, i shut it off, cuz i didn't know how to get the logcat to stop in ddms.
and i have the /proc/last_kmsg... how do i get it to you?
i added a .txt to the end of it so i could upload it, hope that works. is that what you need?
Click to expand...
Click to collapse
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
tiny4579 said:
Try fix uids in amon ra recovery. Amon ra should be listed in from manager. I don't think it's the same as fix permissions in cwm which I believe there is file system based. From looking at your logcat there are a lot of unknown permission errors. Let me know. I'm at work so didn't have a lot of time to respond but wanted to check briefly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
funkpod said:
hey, thanks for looking at it. what do you do for work, that you are working during a holiday?
so, you think i should try fixing user id's in amon ra recovery.
and it should be listed in ROM manager, right?
Now, here's the question, if i'm going to be trying the new RC3 in CM7, and this time i am going to do a clean install, erasing everything. would i still need to fix permissions?
or maybe i should try flashing over RC2 and then fixing permissions?
Click to expand...
Click to collapse
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Sirknifealot said:
Always worth a shot.. If you have the spare time try to flash over and fix permissions as 2nd~to-last thing you do before rebooting, ext mod should be last. Same with if you do a clean wipe to flash RC3 if flash over does not help.
I've personally never had an issue after a clean wipe with permissions, but it would not hurt if you did it anyway. It has been recommended when flash over though as a standard procedure. But only recommended
Click to expand...
Click to collapse
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
funkpod said:
okay, so when flashing rc3, make sure i fix permissions right before the last step, and then flash ext4all mod LAST on the list?
Click to expand...
Click to collapse
If you're wiping I don't see the point of fix permissions as it will fix it back to what it already probably is. I haven't fixed permissions in a while flashing ROMs and I've been ok. Force closes that I got that made me try fix permissions then weren't fixable with fix permissions anyway.
I would wipe, flash ROM, flash kernel if desired, then mod. Though if it's a sense ROM I would switch the order of kernel and mod flashing. So really you can do: ROM, ext4all mod, kernel after a wipe if you choose to wipe to fix your issue.
hey, flashed over to RC3! so far so good, slowly adding things back! will let everyone know how it goes!
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
omniatic said:
Is there a possibility that all or part of this mod could be persistent over multiple wipings?
My reasoning for this question: I originally flashed the 1.0 normal mod on Nils' BGS. In the OP it says it converts the filesystem to ext4. Many moons later, and now on drk's CM9, terminal still lists cache and data as ext4. I did not, however, flash an ext4 mod on any versions of ICS. I know that when I do a factory reset, even though all is formatted, my sd-ext remains ext4, since I set it up that way for Link2sd. Is it possible that the data and cache blocks have also remained ext4 from the original use of this mod, despite wiping and formatting repeatedly?
...sorry...I was on the phone...
Click to expand...
Click to collapse
No, if you actually format the device like when the system runs the format command the filesystem will be ext4. However in your example of CM9 the ramdisk mounts data and cache as ext4. This will actually have a minor improvement over ext3. It'd still be an ext3 filesystem but loaded as ext4 so there's minimal performance gains.
In reality any time you flash a ROM or a boot.img type kernel (not any of mine) you will use the ramdisk of the ROM and reverse part of the effects. But since ROMs like CM9 and newer CM7 versions mount as ext4 you'll still see data and cache showing as ext4. Make sense? I never really did explain it properly before I think.

[Q] i9000 update cm 10.1 to 10.2 - Prob. with Google account

Hallo,
i have a problem with updating cm 10.1 to 10.2 on my i9000. Like i say, i had allready cm 10.1 and prior to that 10.0 and helly bean. Till now everything was fine and every update was OK. I have allready root rights.
Now i tried to flash cm 10.2 like that;
1.
wipe data/factory reset
wipe cache partition
wipe dalvic cache
- flash cm-10.2-20130824-NIGHTLY-galaxysmtd.zip - 2 times
- flash gapps 10.2.x 20130813
- reboot system now
After reboot, i'm in the welcome modus - i choose German - then start - then i can choose the connection WLAN or skip with data. In this part i get allready an error massage "com.google.android.gsf.login" and "unfurnatly google account manager was shut down". After that i'm back again in the choose-connection area. After chosing WLAN or skip and use data, i always get the above mentioned message.
Restore 10.1 again
2.
like above, but extra mounts and storage - format /system
- Result like 1
3.
Just update from 10.1 to 10.2 with CWM, without wipe data/factory reset - wipe cache partition - wipe dalvic cache.
- Result 4.3 is on my mobile, but there ist still the error massage from above.
4.
like 3, but i deleted the Google account in 10.1. Just uodated to 10.2 without wiping.
- Result -> no error massages, but i can't add google account. I clik on add account - google -> but nothing happen.
I don't know what to do. Do somebody have any idea? Where is my oult?
one-dimon said:
wipe data/factory reset
wipe cache partition
wipe dalvic cache
- flash cm-10.2-20130824-NIGHTLY-galaxysmtd.zip - 2 times
- flash gapps 10.2.x 20130813
- reboot system now
Where is my foult?
Click to expand...
Click to collapse
Your foult is that you didn't read pawitp's opening post carefully. All steps untill gapps were fine, then after gapps you should have remained in CWM recovery and go to advanced restore and restore your /data from last nandroid backup from cm10.1, it works perfectly well.
I would advice you not to install 20130824 build anymore as it has some serious bugs (I run it in my i9000 and it works perfectly fine but some people had total re-formatting ofntheninternal SD card and data lost) but wait now for just short, any moment nightly 20130827 will be uploaded. The bugs are fixed there.
Then you can repeat proceeding once again as above and accomplish with /data restore. Then it should work fine again
Ok, i try it
Last question before i try, i have to restore just /data, wich backup do i have to do, full backup or just /data?
Thanx a lot
one-dimon said:
Last question before i try, i have to restore just /data, wich backup do i have to do, full backup or just /data?
Click to expand...
Click to collapse
OK, now the new nightly build is there, CM10.2 20130827
Do all your steps as above (download zip, go to recovery mode, wipe data/factory reset, wipe cache, wipe dalvik cache under "advanced", install 20130827 zip, stop here) now new:
if your last installed build is 10.2 you have already installed gapps for CM10.2 so you can skip re-installing them again
now go to "advanced restore" and choose your last nandroid backup of the CM10.1, where your google account was still working fine
choose now from your last nandroid file the option: "restore /data"
after restore is finished go back to main menu and reboot the system
Unless if you have formatted your SD card meanwhile, all your data will be back like they were in the CM10.1 (also your google account) and your new CM10.2 will work fine.
For thanking, it is common in this forum to click on "thanks" button left beyond all the posts which you find to be helpful
Hy, i tried what you said. I restored 10.1 before it
*
wipe data / factory reset - wipe cache - advanced .. wipe dalvic cache*- install 10.2
then - flash gapps for 10.2
then - restore just data
reboot system
*
4.3 is on my mobile, google account seems to be OK. But then i recognized, that my Contacts, Keep, Google+ and some other points doesn't synchronize. I've tried flash gapps again, then restore data -> error massage "google account closed"
*
My next step was to do above mentioned again - same error massage
*
So, i do it again. After wipe data / factory reset - wipe cache a.s.o. i had a look in my storage/sdcard0. It was full of old data, so i extra formated /system and formated /storage/sdcard0. After that i flashed 10.2 and gapps again and restored data. I receive the same sh.. error again and google account doesn't work.
*
Now i restored 10.1 again completely
*
Any idea?
one-dimon said:
....Now i restored 10.1 again completely....
Click to expand...
Click to collapse
Did you enable contacts sync in your accounts? Other thing you can do is to export all your contacts (in "people" ) as vfc data and after the upgrade import it from your SD card. I did that as I don't like google sync functions (for having few accounts) so I only enabled sync for the apps.
Other great thing is to use free app "SMS backup&restore" and "Call logs backup&restore" (by the same developer) from play store. The apps work for any android version and backup data is compatible to restore as well
Try to post in the development thread of nightly cm10.2 for i9000 or read through, I think also somebody else reported problems with google account, maybe it is solved why it happened.
BTW: for next flashing don't use nightly 20130827 anymore as the new 20130828 is out and it has many bug fixes
______________________________________
Sent from GT-P5110 powered by CM 10.2
Hy, i'm again. I try it with the newest cm, with the same result. I flashed exactly like the developer said. No error message, but play store, contacts and some other things don't work.
I would like to post in the development Center, but I am a to young forum member.
Maybe you could post for me my problem or the link to this posts?
one-dimon said:
Hy, i'm again. I try it with the newest cm, with the same result. I flashed exactly like the developer said. No error message, but play store, contacts and some other things don't work.
I would like to post in the development Center, but I am a to young forum member.
Maybe you could post for me my problem or the link to this posts?
Click to expand...
Click to collapse
Just one question: did you flash the gapps for 4.3 as well? Developer pawitp is a genious person and he doesn't mention it anymore in his first posts (he thinks that everybody knows it.....)
If you didn't, you can do it later as well, just download them and install zip in recovery mode..... Sorry if it doesn't work. Then would be better to wait untilmstable version is released. CM 10.2 works in my i9000 amazing, but another people report bugs.
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
*
Could you*post a question fpr me in the developement thread if this problem is known to the developers and if they have a resolution? Maybe they are allready working on it and solve the problem in next nightlys?
one-dimon said:
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
Click to expand...
Click to collapse
No, mate, if you meant CWM recovery. I would also use Titanium backup app for that, there can't go so wrong.
Could you*post a question fpr me in the developement thread if this problem is known to the developers and if they have a resolution? Maybe they are allready working on it and solve the problem in next nightlys?
Click to expand...
Click to collapse
you have no idea how little free time I have. But you're already on 5 posts, just five more and you will be able to post the questions in development threads. It is anyway better that you describe what the problem is. I think I saw in CM10.2 thread yesterday that the developer pawitp works on that.
EDIT: BTW, restoring /data from nandroid backup made with CM10.1x under CWM recovery -->advanced restore is possible without problems. But I think we have mentioned that already in last posts...
OK, I can understand you.
What do I have to do first: flash gapps or restore /data?
have you checked that dataprotection for these apps is not enabled?
one-dimon said:
OK, I can understand you.
What do I have to do first: flash gapps or restore /data?
Click to expand...
Click to collapse
I've posted your question and left link to this thread in the CM10.2 development topic. Hope somebody will answer soon.
If your Google account worked well in CM10.1x, I would say you should try this way:
download the newest CM10.2 nightly zip (20130830) directly here: http://get.cm/get/amd
download Google Apps zip for Android 4.3
run CWM recovery mode
try option "install zip" and don't install yet, just check if your zip files are visible for the CWM recovery in the folder where you saved them
return to main menu and wipe data/factory reset
wipe cache
wipe dalvik cache under "advanced"
install zip CM10.2 nightly
install GApps for 4.3
go to "advanced restore" and choose your last nandroid backup file made by CM10.1 build where your Google account worked well
now choose (from that nandroid backup file) the option "restore /data"
after your data are restored, go back to the main menu and reboot the system
Let me know if it worked. Please quote at least little bit of my text (click "reply" beyond my post) so I will get the notification that you've quoted me, otherwise I don't see when you answer
p.s. good point by @Marvi70 just one post before (this one) mine
Marvi70 said:
have you checked that dataprotection for these apps is not enabled?
Click to expand...
Click to collapse
What do you mean? How can I check it?
one-dimon said:
What do you mean? How can I check it?
Click to expand...
Click to collapse
in settings -> apps, in the app property of those apps check if dataprotection is enabled (no access to private data). When yes disable it.
Marvi70 said:
Datatings -> apps, in the app property of those apps check if dataprotection is enabled (no access to private data). When yes disable it.
Click to expand...
Click to collapse
OK, I checked all apps, also system apps. Data protection is disabled everywhere.
tetakpatak said:
I've posted your question and left link to this thread in the CM10.2 development topic. Hope somebody will answer soon.
If your Google account worked well in CM10.1x, I would say you should try this way:
download the newest CM10.2 nightly zip (20130830) directly here: http://get.cm/get/amd
download Google Apps zip for Android 4.3
run CWM recovery mode
try option "install zip" and don't install yet, just check if your zip files are visible for the CWM recovery in the folder where you saved them
return to main menu and wipe data/factory reset
wipe cache
wipe dalvik cache under "advanced"
install zip CM10.2 nightly
install GApps for 4.3
go to "advanced restore" and choose your last nandroid backup file made by CM10.1 build where your Google account worked well
now choose (from that nandroid backup file) the option "restore /data"
after your data are restored, go back to the main menu and reboot the system
Let me know if it worked. Please quote at least little bit of my text (click "reply" beyond my post) so I will get the notification that you've quoted me, otherwise I don't see when you answer
p.s. good point by @Marvi70 just one post before (this one) mine
Click to expand...
Click to collapse
Hy, i'm again. I've just tested to flash another ROM. It was slimbean. Everything works fine, there are no problems with gapps. I thing there is a bug in cm 10.2.
one-dimon said:
Hy, i'm again. I've just tested to flash another ROM. It was slimbean. Everything works fine, there are no problems with gapps. I thing there is a bug in cm 10.2.
Click to expand...
Click to collapse
Good to know, thanks for info! Congratulations also CM10.2 will soon be cool, the devs are now fixing the bugs on daily basis
tetakpatak said:
Good to know, thanks for info! Congratulations also CM10.2 will soon be cool, the devs are now fixing the bugs on daily basis
Click to expand...
Click to collapse
I hope so, i allready use cm a long time and i was a happy user till 10.1. I think if my prob. will be fixed, i'll switch to cm again
one-dimon said:
Of course, i flashed gapps for 4.3. Some user posted in developement thread, that they solved the problem with the google account with Titanium Backup. They restored data with TB. Do you know what i have to backup / restore: user apps & data & system data?
Click to expand...
Click to collapse
BTW, after your post about Titanium Backup I've tried indeed to restore data only from my old backup of Angry Birds app, it went perfectly well
Backup file was done with rooted Froyo 2.2 and restored in CyanogenMod 10.2
Before importing the data saved in different ROM, I used the settings exactly like described on the website of Titanium. I've checked again CM development posts about Titanium backup and they talk indeed about the one shouldn't restore whole apps.... but data only seems not to be a problem!
Big thanks, mate!

how to restore Apps and settings after upgrade from CM 9 to 12

My HP Touchpad 16G was running CM9 for a long time. So I finally uninstalled CM9 and using TPToolbox v42 fresh installed CM12.
Before wipe everything on SDCard, I did a backup in CWM and transferred it to my PC. After installed CM12, google backup brought some of my apps back, but I still lost a lot of settings of Apps and saves of my games.
So, I was wondering if I can restore them from my CWM backup. If yes, how to restore only the Apps, not CM9?
Thanks!
shawn8888 said:
My HP Touchpad 16G was running CM9 for a long time. So I finally uninstalled CM9 and using TPToolbox v42 fresh installed CM12.
Before wipe everything on SDCard, I did a backup in CWM and transferred it to my PC. After installed CM12, google backup brought some of my apps back, but I still lost a lot of settings of Apps and saves of my games.
So, I was wondering if I can restore them from my CWM backup. If yes, how to restore only the Apps, not CM9?
Thanks!
Click to expand...
Click to collapse
You won't be able to restore your data as you've now moved from Non data media, to a data media Rom. A lot of games save their data by linking it your Google+ or Facebook accounts. You can check the options menus and connect your games to your accounts in an attempt to recover your saved games. Good luck and enjoy CM12
A lot of the old games don't link to facebook or google to save, such as "cut the rope" and "plans vs zombies" etc.
If restore is not possible from cm 9 to 12, is it possible to upgrade from cm 12 to cm 12 nightly? How?
Thanks!
shawn8888 said:
A lot of the old games don't link to facebook or google to save, such as "cut the rope" and "plans vs zombies" etc.
If restore is not possible from cm 9 to 12, is it possible to upgrade from cm 12 to cm 12 nightly? How?
Thanks!
Click to expand...
Click to collapse
Like I said you can't restore your data, you didn't exactly list which games in your question but my suggestion remains the same. Some user data will get lost during an upgrade, that's to be expected when switching android versions.
You can upgrade your CM12 nightly Rom but if you wish to keep your data I suggest using your recovery.
From the Super Easy way guide in my signature. Enjoy
How to change Roms or update your version of Android:
TPToolbox Method:
After installing a data media rom you can do a clean install of another Rom listed in the guide by again using the TPtoolbox. Return to step 5 B) and install a different Rom. The TPtoolbox will wipe the system, data and cache partitions/volumes and do a clean install, WebOS will not be changed. Your apps and user data will be lost but your media content on the SDcard remains the same. If you wish to completely remove WebOS, Android and all data on the device return to step 5 A) and do a complete data reset.
Note: When installing new roms the TPtoolbox will automatically prompt you to adjust smaller system partitions/volumes from older versions of the TPtoolbox(v40, v41x). For example a 700MB Kikat install will be increased to 800MB for Lollipop or a new Kitkat Rom install.
Recovery Method:
Updating your current Rom with a newer build can be done using your recovery and will keep your current setup and apps. However this can't be done from the TPtoolbox and will require learning about a few Rom flashing techniques from my instructional update guide below.
How to update Android 5.0.x or 4.4x Builds on the HP TouchPad

[Q] Move from CM-11 to CM-13

I have CM-11 (2016-08-15 nightly) installed on my HD+, along with CWM recovery "6046", and am happy with it. However, my other Android devices have Android 6.0, so I thought I'd consider CM-13. Questions:
Is moving to TWRP a requirement? I see statements that CWM recovery is no longer in active development. So what? Are changes being made (see next item) just for the sake of change (a popular activity in software development), or are there real advances that TWRP enables?
In preparation, I downloaded the cm_ovation-ota-MOB31K.161125.zip and open_gapps-arm-6.0-nano-20170117.zip files. I was astounded by the sixe of the latter. What is with the "Open Gapps" files??? I note that the pico one for v4.4 is 2.5 times the size of the one I have been using ( pa_gapps-modular-pico-4.4.4-20141110-signed.zip ). I thought these were supposed to be basic, minimal files.
I'm looking for an install procedure from CM-11. I assume that just means upgrade to TRWP if necessary, and then just use that to install the above zip. I see no discussions of this in this subforum; is it all over in the "Development" forum?
What is the performance of CM-13 like, and is it now stable enough for daily use? I see a long thread peppered with "thank you"s that started two years ago, and I'm wondering if there's anything more succinct.
DeanGibson said:
I have CM-11 (2016-08-15 nightly) installed on my HD+, along with CWM recovery "6046", and am happy with it. However, my other Android devices have Android 6.0, so I thought I'd consider CM-13.
Click to expand...
Click to collapse
FWIW -- I had enjoyed good performance CM11 until about mid last year when many commonly used apps started to become unresponsive and oftentime crashed (force-closed). So over the holidays break I took the plunge and upgraded to Amaces' LN14.1 experimental build lnos_ovation-ota-NMF26Q.170104, so far the performance is as good as it used to be with CM11.
Questions:
Is moving to TWRP a requirement? I see statements that CWM recovery is no longer in active development. So what? Are changes being made (see next item) just for the sake of change (a popular activity in software development), or are there real advances that TWRP enables?
Click to expand...
Click to collapse
Every major release of CM, starting from CM7 -> CM9 -> CM10 to CM11, has required a new and non-backward compatible version of CWM.
I don't believe that CWM 6.0.4.6 can flash CM12 and CM13, and you can find pointers on what recovery versions are needed and are available at https://forum.xda-developers.com/nook-hd/development/boot-sd-external-recoveries-twrp-2-8-3-t3314870.
In preparation, I downloaded the cm_ovation-ota-MOB31K.161125.zip and open_gapps-arm-6.0-nano-20170117.zip files. I was astounded by the sixe of the latter. What is with the "Open Gapps" files??? I note that the pico one for v4.4 is 2.5 times the size of the one I have been using ( pa_gapps-modular-pico-4.4.4-20141110-signed.zip ). I thought these were supposed to be basic, minimal files.
Click to expand...
Click to collapse
I used the minimalist pico package, and then added afterward a couple of missing essential apps like Google Maps.
I'm looking for an install procedure from CM-11. I assume that just means upgrade to TRWP if necessary, and then just use that to install the above zip. I see no discussions of this in this subforum; is it all over in the "Development" forum?
Click to expand...
Click to collapse
The most straightforward route which I found and used is to create a SD-based recovery using the pre-packaged SD image available at https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778, just unzip and burn the image to SD then add to the card the ROM, GApps, and (EMMC) TWRP zip files you wish to flash. Then boot up the SD card into TWRP, (optionally backup your CM11 ROM system & data), do "wipe /data & factory reset", and flash the 3 zip files and you are set to go.
Alternatively you can try to use a similar approach as outlined at https://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171 -- i.e., use CWM 6.0.4.6 to flash new TWRP then boot into the new TWRP to wipe and flash new ROM and GApps. This was the route I took when I upgraded to CM12.1 to try it out.
digixmax said:
... Alternatively you can try to use a similar approach as outlined at https://forum.xda-developers.com/nook-hd/general/how-to-updating-hd-hd-internal-emmc-to-t2863171 -- i.e., use CWM 6.0.4.6 to flash new TWRP then boot into the new TWRP to wipe and flash new ROM and GApps. This was the route I took when I upgraded to CM12.1 to try it out.
Click to expand...
Click to collapse
Thanks very much for the info! That's what I did, and it was simple and (reasonably) quick. I note that CM wants to go ahead and install the CWM recovery. I assume I should not let it do so.
Now, to get Titanium Backup to think it's got root. This appears to be a bit of silliness. I tried several "superuser" apps (including the "phh" one), to no avail so far ...
Edit: OK, here it is ...
belfastraven said:
There is still a "bug" I believe, in that when the cm/ln rom is first installed on a device with a clean data partition (after a wipe or factory reset), even though developer options will say you have root, you actually don't. Changing the root selection to something else and then changing it back causes the necessary system file to be created. As long as you don't wipe data, you will not have to do this again on dirty flashes. What is new in the last few months is that, accessible through developer options, there is a rudimentary root manager available in the rom, where you can determine how root requests from various applications should be handled and see which apps have requested root access.
Click to expand...
Click to collapse

Categories

Resources