We will do some changes on the system partition. The tablet is rooted.
All changes that we do, are reverted after a restart to the origin state. When we overwrite a file in the system partition, the tablet freezed.
(You can touch a file to system, after reboot is deleted)
SuperSU crashes by do some changes in the system.
There is a problem in the AQF3 Firmware or in SuperSU. The older versions works.
I will check this on the next build.
There is a problem in the Firmware AQF3. Next build works fine.
Related
Hey Guys,
first off: I google this before and my own work arounds did not yield any success. So here we go:
Originally I froze the Cyanogenmod Setup Wizard, as it constantly "stoppped working" after booting as I reinstalled a previously working version of (open) Gapps. Well, it still dit not work and the Setup Wizard kept quitting on boot.
Hence I did a nandroid backup with TWRP and completely formatted my internal storage - reinstalled everything from TWRP and tried to restore my "data" backup from TWRP. But what happens then is that CM13 goes into bootloop (I see the booting animation 90% of the time, sometimes it goes into "optimizing app..." mode, only to reboot immediately after finishing the optimization).
I assume this problem occures because I froze the Setup Wizard in the backup, which is required for initializing the system after restoring?
What I've tried so far:
reinstalling/restoring/wiping the different partitions in all possible orders
if I reinstall everything without the backup (includes DATA only!) CM13 boots up just fine, but without my user data, settings etc..
Thus I tried to unfreeze the setup wizard, but a) via ADB does not work (device always offline or cannot connect in bootloop/recovery mode), b) there is no "packages-stoped.xml" in my /system folder of the backup for the package manager (hence i cannot change the disabled/enabled value of com.cyanogenmod.setupwizard), c) replacing the /system folder of my data-backup with an older version: this worked but all my settings were completely gone.
Finally I even tried to delete the package.xml and package.list in the /data/system folder (assuming the freez-value is stored there) and it would be rebuild. However, this did not help.
So I do know by now, that the bootloop problem resides within the /data/system folder of my backup. However, I cannot narrow it more down. Does anyone have more ideas how I might restore from the backup without running into a boot loop?
//edit
I've narrowed it down to the /data/system/users folder. I've found the package-restrictions.xml there. But this is apparently not the one file responsible for the bootloop (exchanged it a working backup). Sadly, all my settings are in there as well
does anyone know how to solve this issue? I can exclude the frozen state or other restrictiond (xprivacy) as causes for the crash of setup wizard. However, this leaves me clueless as to the reasons of the crashs.
Atm. I have to run android without the play google framework (gapps pico) in ordee to circumevent this issue.
p.s. I used open gapps. Flashing differen gapps packages made not difference. And Open Gapps worked before... (as many poeple seem to have problems caused by the gapps package)
Hello guys,
I am running the latest 2.2.0-X OOS, with latest TWRP recovery, and rooted with supersu. The problem arised when decided to encrypt my device. Supersu and root stopped to work. I tried to reflash supersu binaries on TWRP, the installation is successfull, but when i boot my device still no root.
So to my conclusion Supersu app & root doesn't seem to work on an encrypted device. Any ideas or suggestions or workaround?
Thanks
You should be able to do it :/
When you encrypt a device, the only partition encrypted is the "data" partition not the "system" partition (where the root is made).
pedrof1991 said:
You should be able to do it :/
When you encrypt a device, the only partition encrypted is the "data" partition not the "system" partition (where the root is made).
Click to expand...
Click to collapse
I figured out what the issue was: All you have to do is follow this guide:
http://forum.xda-developers.com/not...tSd7OU3zvjXIDCyXg&sig2=QqJIbUNvupVJnERW2w4K_w
* Note : This works on stock kernel, couldn't make root to work on encrypted device using boeffla kernel. don't know about blu_spark
I have a LG G5 H850, with 6.0.1 and stock V10c-EUR-xx.
I disabled disk encryption using the no-verity-opt-encrypt.zip utility by jcadduono.
Now I wiped again using TWRP, but encryption is still disabled as the boot.img/partition still has his modifications to the fstab files (where he does
the change s/\bforceencrypt=/encryptable=/g etc.)
How to I set that back to as it was?
I got into this sitation as I kept finding TWRP could not access the partition - asked for password and there was none.
I do want to use encryption but in my first hour of setting up the phone I had a problem where when I booted into TWRP it would ask for a password and it was not "default_password", and I had not set anything and never used lock screen/pin etc. I tried setting a lock screen/boot screen password - the phone worked but TWRP could not access the filesystem. I tried the cryptfs application and still TWRP was not able to decrypt/access the partition.
Then I tried a terminal with vdc cryptfs changepw command and that just locked me out of the phone completely, as the new or old boot password would not work.
So I went for the no-verity-opt-encrypt.zip solution - but I dont want an unencrypted phone either. Now I want to try encryption and TWRP again - this time setting a pin at the first setup screen opportunity to see if that gets set as the password that TWRP could use. However I can't remove the disable encryption patch!
Ideally I am trying to get to a setup where:
encryption is enabled
I want to be able to boot TWRP and access the encrypted filesystem and install more zip files such as xposed/supersu updates etc anytime in the future.
I dont want to use the "no-verity-opt-encrypt.zip" patch.
I do not want TWRP to be locked out from modifying the encrypted system partition.
Additionally, I havbe not been able to install xposed using TWRP and the zip file (http://dl-xda.xposed.info/framework/sdk23/arm64/xposed-v86-sdk23-arm64.zip) .
In TWRP it installs, I dont see any errors, but on boot up I have no xposed icon. I have been able to install it by downloading the apk and installing as an untrusted source, not sure if there is something wrong in having to do it this way?
Thanks.
current TWRP build for G5 doesn't support encryption
you can use encryption but in TWRP you won't be able to access some partitions (if I remember right is data partition but I might be wrong here)
in order to do so, you need to restore base firmware with LGUP that will turn encryption back on
Thanks. I got it working by flashing just the boot using LG-H85010C-Flashable.Boot.zip
tomb007 said:
Thanks. I got it working by flashing just the boot using LG-H85010C-Flashable.Boot.zip
Click to expand...
Click to collapse
may i ask how did you root it after that? because everytime i try to rooted while encrypted,i flash the zip in twrp (with no errors) but system still has no root! the only way i could root was to format /data in twrp, hence have a decrypted phone!
I am looking for the same thing as you are : encrypted phone with twrp and root access.
I rooted using TWRP adding supersu at the time of installing the OS before the OS encrypts the partition. Once the partition is encrypted TWRP can no longer access it, and I can no longer install supersu or anything else.
I may have installed root before encrypting, then reflashed the boot partition so that encryption is re-enabled, then ran twrp to reapply supersu - which would fail to put files on the encrypted partition - but this is fine as they were already there, and let the twrsp supersu installation modify the boot partition.
The result is an encrypted phone with root and TWRP. However, TWRP can not access the encrypted partition so I don't think I can update supersu using TWRP, and I dont think I can patch the OS easily without wiping the encrypted data and reinstalling everything due to this. As I am not sure if updating the OS works without wiping data, I have yet to try that.
you shouldnt have to mess with data at all to use supersu while encrypted.
my g5 is encrypted and always has been (besides in various testing) and there's never been an issue of flashing supersu.
though there may be some issues if trying to restore encryption and flashing supersu in the same reboot cycle.
and yes, data partition in twrp cant be accessed in twrp if encrypted.. but you can just push a file to the /tmp directory while in twrp and then flash anything... or enable adb sideload and flash something that way... or use an external sd card and put the file on there. the only thing you really miss out of if using twrp while encrypted is being able to manipulate the data partition... it does not stop you from flashing files or running scripts that modify /system or other partitions (besides /data).
supersu uses the unencrypted /cache/ partition to work in when you flash it while encrypted so an encrypted /data partition should not be relevant.
My phone is basically unbootable after a shutdown due to low battery. Things I tried:
1. Wipe System+Cache -> Flash ROM
(Result: Stuck at boot animation)
2. Wipe System+Data+Cache -> Flash ROM
(Result: Bootable)
3. Wipe System+Data+Cache -> Flash ROM -> Restore Data
(Result: Stuck at boot animation)
4. Wipe System+Data+Cache -> Flash ROM -> Restore Data -> Delete /data/system
(experiment)
(Result: Bootable system but Android warns system unstable till factory reset, Apps can launch but behave as if no previous state)
Can I conclude that there is something wrong with my data partition?
Strategy 1
What are the files I could try to minimally delete/modify to get it bookable and have my existing data intact? Or please guide me know how to trace to the problematic files/folders.
Strategy 2
I do have a TWRP Data partition backup before I did the various (dumb) experiments. If I were to start from scratch, how to I copy over /data/data (which I am guessing where all app's data is at) to restore the previous state?
I have tried to:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash and replace the /data/data folder, does not boot
Also tried:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash, boot.
4. Download a single app.
5. Went to TWRP and copy only the app's backup data folder to /data/data
6. Boot to system and launch app. Apps crashes.
7. I understand it has something to do with permissions and I have out of frustration, used an app to allow all actions (I believe a 777 chmod equivalent?) and set the owner and group to the app itself. App launches with previous data, but seems to have problems saving (writing) changes.
Extra info: Phone: Xiaomi Redmi Note 3 (SD)
ROM: Resurrection Remix v5.7.4, Android 6.x.x
As you can tell, I don't know much about how Android works. Please pardon me for the long post and thank you in advance.
ic2e said:
My phone is basically unbootable after a shutdown due to low battery. Things I tried:
1. Wipe System+Cache -> Flash ROM
(Result: Stuck at boot animation)
2. Wipe System+Data+Cache -> Flash ROM
(Result: Bootable)
3. Wipe System+Data+Cache -> Flash ROM -> Restore Data
(Result: Stuck at boot animation)
4. Wipe System+Data+Cache -> Flash ROM -> Restore Data -> Delete /data/system
(experiment)
(Result: Bootable system but Android warns system unstable till factory reset, Apps can launch but behave as if no previous state)
Can I conclude that there is something wrong with my data partition?
Strategy 1
What are the files I could try to minimally delete/modify to get it bookable and have my existing data intact? Or please guide me know how to trace to the problematic files/folders.
Strategy 2
I do have a TWRP Data partition backup before I did the various (dumb) experiments. If I were to start from scratch, how to I copy over /data/data (which I am guessing where all app's data is at) to restore the previous state?
I have tried to:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash and replace the /data/data folder, does not boot
Also tried:
1. Restore /data
2. Copy /data/data to somewhere in /sdcard
3. Wipe, flash, boot.
4. Download a single app.
5. Went to TWRP and copy only the app's backup data folder to /data/data
6. Boot to system and launch app. Apps crashes.
7. I understand it has something to do with permissions and I have out of frustration, used an app to allow all actions (I believe a 777 chmod equivalent?) and set the owner and group to the app itself. App launches with previous data, but seems to have problems saving (writing) changes.
Extra info: Phone: Xiaomi Redmi Note 3 (SD)
ROM: Resurrection Remix v5.7.4, Android 6.x.x
As you can tell, I don't know much about how Android works. Please pardon me for the long post and thank you in advance.
Click to expand...
Click to collapse
use miflash to start fresh with miui, use miflashunlock to check if bootloader is unlocked properly, flash twrp, redownload the rom and gapps, start flashing through twrp
If you're flashing ROM, do not restore data.
Wipe system+data+cache+dalvik ,then flash ROM+gapps then reboot.
Don't restore anything from other backup
I have updated my LineageOS 16 build, and then my phone bootlooped. Thus, I discovered that the cause of that was the file data/system/packages.xml. However, if I delete that file, all user apps and data of most system apps are deleted.
What is the solution?
smnthermes said:
I have updated my LineageOS 16 build, and then my phone bootlooped. Thus, I discovered that the cause of that was the file data/system/packages.xml. However, if I delete that file, all user apps and data of most system apps are deleted.
What is the solution?
Click to expand...
Click to collapse
Try to wipe system, data, cache/dalvik with TWPR and reflash the ROM. (Perform a clean flash)
However you'll lose your data so do a backup.