Database Users

[Q]IMPOSSIBLE DEODEX > encrypted dalvik-cache

I learned tems that the NOTE 3 does not work deodeks.
I also heard that the application of the recovered Titanium backup does not work
This comes from the fact that the dex files could not move in / data / dalvik-cache
disprove me please?

A.S._id said:
I learned tems that the NOTE 3 does not work deodeks.
I also heard that the application of the recovered Titanium backup does not work
This comes from the fact that the index files could not move in / data / dalvik-cache
disprove me please
Click to expand...
Click to collapse
I really doubt dalvik-cache is encrypted. That would be A LOT of overhead.
Certainly not impossible to deodex either.
{
"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"
}

tnx for reply, but i made deodex some time, and with zipalign, and without - this can't boot system.
Going only to bootanimation and that's all.
I think framework can't start...

And why after titanium restore app, dex files do not appear into dalvik-cache?

A.S._id said:
And why after titanium restore app, dex files do not appear into dalvik-cache?
Click to expand...
Click to collapse
Possible Titanium needs to be updated to work properly on the Note 3. Try manually creating a folder as su in dalvik-cache and create a file.
su
cd /data/dalvik-cache
mkdir test
cd test
touch testfile
If that works, then I would assume something with how Titanium works has changed.

Latest update..
A.S._id said:
tnx for reply, but i made deodex some time, and with zipalign, and without - this can't boot system.
Going only to bootanimation and that's all.
I think framework can't start...
Click to expand...
Click to collapse
Hmmm... My latest Pre-ROOTED DeOdexed Package (Apps & Framework) for SM-N9005 is working just fine!!
TESTING in progress but System is up and running...
All files deodexed and no errors has been reported so far..
Next for testing is Pre-Rooted DeOdexed KNOX FREE ROM (CWM)... in progress...
stay tuned

Can't delete supersu folder on internal storage

How Can I delete the supersu folder using twrp or adb? I had root then let the SuperSU app do a full unroot and the supersu folder is still there. I even flashed the stock rom and the suspersu folder is on the internal (root) storage.
Thanks in advance
update: twrp internal storage wipe didn't help

Was it systemless root? I only ask because system root places folder in /system/app or in /data/app if installed as a regular app. I never tried systemless root so not sure where that goes but would assume the same place. Wiping internal with twrp should have erased it if it's in /sdcard. Since you can see the folder can you open it?

Fe Mike said:
Was it systemless root? I only ask because system root places folder in /system/app or in /data/app if installed as a regular app. I never tried systemless root so not sure where that goes but would assume the same place. Wiping internal with twrp should have erased it if it's in /sdcard. Since you can see the folder can you open it?
Click to expand...
Click to collapse
SR1-SuperSU-v2.78-SR1-20160915123031 is the version I sued, but I sued with Android 7.1.1 preview...Phone wouldn't boot so i flashed the latest 7.0 z stock. Now I can get rid of this /supersu folder.
{
"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"
}

Try from TWRP file mamager

rquinn19 said:
Try from TWRP file mamager
Click to expand...
Click to collapse
Yeup, I can delete but it comes right back after reboot so i think the permissions are messed up.

Hi...i know this is old thread unsolved.
If after a year changed there are way to remove /supersu folder please share..thanks
Edit:after few time changing twrp version to test which version could remove "supersu" folder.file inside that folder change.i think not supersu keep creating it but twrp itself.it's just my conclusion

Gapps is bugged / TWRP does not recognize its own backup (x722)

hello, I require your help to operate my cell phone, I'll tell you step by step what I've done... [it is obvious that my native language is not English]
first, i installed TWRP following this tutorial https://forum.xda-developers.com/le-pro3/how-to/leeco-le-pro-3-root-t3476560
second, backup the complete system with twrp 3.1.1-0 (O.S. 5.8.0.20S Stable, android 6.0.1, Banggood international version). This left me a folder full of files which twrp does not recognize when I want to install that backup again.
{
"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"
}
third, Install the ROM by following this tutorial https://forum.xda-developers.com/le...ent--and-mods/stock-eui-5-8-20s-x722-t3680624 Something seems strange to me that when I run the .bat, the phone reboots in a couple of seconds and the only change I see is that it installs the original recovery, since everything else stays the same, even the system version (EUI version: 5.8.001D (Dev))
Finally install S.U. official (all correct), and OpenGApps, use the Stock and Nano (ARM64, Android 6.0) versions, and both show error when starting the system,
does not allow me to do anything (attached image).
So here I am, with a new cellphone, without being able to restore the copy made with twrp, using a EUI developer version, and without being able to install the Gapps.
---I would greatly appreciate your help---

I have just solved my problem, since after installing my TWRP backup (which I was taught a little recently), It could not start because asked for a false password, then, without deleting anything, i installed from fastboot the ROM X722-5.8.020S-by-Batyan, that is here in xda, and arranged.
https://forum.xda-developers.com/showpost.php?p=74129299&postcount=41
How can I end the post?

Kaidodal said:
I have just solved my problem, since after installing my TWRP backup (which I was taught a little recently), I could not start because I asked for a password and it did not accept it, then, without deleting anything, install from fastboot the ROM X722-5.8.020S-by-Batyan, that is here in xda, and arranged.
How can I end the post?
Click to expand...
Click to collapse
Great news. You don't need to do anything. You've done your part. :good: Just leave it up for people in the future to look at and learn from.

Phone Is decrypted after rooting

I MEAN ENCRYTING
So i decided after a month of having my phone its about time i rooted it.
So i wanted to stick with Stock Rom so i just rooted without installing a customer rom.
Done the whole process,
1-Flashed TWRP.
2-Wiped Data and factory reset through TWRP.
3-Installed Magisk zip through TWRP.
4-Rebooted.
I now have a stock rom rooted with TWRP recovery, So after setting up my phone i downloaded all my appropriate apps that i use with root.
But i have noticed whilst converting a user app into system app it tells me that there is sufficient room on system partition to convert, So i decided to download JRummy root explorer and noticed no items in my root directory shows up.
After this i noticed my phone is encrypted. How do i get stock rom rooted and decrypted so that i can access my root directory.
IMAGES BELOW ATTATCHMENTS
{
"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"
}
Thank you in advance :good:

shakeynath said:
I MEAN ENCRYTING
So i decided after a month of having my phone its about time i rooted it.
So i wanted to stick with Stock Rom so i just rooted without installing a customer rom.
Done the whole process,
1-Flashed TWRP.
2-Wiped Data and factory reset through TWRP.
3-Installed Magisk zip through TWRP.
4-Rebooted.
I now have a stock rom rooted with TWRP recovery, So after setting up my phone i downloaded all my appropriate apps that i use with root.
But i have noticed whilst converting a user app into system app it tells me that there is sufficient room on system partition to convert, So i decided to download JRummy root explorer and noticed no items in my root directory shows up.
After this i noticed my phone is encrypted. How do i get stock rom rooted and decrypted so that i can access my root directory.
IMAGES BELOW ATTATCHMENTS
Thank you in advance :good:
Click to expand...
Click to collapse
It's a know issue
Use a root browser and delete apps from System / app.
I deleted gmaps and YouTube to gain 94mb
Both apps still work fine
Sent from my ONEPLUS A6010 using Tapatalk

There is no link between encryption and space left in /system
It's just that OnePlus decided to use the whole system partition

Can't install oxygen

Hello. I just got OnePlus 5 yay. I tried to root it. I played a bit with the TWRP recovery and eventually I can't install the oxygen ROM, old or latest. I get this error 7:
{
"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"
}
Tried changing file system type for all folders and also tried to remove compatibility.zip out of ROM with 7zip.
I can install other ROMs like MIUI and LineageOS successfully.
When I'm trying to go Factory Reset i get this message. I believe there's connection between the two?

Yossizr said:
Hello. I just got OnePlus 5 yay. I tried to root it. I played a bit with the TWRP recovery and eventually I can't install the oxygen ROM, old or latest. I get this error 7:
Tried changing file system type for all folders and also tried to remove compatibility.zip out of ROM with 7zip.
I can install other ROMs like MIUI and LineageOS successfully.
When I'm trying to go Factory Reset i get this message. I believe there's connection between the two?
Click to expand...
Click to collapse
Error 7 means corrupt zip file.
So maybe you have a wrong starting point for your rooting project
Where did you start with?
What is you current twrp recovery (file name)?
What is your current Rom(file name)?
What is your magisk version?
Is your storage encryped or decrypted?

I can see the error there is a assert command. The zip file isn't for your device. If you have a full rom backup (twrp and stock rom zip recommended), then you may just edit the updater-script and remove the assert check system from the updater script. Then create a zip file of the folder contents. Then try again. If it doesn't help, report back here.
Sent from my Coolpad COR-I0 using Tapatalk

I actually had this issue last night when I went from Pie to Android 10. I did the dumb mistake of flashing the dumpling TWRP instead of Cheeseburger. What I suggest is you reflash the latest TWRP for your device and try again. Below is a list of them for OP5 and I would recommend Coreworkx TWRP
https://forum.xda-developers.com/showpost.php?p=77407412&postcount=4