Hi all,
since I use Temasek's UNOFFICIAL CM11 my device has various reboots and I do not know why. This occurs since the first V3 I used up to current V20. With my old CM10.1 I nearly hat the same configuration and apps and did not have such reboots.
Because I do not know the real source of the problem (CM11, Boeffla-Kernel, Xposed/Xprivacy, ???) maybe someone can help me finding out the root cause of my problems? Or whom I shall address it to!?
Attached you will find some logcat syslogs of some device reboots including backtraces ecc. (I just stripped some private data). If you need more or with different settings, let me know!
I am not very keen on analyzing those logs, so I'd appreciate your help.
Tnx in advance,
Enkidu
Did you start from scratch already? Factory reset + /system format + fsck on /data + Rom re-installation?
There are several 'Could not write' and 'Too many open files' errors. They look suspicious. If they don't go away after clean reinstallation you might be affected by a low level NAND/eMMC bug.
enkidu70 said:
Because I do not know the real source of the problem (CM11, Boeffla-Kernel, Xposed/Xprivacy, ???) maybe someone can help me finding out the root cause of my problems?
Click to expand...
Click to collapse
Sure, here is how I analyse errors. I think it's called "divide and conquer". If the root cause of an issue in a complex system isn't obvious, try to exclude possible causes. Either start with a few modifications as possible (i.e. only CM11, their kernel, no flashed modifications, uninstall Xposed) or take one modification away at a time (e.g. keep CM11 and the kernel, but disable the Xposed modules one after another, then uninstall Xposed, etc.) Every modification you take away while the error keeps showing up can be excluded as possible cause. With this, you should be able to narrow down which modification makes the error show up. To be sure, try again without the modification for some time and then with only this modification. Once you are sure, check if you can narrow it down even further, e.g. by reverting to default settings.
Both logs show that there are "Too many open files", but that doesn't come out of nowhere. It's probably a symptom as well, but might help to find the root cause once you have narrowed it down to the modification (or to the ROM itself).
enkidu70 said:
(CM11, Boeffla-Kernel, Xposed/Xprivacy, ???)
Click to expand...
Click to collapse
I'm on the same setup (but Temasek kernel) with Xposed/XPrivacy and it runs stable. Maybe try another kernel.
DualJoe said:
Did you start from scratch already? Factory reset + /system format + fsck on /data + Rom re-installation?
Click to expand...
Click to collapse
Yes and no. I started from scratch with CM11. And I have these reboots since the beginning.
I frequently do nandroid backups and restores, so filesystems should be ok...
DualJoe said:
There are several 'Could not write' and 'Too many open files' errors. They look suspicious.
Click to expand...
Click to collapse
In my opinion this is part of the problem. For me it seems that something is opening too many files and after a while system is out of free filehandels and has to reboot... But I am not sure.
rovo89 said:
Sure, here is how I analyse errors. ... Once you are sure, check if you can narrow it down even further, e.g. by reverting to default settings.
Click to expand...
Click to collapse
Tnx. I already wanted to do something similar. Today I installed a kind of permanent logcat via init.d writing all to my internal sd so that I can see if it reboots. (Soft reboots are so fast and I did may have missed some of them.)
rovo89 said:
Both logs show that there are "Too many open files", but that doesn't come out of nowhere. It's probably a symptom as well, but might help to find the root cause once you have narrowed it down to the modification (or to the ROM itself).
Click to expand...
Click to collapse
I still hope someone just tells me "ah take a look at ... that's it!" So that I need not to track it down by degrading all my security settngs.
Tnx for your replies!
Enkidu
enkidu70 said:
I still hope someone just tells me "ah take a look at ... that's it!" So that I need not to track it down by degrading all my security settngs.
Click to expand...
Click to collapse
I doubt you can degrade yourself into such state - at least not with any high level stuff. Your problems are below DalvikVM. I would rather accuse the kernel or even lower the eMMC itself. That's why i recommended to take a backup and reinstall from scratch (with Temasek or stock kernel) to make sure the hardware is ok.
- Check dmesg output (cat /proc/kmesg).
- Filesystem integrity errors cannot be fixed by restoring backups since /data won't be formatted by this (due to internal sdcard). I still point to fsck from recovery.
- dd create an image in Android (busybox dd if=/dev/urandom of=/data/test.bin bs=1M count=1000; sync) and watch if errors occur. If they do try the same in recovery.
But my first pick is still kernel issue...
DualJoe said:
I still point to fsck from recovery.
Click to expand...
Click to collapse
How can I do a fsck from recovery? I use CWM 6.0.4.4 but I can not connect with adb:
$ adb shell
error: insufficient permissions for device
DualJoe said:
- Check dmesg output (cat /proc/kmesg).
Click to expand...
Click to collapse
What shall I look for??? There is lot of output...
DualJoe said:
- dd create an image in Android (busybox dd if=/dev/urandom of=/data/test.bin bs=1M count=1000; sync) and watch if errors occur. If they do try the same in recovery.
Click to expand...
Click to collapse
Tnx, I will do so.
Anyway. When I do a full backup of my int. sd, format /data, restore a nandroid backup and restore my backup of int. sd, this would ensure that /data is ok?
Enkidu
I don't know current CWM versions but maybe try 'adb root' first.
Also make sure it's SELinux aware (CM11 compatible). Maybe this is even the culprit that its somehow mixed up or something due to older backups (in case your using incremental backups) and SELinux permissions are corrupt. I prefer TWRP these days because it uses standard tar format.
Regarding dmesg.. I don't know. Maybe pipe in a file and search for 'error' or something.
Doing a backup/format/restore should recreate the filesystem, yes. It doesn't help though if SELinux permissions of the backup are messed up. I have no clue how to check that though. If in doubt you can start from scratch and inject the data manually (after manually unpacking the backup). This might be not so easy on incremental updates though.
DualJoe said:
I don't know current CWM versions but maybe try 'adb root' first.
Click to expand...
Click to collapse
(Un)fortunately this did not change anything. BUT now I switched to TWRP Recovery 2.6 and this seems to work perfect! adb shell works as expected. And it looks and seems to be much better than CWM! (I was on CWM since ages and didn't look for alternatives... )
DualJoe said:
Regarding dmesg.. I don't know. Maybe pipe in a file and search for 'error' or something.
Click to expand...
Click to collapse
I will include it in my "syslog" script that collects all logs. (I installed it to init.de and initiate a logcat to write it to my internal sd...)
DualJoe said:
It doesn't help though if SELinux permissions of the backup are messed up.
Click to expand...
Click to collapse
Well, when I find time I will install it from scratch and restore my apps by using Titanium...
Tnx for you support.
Cheers,
Enkidu
DualJoe said:
- Filesystem integrity errors cannot be fixed by restoring backups since /data won't be formatted by this (due to internal sdcard). I still point to fsck from recovery.
Click to expand...
Click to collapse
Well... Now I installed TWRP 2.6.3.1 (latest available) but I have more issues:
Where do I find fsck? Trying 'fsck' just results in file not found.
When I try to install e.g. pa_gapps my phone does not boot anymore. It just shows Temasek's logo forever... What can I do?
Tnx in advance,
Enkidu
1. Look in /sbin or use 'ls /sbin |grep fsck'. Should be 'fsck.ext4' 'e2fsck'.
Be sure to have /data unmounted and do '/sbin/e2fsck -fy /dev/block/mmcblk0p12'. Optionally you can do an 'echo $?' afterwards to get the exit code. You can look up corresponding codes here.
(Its a pain but it's even possible to do that in TWRPs built-in terminal.)
2. Use Banks Gapps (see Temasek 1st post). Mount /system, go to /system/addon.d and delete all scripts there (rm /system/addon.d/*.*). Then (re-)install/update Temaseks rom first (will delete old gapps) and Banks Gapps afterwards.
The addon.d scripts are called when you update/install roms. They would save/backup the old gapps if not deleted beforehand. (Only) this time we don't want that so we delete them.
DualJoe said:
2. Use Banks Gapps
Click to expand...
Click to collapse
*Pooohhh* pa_gapps were just nice because there is just ONE package with all in it! Now I have to download and install a bunch of files...
Also it seems that there are not all gapps included? (pa_gapps is arounf 270MB or so. BaNkS just around 100MB!?)
Ok, I will give this a try because TWRP is much better...
What a never ending story this time...
Tnx,
Enkidu
I have no clue if pa-gapps are still valid for cm11.
There should be a full package for banks as well.. The smaller ones are just optional if i remember correctly.
DualJoe said:
I have no clue if pa-gapps are still valid for cm11.
Click to expand...
Click to collapse
Yes, they are. See http://forum.xda-developers.com/showthread.php?t=2397942
Currently I am back to TWRP but I have some problems... Let's see if I can fix'em...
Well... The more I try the worser it becomes...
TWRP installed, all filesystems checked (only problems on fat32 extSD, nothing really important), /data is formatted, other gapps, permissions fixed, ...
So it is better to do a full wipe... Damned, I hate that.
Tnx for all your help. I learned a lot!
Cheers,
Enkidu
Related
THIS WILL NO LONGER BE MAINTAINED and is officially killed
go here if you want rw access and get the version without a kernel.(assuming you have a kernel installed that has aufs support)
IF YOU FLASHED THE UPDATE.ZIP THAT WAS ON THIS PAGE...PLEASE DO THE FOLLOWING:
You need to remove the init script and static busybox that were installed on your device. You have to do this in recovery mode since your rw access is not real.
Download the version linked to above and place it at the root of your sdcard.
open rom manager
select boot to recovery
boot to recovery while plugged in to computer
then from computer:
Code:
adb shell
mount /system
mount /data
rm /system/etc/init.d/99sysrw
rm /data/bin/busybox
umount /system
umount /data
exit
and from the phone:
flash BlaY0's update.zip you put on the sdcard
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
wow, best news that I have heard all day.
Ah! Thank you so much. I was just asking about this a couple weeks ago.
Sent from my T-Mobile myTouch 3G Slide using XDA App
does this mean that we can use metamorph now?
sorry if its a stupid question
Hayzie said:
Really cool for your contributions.
I have no clue what you said, though. Will I be able to uninstall system apps with this? I'm guessin not as you were mostly speaking of partitions.
Lemme guess, brings ext2/3 etc together for something?
Click to expand...
Click to collapse
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
rodriguez27 said:
does this mean that we can use metamorph now?
sorry if its a stupid question
Click to expand...
Click to collapse
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
thanks for the quick info
I'm gonna try this out with Android Commander. With this I should be able to remove apps and delete files without restarting into recovery and mounting everything. Right?
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
Click to expand...
Click to collapse
apparently I was wrong.
as a test I did...
Code:
rm system/app/com.amazon.mp3.apk
while the phone was booted and it worked!
Even after a reboot I do not have com.amazon.mp3.apk installed
It worked for me too, I used android commander booted and running and removed out of /system/apps android.tether.apk, mytouchmusic-signed.apk, and twitter.apk. I had a force close when I removed one thing (I am sure it was running in the background)
They all were gone after a reboot too, I was also able to update adfree just fine.
Any way this can be built into roms?
Thanks for the hard work!
dumfuq said:
No, You will not be able to uninstall apps with this (at least I don't think). It doesn't actually let you write to the /system partition, it just creates an overlay.
And No it does not even look for an ext partition, it just uses the data partition.
Don't really know, I haven't tried. Bear in mind however since it is on your data partition, space could be an issue. Any files changed would then be stored in /data/sysrw.
Click to expand...
Click to collapse
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
sino8r said:
Hey dumfuq, thanks for this! Great idea on porting this badboy! One question though... from what I understood from the source thread is that will use the EXT. Partition for data if you have it right? So it won't break a2sd? I think I understood that correctly. Plus you need your kernel and that should make it work on any rom. I assume it won't overwite the OC kernel either. I'm excited to try this one out but I'm in the middle of rebuilding my rom so I can make a new backup (my old corrupted finally). I will test out as much as I can and let you know if different roms work. I should be done reinstalling by tomorrow (i have like 200 apps, lol!). This might turn out to be a good way to skip nandroiding and wiping all together if it turns out to work properly with a2sd/a2fat32... don't ya think?
Click to expand...
Click to collapse
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
dumfuq said:
This version is not the same as blayo's for the legend. It is closer to the desire one (although I used info from both).
Mine will not even try to detect an ext partition at this point, it just uses the data partition regardless of what is available.
Also nothing at all will get overwritten with this unless you happen to have an /system/etc/init.d/99sysrw file. It doesn't copy the kernel or modules, instead it just assumes you have a supported version . The only thing this update.zip does is add the script into init.d.
Click to expand...
Click to collapse
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
sino8r said:
I see... so basically, only cm based roms will work. Well, eventually, most us will move to cm based roms once bluetooth and a few minor bugs are worked out. Well, thanks for the info!
Click to expand...
Click to collapse
I haven't used them, but I think the newer sense roms support init.d scripts so you should be all good.
Working great on Fenix 2.0 with one of dumfuqs OC kernals...thank you much for this.
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
dumfuq said:
V2 is posted. It is essentially BlaY0's script for legend. I've only tested with no ext partition, but hopefully if you have one it will use it to store sysrw.
Click to expand...
Click to collapse
just so you guys now, v2 probably doesn't work for people with who want it on the ext. Blay0 fixed his though (to support non ext users), so I'll give it a look here soon.
Both versions do not work on stock kernel. Am I missing something? Should I use dumfuq kernel or cyanogenmod kernel in order to use this?
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
WHAT!!?? My slide has finally lost it's parasite, com.amazon.mp3 you are toast now. You and your friends kickback, talkback, soundback, twitter... not sure what else I erased, oh genie widget. Thanks dumfuq!! You are the man
Everyone that does this, make sure to check cyanogen's wiki on making a barebones rom so you don't delete something you actually need (of course you did make a nandroid before doing this so no need to worry if you do).
You won't actually delete anything... overlay just makes you (and system) think it is deleted.
I wanted to post this here since I've been busting my tail on an update for a week now. This WILL flash, Backup & Restore android 4.4 roms! USB mounting, internal & external sdcard mounts as well. There are still a few bugs to work out but give it a go & some feedback. It's still a WIP but plenty stable to use daily for now.
Also anyone interested in flashing the CandyKat sweetener packs, you may now do so with this recovery!!
TWRP 2.8.7.0
I am not responsible for misuse, bricks, or exploding devices! Flash at your own risk! You can download the zip file & flash it from within your existing recovery & reboot to recovery.
CREDITS: Javelinanddart for fixing mounts, f2fs, & for fixing vibration for 5.0 & up Disconnecktie && Santod040 I have bugged these guys to death to get this working so Please stop in & thank these guys as well. They are a huge part of the success of this! Obviously this couldn't happen without Omniroms Source! And a huge thanks for
Dees_Troy for his guide to compiling twrp recovery!!
TWRP Themes have changed a bit & if you use a them then you'll want to checkout this link.
THEMING TWRP THE NEW WAY!
What's new in 2.8.7.0
- Initial ground work for software drawn keyboard (_that)
- Fix handling of wiping internal storage on datamedia devices (xuefer)
- Allow DataManager to set and read values from the system properties (xuefer)
- Fix crash when taking screenshots on arm64 devices (xuefer)
- Fix error message after an ORS script completes (Dees_Troy)
- Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
- Add system read only option - more details below (Dees_Troy)
- Add resize2fs and GUI option to run resize2fs (Dees_Troy)
- Fix crash loop caused by empty lines in AOSP recovery command file (_that)
- Prevent duplicate page overlays such as multiple lock screens (mdmower)
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won't prompt to install SuperSU and TWRP won't try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don't take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
THEMING?
USE 1080P THEMES
Yeah!!
This is working perfect! Damn I missed TWRP. So freaking sweet!!
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Works well except mount memory
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
Mounting which partition? Anyone that finds an error or a bug should try posting the recovery log after said error. Don't post the entire log in a post but put it on pastebin or something similar. Having the logs greatly increases the likely hood the issue will be fixed. Thanks.
Liwais said:
Works well except mount memory
Click to expand...
Click to collapse
What do you mean by mount memory? Where you add something from the pc to the sd card & it shows up on the internal when in twrp? The internal sd card mounts when connected to the pc, not the external sd. I don't know if that's how it's suppose to work or not. This is my first twrp attempt and I had to build it from scratch basically. Like Disconnecktie stated, a log may be helpful.
Great work. Missed TWRP. Just had to tick off my internal sd. Panicked when my partition wasn't visible with my ROMs to flash. LOL.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
skearton said:
For some reason (most likely that I'm a dummy, or missed reading somewhere)
Recently my SD card took a poo, so I've been saving to internal memory.
I flashed TWRP. When I look in sdcard I have no files visible. When I am booted into CandyKat I can see my files with my file explorer. Am I missing a valid mount somewhere? When I go to / I don't see a folder called storage, and in my /sdcard all I see is a folder called TWRP which is empty.
THanks!
Click to expand...
Click to collapse
When you are in TWRP recovery are you selecting "Internal SDcard" or "MicroSD card"
Edit: Latest twrp recovery with vibrations enabled!
gimmeitorilltell said:
Updated OP with better mount paths & usb mounting working better. Guys if you all test this latest and give feedback, I'm working on getting this to the official site and in Bigbiff's thread. I appreciate your input. I have worked tirelessly to make this work but I may be missing something. Let me know what you find, working or not. I know the vibrate isn't currently working in recovery but I am looking into that.
Click to expand...
Click to collapse
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
No it was not. I've been waiting on more feedback from the update or any of my twrp builds. Now that I'm aware of it, I'll look into that so we can get it official in Bigbiffs twrp thread. I think it's close enough for him to release it as an official but this is my personal feelings. It'll be a couple days maybe before I get back to it since I've spent the last week concentrating on this, it's time for me to move on to other things for a moment.
Sent from my HTC One Max using Tapatalk!
Newest build is working g sweet gimme. Love how ya added the button vibrate too. So far I've done 3 full wipes/flashes and your twrp has been flawless thanks for bringing this to us gimme.
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
developweb said:
Haven't tried your update yet but on the last build in order to use themes I had to load them into /data/media/0/TWRP/theme/ which I believe will be overwritten as soon as I flash another ROM. Is this one of your corrected paths?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
gimmeitorilltell said:
We can probably keep this here until the bugs are worked out. Have you tried the latest here yet? I don't theme my recovery but I'm willing to so I can get it correct.
Also that may be something you can set in twrp, set a different default path for themes but I'm not 100% sure.
Click to expand...
Click to collapse
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
developweb said:
Default path in latest is correct now. Themes work from the correct directory now (/sdcard/TWRP/theme/ui.zip ) so they won't get deleted. Love button vibration as well! Excellent work.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
gimmeitorilltell said:
Thank you for the feedback, it is very much appreciated! If you run into anything else, good or bad, Please feel free to give a shout out. I have OCD and with the vibration as an option, well it just was NOT an option to NOT work.. Lol
Click to expand...
Click to collapse
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Liwais said:
I had in mind when're in rekaveri not mount the memory to your PC
Maybe this Problem just me, let me know
Click to expand...
Click to collapse
I'm not sure that I understand what you're saying? The internal sd mounts to the pc once you go into twrp & mount it.
developweb said:
I tried to install the full aroma rom patch by pollution and it seemed to work but gave com.android.phone error on boot. So I thought easy fix, I'll restore the backup I made with TWRP yesterday and got even more errors. Yes, I factory reset before restoring. It seems that this TWRP is not doing everything like it used to under the 4.2's. I'm going to go back to CWM and restore a CWM backup, regroup, recharge.......and try again from scratch to test this thing out again. Wish me luck.
Click to expand...
Click to collapse
Best of luck to ya! I have restored my nandroid with twrp but not in my latest version. I'll give it a try this evening and see what happens on my end. I have not used the aroma installer because I personally would rather not use it. I just use the camera fix from Pollution since I don't have the screen flicker or any other issues with my phone.
Depreciated!! See this thread for the new recommended package. All of my instruction below is still valid, just use the new package from thread linked here.
http://forum.xda-developers.com/showthread.php?t=3234422
~~DISCLAIMER~~Flashing roms, kernels, and mods come with NO guarantee, NONE, ZILCH, NADA . . Do NOT use this package if you do not grasp and understand this concept. You have been warned.
This is a recovery flashable that will extract your boot.img, unpack all pieces, modify fstab.shamu to disable forced encryption, repackage, and flash boot.img back to system. It does NOT actually unencrypt your device. More on that later.
It will work on ANY kernel for this device, regardless of whether it is the stock kernel, or a custom ROM kernel. Also to date, it has shown to work on any version of android . . it is essentially future proof (unless google throws us a major curve ball in the future and radically alters how encryption is triggered at first boot).
Why use this? Who is this package for?
-If you are running 100% Stock Rom, but have a recovery installed and wish to unencrypt your storage. No root needed.
-Running a custom kernel you like, but it forces encryption and you want to change that.
-Currently unencrypted but want to flash a rom that uses FORCEENCRYPTION by default (cyanogenmod12).
-Just bored and want to toss the dice and see what happens.
That is pretty sweet right? Now you can flash anything and as long as you flash this afterwords, you wont have to worry about booting a rom and seeing that dreaded "Encrypting" screen anymore.
What doesn't this do?
-Well, to be blunt . . it does NOT actually UNENCRYPT your device. You will have to bite that bullet on your own, but I will offer some advice on that front later.
Changelog:
03/30/2015
Remove my ill advised attempt to auto patch nightlies, not possible
01/12/2015
Initial Build/Release
Includes fully working patch to initrd, specifically fstab.shamu to revert FORCEENCRYPTION by default.
Buglist:
Auto patch support removed, would never work anywayaddon.d support not currently working - fix is to flash this package with every nightly to preserve unencryption
How to download and install?
Download - NO_FORCE_ENCRYPT_shamu_v1.0-signed.zip
Reboot Recovery - TWRP only has been tested as working
Select "Install" and navigate to where ever you stored that file . . likely /sdcard/downloads/
Take a deep breath and wait for it to finish.
TADA . . done. Reboot and Profit!!
NOTE: You can feel free to flash this as part of a line of other packages.
Example: You are already unencrypted and want to flash Cyanogenmod 12 (assumes you have all packages downloaded already)
-TWRP factory reset (optional but recommended when coming from another rom)
--TWRP's built in factory reset function does quite well, but if you are like me and want a clean slate . .
---TWRP>Wipe>ADVANCED WIPE> and check System, Data, Cache (will leave internal storage intact). This is recommened specifically in conjunction with switching GApps.
-Install> and select all packages at once. I recommend the following order . . Rom, then my Kernel Patcher, then SuperSU (optional), then GApps last.
That was certainly easy right? Well the truth is, unless you are already unencrypted . . nothing will be different. You will still be encrypted. Bummer right? But that is where these next steps come in. They will give you the options available to reach the fabled unencrypted status!!
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset (may not work properly with a custom recovery installed)
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot format userdata
[note - I originally said to use the fastboot erase userdata function. This caused a recovery bootloop. Switching to "format" instead solved this issue. Thanks @aussie1234 for pointing this issue out to me]
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Some may notice there is an experimental addon.d included. This NOT WORKING YET. DO NOT TRY AND USE IT. Not quite sure yet where in the chain it is broken, but that will be a problem for another day. In theory it should, but . . read the "disclaimer" at the top of this post. The idea here is to be able to flash nightlies as they roll out without having to re-apply this patch manually every time. This function is NOT supported on Stock Roms. If you try it and it works, let me know. Do NOT come yelling to me that it did not work and crying that you are now encrypted again. No whiner babies allowed.[REMOVED: didn't work and caused conflicts with some packages]
At the core of this tool is a script build by @dk_zero-cool which can be found . . [DEV][INITRD][2013-10-25] Injector - An Android Ramdisk Injection Tool
Ultimately, this package is as much his as it is mine. It is his magic script that did the hard part, I just put it to work in a new way.
Please don't share this package directly, link them back here if needed. That way, they can get proper support and instruction for its use.
Also thanks to @rascarlo . . his github made it easy to find what needed modded.
Nice! Now just to double check, im unencrypted so if i flash cm12 and this cm12 wont encrypt my phone while still using cm's kernel?
That is correct. In my tests it has worked just fine that way.
Edit: In fact, I just tested this exactly and works as expected.
On a side note, I can confirm that addon.d support does NOT work - do not attempt it. I updated the OP to reflect this and add a stronger warning. Right now you MUST flash this everytime you flash a rom that forces encryption.
Just what the doctor recommended for a flash-addict like my self....
Thanx :silly:
. . . uploaded from a hand-held Killer WHALE
Works like a charm much alohas bradah hixanthus
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
bmwh0r3 said:
So say I flash a ROM. I want to do ROM, kernel, your boot.IMG, the gapps followed by a factory reset/erase user data if I understand correctly?
Example : DirtyUnicorns then leankernel your zip and then gapps
Click to expand...
Click to collapse
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
Just do the factory rest then if already encrypted unless data is removed it will stay encrypted
Sent from my Nexus 6 using Tapatalk
hlxanthus said:
Well if you flash lean, don't bother with my flashable, as lean is already set for no force encryption isn't it?
Click to expand...
Click to collapse
bmwh0r3 said:
I'm not sure anymore. Will look. I tend to break things when flashing because I don't read closely. On my vzw note 3, I was well known to break everything. Kinda scary now that I have a nexus lol
Yes you're correct. I wonder why I can't get decrypted then?
Click to expand...
Click to collapse
hlxanthus said:
Below are the only three options I know of unencrypt once you are running a patched kernel. Select one below that works for you.
~~WARNING~~
The below methods WILL erase EVERYTHING from data, including your INTERNAL STORAGE. Backup all important files, pictures, etc before proceeding. You have been told!!
-Go to Android>Settings>Backup & restore>Factory data reset
-Reboot to recovery and go to TWRP>Wipe>FORMAT DATA . . type "yes" to confirm
-Reboot to bootloader and type . .
Code:
fastboot erase userdata
Edit: make sure you boot android first after unencrypting before going into recovery. This will allow the proper creation of multiuser partitions, otherwise, twrp will not use the proper /data/media/0/ as root of storage.
Click to expand...
Click to collapse
https://github.com/imoseyon/leanKernel-shamu/commit/58ac4f97d882414bdea35d0d1ef0cd6f9027a3bb
Yes, lean kernel doesnt force encryption. If you are currently on lean kernel, so one of the three methods to unencrypted from above (quoted from my OP)
This worked great for me! Thank you SO much!
jtorress said:
This worked great for me! Thank you SO much!
Click to expand...
Click to collapse
It really is that simple isn't it? Glad it was of help!!
Mine is encrypted n6 running cm12 nightly .
So flashing this will format my storage or just data partition ?
I dont wanna loose my personal data's :/
This will not wipe anything. The package only turns an encryption forced kernel into a no force encryption kernel. It is then up to you to follow one of the three options from my OP to reach actual unencryption status.
But you can relatively easily do it, though it will take a little time. Boot to recovery, flash my package, and then create a nandroid backup. Then backup the entirety of your internal storage to your PC or OTG storage device. Once that is done, do one of the 3 methods to unencrypt. Once you do that, boot android (this step is important as it builds proper multiuser partitions) then restore data to your internal storage. Then boot back to recovery and restore your nandroid backup. That will take you back to the exact point you were before but now unencrypted.
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
indigo888 said:
I did all steps,but it still shows me that I'm encrypted. What am I doing wrong?
Click to expand...
Click to collapse
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
hlxanthus said:
Walk me through in your own words what you did. Maybe we can figure out where you went wrong.
Click to expand...
Click to collapse
I flash package and made nandroid backup in recovery.Then made factory reset and boot Android till welcome select language. Then switched off into recovery and restored backup....
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
hlxanthus said:
And when you say you did a factory reset, how did you do that? A twrp factory reset will not work as it leaves the internal storage in tact. I am very explicit on the 3 ways to do this part (at least I thought I was).
Click to expand...
Click to collapse
I did it from menu/settings/backup and reset.
indigo888 said:
I did it from menu/settings/backup and reset.
Click to expand...
Click to collapse
Might be worth trying the other two methods as well. TWRP's format data method and the fastboot userdata method are pretty thorough. Should get you up and running
On soak test build link2sd not mounting the partition after reboot...
EDIT: As of now Link2SD is working fine on latest version of Link2SD...
u rooted lollipop ??? if yes !! how ??
ChaTy said:
u rooted lollipop ??? if yes !! how ??
Click to expand...
Click to collapse
Installed stockrom>flashed twrp>flashed superuser zip>flashed flashable 5.0.1 zip by @tech_master
aAll working well except link2sd:good:
ohh...any thing i can do now??
m on 5.0.2 lp.. with unlocked bootlader... and i fear to revert back to kk as i think it would brink my device!
Yes the mount script is not running automatically on boot. Why is this so? Is there any possible workaround?
ChaTy said:
ohh...any thing i can do now??
m on 5.0.2 lp.. with unlocked bootlader... and i fear to revert back to kk as i think it would brink my device!
Click to expand...
Click to collapse
No any work around found. Tryied all workaround like installing init.d toggler also no use. So i, flash my cm11 backup. Using cm11 now. (between i dont like lollipop visuals and stock rom is no extra features, not even xposed will work so i use cm12 only when arrive)
After flashing Cm11 i found on the Web that in twrp recovery go to advanced and select fix permission and try mounting link2sd but before you do take full nandroid backup.. If brick happens....
Adarsh1998 said:
On soak test build link2sd not mounting the partition after reboot...
Click to expand...
Click to collapse
I just installed the latest link2sd update. It first shows partition not mounted then shows an error message and shows the option to recreate mount scripts or quick reboot because the mount script is loaded after system startup and after quick reboot second partition is really mounted. I think after every reboot this quick reboot is necessary , but at least its now working.
And apps2sd is working for all the apps.
rkmiks said:
I just installed the latest link2sd update. It first shows partition not mounted then shows an error message and shows the option to recreate mount scripts or quick reboot because the mount script is loaded after system startup and after quick reboot second partition is really mounted. I think after every reboot this quick reboot is necessary , but at least its now working.
And apps2sd is working for all the apps.
Click to expand...
Click to collapse
What partition you using? .,ext2, ext3, ext4,fat32?
Please tell how you mountend step by step
Are you able to link apps?
I think i found the error guys the problem related to lollipop is older version of lollipop.
By version 4.0 this problem vas solved.. .. Anyone plz try and reportback.. ..
It still doesn't automatically mount the second partition. Boots up, shows the error, after quick reboot, it then starts working. I guess init.d scripts aren't working at all. They are not at all mounted at boot no matter what. Tried init.d toggler, enabler and what not, nothing works at all. Problem is with lollipop probably.
Adarsh1998 said:
What partition you using? .,ext2, ext3, ext4,fat32?
Please tell how you mountend step by step
Are you able to link apps?
Click to expand...
Click to collapse
I am using ext4 . And yes I can link apps now. I didn't do anything special. Its just like after booting once it needs to quick reboot once again to mount the second partition and then the linked apps appear. Its still not perfect but its working. I would not suggest to link any important apps , I am only linking games and theme apks etc. so that if something goes wrong it doesn't matter.
Adarsh1998 said:
After flashing Cm11 i found on the Web that in twrp recovery go to advanced and select fix permission and try mounting link2sd but before you do take full nandroid backup.. If brick happens....
Click to expand...
Click to collapse
What do you mean by this? Are you trying to say that after we have lollipop, we have to go to twrp recovery and fix permissions and then try back link2sd and it would work then? Where did you find this info? Can you please provide the link?
nilanko said:
What do you mean by this? Are you trying to say that after we have lollipop, we have to go to twrp recovery and fix permissions and then try back link2sd and it would work then? Where did you find this info? Can you please provide the link?
Click to expand...
Click to collapse
Here http://forums.androidcentral.com/general-help-how/387679-link2sd-ext4-xt303-problems.html refer 3rd post
Thanks but I dont think it's gonna work. Problem is not with permissions, problem is that init.d scripts are simply not run at boot at all and until and unless tht happens, nothing can be done. I used a test script which supposed to run at boot but it simply didn't run. I dont know whats going wrong with lollipop. I hope some senior member throws some light upon this issue and I hope the creator of link2sd is also listening.
[solved]
I confirmed that in lollipop build link2sd v4.0 released yesterday only work..
But one roblem there that after reboot u have to quick reboot everytime. This is I think bug in the init.d of the ROM not the link2sd fault...
It's up to mfn subscribers to report this bug as soon to make sure final build will come buggless........
If I am wrong..correct me.
Don't use cracked plus version it won't work
Adarsh1998 said:
Don't use cracked plus version it won't work
Click to expand...
Click to collapse
Who to make link2sd working? i have a ext3 partition, but not work on lollipop, i have mount error, at all boot
brundark said:
Who to make link2sd working? i have a ext3 partition, but not work on lollipop, i have mount error, at all boot
Click to expand...
Click to collapse
I tried with ext4.. On thing is after restart dont creat another mount script.. simply go to reboot and chose quick reboot. .. .
But my phone restarts itself outta nowhere in every ROM! There was no Xposed module installed nor any other apps who want root permissions (I installed fresh KitKat 4.4.4 but still)
My main point is, it doesn't soft reboot, which makes all linked apps disappear after booting up. Any fix for this? (My phone was fell on the floor once which made it's screen cracked and I can't hear any audio anymore. I put the new screen but... :/ I don't think it'll be related to all of sudden reboots)
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
keeganjk said:
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
Click to expand...
Click to collapse
I wiped my device and reinstalled FreedomOS, once I restore all my settings, folders, etc. I'm going to see if it works.
I wiped my device and reinstalled FreedomOS, it still shows up with the same error.
I just wiped and reinstalled OxygenOS http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_4.5.10/. Once I reconfigure all my settings, files, etc, I'm going to see if it works.
I got it working by installing the official recovery, official OOS Image, and then flashed the Bluspark TWRP. It worked a few days ago, but now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
keeganjk said:
I got it working by installing the official recovery, official OOS Image, and then flashed the Bluspark TWRP. It worked a few days ago, but now it has the same error when I try to make a backup. (I feel like it might be from installing https://forum.xda-developers.com/android/software-hacking/kali-nethunter-magisk-t3676681, but they say it's unrelated). Doors anyone know why this is happening again?
Click to expand...
Click to collapse
There seems to be a bug I guess it unmounts data storage while backing it up. I've had this issue specially when the backup was pretty huge and was stored on external sd so I guess it's similar to it have you tried google it?
And even better copy a log after you got the message so we can see what cause it
Sent from my FRD-L09 using Tapatalk
keeganjk said:
I have installed FreedomOS on my OnePlus 5. I'm not sure if this is related to FreedomOS, but when I try to make a backup in TWRP with data, system, and boot, it has an error with createTarFork() shortly after it gets to backing up data. It also says 'read only filesystem' when I try to open Terminal from Advanced and run 'cd /data/media/0/TWRP/BACKUPS/bad7d639 && rm -rf backup-name'. What can I do to fix this and why is this happening?
EDIT: I have 32GB storage left
Click to expand...
Click to collapse
I have the same error only if theme for twrp is present. S7edge twrp 3.1 nougat
LastStandingDroid said:
There seems to be a bug I guess it unmounts data storage while backing it up. I've had this issue specially when the backup was pretty huge and was stored on external sd so I guess it's similar to it have you tried google it?
And even better copy a log after you got the message so we can see what cause it
Click to expand...
Click to collapse
I don't have a log, I just got it working again (for now). I restored an earlier backup and now backups are not having errors. I think it had something to do with a substratum theme.
totoascend88 said:
I have the same error only if theme for twrp is present. S7edge twrp 3.1 nougat
Click to expand...
Click to collapse
Hmmm... I've been wanting to theme TWRP bit couldn't find out how. I've fixed the problem for now, I restored from an earlier backup. I think it had something to do with a substratum theme.
keeganjk said:
Hmmm... I've been wanting to theme TWRP bit couldn't find out how. I've fixed the problem for now, I restored from an earlier backup. I think it had something to do with a substratum theme.
Click to expand...
Click to collapse
It can be so. Next time try get a log so it can be fixed by twrp theme
Sent from my FRD-L09 using Tapatalk
LastStandingDroid said:
It can be so. Next time try get a log so it can be fixed by twrp theme
Click to expand...
Click to collapse
Ok
LastStandingDroid said:
It can be so. Next time try get a log so it can be fixed by twrp theme
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
It started happening again... I don't know why, I restored from a backup and all I did after before trying to backup again was install a couple of apps...
Here is the "important part"of the log:
Code:
Backing up Data (excl. storage)
Backups of Data do not include any files in internal storage such as pictures of downloads.
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
It then goes into read-only mode; I can't delete backups or anything in the terminal until I reboot into recovery...
LastStandingDroid said:
It can be so. Next time try get a log so it can be fixed by twrp theme
Sent from my FRD-L09 using Tapatalk
Click to expand...
Click to collapse
I fixed it by booting into TWRP and running:
Code:
rm -rf /data/local/nhsystem
.
nhsystem is from Kali Nethunter, something I believe needs to be removed and reinstalled after a restore
keeganjk said:
I fixed it by booting into TWRP and running:
Code:
rm -rf /data/local/nhsystem
.
nhsystem is from Kali Nethunter, something I believe needs to be removed and reinstalled after a restore
Click to expand...
Click to collapse
hello, can you explain how you run twrp :
Code:
rm -rf /data/local/nhsystem
.
I could resolve my nandroid /data backup error on my EMUI 8.0 Mediapad M5 device with those following steps:
1 - Use a correct TWRP implementation
TWRP need to access the uncyphered partition /data.
There no possibility to backup it, if TWRP does not implement deciphering user data partition.
2 - Remove all users except user 0 (the administrator)
You can verify that there is no unwanted users, looking at directory /data/user : the only subdirectory should be "0".
To remove the others users :
Remove the PrivateSpace if you have one (Settings > Security & Privacy > PrivateSpace, and tap on the garbage can).
Remove all the secondary users (Settings > Users & accounts > users, and tap on each users to delete them). Keep just the main administrator user.
On EMUI, remove all twins applications (Settings > Apps & Notifications > App Twin, and disable all twin apps).
On OxygenOS, remove all parallel apps (Settings > Apps > Parallel Apps, and disable all parallel apps).
On MIUI, remove all dual apps (Settings > Dual Apps, and disable all dual apps)
On others devices ... you must find all parameters that create those unwanted users.
If you are not able to get the correct settings to suppress those users, in last resort you can try this command : "pm remove-user user-no. (For example "pm remove-user 999").
3 - Do not forget to protect your backups by a password
This would be stupid to cipher your /data partition and keep backups of this partition unprotected.
These steps fixed the nandroid backup problem for /data partition on my Huawei Mediapad M5 device.
I post on this forum because I hope that this will be helpful for others devices owners.
keeganjk said:
I fixed it by booting into TWRP and running:
Code:
rm -rf /data/local/nhsystem
.
nhsystem is from Kali Nethunter, something I believe needs to be removed and reinstalled after a restore
Click to expand...
Click to collapse
I have the same issue, funnily it only breaks after installing kali-linux-full in the chroot.
Anybody any ideas what could cause it within the nhsystem folder??