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
Related
Is anyone having a problems uninstalling stock apps from the stock 3.70 with titanium pro? ? When I click on uninstall in the batch it shows up removed from the list, but still shows in the app drawer even after a reboot. I didn't have this problem with stock 3.30 rom. And yes I'm rooted.Thanks!
StayEVO
same here, then my market stopped working.....maybe wait for an update to TItanium Backup?
Download the version of busybox that tib recommends and don't use batch uninstall. Uninstall one by one.
I never have problems with tib uninstalling anything.
Had the same issue with Titanium after the 3.70 update.
I used root explorer to just move the apps out of the /system/app folder and that took care of it.
Still curious as to why Titanium can't do it anymore
Lots of folks are having this issue on 3.70.x roms. Use root explorer.
For the one that said use it's version of busybox, tried that. Tried Chuck Norris mode too, still nada.
Yeh .. I downloaded busybox from Titanium. Rebooted the phone and finally got it to delete.. weird..??
StayEVO
Then there is something wrong with your rom installs.
I built a rom myself based off the 3.70 update. I also have hw003. I have removed everything sprint related (nova, nav, tv, etc) including sense completely using nothing but tib.
EDIT: For good measure here's a shot of my software build and my app drawer. Excuse the colors, I was calibrating my colors at the time I took the screenshots.
{
"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"
}
Same issue here. Use root explorer to delete files either in system or in data. Just make sure you reboot if you delete files from data because they won't be you reflected in the launcher right away
Spoken from my Evo using Ultra Keyboard and XDA App
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
Hi Guys,
Iam now writing a guide to let you know that how to flash stock Rom using latest twrp recovery by both codeworkx or official
Steps :
First open the downloaded stock rom using any zip utilities, for example winrar.
navigate to the following directory
Code:
META-INF\com\google\android
now open the update script using any text editing tool. like notpad++
Remove the first two lines.
Now you re good to go.
If you are still getting the error
then please replace all occurrence of the device name from "le_s2_ww" to "s2" . You can use the find and replace feature of the Notepad ++
Comment below if you have any queries. :angel:
Hit thanks if you thinks it is usefull
Visit my webiste please : https://www.confusedweb.com
{
"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"
}
Tq
nice
now after doing so the recovery says rhat the update-binary is missing
You are Great.. Thank a lot.
Thank You
Excellent... worked perfectly. Thank you.
I downloaded x527 stock from here:
https://devs-lab.com/download-letv-official-stock-rom.html#How_to_install_LeTv_Stock_ROMs
But when I want to do your point 3, I just find a metadata and a otacert file in it and no update script?
FridrufHau said:
I downloaded x527 stock from here:
https://devs-lab.com/download-letv-official-stock-rom.html#How_to_install_LeTv_Stock_ROMs
But when I want to do your point 3, I just find a metadata and a otacert file in it and no update script?
Click to expand...
Click to collapse
You are in the wrong path!
Look at
Code:
META-INF\com\google\android
not at
Code:
META-INF\com\android
Oh this is embarrassing
Maybe one last question, as I did a lot of version back and forth and I am not able just to flash the bootloader or/and modem file of 19s, I would like to do a clean install of the recovery.
So if I do factory reset with data and cache and start the instalation this will be complete clean?
Or should I delete some files or folders which are beside the sdcard folder, too?
JamBax said:
You are in the wrong path!
Look at
Code:
META-INF\com\google\android
not at
Code:
META-INF\com\android
Click to expand...
Click to collapse
Lol , I made a factory reset and flashed the modified update.zip and now I lost my baseband. What should I do now, I don't really want to use my backup because of the wrong modem version...
hi everyone,
I have this issue: zygote is asking for root permission under S7 Edge 6.0.1 superSU Pro 2.79-SR3 and I want to get rid of it, keeps popping every 30 to 40 min. Any help would be great
{
"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"
}
That is weird. Zygote is an Android daemon that is used to launch apps. It shouldn't be requesting su permissions from the user. Do you give it permission or do you deny? Are you on a custom ROM?
Bigbabyjesus said:
That is weird. Zygote is an Android daemon that is used to launch apps. It shouldn't be requesting su permissions from the user. Do you give it permission or do you deny? Are you on a custom ROM?
Click to expand...
Click to collapse
thanks for responding, I'm on stock Rom and I allways deny permission without any issue in launching apps, everything is smooth without errors. I did some researches on that case, and I've found that it was impossible for Zygot to ask for root permission, so I guess it's just a malware, but it's not detected with Avast Pro, I'm really confused
Do you install apps from anywhere other than the playstore? Maybe you need to wipe and reinstall stock through TWRP. It can be hard to find malware by hand.
Bigbabyjesus said:
Do you install apps from anywhere other than the playstore? Maybe you need to wipe and reinstall stock through TWRP. It can be hard to find malware by hand.
Click to expand...
Click to collapse
Yep I Have some alternative shops, I suspected that they were the gate from wich the malware came from so I deleted all of them except Aptoid, but the Evil is already inside now. BTW a wipe is not even to considered since I don't have time to reinstall and reconfigure more than 30 handy tool apps (drive droid, Exposed and its modules, lucky patcher and many more .....). thanks for caring, anyway I'll try to uninstall suspected apps and see.
Good luck.
Rooted, TWRP and Magisk but when trying TWRP backup: Can not create '/data/media/0TWRP' folder (Required key nor available). Failed to make backup folder.
Already selected my security for lock screen to none and cleared my credentials.
Anyone know what to do?
{
"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"
}
kunal420 said:
Rooted, TWRP and Magisk but when trying TWRP backup: Can not create '/data/media/0TWRP' folder (Required key nor available). Failed to make backup folder.
Already selected my security for lock screen to none and cleared my credentials.
Anyone know what to do?
Click to expand...
Click to collapse
Learn how to read would be the first step
kunal420 said:
Rooted, TWRP and Magisk but when trying TWRP backup: Can not create '/data/media/0TWRP' folder (Required key nor available). Failed to make backup folder.
Already selected my security for lock screen to none and cleared my credentials.
Anyone know what to do?
Click to expand...
Click to collapse
Probably it's something with the TWRP and OP6T encryption. I also faced this error not long time ago. Try to do the backup on an external USB through OTG.
As long as it is not possible to decrypt the 6T, you won't be able to do a full backup. Does also not work via OTG as the encrypted data cannot be read from internal memory.
kunal420 said:
Rooted, TWRP and Magisk but when trying TWRP backup: Can not create '/data/media/0TWRP' folder (Required key nor available). Failed to make backup folder.
Already selected my security for lock screen to none and cleared my credentials.
Anyone know what to do?
Click to expand...
Click to collapse
It's because your phone is encrypted, but you can still take a nandroid backup using this thread.
https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482