On my rooted Defy - how do I install a zip-file??
Like this one;
http://forum.xda-developers.com/showpost.php?p=12426274&postcount=24
install the 2ndinit apk 1.4.2 newer ones wont work with some files
then reboot 2 times.
third reboot: press volume down, when the led is blue.
now choose recovery by pressin vol up or down and power to accept.
then choose costum recovery, and apply zip from sd. choose your file and confirm.
done
hope this answers your question
Thanks, seems simple enough
uh, where do I find 2ndinit.apk
You can find it here.
I know how to install .zip but I have a question. CWM3.1 does not flash some .zip like a baseband or a theme. It says "aborted". I think that the problem is that the file is not signed or something. In CWM2.5.1.8 works but the problem is that CM7 or MIUI changes it to CWM3. So, what should I do?
Thanks!
Works fine, even the mentioned zip-file!
The "issue" is that the latest CWM3.x no longer support "amend scripting" (stored in update-script) and won't apply zip's created with such scripts. Therefore all .zip which where written using the old method should be converted to edify scripting (which use different statements - more details here-).
is there an way to downgrade the 2ndinit? an how-to would be very nice
You can replace the recovery file from /system/bootmenu/recovery/sbin with the one from 2nd init 1.4.2 . The file persimmon should be rwxr-xr-x (755).
nepotu said:
You can replace the recovery file from /system/bootmenu/recovery/sbin with the one from 2nd init 1.4.2 . The file persimmon should be rwxr-xr-x (755).
Click to expand...
Click to collapse
and how do i do that? with rootexplorer? what for do i need the file permission? to change it or to set it after changing the files?
Yup. You can replace it using an app like root explorer. And the file permission should be set up after you copy the file (if you have the wrong file permission it won't work).
EDIT: I haven't tried yet to downgrade it this way but that's what I've read on the forum, therefore I cannot guarantee you it will work.
sry for me being a noob. i found the file named recovery in the folder you mentioned. but have got only the file 2ndinit.apk..... where do i get the recovery file from 2ndinit.apk ?
thank you for your time!
You can unpack it using a tool like Apk Manager 4.9 or simply by using 7zip to extract the files from the apk which is in fact some sort of archive. However as I've mentioned in the previous post I didn't tried to downgrade using this method. All I can say is that I've read here on xda about this method, therefore I cannot guarantee you this will work. I think is better to wait someone with more experience to answer.
As an unexperienced user i think i'll wait for a better solution.
As i read, this problem appears quite often, how come that nobody tried to make a solution for this problem?
Hello,
I recently uninstalled some (system / T-Mobile) apps with Titanium Backup. And I did not make a backup first. The phone still runs fine but the OTA fails.
I tried so far:
- RUU 1.28 -> does not work, because system is already 1.29
- find rom.zip and unpack -> Ok, but cannot unpack system.img, unyafs fails.
The file which the OTA misses, according to logfile is named: 4661_TMODE_Music_One.odex
If someone could sent me this file or upload it somewhere I would be thankful.
There is a good chance that there are more files missing, but the log stops after the first fail.
I see in the system.img that there are at least 4 files with similar names:
4661_TMODE_Music_One.odex
4661_TMODE_Music_One.apk
4662_TMDE_Games_One.odex
4662_TMDE_Games_One.apk
If anyone knows how to unpack these, this would also helpful.
deleted
I think the best way to get all your bloatware back is to lock the bootloader and then flash the 129 RUU. Here is the link for the RUU if its T-mobile uk.
http://www.filefactory.com/file/6y1...Radio_1.1204.105.14_release_260731_signed.exe
Once your back to stock you can unlock again with your unlock token, flash cwm and make a stock nandroid backup.
If you need a file factory password pm me.
No, it's T-Mobile Germany, so I guess this will not help.
At the moment I'm trying to unpack the files from the system.img, but none of the methods described in the forums are working.
It is almost crazy, I can see the filenames and contents (lots of "PK" headers for instance) within the system.img but I've no idea how to extract them.
Get in touch with football. He might be able to get the RUU for you.
ghori1989 said:
Get in touch with football. He might be able to get the RUU for you.
Click to expand...
Click to collapse
Ok, tried that, waiting for the reply.
Meanwhile I'm able to mount the system image with some modifications as ext4 image and copy the contents. If there is an interest for this, I propably could write some tool to make this automatic.
Anyway, it did not help me, because the versions of the files in the image do not match the ones expected from the OTA.
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"
}
Someone was "helping" me root my Mi Mix2. I can't be 100% sure what went wrong, but he managed to get it stuck in Fastboot mode, such that no matter what I do (i.e. any combination of power offs, or simultaneous button presses, or commands from terminal). I suspect he did not understand me when I said Magisk was tool best suited...he may have used some more familiar or standard tool like SuperSU or something to try and root.
Assuming I have sufficiently described my problem, is there anything I can do to get the phone back into a usable state?
Is your bootloader unlocked? If yes try to flash ROM using miflash tool.
I appreciate the response/suggestion.
fotocreaman said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Yes. I double checked with "fastboot oem device-info" commmand
fotocreaman said:
If yes try to flash ROM using miflash tool.
Click to expand...
Click to collapse
On your advice I did that, including downloading current (?) version and current(?) version of stock ROM. I received a message to effect that a flash script (.bat) file was missing (or at least not found).
Other threads regarding this error suggest unzipping something (?) twice but I didn't see a file inside the original zip file that could be additionally unzipped, and certainly nothing with a .bat extension.
Can you put here the exact error message and when it exactly occurs? Describe the steps you did to get to that point
Hi aa040371
1- download fastboot rom for your phone and unzip it twice , put folder in C:\ storage http://update.miui.com/updates/v1/fullromdownload.php?d=chiron_global&b=F&r=global&n=
2- Look at the tutorial to use miflashtool https://c.mi.com/thread-1857937-1-1.html
regards
I'm Still Here...
So, after more than a few detours and distractions, I have my phone (Mi Mix 2S, not the plain "2" I originally indicated!) basically back to stock...good frustration-tolerance building exercise.
I am currently in the process of trying to get TWRP to remain after booting to OS. I have researched/read numerous threads on this -- e.g. boot into TWRP, flash TWRP, reboot directly into TWRP again -- but somehow none of them do the trick. Every time I boot into the OS, the Recovery partition gets overwritten and I am back to the stock recovery tool. If I can trust/believe what at least one person has indicated online, this appears to be due to a script in /system/bin, but I can't get at that file to rename or delete it. In fact, I can't even see it in the file system as that area is completely locked down. I know it is there as a Find command executed via ADB shell lists it even though it indicates it is off-limits.
So I turned my attention to loading a rooting app/tool instead hoping that would let me get TWRP to hang around for long term...another excursion in futility. My phone model is M1803D5XA, so according to one more forum thread somewhere, I am supposed to be using SuperSU rather than Magisk? Whatever...it seems impossible: most of the zip files I located don't pass security/file-signing check. The one I found that at least starts to load/install (SR5-SuperSU-v2.82-SR5-20171001224502) works fine right up until it fails while trying to update "sepolicy" files. For some reason I have to sideload SuperSU from TWRP because I am not allowed to push a file even to my SDcard via ADB.
I just don't get why this all has to be so difficult, as in each and every step along the way. I feel like Sisyphus or Job or someone similar...sigh Any thoughts or suggestions still welcome...thanks.
aa040371 said:
So, after more than a few detours and distractions, I have my phone (Mi Mix 2S, not the plain "2" I originally indicated!) basically back to stock...good frustration-tolerance building exercise.
I am currently in the process of trying to get TWRP to remain after booting to OS. I have researched/read numerous threads on this -- e.g. boot into TWRP, flash TWRP, reboot directly into TWRP again -- but somehow none of them do the trick. Every time I boot into the OS, the Recovery partition gets overwritten and I am back to the stock recovery tool. If I can trust/believe what at least one person has indicated online, this appears to be due to a script in /system/bin, but I can't get at that file to rename or delete it. In fact, I can't even see it in the file system as that area is completely locked down. I know it is there as a Find command executed via ADB shell lists it even though it indicates it is off-limits.
So I turned my attention to loading a rooting app/tool instead hoping that would let me get TWRP to hang around for long term...another excursion in futility. My phone model is M1803D5XA, so according to one more forum thread somewhere, I am supposed to be using SuperSU rather than Magisk? Whatever...it seems impossible: most of the zip files I located don't pass security/file-signing check. The one I found that at least starts to load/install (SR5-SuperSU-v2.82-SR5-20171001224502) works fine right up until it fails while trying to update "sepolicy" files. For some reason I have to sideload SuperSU from TWRP because I am not allowed to push a file even to my SDcard via ADB.
I just don't get why this all has to be so difficult, as in each and every step along the way. I feel like Sisyphus or Job or someone similar...sigh Any thoughts or suggestions still welcome...thanks.
Click to expand...
Click to collapse
Recovery will get overwritten by dm-verity, you have to flash either magisk or another mod that disables dm-verity, but personally I suggest to use a custom rom if you don't care about miui
HrX said:
Recovery will get overwritten by dm-verity, you have to flash either magisk or another mod that disables dm-verity, but personally I suggest to use a custom rom if you don't care about miui
Click to expand...
Click to collapse
Hello...thanks. I definitely don't care about MIUI...in fact the whole exercise I am struggling through is so I can get LineageOS onto my phone. I've probably read 50+ threads/posts on 6-7 different forums regarding unbricking/unlocking/rooting/TWRPing/customROMing my particular phone, but this is the first time I've seen mention of DM-Verity. I'll look into it...not really hopeful, though. But anyway...thanks again.