I've edited my imageres.dll file and have it all nice nice, but when I try to paste it into system 32 (tried safe mode) It will not let me overwrite that file.
I've tried Safe mode, Taking Control, Granting full control permissions of file, system32 folder, windows folder, and C folder (both taking control, and granting full permissions to: User (me) and Administrator (also me) Yes, i'm on windows 7 64bit but there is no Win 7 Forum here, however the imageres.dll is mentioned here, and I'm assuming the file is more-or-less the same. Besides taking ownership in C for Win 8 being bad? I did this to both System32 file and Syswow64 file- its now apparent to me that both are in USE and thats why I can't overwrite/modify them =/ So how do I use my modded one? (startup sound etc.)
Following this:
Code:
How to Take Ownership in Windows 7
1. Locate the file or folder on which you want to take ownership in windows explorer
2. Right click on file or folder and select “Properties” from Context Menu
3. Click on Security tab
4. Click on “Advance”
5. Now click on Owner tab in Advance Security Settings for User windows
6. Click on Edit Button and select user from given Change Owner to list if user or group is not in given list then click on other users or groups. Enter name of user/group and click ok.
7. Now select User/group and click apply and ok. (Check “Replace owner on sub containers and objects” if you have files and folder within selected folder)
8. Click ok when Windows Security Prompt is displayed
9. Now Owner name must have changed.
10. Now click Ok to exist from Properties windows
Once you have taken the ownership of file or folder next part comes is Granting Permissions to that file/folder or object.
How to Grant Permissions in Windows 7
1. Locate the file or folder on which you want to take ownership in windows explorer
2. Right click on file or folder and select “Properties” from Context Menu
3. Click on Edit button in Properties windows Click ok to confirm UAC elevation request.
4. Select user/group from permission windows or click add to add other user or group.
5. Now under Permission section check the rights which you want to grant i.e check “Full Control” under the “Allow” column to assign full access rights control permissions to Administrators group.
6. Click Ok for changes to take effect and click ok final ok to exit from Properties window.
Now you can access files of folder in windows 7 with full permissions and take full control.
also tried cmd prompt
Code:
takeown /F "C:\Windows\System32\imageres.dll"
with Sucess message (probably the same as my right click takeown reg file context thing)
I'm the only person/login/user on my PC. Ugh this is a pain in the butt. No matter what I've googled/tried hasn't worked. I don't have a linux CD/USB boot *(dunno if I do? but don't think I do) to repair/replace file, I may have Win 7 repair on my CD, maybe not.
EDIT: replacing the startup sound in imageres.dll in System32 and SysWOW64 folders still leaves me with default windows startup sound =( Only other file was imageres.dll in winsxs folder- copied, edited the copy, deleted the original with Fileassassin (it was locked, wouldn't edit, blah blah) STILL uses old windows start up sound, WHyyyyyy? theres MUI files with info for imageres.dll but IDK what's left where this sound exists =/ or where its coming from.
there used to be this program made for replacing system files
i don't remember its name, though
http://www.askvg.com/right-click-re...utility-to-replace-system-files-in-windows-7/
No manual methods worked for me, but just came across this and it worked, WOOT!
http://winaero.com/download.php?view.10
Starting with Windows 8, the administrator is no longer the same as root. Microsoft has very, VERY severely limited the administrator's abilities with many aspects of the system. This was done in an ill-conceived notion that they could curb piracy of Windows Store apps (like there's anything worth stealing in there, including games). People have already found a way to pirate Windows Store apps, so it was all just a way to irritate admins and hobbyists in the end.
@dragon_76: Care to explain what you mean by that? For one thing, Administrator on NT has never been "the same" as root (on POSIX); there's always been the local SYSTEM SID (which does some of the things which root would handle, such as being the process that drivers and initial user-space processes run as) and while I'm not entirely sure when the TrustedInstaller SID was added (may have been there since NT3.1 for all I know), it's been a part of Windows since well before Win8. For another thing, unlike root on a POSIX system, Administrator does not (and never has) automatically have access to everything; it's a SID like any other, and ACLs can be put in place to control its access.
Now, two powers that Administrator (and members of the Administrators group) do have are as follows:
1) Take ownership of any securable object (this allows completely overwriting the ACLs).
2) Impersonate any other SID (although some, like TrustedInstaller, are possibly trickier to impersonate in Win8 than they used to be; I need to investigate that).
If what you're complaining about is the fact that \Program Files\WindowsApps\ is now owned by TrustedInstaller and harder to mess with than you'd like, um... sorry? It's not *that* hard to take ownership (or set it back) from TrustedInstaller; you can do it as Admin, in fact.
*Ahem*
Back to *actually* being on-topic, older versions of Windows* had a background service that would undo any modifications to system files by replacing them with un-tampered copies from a backup location. Starting with Vista, such a service supposedly no longer exists, but it would be easy to implement something like it using VSS. So, you should verify that the file isn't being reverted. The simplest check is the modify timestamp and (if it's different on your file than on the stock one) the size. Somewhat more advanced is to use a hash function, such as MD5 or something from the SHA family, on the on-disc file and see whether it matches the version you put there.
Beyond that, you can easily replace system files if you do it while the OS isn't booted. Linux can do it, although that has risks. Better is to use WinPE (the Pre-installation Environment that bootable Windows disks and recovery tools load) and replace it from there.
Incidentally, you can use the command line tool icacls (which may even be present in WinPE by default) to both change ownership and set permissions on files and folders.
* Pre-Vista, which was the first version to switch to using TrustedInstaller to protect system files rather than letting Admin write to them by default. That's the last major change I'm aware of in the powers of the Administrator account on Windows, incidentally...
Hello everyone !
As some of you probably know, to be able to send and receive mms in japan (sms are not used most of the time, lots of phone are not even able to use them), you need to modify the mms.apk, to make your phone a fake iphone.
After some research and tests, I have been able to find a way to modify any mms.apk of any rom, as long as the phone is rooted.
But as I update my phone really often with CM, I didn't wanted to do the all process over and over again.
Then I created some little batch files, which I share to you now, for the ones who want the same things.
Those batch files should work on any rom and phones, as long as they are rooted, with adb right.
I have no credit for the tools used by those scripts, I only created the batch files which use them.
And I am not responsible of any damage those scripts could do to your phone !!
/!\ This script is available for windows only /!\
Installation process :
1.unzip the file somewhere (if updating, delete everything and unzip again)
2.connect your phone to your computer and check if you can access to your phone in adb root mode. For JB roms, I saw that changing the usb mode to PTP helps sometime.
3.launch "mms_mod.bat" in admin mode
4.if at the end of the process your phone doesn't reboot and you sms icon doesn't disappear from your android home, which happens most of the time, launch the "put_mms_again.bat" in admin mode.
5(a).if everything work, your phone should reboot, and your sms icon should disappear from your android home. It is normal, don't panic, just take it back from your applications launcher.
5(b).if everything work except pushing the file inside your phone (inside /system/app), do it manually with root explorer for example (don't forget to change the Mms.apk file permission after copying it), you can find the modded Mms.apk in "Output\[device model]\[date&time]\Modded_file\". Then reboot your phone.
Now it's ok, your phone should now works on softbank network!!
Don't forget to use mms mode when you want to send something to a japanese phone!
Please note that if anything goes wrong, you can find a backup of your Mms.apk in "Output\[device model]\[date&time]\Backup_file\"
Oh, and if it is not done already, don't forget to setup the softbank's APN.
For that, just download the program named "Tweakker" on google play, it is perfect for that. But be careful, the default APN to use depends of your phone plan.
Tell me if you have any suggestion or bug !
Change log :
2013/09/20 - release 0.2
- cleaning code and adding a backup feature which keeps the original and modded Mms.apk for each operation
2013/09/20 - initial release
Stremon said:
Hello everyone !
As some of you probably know, to be able to send and receive mms in japan (sms are not used most of the time, lots of phone are not even able to use them), you need to modify the mms.apk, to make your phone a fake iphone.
After some research and tests, I have been able to find a way to modify any mms.apk of any rom, as long as the phone is rooted.
But as I update my phone really often with CM, I didn't wanted to do the all process over and over again.
Then I created some little batch files, which I share to you now, for the ones who want the same things.
Those batch files should work on any rom and phones, as long as they are rooted, with adb right.
I have no credit for the tools used by those scripts, I only created the batch files which use them.
And I am not responsible of any damage those scripts could do to your phone !!
/!\ This script is available for windows only /!\
Installation process :
1.unzip the file somewhere
2.connect your phone to your computer and check if you can access to your phone in adb root mode. For JB roms, I saw that changing the usb mode to PTP helps sometime.
3.launch "mms_mod.bat" in admin mode
4.if at the end of the process your phone doesn't reboot and you sms icon doesn't disappear from your android home, which happens most of the time, launch the "put_mms_again.bat" in admin mode.
5.if everything work, your phone should reboot, and your sms icon should disappear from your android home. It is normal, don't panic, just take it back from your applications launcher.
Now it's ok, your phone should now works on softbank network!!
Don't forget to use mms mode when you want to send something to a japanese phone!
Oh, and if it is not done already, don't forget to setup the softbank's APN.
For that, just download the program named "Tweakker" on google play, it is perfect for that. But be careful, the default APN to use depends of your phone plan.
Tell me if you have any suggestion or bug !
Click to expand...
Click to collapse
I get the error message "adbd cannot run as root in production builds" on step after I run adb root.
Doug_74 said:
I get the error message "adbd cannot run as root in production builds" on step after I run adb root.
Click to expand...
Click to collapse
this is because your rom doesn't allow adb to run in root mode
was the Mms-signed.apk created successfully inside the script folder ?
if there was no error before, it should be the case.
in that case, rename Mms-signed.apk to Mms.apk, and put it manually to your /system/app/ phone folder.
Don't forget to save your Mms.apk before, and to change the access rights of Mms.apk after copying it to system folder.
Stremon said:
this is because your rom doesn't allow adb to run in root mode
was the Mms-signed.apk created successfully inside the script folder ?
if there was no error before, it should be the case.
in that case, rename Mms-signed.apk to Mms.apk, and put it manually to your /system/app/ phone folder.
Don't forget to save your Mms.apk before, and to change the access rights of Mms.apk after copying it to system folder.
Click to expand...
Click to collapse
No error and the file shows up, but is very small only 1.69kb. Shouldn't the file be closer to the original which is 8.56mb? I have s Samsung GS4 and the original file is SecMms.apk. I noticed the twframework-res did not run on the script just framework-res does this matter?
After messing with this for sometime I can see where the script is looking for Mmm.apk, but since I have a Samsung phone the file is SecMms.apk, so this is the problem I believe. Looks like you would need to have additional script just for Samsung to include twframework-res and framework-res, also to look for SecMms.apk. This is a nice script you built, BTW.
Doug_74 said:
No error and the file shows up, but is very small only 1.69kb. Shouldn't the file be closer to the original which is 8.56mb? I have s Samsung GS4 and the original file is SecMms.apk. I noticed the twframework-res did not run on the script just framework-res does this matter?
After messing with this for sometime I can see where the script is looking for Mmm.apk, but since I have a Samsung phone the file is SecMms.apk, so this is the problem I believe. Looks like you would need to have additional script just for Samsung to include twframework-res and framework-res, also to look for SecMms.apk. This is a nice script you built, BTW.
Click to expand...
Click to collapse
Be careful, if your GS4 use a special samsung mms program, this script will not work with it anyway, because the script modify some file inside the Mm.apk, which are probably not the same inside your SecMms.apk.
I bought the XZ1C from USA to India as it is not available at all in Indian markets (and never will be - because no compact devices were launched in India). I love this device except for one thing. Low internal memory - and I bet others might also be annoyed by this. There's two workarounds that I could immediately think of but can't be implemented with this Device.
1. Adoptable storage : Adopt external SD card as internal storage - this is one of the coolest features Oreo has to offer, but can't be used in this device. I went through a lot of blog posts and followed the steps, also read about the adoptable storage leading to no solution. I have a Samsung 128GB EVO SD card and I tried to adopt it as an internal storage in more than one ways with no success.
2. Move apps to SD : I thought I could move at least some apps if not all to external SD but this feature that was introduced in Android 2.2 (I remember using it on my Samsung Galaxy Apollo i5801) and re-introduced in 5.0. But this is also not working. I also tried enabling 'Force allow apps on external' under developer options which didn't work.
As I don't have this phone officially supported in my country, I want to check if someone can contact Sony support in their country (US, UK, Germany) to help fix this through an update maybe?
Another purpose of this thread is to discuss alternate workarounds if anyone has tried any and worked for them.
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I agree with you. I am going to wait for a while and see if Sony pushes an update that provides move apps to SD option (which I highly doubt they will). But if there comes a point where I desperately need space, I will root the phone. Out of 6 phones that I've used in past 6 years, this is the first one I haven't rooted and ain't planning to.
Possible Solution
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
What I've done now is to factory reset the phone with the sd card inserted and boot and setup the phone with the sd card in place this time. Then format it again thru the phone (I have not activated sd card encryption yet) and all of a sudden spotify, netflix, ... work with the sd card just as expected.
So perhaps one of you, who experience the same thing, might want try out if this is reproduceable.
Keep the sd card in the phone
Factory reset (I did it via the Xperia companion desktop software)
Boot it up again
Format SD Card
Click to expand...
Click to collapse
Antilogy said:
I've looked at a thread from the sony forums. Some people were able to get the microSD card to work by factory resetting the phone with the SD card inside. Hope this helps.
Click to expand...
Click to collapse
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disable by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
That means the TC should be able to do that.
Antilogy said:
That means the TC should be able to do that.
Click to expand...
Click to collapse
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can ?)
Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
Dany XP said:
What r u referring to?
( and "tc" =?... This ain't Twitter u know.. U can write as long as u can )
Click to expand...
Click to collapse
Sorry. I meant to say topic creator. In this case that would be @kaustubhg123.
You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.
mhaha said:
Unfortunately you're out of luck. I don't think any Xperias to date has ever supported adoptable storage.
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that.
You'd probably have to look at root options, but beware, unlocking the bootloader to root comes with consequences and compromises.
Click to expand...
Click to collapse
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).
Supa_Fly said:
I'm still very very green to android and to using Xperia Android phones ... what consequences and compromises are to be faced wtih rooting bootloader? From looking at former threads from over 4yrs ago it seemed that rooting was THE holy grail and raison de T'etre for having an Android (reason for being/having).
Click to expand...
Click to collapse
Sony have given developers and java enthusiasts the finger with this latest bootloader. There isn't a way to save the encrypted keys (unique to your phone) before unlocking it. So you can unlock it to do development, but it's a one way step, which breaks the camera and a few other functions.
In the past my two main reasons for rooting were to theme the phone a different colour and to save battery. Theming can be done without root now and my battery lasts three days anyway.
Having said that, I have just flashed sToRm//'s TWRP + KERNEL + ROOT + DRM fix/restore (because there’s a rooting enthusiast inside every android owner) and everything is working perfectly. The camera is working and all the software functions correctly.
But rooting the phone to get you control over moving apps to the SD card is a bit extreme and a lot of work for a very minor inconvenience. What are you doing with a small compact phone if you want to use two or three hundred apps?
Dany XP said:
Don't understand what u guys are talking about.
Either use SD card as internal memory (I know for sure that is disabled by Sony, for good reasons..) or simply make Netflix, Spotify etc use sd card to keep music / movies... Because If it's the second case, I can do that without any problem, just inserted my Samsung Evo 128 gb use it on the go, no pb,no particular steps...
Click to expand...
Click to collapse
What good reasons?
I have enabled all apps to save their things on SD card (The camera app stores all photos on SD by default but the stupid Album app stores its thumbnails data on internal memory for no reason). My main big issue is with WhatsApp which stores its data on internal memory and provides no option to store it on SD card. WhatsApp is almost 11GB on my phone now.
mhaha said:
As for moving apps to SD, it was never an option for this phone. I don't know if this was a decision with Sony's Oreo implementation across all models, or just certain models, or what, but you can't do that..
Click to expand...
Click to collapse
The Xperia V & Z1c both allowed apps to store their data on SD (Spotify, Audible, etc.) but can't do it on this phone :/ Apparently, Oreo blocks us from using our SD card in this way.
luminoso said:
You can actually use a little neat trick:
Unlock your bootloader
Install XperiFix ( https://www.xperifix.com ) - XDA Thread to restore camera and X-R,BionZ functions (thanks a lot Sony, for nothing)
Xperifix auto install Magisk 16
Use [Magisk Module] Magic Folder Binder (fbind) module to "join" your internal folders with SDCARD and bind folders like Downloads, DCIM, .android
For example if you download a file, even if the phone downloads it to the internal memory it will be actually on the SDCARD. fbind also moves the old data to sdcard when you configure fbind.
Click to expand...
Click to collapse
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card
reckfield said:
so, luminoso, in that case, can i transfer apps from phone to sd card?
because you are talking about bind the download folder, but having 10gb on my whatsaap i was really interested in move this ffrom phone storage to sd card
Click to expand...
Click to collapse
You can bind whatsapp folder in that case
luminoso said:
You can bind whatsapp folder in that case
Click to expand...
Click to collapse
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?
reckfield said:
I decided to go ahead with xperifix, i have g441 compact xz1 european version, last firmware a.12a.179. i tried several times , but its not working with xperifix 2.5 last version
i attached some logs
error: device unauthorized.
This adb server's $ADB_VENDOR_KEYS is not set
Try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
06-6-2018_18-14-51 ===> List /system
Luminoso, do you have any idea¨?
Click to expand...
Click to collapse
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.
Raz0Rfail said:
Patching of your twrp recovey is needed.
I had to patch it with the last recovery (26. May) https://forum.xda-developers.com/xp...t/recovery-twrp-3-1-1-stock-security-t3706704
if you do it your twrp is not safe !
At first download Android kitchen, extract it.
Copy your twrp file into the folder and open unpackimgbat
After finish you have a folder called "ramdisk", open it.
Inside you open the file "prop.default" with your texteditor.
find the following two parameter and set them to 0:
ro.secure=1
ro.adb.secure=1
save the file, go one folder up and click on repackimg.bat.
You have a "new-recovery.img" file.
Boot your device into fastboot:
fastboot flash recovery <path of your new recovery.img>
The solution works, but device security is in danger.
You can use it, or wait for a new twrp.
Click to expand...
Click to collapse
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
2. when will the new twrp launch? because the last update on twrp's website was december 2017
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem
reckfield said:
Thanks raz0rfail, it seems that has a solution in this.
three considerations allow me to ask you.
1. firstly, im encouraged to follow your instructions, but im entering a completely new field, Idont know whats android kitchen , how to copy "my twrp file into the folder", and after carrying out this instructions, should I open again xperifix, and launch the rooting process? if so, There is any risk xperfix overwrite the "previous patched" twrp as you told me in the last post?
Xperifix will always download the twrp image from his servers, you have to go a little around to use your twrp file, or he updates his img-file on his server.
2. when will the new twrp launch? because the last update on twrp's website was december 2017
Your device twrp has nothing to do with the generic release from twrp. Read the text below your qoute.
3. Storm's xperifix 3.0 it is worth it to wait its release? because maybe waiting one month more, probably my twrp problem could be solved?
I don't know what he will change, but if he always redownload the twrp file from his server, he has to update the img-file.
I'm confused, but thank you for you reply, at least you give me a little of chance of fix this problem
Click to expand...
Click to collapse
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.
Raz0Rfail said:
OK I will start from scratch with explaining:
TWRP (TeamWin Recovery Project) brought a TWRP version out called 3.2.1 or so, but released twrp version is generic for all android devices.
So some devices have special requirements for a working twrp recovery and a Device Developer patch the generic twrp version to get it working on this device.
It needs time but on many devices it's mandatory.
So i meant in the last thread entry not the generic twrp version from TWRP creator, i meant the modificated version from our device developer which creates our twrp version.
Currently he hasn't released a version which works with the last XZ1 compact firmware 47.1.A.12.205.
And if you use a different twrp which not works on your new firmware, you will get the message $ADB_VENDOR_KEYS is not set or the message adb device is unauthorized.
My tutorial shows you how to modificate your twrp version which you get from Xperifix to get it working with the new firmware.
But if you use my twrp, your device isn't secured as you used a the correct twrp recovery from our device developer.
So you can decide if you want to use the new firmware and magisk and my cam and stay a little unsecure or you wait if the device has created a working twrp for the firmware and xperifix has updated the img-file on his server.
Execution steps for patching your twrp recovery image and get cam and magisk working again on new firmware.
At first download Android Image kitchen from here:
https://forum.xda-developers.com/showthread.php?t=2073775
Download minimal adb and fastboot from here:
https://androidfilehost.com/?fid=962187416754459552
Extract both Zip-Files on a place you want.
Then you have under C:\Xperifix\DATA\TWRP an .img-File called xz1c-twrp.img if Storm didn't change the paths.
Copy this file into the folder where you extracted Android Image Kitchen.
Execute Unpackimg.bat and change parameter in the file as described. Then execute repackimg.bat.
Open cmd.exe with windows-key + r-key. Enter cmd.exe and execute it.
Open the folder where you have extracted minimal adb and fastboot and copy the filepath of it.
switch back to cmd and enter the command cd + your path and press enter.
You should now be inside your folder inside cmd.
Then open the folder where you have extracted android Image Kitchen and right click on the new-recovery.img and in contextmenu click copy path.
switch back to cmd and enter the following command:
fastboot flash recovery and right click and click on insert to insert the image path. But don't execute it!
Next step have to do with Xperiix:
Reboot your phone into fastboot and start executing XperiFix.
if You got the message in XperiFix that the recovery is flashed unplug your phone and boot it again into fastboot.
Now execute the command inside cmd.exe
click up on your keyboard to get the last command inside cmd and replace the word "flash" with "boot" and your phone start booting into correct twrp image.
Now let Xperifix work until it's finished and you should have a working cam and magisk.
Click to expand...
Click to collapse
the descriptions are absolutely precise to follow and thanks you,
in the folder data, according your description there must be this directory C:\Xperifix\DATA\TWRP an .img-File.
on my xperifix there is not such folder. attach you some images, (I also reinstall xperfix 2.5 ruling out if I lost some folders)
{
"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"
}
Hope I created new thread in right path. As by title, I found nothing about this 7'' tablet . I tried to unlock the bootloader with the command:
fastboot oem unlock-go
but it returns:
failed (remote: unknown command)
Meanwhile, I found nothing about a TWRP for this device. Are there chances that something will be developed? Is it a question of time? Thanks in advance.
i have the same problem. No one help us?
im trying to root mine so i can get the proximity sensor locked. I am building a tablet install in my RX8, using this tablet. However as soon as I pop it in the housing the screen has a mind of its own, sometimes it works sometimes it makes me want to smash it up
Systemlessly Root Lenovo Tab 4 7 TB-7504X
Hello all!!?
Here I will guide you to root Lenovo Tab 4 7 TB-7504X with the chipset MT8735B and Android version 7.0 that also systemlessly!! So let's get tuned into the Step by Step Guide...?
Firstly, I am not responsible for any kind of demage caused to your phone!!
Actually there are two methords of doing so...
Moving on to first one (Simplest),
You need to download latest version of MTK Easy Su v1.0.6 and the Magisk Manager specifically v7.1.1 I will provide link for both of them below...
Install both of them...
Now Firstly open the MTK Easy Su apk and just tap on 'Activate Bootless Root' if it says 'Exit value 0' in the Log section that means you have Root access on your phone...
Note:- Don't try to update Magisk or Magisk Masnager or Set environment for modules to work properly in Magisk Manager, else you will brick your phone
- Don't update Magisk Manager Directly from the apk
- The following process is done on lock bootloader so be carefull.
- You will have to Open the MTK Easy Su apk and tap on 'Activate Bootless Root' each and every time you Reboot your phone...
Pros:-
- Systemless Root
Cons:-
-Will not be able to Update Magisk Manager or Migisk itself
- Will not be able to install Magisk Modules
Second Method:-
For this to work on your phone you need couple of apks and Files...I will provide all the links at the end of this post...
Again, I am not responsible for any kind of demage caused to your phone!!
- Firstly, You need to download an apk named 'init.d Scripts Support' and also need to know your phone's architecture i.e 32 bit or 64 bit if you don't know just download any apk like CPU-Z or anything like that and note your phone's architecture...
- Now, you need to create an folder named 'init.d' in your phone's internal storage and again create another folder named 'bin' inside the 'init.d' folder
Now, you need to move some files in these folders to gain Root access...So let's move on...
- Firstly, Unzip all the Files...
- Open folder named 'magisk-boot' and copy the file named 'magisk-boot.sh' and paste it in 'init.d' folder
- Moving on to next file, then open folder named 'mtk-su_r22' then open the folder based on your phone's architecture i.e 'arm' or 'arm64' (For 32 bit architecture open 'arm' & For 64 bit architecture open 'arm64') and copy the file named 'mtk-su' and just paste the file inside the 'bin' folder of 'init.d' folder
- Moving on to last file to copy, open the folder named 'Magisk-20.4', then open folder named 'arm' there you will find 3 files here, we are just conserned about 2 files named 'magiskinit' & 'magiskinit64'. Just copy one of the two files based on your architecture (If 32 bit then copy 'magiskinit' & if 64 bit just copy 'magiskinit64') and paste it in 'bin' folder of 'init.d' folder. The one who have 64 bit architecture need to make a small change in the file 'magiskinit64' we just copied to 'bin' folder. Just rename the file and remove '64' written behind the file name.
Now your 90% of work has been completed!!
Now install the latest version of 'Magisk Manager' currently v7.5.1 is the latest.
- Now open 'init.d scripts support' apk and check the 'Run scripts at boot time' option.
- Then set 'Execution delay' to 'No delay'
- Now tap on 'Selected folder' and just locate the 'init.d' folder and select it.
Note:- Please let be the option 'Try to acquire root privileges' Uncheked!!
Lastly Reboot your phone and after Rebooting open the 'init.d scripts support' apk and just tap on 'Run scripts now' it will show 1 File selected and then it will Show 1 File Executed'!!
Then just tap 'Show last execution results' (You may need to watch an add every 24 hours) and if it shows 'client: launching new main daemon process' at the very least of the execution results...Congratulations!! Now you have got Systemless Root on your Lenovo Tab 7 TB-7504X successfully!!
Note:-
- Don't Mess around things you don't know on a locked bootloader or you would brick your device
- Don't update Magisk via the apk itself
- Be Carefull while installing Magisk Madules on a locked bootloader
- You will have to Run the init.d scripts support apk each and every time you reboot your phone to have root access enabled
You can search on YouTube for 'How to root Lenovo Tab 7 TB-7504X' (Second Method) the video is recently made by me
Channel's Name:- Tricky Everything
Sorry For the poor video and audio quality
If You Like the video please Like,Share, Subscribe and Comment...
Important Note:-
You can update the files Needed to have root access (basically Magisk itself) just be sure to place the correct file in the correct location and with the correct name!!
Files Needed to Root (First Method):-
MTK Easy Su v1.0.6 apk
Magisk Manager v7.1.1 apk
Files Needed (Second Method):-
MTK su_r22.zip (latest version)
Latest Magisk-boot.zip
Magisk-20.4.zip
Magisk Manager-v7.5.1 apk
RidhamSai said:
Systemlessly Root Lenovo Tab 4 7 TB-7504X
Hello all!!?
Here I will guide you to root Lenovo Tab 4 7 TB-7504X with the chipset MT8735B and Android version 7.0 that also systemlessly!! So let's get tuned into the Step by Step Guide...?
Firstly, I am not responsible for any kind of demage caused to your phone!!
Actually there are two methords of doing so...
Moving on to first one (Simplest),
You need to download latest version of MTK Easy Su v1.0.6 and the Magisk Manager specifically v7.1.1 I will provide link for both of them below...
Install both of them...
Now Firstly open the MTK Easy Su apk and just tap on 'Activate Bootless Root' if it says 'Exit value 0' in the Log section that means you have Root access on your phone...
Note:- Don't try to update Magisk or Magisk Masnager or Set environment for modules to work properly in Magisk Manager, else you will brick your phone
- Don't update Magisk Manager Directly from the apk
- The following process is done on lock bootloader so be carefull.
- You will have to Open the MTK Easy Su apk and tap on 'Activate Bootless Root' each and every time you Reboot your phone...
Pros:-
- Systemless Root
Cons:-
-Will not be able to Update Magisk Manager or Migisk itself
- Will not be able to install Magisk Modules
Second Method:-
For this to work on your phone you need couple of apks and Files...I will provide all the links at the end of this post...
Again, I am not responsible for any kind of demage caused to your phone!!
- Firstly, You need to download an apk named 'init.d Scripts Support' and also need to know your phone's architecture i.e 32 bit or 64 bit if you don't know just download any apk like CPU-Z or anything like that and note your phone's architecture...
- Now, you need to create an folder named 'init.d' in your phone's internal storage and again create another folder named 'bin' inside the 'init.d' folder
Now, you need to move some files in these folders to gain Root access...So let's move on...
- Firstly, Unzip all the Files...
- Open folder named 'magisk-boot' and copy the file named 'magisk-boot.sh' and paste it in 'init.d' folder
- Moving on to next file, then open folder named 'mtk-su_r22' then open the folder based on your phone's architecture i.e 'arm' or 'arm64' (For 32 bit architecture open 'arm' & For 64 bit architecture open 'arm64') and copy the file named 'mtk-su' and just paste the file inside the 'bin' folder of 'init.d' folder
- Moving on to last file to copy, open the folder named 'Magisk-20.4', then open folder named 'arm' there you will find 3 files here, we are just conserned about 2 files named 'magiskinit' & 'magiskinit64'. Just copy one of the two files based on your architecture (If 32 bit then copy 'magiskinit' & if 64 bit just copy 'magiskinit64') and paste it in 'bin' folder of 'init.d' folder. The one who have 64 bit architecture need to make a small change in the file 'magiskinit64' we just copied to 'bin' folder. Just rename the file and remove '64' written behind the file name.
Now your 90% of work has been completed!!
Now install the latest version of 'Magisk Manager' currently v7.5.1 is the latest.
- Now open 'init.d scripts support' apk and check the 'Run scripts at boot time' option.
- Then set 'Execution delay' to 'No delay'
- Now tap on 'Selected folder' and just locate the 'init.d' folder and select it.
Note:- Please let be the option 'Try to acquire root privileges' Uncheked!!
Lastly Reboot your phone and after Rebooting open the 'init.d scripts support' apk and just tap on 'Run scripts now' it will show 1 File selected and then it will Show 1 File Executed'!!
Then just tap 'Show last execution results' (You may need to watch an add every 24 hours) and if it shows 'client: launching new main daemon process' at the very least of the execution results...Congratulations!! Now you have got Systemless Root on your Lenovo Tab 7 TB-7504X successfully!!
Note:-
- Don't Mess around things you don't know on a locked bootloader or you would brick your device
- Don't update Magisk via the apk itself
- Be Carefull while installing Magisk Madules on a locked bootloader
- You will have to Run the init.d scripts support apk each and every time you reboot your phone to have root access enabled
You can search on YouTube for 'How to root Lenovo Tab 7 TB-7504X' (Second Method) the video is recently made by me
Channel's Name:- Tricky Everything
Sorry For the poor video and audio quality
If You Like the video please Like,Share, Subscribe and Comment...
Important Note:-
You can update the files Needed to have root access (basically Magisk itself) just be sure to place the correct file in the correct location and with the correct name!!
Files Needed to Root (First Method):-
MTK Easy Su v1.0.6 apk
Magisk Manager v7.1.1 apk
Files Needed (Second Method):-
MTK su_r22.zip (latest version)
Latest Magisk-boot.zip
Magisk-20.4.zip
Magisk Manager-v7.5.1 apk
Click to expand...
Click to collapse
i dont see any link bro