Database Users

[Q] after wipe system can't push new rom

hi guys,
yesterday i wanted to install vanir rom after having the latest nightly of PA. i accidentally wiped the system partition and now obviously have no zip on my phone to install. i am now at recovery level.
i have tried using adb sideload but received a message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and afterwards have tried to use this thread http://forum.xda-developers.com/showthread.php?t=1667929
but received these messages (the first is while on recovery, the second is after pressing on adb sideload in the recovery
right now only the data partition is mounted but i am not sure whether it's suppose to be like this, and i still don't have zip inside my phone.
the recovery is team win recovery project v2.6.2.0
please help as i am getting crazy. i wouldn't mind using the toolkit if i knew which option to chose.
thank you

Hi, to install a 4.4+ rom you need to update your recovery to 2.6.3.3 and then try sideload again.
P.s you wiped the user data partition.

well i was already noted it is something like this but i also cannot install the PA RC2 via the adb sideload.
is there a previous version available, as i didn't find any?
and how can update the recovery in such a state?

Download the recovery img not zip!
Copy the img to adb folder boot to bootloader , open cmd and type: fastboot flash recovery file_name.img .
link : http://techerrata.com/browse/twrp2/mako

Thanks it worked! I installed the factory img of kitkat I'll try installing vanir later!

[SM-N900] how to fix all Aurora issue with Titanium Backup?

Issue Fixed By wiping Dalvik Cache, Data & Cache and then installing UPDATE-SuperSU-v2.45.zip right after in TWRP.
I have Tried 2 Aurora ROM so far; [AURORA]N900 S6-Note 5 Features Port 4 Rev 3 and Aurora Team S6 Full Port For Note 3 N900 v5.2 [15/11/2015] but both of them Titanium Backup not working as it give me this error:
Error
Sorry, I could not acquire root
privileges. This aapplication will
*not* work! Please verify that your
ROM is rooted, and try again.
This attempt was made using the "/system/xbin/su" command.
Click to expand...
Click to collapse
what do you think is wrong?
as i have even try cf-root but not solve the issue
and i could testified that the phone is rooted with Busybox installed

Root again/ update supersu.

JJEgan said:
Root again/ update supersu.
Click to expand...
Click to collapse
yah updated, i eve try Update Supersu 2.46.zip but didn't solve the issue, but if i can restore data backup through TWRP every thing will work but i just dont like restoring all data backup as it restore some stockapps of previours rom.

See this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
as you can see there is no issue with the root.
but still if i open titanium backup i still get this error:
but titanium backup will work when i restore data backup from recovery, and that hurt the rom as some apps stopped working like weather, clock etc.

Remove Device Encryption on Stock Rom?

Out the Box my device Was running an encrypted file system which seems to affect some areas and leaves others untouched, and id rather just remove it for the performance increase. (similar to here https://www.anandtech.com/show/8725/encryption-and-storage-performance-in-android-50-lollipop )
I have flashed TWRP 3.1.1 for the kugu, and while i do not get prompted about the decryption on the stock rom, I am unable to boot custom roms due to the encryption. Entering in my pin, which should then grant the masterkey the ability to decrypt is rejected. It states my pin is correct, but that it is unable to decrypt the volume and i need to perform a full wipe. Ive tried this route, wiped the phone, installed a rom again, and when trying to boot it...same thing.
Don't know whats up with that. My Device is Bootloader unlocked and I've tried a variant or two of TWRP.
Ive tried the DRM fix Genesis Kernel, and the patch it yourself Genesis Kernel both of which state they disable forced encryption.
Ive tried to install Paranoid Android, but i am unable to proceed past the point where it requests you to decrypt the phone.
Ive Tried Factory Resets, i've tried data wipes, and i've tried downgrading. Anyone else having similar issues?
How Do I Get around this and remove device encryption? I don't recall ever enabling it, nor being asked about it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I think you need to wipe the user data and format with TWRP, then set up the phone.
If you let nougat do it itself, it will be encrypted.
Or, something like that?

File and folder names suddenly all randomized

Hi,
I had a OP5 with stock 4.5.14, TWRP, SuperSU and wanted to update to 5.0.1 with TWRP 3.2.1-0 for Oreo by codeworkx and Magisk 15.2
I deleted SuperSU within the app, said to restore boot but keep recovery. After reboot it got stuck, black screen and blue LED.
I booted into TWRP, flashed the codeworkx TWRP, and downloaded this supersu uninstaller: https://www.theandroidsoul.com/unroot-supersu-uninstallation-failed/ because Magisk wouldn't install (Error 1), I assumed because Supersu hasn't been deleted properly.
This supersu uninstaller seemed to have screwed up my internal storage since all files seem to be there (file sized match as far as I can tell) but all file and folder names are randomized and I can't read anything, neither can I write new files on it. In windows it starts copying but it gets stuck.
I was able to install a "signed" supersu uninstaller from this forum and after that I could flash Magisk and the no verity zip.
My phone boots now into 5.0.1 and Magisk seems to be installed. So it seems to work but what can I do about the internal storage?! Is this some kind of encryption or has this supersu uninstaller messed it up? If so, how can I fix it? Thanks!
Here's how the internal storage looks like: View attachment 4382242

the files and folders look the same if I go to the file manager on my phone, so it's not a windows issues. help please!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I formatted data in TWRP which fixed it. Not sure what caused it, if flashing the supersu uninstaller ****ed up the file system or corrupted the permissions, or something else entirely. Fortunately I did a backup of all my important files.

That's normal because of an error in decryption when moving from Nougat to Oreo.
Once you are on Oreo, dirty flashing new Oreo versions should be ok.

Latest TWRP 3.5.2 BROKEN With LineageOS 18.1 - Galaxy S10+ Exynos

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This's my error message in TWRP:
It appears everywhere, while flashing, wiping or trying to backup/restore.
OS: LineageOS 18.1
Recovery; TWRP 3.5.2 (Latest)
Rooted with Magisk and flashed pre-rooted TWRP image
-----------------------------------------------------
Error reason:
LineageOS 18.1 encrypts /data in a way that prevents TWRP from decrypting it.
Even when choosing no locking mechanism (Pin, Swipe etc.) decryption still fails.
Error symptoms:
Backup/Restore via TWRP is not working due to /data error
Constant warning message "could not open /data permission denied"
Lineage Recovery has the exact same problem, it actually doesn't even display the internal storage due to its inability to decrypt it.
-------------------------------------------------------
How I've "fixed" it:
Formatting /data stops the error messages, but that's just because the encryption is removed by wiping the entire drive.
This also messes up the ability to create backups in TWRP.
-------------------------------------------------------
For comparison, this is what the log is supposed to look like when /data decryption has been successful:

Just found out that can't backup rom...
OS: LineageOS 18.1
Recovery; TWRP 3.5.2 (Latest)
Rooted with Magisk and flashed pre-rooted TWRP image
...setup is just like yours.
If you have found out some better solution than format, please share link.
Thank you!