Related
hi,
i did a big mistake. I wanted to install some vpn apps, which requires write permission on /system. I downloaded root explorer und tried to set all permissions for the system folder. But the app stills lacks the wanted permissions, so i started root explorer again and additionally checked the checkboxes under "special permissions". After doing that android crashed, the "systemui" process crashed and restarted and crashed ...
I rebootet the device, but i only see "google" and then comes a reboot and the device boots into recovery (TWRP 2.6.3.4). I already tried the "fix permissions" under advanced, but it didn't helped.
Is there any way to fix whatever i did wrong and not lose any data?
Any help would be greatly appreciated
Greetings k1x1987
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
d
jyuuken said:
Reflash rom without wiping.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for your help. I don't want to miss something this time and complety brick my device. Could you/anybody tell me exactly what and how do flash to recover my device?
I did all the rooting stuff with the "Nexus Root Toolkit" program and followed strictly guides, except this time
Do i have to flash the rom with ADB? which file(s) should i flash system.img only? Or i have to flash more files?
A short noob guide would be really appreciated :good:
Greetings k1x1987
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
es0tericcha0s said:
So you are just rooted on the stock setup? Then you should be able to flash a stock odexed rom that matches your current set up (4.4.1 or 4.4.2) and you should wipe, but just the caches. You'll likely need to adb push rom.zip /sdcard when in recovery. You probably could adb sideload as well, but not sure if that wipes anything else. Never had to mess with sideloading.
For future reference, once you are up and running, I think what you would need to change is the SELinux permissive state. There's an app do that. Then the most you would need is to hit the R/W button when you're in /system with Root Explorer. Or with the newer Root Explorer versions, once you try and make a change that needs R/W permissions, it'll stop and ask you if you want RE to switch it for you to complete the task.
Click to expand...
Click to collapse
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
k1x1987 said:
Thanks for your help. Yes, i am complety stock besides root and franco kernel. I already downloaded factory image (4.4.2). Should i flash the zip, which contains all the system.img, userdata.img etc. (i think it was 5 files) or just specific ones? It would be n1 if my data dont get lost.
Thanks in advance.
k1x1987
Click to expand...
Click to collapse
Just flash the system.img in fastboot.
Most devs recommend wiping /system first.
fastboot erase system
fastboot flash system system.img
I would also erase cache too.
fastboot erase cache
That will clear the cache, not the dalvik, but think that should be enough to get going.
...and once it is fixed, never change system permissions again.... Same a Linux, never change permissions at /root
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
k1x1987 said:
.. phone works again
thanks at all for the help. But now i cant get any cell service. I looked under settings/about the phone/status and saw that my "IMEI" is "unkown". Could this be the problem? I read about restoring imei, should i try this and it this the cause for me not getting any service?
Thanks
Click to expand...
Click to collapse
Using fastboot, flash the cache image from the factory image, fastboot flash cache cache.img
^ That should do the trick. If not, well, let's not go there yet. The cache should fix it. If that does, do yourself a favor and back up your EFS folder and save it somewhere safe. Either use TWRP or flash the EFS backup tool from here: http://forum.xda-developers.com/showthread.php?t=2514095
how to copy TWRP nandroid backup to device?
I need to restore and I don't know how to copy from my hdd to the phone.
The phone is not booting but I can get to twrp recovery.
Latest TWRP has MTP mode.
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
You'll need to give us more information.
Why did it fail? Why did your phone stop booting?
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
gil80 said:
but it doesn't allow me to copy one of the backup files which is: data.ext4.win000 and it's 1.5GB
Click to expand...
Click to collapse
I have had the same problem with my motox 14 the way I found around it was to copy the file to a different fold and use twrp file explore to move it to the back up folder. That has worked for me and a few others try it out it will work.
how can you copy using twrp while in recovery? are you able to access your PC from recovery?
gil80 said:
1. flashed bigxie_hammerhead_LRX21O-signed.zip
2. flashed CF-Auto-Root-hammerhead-hammerhead-nexus5
3. booted fine but still had apps like Ti backup & TWRP not working due to root permissions
4. Went to recovery and performed Fix permission.
5. stuck in boot loop
Click to expand...
Click to collapse
You'll need to factory reset then reflash the ROM
Fix permissions was not required here. You need titanium beta from his twitter feed.
ok i got the phone working and lost my data but I have it backed on PC.
I just see that 10GB is used but when I browse the phone using file explorer, the device is empty.... what??
Is it a known issue?
when the phone is connected to PC I see that 10GB is used but when I i browse the device it shows as empty
No. Do a full flash of userdata.img
Please explain
What would I achieve by flashing it?
gil80 said:
Please explain
What would I achieve by flashing it?
Click to expand...
Click to collapse
A fix for your problem. I shouldn't really need to explain that.
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
gil80 said:
Thanks!
I got it working now. Only need to figure out why it shows 16GB instead of 32 and why root permissions are not working
Click to expand...
Click to collapse
Well the answer in the 100 other threads about space say that you must wipe data and cache.
Root should be fine, but as already mentioned, not with official titanium release.
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
gil80 said:
I already did a wipe data and cache. So I don't understand why I still get this but I'll try again.
The Ti Backup link in the twitter feed is no longer valid, but for example, ES file explorer and clean master and also TWRP app are not performing as if they are rooted.
I'll try to re-install CF-Auto-Root-hammerhead-hammerhead-nexus5
Click to expand...
Click to collapse
ES doesn't work properly, correct. Not all apps have been updated to work with L yet either.
L is much more secure than KK. There are ways to root.
1) chain fire - makes small change in RAMdisk that allows sudaemon to work at boot
2)flash a permissive kernel - this lowers protection within selinux.
More apps work with the 2nd method, but still not all.
New titanium coming to play soon.
https://twitter.com/titaniumbackup
Hi all!
Today i had to reset my phone (Magisk's fault) and therefore i installed Android O (with Funky Huawei -> should be a clean installation).
Bootloader is unlocked, TWRP and SuperSU is installed, but the internal storage is encrypted... TWRP file explorer shows random hashed files in internal storage and TWRP backup is not possible (createTarFork() ... Error: 255).
How can i decrypt my internal storage?
Is there also a decrypted boot image like before?
Hope anyone can help me...
Best regards,
Florian
So I went back to Nougat and B198 to encrypt the data partition...
But I am still interested in encrypting Android 8 for future updates.
Is there a way o do yet?
htcdesire-hd said:
So I went back to Nougat and B198 to encrypt the data partition...
But I am still interested in encrypting Android 8 for future updates.
Is there a way o do yet?
Click to expand...
Click to collapse
Yes. /vendor/etc/fstab.hi3660
Open file in a text editor (root enabled) and change:
'fileencryption=aes-256-xts:aes-256-cts' to 'encryptable'
Save file. Now you should be able to decrypt. You can remove verity and avb flags as well in that fstab.
To encrypt again, add the fileencryption flag back again and reboot.
ante0 said:
Yes. /vendor/etc/fstab.hi3660
Open file in a text editor (root enabled) and change:
'fileencryption=aes-256-xts:aes-256-cts' to 'encryptable'
Save file. Now you should be able to decrypt. You can remove verity and avb flags as well in that fstab.
To encrypt again, add the fileencryption flag back again and reboot.
Click to expand...
Click to collapse
can i make it? is it neccessary? And im running oreo b361, if i want to make decyript, will i format my phone?
mavera said:
can i make it? is it neccessary? And im running oreo b361, if i want to make decyript, will i format my phone?
Click to expand...
Click to collapse
Yes, no, partially.
You do need root. Decrypting, in my opinion, is not necessary. It's only good if you want to backup /data (I'd use titanium backup). Decrypt will format /data, which essentially is your phone. That's where all userdata is kept (all playstore apps, data, etc etc) so I would back those up using titanium backup or Huawei backup, then copy sdcard as well.
@ante0 thank you for your answer!
I made the experience that root apps are not working properly (changes in data partition are not permanently and will be lost after a reboot) when the data partition is not decrypted...
htcdesire-hd said:
@ante0 thank you for your answer!
I made the experience that root apps are not working properly (changes in data partition are not permanently and will be lost after a reboot) when the data partition is not decrypted...
Click to expand...
Click to collapse
Hmm. Then something else is wrong. Data is only encrypted, but it's not protected by avb or verity, so it shouldn't revert at all.
What were you changing if you remember?
ante0 said:
Hmm. Then something else is wrong. Data is only encrypted, but it's not protected by avb or verity, so it shouldn't revert at all.
What were you changing if you remember?
Click to expand...
Click to collapse
E.g. I removed the WhatsApp shutter sound file (/system/media/audio/ui/camera_click.otg) but after rebooting with encryption the file was there again and with decryption everything worked... This happened about a year ago and therefore I have always been decrypting until now...
Is there a disadvantage if the phone is decrypted?
htcdesire-hd said:
E.g. I removed the WhatsApp shutter sound file (/system/media/audio/ui/camera_click.otg) but after rebooting with encryption the file was there again and with decryption everything worked... This happened about a year ago and therefore I have always been decrypting until now...
Is there a disadvantage if the phone is decrypted?
Click to expand...
Click to collapse
/system is protected by verity though, if you didn't remove the verity flag it does revert things.
No real disadvantage. You still need to unlock bootloader after updating (might not be needed when you go oreo to oreo, my bootloader stayed intact when I went from B329 to b361), which requires formatting data. So you still need to redo the decryption when you update.
ante0 said:
/system is protected by verity though, if you didn't remove the verity flag it does revert things.
No real disadvantage. You still need to unlock bootloader after updating (might not be needed when you go oreo to oreo, my bootloader stayed intact when I went from B329 to b361), which requires formatting data. So you still need to redo the decryption when you update.
Click to expand...
Click to collapse
Ok thank you for your answer! I will try to remove verity flag and keep the phone encrypted, when Oreo is officially released.
EDIT:
I upgraded to Android 8 and rooted my Mate 9 and everything seems to work now. I did not test the decryption so far...
ante0 said:
Yes. /vendor/etc/fstab.hi3660
Open file in a text editor (root enabled) and change:
'fileencryption=aes-256-xts:aes-256-cts' to 'encryptable'
Save file. Now you should be able to decrypt. You can remove verity and avb flags as well in that fstab.
To encrypt again, add the fileencryption flag back again and reboot.
Click to expand...
Click to collapse
My device is rooted, but i can not write into system partition ("/system/app mover" app shows an error that it can't remound /system)...
How can i enable writing to the /system partition?
By removing the verity flag in fstab? How do i manage to do that?
ante0 said:
Yes. /vendor/etc/fstab.hi3660
Open file in a text editor (root enabled) and change:
'fileencryption=aes-256-xts:aes-256-cts' to 'encryptable'
Save file. Now you should be able to decrypt. You can remove verity and avb flags as well in that fstab.
To encrypt again, add the fileencryption flag back again and reboot.
Click to expand...
Click to collapse
Hi ante0,
As I am total noob on this matter, just one question to make sure:
Do I remove the whole fileencryption=....-cts part and replace it with the text encryptable?
Regards,
Dioky said:
Hi ante0,
As I am total noob on this matter, just one question to make sure:
Do I remove the whole fileencryption=....-cts part and replace it with the text encryptable?
Regards,
Click to expand...
Click to collapse
Yes.
wait,check,fileencryption=aes-256-xts:aes-256-cts
Should say
wait,check,encryptable
Or you can just remove it so it just says
wait,check
Troubles again and sweet victory
ante0 said:
Yes.
wait,check,fileencryption=aes-256-xts:aes-256-cts
Should say
wait,check,encryptable
Or you can just remove it so it just says
wait,check
Click to expand...
Click to collapse
It worked, but I ran into trouble again: bootloop.
This time it was my bad because I forgot to re-flash update_data_public.zip and update_all_hw.zip after the Format Data... :cyclops:
When I realised the mistake I made, I tried to make up for it by TWRP-flashing both files.
During flashing I got a few errors in red text that frightend me.
In hindsight I should have neglected them, but I tried to reflash and from that on I ran into trouble.
Because I wanted to have a nice clean install, I decided to return to base and reflash the whole stock ROM with HWOTA8 procedure.
Next I started to look around on the net for another more experiences. That led my to the German Firedance1961.
He wrote an elegant script for the latest Oreo build 363, which automates some tweaks during the flashing process.
As ante0 suggested, that script indeed does leave blank after 'wait,check'
It adds a GPS tweak, SuperSU v2.82, Busybox, AdAway, some theme-options and decrypts DATA partition that stays decrypted after reboot. All in one go.
The process for those interested:
Needed:
Unlocked bootloader.
Steps:
1. Put update_data_public.zip and update_all_HW.zip from the L09/L29B363 ROM together with the Firedance FSTAB-mod script in the root of your external SD-card;
2. Flash TWRP 3.2.1-0 Oreo with Fastboot
3. Boot into TWRP and perform Format DATA. STAY IN TWRP and return to TWRP Install menu;
4. Now flash in this order:
I. update_data_public.zip;II. updata_all_hw.zip;You'll see some red errors during the process. Don't worry.
III. Firedance FSTAB-mod script.From this moment on you can backup DATA partition in TWRP.
5. Wipe cache and Dalvic
6. Reboot, done.
Regards,
will try that Firedance, got same problem with encryption
Firedance FSTAB-mod script - link is dead or file removed.
Hi!
I have some problems with my Oreo stock firmware on G930f. I removed some system apps, like Facebook, Instagram and so on. Nothing that the system should need. But after this my camera stopped working, and flashlight says that an other app is using it. Is there a way to fix this without needing to flash firmware again? I don't want to format my data partition and set everything up again...
Thanks in advance!
You can flash the same firmware again without losing data if you use HOME_CSC instead of CSC along with AP, CP and BL
If you are rooted you'll have to root again and remove those apps again, but this time remove them one by one, reboot and test the camera after each, see if one of them kills it, then you know which one not to remove
Or use a package disabler instead of removing them, then you can just enable them again
*Detection* said:
You can flash the same firmware again without losing data if you use HOME_CSC instead of CSC along with AP, CP and BL
If you are rooted you'll have to root again and remove those apps again, but this time remove them one by one, reboot and test the camera after each, see if one of them kills it, then you know which one not to remove
Or use a package disabler instead of removing them, then you can just enable them again
Click to expand...
Click to collapse
Thanks!
Do you have an idea how to flash TWRP again without having to format data?
C_Karhu said:
Thanks!
Do you have an idea how to flash TWRP again without having to format data?
Click to expand...
Click to collapse
Not sure it's possible as TWRP can't read encrypted partitions, and stock firmware encrypts data
*Detection* said:
Not sure it's possible as TWRP can't read encrypted partitions, and stock firmware encrypts data
Click to expand...
Click to collapse
So the encryption is the issue? Maybe I'll try the flashable ecryption remover and see what happens!
Edit: Didn't go very well, so I formated data instead. Guess I'll leave the system partition alone from now on.
C_Karhu said:
So the encryption is the issue? Maybe I'll try the flashable ecryption remover and see what happens!
Edit: Didn't go very well, so I formated data instead. Guess I'll leave the system partition alone from now on.
Click to expand...
Click to collapse
lol, just make a Nandroid backup in TWRP, and if you break it again you can restore to exactly how it was when you backed up
Make regular backups and save them from the phone to PC, you can always restore that way
I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup Boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img (extract from ap section of downloaded firmware for stock) or install UPie
2. Restore Boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files to /system/system
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.
If anyone can think of another system directory which I can backup and restore please let me know.
physwizz said:
I am developing this method because TWRP will not restore correctly ever since I upgraded my bootloader from U2 to U4.
Boot and Data will restore but System will not, so I do the following.
Backup
1. Use TWRP to backup boot and Data and reboot
2. Use a root explorer to copy /system/app to external sd
3. Copy /system/priv-app to external sd
Debloat by deleting apps from these 2 backup files
Restore
1. Boot into TWRP and install system.img
2. Restore boot and Data as usual
3. Go to Advanced - File Manager
4. Delete /system/system/app and /system/system/priv-app
5. Copy and paste backup app files
6. Reboot
Note: TWRP has its own system which holds the ROM system as a sub directory.
Click to expand...
Click to collapse
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.
Jeremy_J7 said:
This is great. I have issues that caused my settings app to show extra and weird options after a restore from TWinRP in the past. But since then I've updated to a new TWRP but haven't done any restoring because of what the previous one did. Hope this works when I need it to.
Click to expand...
Click to collapse
I think the system settings are stored in /data
I'll add it to the list.
physwizz said:
I think the system settings are stored in /data
I'll add it to the list.
Click to expand...
Click to collapse
Test it before you add to the list, can't be giving these people false information bro ?
Jeremy_J7 said:
Test it before you add to the list, can't be giving these people false information bro
Click to expand...
Click to collapse
True
I debloated from here
https://forum.xda-developers.com/galaxy-a20/development/debloat-samsung-a20-variants-t4070957
Then I added the updated camera from Ultimate Pie.
My app folders are here
https://mega.nz/file/dtkkES5L#YfHwWC3rlswwYUeA_cdUESCMQo8rvq8k8n20N-oc-8w
Alright will take a look, is this bootloader specific?
Jeremy_J7 said:
Alright will take a look, is this bootloader specific?
Click to expand...
Click to collapse
Not sure.
If it doesn't work it might reboot into recovery and then you need to copy and paste your own /app and /priv-app folders back in place.
@jajk
Try this
@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?
jajk said:
@physwizz My appetite for being screwed by Samsung and the dirty traps they lay is severely diminished. Since going to U4, I can't reliably get TWRP to work without triggering the evil red text screen of death.... I have been watching what is happening with the work on custom kernels and Ultimate Pie ROMs but definitive information on what is actually working reliably or not is very patchy..... one person will say "Yep, this definitely works" the other will say "nope can't even boot"... almost like some people don't even own this phone or have not actually tried what they are promoting or are unable to follow instructions properly....
So....starting from stock U4, I can root and install TWRP, magisk and dmverity no problems at all but after going back into the O.S and attempting to reboot into recovery a 2nd time....bang! Samsung screws me!!!! The question is.....is there a custom kernel for U4 and above that truly removes all of Samsung's dirty tricks (security features) and a custom ROM that also holds no hidden surprises?
Click to expand...
Click to collapse
If you're talking about the red text that talks about 'official binaries' when booting after you flash TWRP (FRP LOCK) then there's a very easy fix.
@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....
jajk said:
@physwizz Yes the evil red text...but it is not after flashing TWRP, it is only if you try to go back into TWRP.
I already know of one easy fix... called don't buy Samsung. All this wouldn't be a problem if manufacturers could resist the temptation to "monetize" private data but that ain't going to happen anytime soon in this dog eat dog world.....
Click to expand...
Click to collapse
I got that because i was using old data
solved by doing a clean install
The data was then good in future
@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different
jajk said:
@physwizz Went through the Samsung dance from scratch, installed UltimatePie4, rebooted into Ultimate Pie no problems, completed the initial setup.....rebooted and back to red text of death!!!
Yes, I did all the format /data etc.... it is not a procedural problem on my part but my phone has always given me more grief than you appear to have - something is different
Click to expand...
Click to collapse
You didn't restore old data?
Clean install?
@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....
jajk said:
@physwizz Did nothing but complete the initial setup after install and rebooted.....all started from a clean install of U4, then rooted and TWRP from your tar file, then installed new ROM with data freshly formatted i.e. absolutely no messing around with the stock ROM or custom ROM through the entire process and never getting to the point of rebooting into TWRP which triggered the previous red text of death.....
Click to expand...
Click to collapse
What does red writing say?
@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....
jajk said:
@physwizz Writing says "You have just been screwed by Samsung yet again" or something about official binaries which is the same thing....
Click to expand...
Click to collapse
I've had that twice
1. When I forced reboot before UPie was finished installing
2 when I didn't wipe caches , data and system before installing UPie
Could also be Samsung Conspiracy Theorist Detection Program (SCTDP) lol