XPOSED FOR XPERIA M4 AQUA- STOCK 5.0
Hello guys, i updated the guide, for install xposed on stock 5.0 rooted firmware.
Much thanks to @husam666 and anyone who made twrp,xposed and all other...
PLEASE NOTE: AFTER THIS STOCK CAMERA WILL NOT WORK. USE GOOGLE CAMERA
Requirements:
Unlocked bootloader & root (CLICK HERE TO SEE HOW TO DO IT...)
Xposed apk file:http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440
Xposed zip file: http://forum.xda-developers.com/attachment.php?attachmentid=3543411&d=1447616600
The guide will not show how to unlock bootloader and root phone, only xposed install procedure.
Step 1:
Install xposed apk file in the phone, then run adb tools on pc.
Step 2:
Reboot phone into recovery TWRP. (press vol- button at power, when phone vibrate, press it for much time). Screen will be black, not worry, its all ok.
Step 3:
type (in adb) these 2 commands:
Code:
adb devices
(If your device is here, you can continue.)
and
Code:
adb shell
Step 3:
A prompt like ~ # will appear, type these commands :
Code:
mount -w /dev/block/platform/7824900.sdhci/by-name/system /system
mount -w /dev/block/platform/7824900.sdhci/by-name/userdata /data
mount -w /dev/block/platform/7824900.sdhci/by-name/cache /cache
Step 4:
Now type:
Code:
twrp sideload
Step 5:
Type
Code:
adb sideload <path_to_zip>
(without <> and with the real directory of the zip.)
Step 6:
When done, type that:
Code:
adb reboot
ALTERNATIVE BEST METHOD: Install new TWRP touch recovery with working display, put zip into sd internal and flash. At the end of flash wipe dalvik cache /cache.
The phone will reboot and you have xposed installed!.
Attention: XDA, Me and all other members not take responsability for damaged phones or other problems.
I can't wait to know how to install Xposed! THANKS AGAIN!
Guide updated!
Could you explain better the point 5: <path_to_zip> ?
It could be useful, so we are sure not to miss anything.
EnricoLH said:
Could you explain better the point 5: <path_to_zip> ?
It could be useful, so we are sure not to miss anything.
Click to expand...
Click to collapse
The path to the zip file of xposed, can be something like c:\downloads\xposed-v74-sdk21-arm64.zip
Also I would like to note that you should do this after you flashed the zip so that you don't get low storage space error
celtique said:
For those with "Low Space" after sideloading xposed, do as follow:
Code:
adb shell
twrp wipe cache
twrp wipe dalvik
reboot
It will take long to boot.
It stuck after 10 min, simple press the tiny button next to SD Card and the power on again.
Enviado desde mi E2306 mediante Tapatalk
Click to expand...
Click to collapse
error: protocol fault (no status)
Argh...always this message when I try to sideload
Edit : If sideload crashes for you, after mounting, instead of sideload, type
twrp install /data/media/0/<yourxposedfile.zip>
and wait for it.
After the "Done processing script file", plug out your cable and press power and vol+ until it vibrates 3 times.
Press power to boot
Pay attention to copy the xposed zip file in internal memory and not in your external SD Card
Guys later i will update guide for fixing problem of memory.
Infinite thanks to @husam666.
alby_var said:
Guys later i will update guide for fixing problem of memory.
Infinite thanks to @husam666.
Click to expand...
Click to collapse
If you can add the part I wrote for those who have sideloading problem, it can be useful
husam666 said:
The path to the zip file of xposed, can be something like c:\downloads\xposed-v74-sdk21-arm64.zip
Also I would like to note that you should do this after you flashed the zip so that you don't get low storage space error
Click to expand...
Click to collapse
After do that, stuck at boot...
After install xpoxed, memory error, after fix memory error (wipes from recovery,hard reset,flashtool wipe) you will lose de camera. No way to hold the camera working after 13 flashins. Firm 112.
Somebody can confirm that after install xposed,fix the memory error,have working the camera?
Flamenawer said:
After install xpoxed, memory error, after fix memory error (wipes from recovery,hard reset,flashtool wipe) you will lose de camera. No way to hold the camera working after 13 flashins. Firm 112.
Somebody can confirm that after install xposed,fix the memory error,have working the camera?
Click to expand...
Click to collapse
I lost my camera, too. Too lazy to figure out what caused it, so I'm reflashing /system
husam666 said:
I lost my camera, too. Too lazy to figure out what caused it, so I'm reflashing /system
Click to expand...
Click to collapse
Same for my camera not working
Which way I can uninstall xposed without losing everything ?
Thanks
Envoyé de mon E2333 en utilisant Tapatalk
flexouille1 said:
Same for my camera not working
Which way I can uninstall xposed without losing everything ?
Thanks
Envoyé de mon E2333 en utilisant Tapatalk
Click to expand...
Click to collapse
There's a zip file that uninstalls it, not sure if you'll get your camera back
I didn't test the camera. I lost apps in SD card.
I flashed an Uninstaller and it gone back to normal
Flamenawer said:
After install xpoxed, memory error, after fix memory error (wipes from recovery,hard reset,flashtool wipe) you will lose de camera. No way to hold the camera working after 13 flashins. Firm 112.
Somebody can confirm that after install xposed,fix the memory error,have working the camera?
Click to expand...
Click to collapse
Try to sideload and older version of xposed64.
Enviado desde mi E2306 mediante Tapatalk
This moded camera from z3 work, http://forum.xda-developers.com/cro...ps/mod-xperia-camera-unlocked-t3071161/page49
Only problems, will show 20mpx,but will work at 13mpx in auto mode. And camera not work too. Is a starting.... until a xposed version that work. You need have the xposed 20 superior auto module.
I will look for a old version of xposed.
I flashed the original firmware (26.1.B.2.129) and I have my camera back.
[Noob question] Could somebody explain what benefits of Xposed installing bring to the phone?
lordgamma said:
[Noob question] Could somebody explain what benefits of Xposed installing bring to the phone?
Click to expand...
Click to collapse
It brings you modifications of the framework without touching any apks
Someone succeded to install it without bugs (no photo, no sd)?
Related
I'm trying to understand how to be able to mod a recently bought chinese phone "infocus m512", it's based on qualcomm snapdragon msm8926 and has android 4.4.2 installed which comes with "su" already installed, so basically the phone is already rooted.
I've found out the following:
/system is read only and cannot be remounted with r/w using the "su" available.
powering with both volume buttons pressed boots into some mode where the system is r/w but any changes made are not kept. I think it is FTM mode, the device is then recognized by ADB but not by FASTBOOT.
powering with vol down button pressed boots into download mode and the device is not recognized by ADB or FASTBOOT.
Any help understanding how to:
1. modify the /system partition
2. what can be done in FTM mode, and why changes to system do not stick
3. how to possibly use download mode to flash modified imgs?
4. find out if any write protection is enabled on the device
Thanks
sirpy said:
I'm trying to understand how to be able to mod a recently bought chinese phone "infocus m512", it's based on qualcomm snapdragon msm8926 and has android 4.4.2 installed which comes with "su" already installed, so basically the phone is already rooted.
I've found out the following:
/system is read only and cannot be remounted with r/w using the "su" available.
powering with both volume buttons pressed boots into some mode where the system is r/w but any changes made are not kept. I think it is FTM mode, the device is then recognized by ADB but not by FASTBOOT.
powering with vol down button pressed boots into download mode and the device is not recognized by ADB or FASTBOOT.
Any help understanding how to:
1. modify the /system partition
2. what can be done in FTM mode, and why changes to system do not stick
3. how to possibly use download mode to flash modified imgs?
4. find out if any write protection is enabled on the device
Thanks
Click to expand...
Click to collapse
Had any luck?
moding infocus m512 progress report
I was able to get fastboot to recognize the device using the -i option.
I was able to extract the recovery img and unpack it, also compiled a modified mkbootimg.
I did re-flash the splash img using fastboot so it seems there's no some kind of protection against flashing.
I will try to flash a modified boot and recovery that will mount the /system as rw and see if it works.
I still think maybe there's some kind of selinux settings involved preventing mounting system as rw, i will have to dig deeper for that.
GalaxyWhy said:
Had any luck?
Click to expand...
Click to collapse
sirpy said:
I was able to get fastboot to recognize the device using the -i option.
I was able to extract the recovery img and unpack it, also compiled a modified mkbootimg.
I did re-flash the splash img using fastboot so it seems there's no some kind of protection against flashing.
I will try to flash a modified boot and recovery that will mount the /system as rw and see if it works.
I still think maybe there's some kind of selinux settings involved preventing mounting system as rw, i will have to dig deeper for that.
Click to expand...
Click to collapse
Sounds good Keep me posted!
EDIT:
Are you running the most updated software? - http://www.infocusphone.com/m512updates.html
Yours came rooted you say? Where did you buy it from? - I got mine in pandawill.com and I'm waiting for it to arrive, hooeukly its rooted ?
Sent from my LG-D802
rooting infocus m512
GalaxyWhy said:
Yours came rooted you say? Where did you buy it from? - I got mine in pandawill.com and I'm waiting for it to arrive, hooeukly its rooted ?
Sent from my LG-D802
Click to expand...
Click to collapse
I bought it on lightinthebox.com anyways it shouldn't be much a problem to root it, since it's possible to flash a boot img to the device using fastboot.
I finally was able to trace the issue of not being able to mount /system as read/write to an error in the ext4 file system
it seems like the stock system.img has errors in its file system, so when the device initially mounts the /system partition it immediately remounts it as read-only because of the errors.
I was unable to flash a repaired system.img using fastboot (it dies in the middle, maybe because its such a large file), but I was able to modify the boot.img fstab.qcom to add the option errors=continue to the mount options of the /system partition. and now it is possible to mount /system as read write and you can do whatever you want as root.
{
"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"
}
In this picture it shows the phone having a recents button but on the website I bought it off it has a menu button. Which one does yours have?
You seem to know more about this stuff than me, I've usually bought well supported devices and rooting was a one click process. I just wanna get root access to be able to use Xposed Modules
Sent from my LG-D802
How'd you go?
I just received mine and I want to root it
rooting infocus m512
GalaxyWhy said:
How'd you go?
I just received mine and I want to root it
Click to expand...
Click to collapse
are you sure your device isn't already rooted? try to install supersu.
if you are sure it is not rooted you can root it the following way:
1. install adb
2.download su binary from somewhere
3. boot into Field Test Mode by (with phone turned off and connected to usb) holding both volume keys and power key together, when phone turns on release the power button and wait until the blue led turns off, then release volume keys. after a sec or two you should see some text on the screen.
4. connect to device via abd, run "adb shell"
5. mount the system as read/write by
(i'm not sure about /dev/block/mmcblk01/platform/by-name/system, it is something similar but you can find out yourself by search the subdirectories)
Code:
mkdir systmp
mount -t ext4 -o rw /dev/block/mmcblk01/platform/by-name/system /systemp
chmod 4755 /systmp/xbin/su
6. exit shell and run "adb push <path to su binary> /systmp/xbin
7. run "adb reboot"
8. install supersu or some other su manager.
let me know how it went.
sirpy said:
are you sure your device isn't already rooted? try to install supersu.
if you are sure it is not rooted you can root it the following way:
1. install adb
2.download su binary from somewhere
3. boot into Field Test Mode by (with phone turned off and connected to usb) holding both volume keys and power key together, when phone turns on release the power button and wait until the blue led turns off, then release volume keys. after a sec or two you should see some text on the screen.
4. connect to device via abd, run "adb shell"
5. mount the system as read/write by
(i'm not sure about /dev/block/mmcblk01/platform/by-name/system, it is something similar but you can find out yourself by search the subdirectories)
Code:
mkdir systmp
mount -t ext4 -o rw /dev/block/mmcblk01/platform/by-name/system /systemp
chmod 4755 /systmp/xbin/su
6. exit shell and run "adb push <path to su binary> /systmp/xbin
7. run "adb reboot"
8. install supersu or some other su manager.
let me know how it went.
Click to expand...
Click to collapse
Yeah 100% mine didn't have root but I figured it out after lots of searching around. I posted my method here http://forum.xda-developers.com/gen...discussion-t2893455/post55787107#post55787107 so others could do it if they wanted to
Similar problem here
sirpy said:
I finally was able to trace the issue of not being able to mount /system as read/write to an error in the ext4 file system
it seems like the stock system.img has errors in its file system, so when the device initially mounts the /system partition it immediately remounts it as read-only because of the errors.
I was unable to flash a repaired system.img using fastboot (it dies in the middle, maybe because its such a large file), but I was able to modify the boot.img fstab.qcom to add the option errors=continue to the mount options of the /system partition. and now it is possible to mount /system as read write and you can do whatever you want as root.
Click to expand...
Click to collapse
My phone is (seemingly) rooted, however I cannot modify platoform.xml (tried root explorer, total commander and what not). Also cannot remount the system partition using adb remount.
Can you provide details on how exactly did you modify fastab.qcom (and by the way, is it the file residing in the file system root directory)?
I tried modifying it and it seemed to succeed, however on reboot I had the original fstab.qcom.
Also, it seems that the su binary that I am using is not up to date. Each time I enter SuperSU it says that su binary needs to be updated, however the update fails (I tried both the normal way and the TWRP/CWM way). You wrote in a later post that the phone should be easily rooted using su that I can "download from somewhere". Can you point me to where I can find a suitable su binary?
modifying fstab
Beni.Falk said:
My phone is (seemingly) rooted, however I cannot modify platoform.xml (tried root explorer, total commander and what not). Also cannot remount the system partition using adb remount.
Can you provide details on how exactly did you modify fastab.qcom (and by the way, is it the file residing in the file system root directory)?
I tried modifying it and it seemed to succeed, however on reboot I had the original fstab.qcom.
Also, it seems that the su binary that I am using is not up to date. Each time I enter SuperSU it says that su binary needs to be updated, however the update fails (I tried both the normal way and the TWRP/CWM way). You wrote in a later post that the phone should be easily rooted using su that I can "download from somewhere". Can you point me to where I can find a suitable su binary?
Click to expand...
Click to collapse
Once you solve the readonly issue. you should be able to download and update supersu.
I've modified the fstab by extracing the boot.img opening it, modifying the fstab file and flash the modified boot.img back to the device.
you should be able to find numerous guides by googling on how to extract android boot.img.
for a quick fix, you can download the rom from needrom.com, and flash it. this rom is rooted and doesnt have any readonly issue on the system partition. (but you will loose everything on the phone)
sirpy said:
Once you solve the readonly issue. you should be able to download and update supersu.
I've modified the fstab by extracing the boot.img opening it, modifying the fstab file and flash the modified boot.img back to the device.
you should be able to find numerous guides by googling on how to extract android boot.img.
for a quick fix, you can download the rom from needrom.com, and flash it. this rom is rooted and doesnt have any readonly issue on the system partition. (but you will loose everything on the phone)
Click to expand...
Click to collapse
Sirpy,
Thanks for the info.
Given your diagnosis that the problem stems from errors on the file system, would it, in your opinion, be possible to repair the file system? I googled around and found a couple of threads that mention various flavors of fsck to be run in recovery mode using adb.
Does it makes sense, in your opinion? Have you tried it? If yes, which fsck did you use (plain fsck, fsck.exfat, e2fsck, or what else)? Or do you think it might be dangerous and the risk is not worth it?
About the rom from needrom - people have been complaining about GPS problems (the workaround seems to be to flash the latest InFocus firmware before flashing the needrom rom) and also about lack of phone memory after installing this firmware (did not see a stable workaround for this). If I go in this direction, I will probably try using the MIUI ROM (from Looserom and 4PDA.ru) instead.
I am currently using the original stock version (15CN_1_03A) and everything seems to be working reasonably well. My only problem is the complaint from SuperSU about the need to install a new su binary, however the current su seems to be working (more or less), so I will probably wait.
Beni.Falk said:
Sirpy,
Thanks for the info.
Given your diagnosis that the problem stems from errors on the file system, would it, in your opinion, be possible to repair the file system? I googled around and found a couple of threads that mention various flavors of fsck to be run in recovery mode using adb.
Does it makes sense, in your opinion? Have you tried it? If yes, which fsck did you use (plain fsck, fsck.exfat, e2fsck, or what else)? Or do you think it might be dangerous and the risk is not worth it?
About the rom from needrom - people have been complaining about GPS problems (the workaround seems to be to flash the latest InFocus firmware before flashing the needrom rom) and also about lack of phone memory after installing this firmware (did not see a stable workaround for this). If I go in this direction, I will probably try using the MIUI ROM (from Looserom and 4PDA.ru) instead.
I am currently using the original stock version (15CN_1_03A) and everything seems to be working reasonably well. My only problem is the complaint from SuperSU about the need to install a new su binary, however the current su seems to be working (more or less), so I will probably wait.
Click to expand...
Click to collapse
Well, yes you can try to run fsck. you should follow the method i've outlined in previous post on how to boot the device into ftm mode. then you should be able to run fsck on the system partition (/dev/block.../by-name/system). you will need to run fsck with ext4 option, though i'm not sure if fsck is included, so you might need to download the android version of it and copy it to your device in ftm mode to the root directory change its permissions to 755. (remount / partition as rw)
Firmware download link not working
Hi there..... this is my first message here , my first problem is that i am not able to download new firmware by Infocus page, it starts to download but cames to nothing. By the way I tried to update on wifi to a new 15CN_1_080 available by updating menu software on phone but after restarting i see Android System recovery <3e> 00cn_0_23A and i can choose : Reboot system now or Apply update from internal storage or Apply update from sdcard or Wipe data/factory reset or Wipe cache partition. At the end of the phone display in yellow text i read : finding update package…Opening update package…verifying update package…Installing update… Mounting partition Verifying current system…." /hidden / data / CDA /100CN / CDA / setting.xml " has unexpected contents. E: Error in / data / media / 0 / update.zip (status 7 ) installation aborted .
Until now the phone is multilanguage by default with version 15CN_1_03A . How to procede to go on ?
Therefore i am not sure phone is not already rooted, how can i verify it status and if it is already good to be flashed with a new custom rom ?
thanks a lot
Tinox said:
Hi there..... this is my first message here , my first problem is that i am not able to download new firmware by Infocus page, it starts to download but cames to nothing. By the way I tried to update on wifi to a new 15CN_1_080 available by updating menu software on phone but after restarting i see Android System recovery <3e> 00cn_0_23A and i can choose : Reboot system now or Apply update from internal storage or Apply update from sdcard or Wipe data/factory reset or Wipe cache partition. At the end of the phone display in yellow text i read : finding update package…Opening update package…verifying update package…Installing update… Mounting partition Verifying current system…." /hidden / data / CDA /100CN / CDA / setting.xml " has unexpected contents. E: Error in / data / media / 0 / update.zip (status 7 ) installation aborted .
Until now the phone is multilanguage by default with version 15CN_1_03A . How to procede to go on ?
Therefore i am not sure phone is not already rooted, how can i verify it status and if it is already good to be flashed with a new custom rom ?
thanks a lot
Click to expand...
Click to collapse
i think that your version 03A is the latest so no need for firmware upgrade.
you probably have some update.zip on your internal storage/sdcard which doesn't work and the system tries to install it on each reboot.
you need to delete it. if you can't access your phone storage via usb, you should follow the methods i've detailed in previous posts on how to boot into FTM mode and mount the different partitions, so you can access them in FTM mode.
already upgraded by seller ?
sirpy said:
i think that your version 03A is the latest so no need for firmware upgrade.
you probably have some update.zip on your internal storage/sdcard which doesn't work and the system tries to install it on each reboot.
you need to delete it. if you can't access your phone storage via usb, you should follow the methods i've detailed in previous posts on how to boot into FTM mode and mount the different partitions, so you can access them in FTM mode.
Click to expand...
Click to collapse
It is possibile seller already did root and installed ROM by needrom ? How could i check if it is already rooted ?
Tinox said:
It is possibile seller already did root and installed ROM by needrom ? How could i check if it is already rooted ?
Click to expand...
Click to collapse
download any terminal app, and type "su" in the terminal.
Looking for firmware link
Thanks Sirpy,
I check that in terminal and SU is not found so i am at the starting point for rooting phone but i am not able to download upgrade firmware 15CN_1_080 by Infocus page. Anyone able to give a working link or torrent link ? thanks
sirpy said:
download any terminal app, and type "su" in the terminal.
Click to expand...
Click to collapse
Tinox said:
Thanks Sirpy,
I check that in terminal and SU is not found so i am at the starting point for rooting phone but i am not able to download upgrade firmware 15CN_1_080 by Infocus page. Anyone able to give a working link or torrent link ? thanks
Click to expand...
Click to collapse
well as I said, from what you previously described you don't need the upgrade, you already have the latest.
Intro
This is a guide for people who want to make some modifications to config files, or other files, on System partition but do not want to root their phone or install custom recovery in order to keep OTAs and some apps, which don't play nicely with rooted phones, working. Examples of those config mods could be changing DPI or changing volume levels etc, which you would only do once and forget about it.
While root allows you to do those kinds of changes from within android, this methods would require a PC.
If you are familiar with temporary booting into a custom recovery, skip to step 5.
The usual i am not responsible for any of your actions / bricked phones disclaimer applies.
Prerequisites
- A working adb / fastboot environment. Please use Android SDK, if you installed your adb and fastboot using other tools, things might not work, so please just install SDK, install Google USB Driver from SDK manager, install Platform-Tools from SDK manager (should be installed by default) and then add your sdk platform-tools path to your PATH environment variable to have it available in cmd in every path.
- Unlocked bootloader
- TWRP image for you phone (.img) https://twrp.me/devices/huaweinexus6p.html
Follow the [GUIDE] Unlock/Root/Flash for Nexus 6P for that.
Instructions
Here is an example of modifying DPI. I prefer build.prop method of modifying DPI because using the adb wm density command usually caused some issues for me, but modifying via build.prop didn't.
1 - With you phone ON, connect it to the PC and make sure adb is working by running
Code:
adb devices
and making sure that device is listed
2 - Reboot into bootloader. and make sure fastboot is good to go too. Run commands one at a time:
Code:
adb reboot bootloader
fastboot devices
3 - Place your TWRP image file in some easily accessible folder, for the sake of this example i will use C:\Mods.
4 - Temporary boot into TWRP (we are not flashing it here at all).
Code:
fastboot boot c:\Mods\twrp-2.8.7.0-angler.img
Here is where things may not work. If you don't see your phone boot into TWRP then either your adb / fastboot environment not setup correctly (installed via a tool instead of SDK) or your img file is corrupt.
One thing that works for me when TWRP refuses to boot is to restart cmd and issue the command again this closes and reopens adb/fastboot daemon.
5 - Once TWRP is up on your phone it may display a warning saying "TWRP has detected an unmounted system partition". Swipe to allow modifications at the bottom. This screen may not come up at all.
6 - Go to Mount >>> Tick System >>> Make sure "Only Mount System Read Only" is unticked >>> Press Back button
7 - Back on your PC check if your device is listed
Code:
adb devices
8 - Pull the file you need to modify from system partition to your PC. Please note the direction of the slashes:
Code:
adb pull /system/build.prop c:/Mods
9 - Now you should see build.prop in your c:\Mods folder. Use Notepad++ or something like that to edit the file. Find the line with lcd_density= and change it's value to whatever you need and save the file.
10 - Push the file back to your phone:
Code:
adb push c:/Mods/build.prop /system
11 - Reboot
Code:
adb reboot
12 - Profit.
Hope this will help anyone who is looking to do some mods without installing custom recovery and rooting your phone.
Cheers.
Would this work for adding the tethering bypass line in the build prop?
Yes it will. What's the line again I was looking for it the other day and couldn't find it...
Works are per OP's original post, tested and boosted the headphone volume without a problem.
Headphone path is /system/etc/mixer_paths.xml
So as per OP's example to pull: adb pull /system/etc/mixer_paths.xml c:/Mods
push: adb push c:/Mods/mixer_paths.xml /system/etc
I'm using the OP's "Mods" folder to demonstrate the file path but this may vary on your PC.
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
skrowl said:
Can I use this to push SuperSU / etc to my device without having to permanently flash TWRP?
Click to expand...
Click to collapse
You can certainly push the files to system partition and they will retain there after reboot. So if you know which files have to be pushed for SuperSU then give that a go. It shouldn't break anything.
I haven't tried pushing SuperSU files to system partition before so I can't guarantee that OTAs will work after this. The only way to find out is to try it i guess...
Can you run nandroids?
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
NCguy said:
Can you run nandroids?
Click to expand...
Click to collapse
Im not sure what you mean?
rohit25 said:
not sure if it's allowed or not.. but with this can i push hosts file onto the phone as well for ad-blocking...?????
Click to expand...
Click to collapse
If it's on the system partition then I yes you can.
locolbd said:
I will say thanks now and try it later. These are the type of tweaks I would like to make to my phone. Do you know if changing the DPI cause any stock applications to show up broken like they do on the Samsung phones?
Click to expand...
Click to collapse
I've never had a problem with changing DPI using this method on a nexus phone if that helps.
denk said:
Im not sure what you mean?
Click to expand...
Click to collapse
Can you run nandroids backups from TWRP by just booting into it?
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
I got this too when I flashed MOAB via adb sideload. I'm just wondering if the same warning appears with the adb push method. Also, the file's permissions don't need to be set after adb push?
My main concern is if Android Pay still works with the red triangle warning. Anyone?
FYI Flashing back to stock is no issue for me.
NCguy said:
Can you run nandroids backups from TWRP by just booting into it?
Click to expand...
Click to collapse
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
locolbd said:
okay so after i did this i get the following during boot up
"Your device is corrupt. It can't be trusted and may not work properly". Does this mean i will not get Securty Updates any more? I saw i had an update before i performed this however, now i do not see that update notifications any more.
Click to expand...
Click to collapse
Thanks for trying it out! Sometimes OTA notifications take a little while to come up after reboot. But based on the warning Im afraid that they might be disabled now. It looks like it runs some sort of a check on the system partition to verify its legitimacy. So modifying files would be fine on it using this method but looks like adding them won't work.
TWRP just released their recovery with decryption support so you can just follow the standard procedure or just temporary booting into TWRP and rooting from there which works as well.
denk said:
I think if you get the latest TWRP which supports decryption of data partition (where all your stuff is) you should be able to back it up.
Edit: backup works on nexus 5 with temporary TWRP boot. Sorry I'm still waiting for my 6p to arrive.
Click to expand...
Click to collapse
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
NCguy said:
On your Nexus5 I assume you are also unrooted? And have you tried a Nandroid restore, booted TWRP, no root?
Click to expand...
Click to collapse
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
denk said:
Just ran a restore to test it for you. Works fine as well.
My N5 is unrooted.
.
Click to expand...
Click to collapse
Thanks a lot for that. I didn't unlock the bootloader. Ugh. Time to start over. To me nandroids alone make it worth the effort.
[GUIDE/TUTORIAL/HOWTO] Sony Xperia Tablet Z LTE or Wifi Any version to Android 9 Pie
[GUIDE/TUTORIAL/HOWTO] Sony Xperia Tablet Z SGP321 LTE/4G (pollux) or Wifi (pollux-windy) Any version to Android 9 Pie / LineageOS 16
This detailed step-by-step guide helps you transform your Sony Xperia Tablet Z to a powerful one with Android 9 Pie.
To make sure you are with a Xperia Tablet Z 4G / Pollux / SGP321 (SGP351 for USA, SO-03E for Japan) :
On the tablet, go to Menu -> Settings -> About tablet. Check that the "model number" is correct : SGP321 (Europe).
Same for the Wifi/Pollux_windy version.
### You must be logged as a Microsoft Windows administrator to run console commands below.
### When you lose control of your Xperia tablet Z, hold Power + Volume+ until tab restarts.
CHANGELOG
v14. If you want Magisk, use v25.2+
v13. Drop Magisk (if you want it, use v24.1), update pack
v12. Permanent TWRP recovery, overclock with Smartpack kernel manager
v11. Move to Android 9, replace addonsu with Magisk root, revert to 2016 adb + fastboot (fastboot flash fails with latest versions), fix glitches in tutorial
v10. Updated pack for TWRP 3.4.0-0 + LOS download links
v9. Updated pack for TWRP 3.3.1-0
v8. Moved to Official LineageOS 15.1 available to bring you Android 8.1 Oreo
v7.2. Refresh OpenGapps download link
v7.1. Refresh pack v2 (TWRP 3.2.3-0) and tutorial
v7. recovery TWRP 3.2.2-0 and new FOTAKernel installation
v6. Google Play certification, recovery TWRP 3.2.1-0, new pack for easier install
v5.5. Overclock
v5. Updated tutorial to latest ROMs and utils
v4. Upgraded tutorial
v3. Moved to Android 7.1
v2. Tutorial updated for permanent recovery, Black kernel, pack has no more missing fastboot files, drivers included, F2FS optimizations
v1. Initial release
1) DOWNLOAD FILES
- djibe Xperia Tablet Z pack (~ 48 MB) : http://bit.ly/djibe-xperia-tabletz-v2
(contains Xperia USB drivers + adb + fastboot + recovery TWRP 3.4.0-0 for both LTE/4G/Pollux version and Wifi/Pollux_windy + Smartpack Kernel Manager)
+ ROM Unofficial LineageOS 16: https://forum.xda-developers.com/xperia-tablet-z/orig-development/rom-lineageos-16-0-t3924942
Download latest build for Tablet Z LTE/Pollux: https://anonfiles.com/h7n8z0Rdx3/lineage-16.0-20220131-UNOFFICIAL-pollux_zip
Download latest build for Tablet Z Wifi-only/Windy: https://anonfiles.com/Ddncz2Rfx2/lineage-16.0-20220131-UNOFFICIAL-pollux_windy_zip
WARNING. Download correct version, Pollux for your 4G/LTE model, Pollux_windy for your Wifi-only model
ROM backups: https://androidfilehost.com/?w=files&flid=140468&sort_by=date&sort_dir=DESC
+ BitGApps ARM 9: https://github.com/BiTGApps/BiTGApps-Release/releases
or OpenGApps ARM 9 Nano: https://opengapps.org/?arch=arm&api=9.0&variant=nano
+ a microSD card. Copy ROM, OpenGApps, +/- Magisk +/- SmartpackKernel.apk on microSD card and insert it in tablet.
+ Charge tablet to 100%.
NB. Use a USB2 port to connect tablet to PC.
2) INSTALL DRIVERS
Commands below are for Windows 10 installation of unsigned drivers.
### For other Windows versions, Google "windows X install unsigned driver".
On the keyboard of PC, use "Windows key + R" combo.
In the command prompt that opens, type:
Code:
shutdown -r -t 0 -o
This opens a Windows menu:
Go to Troubleshooting > Advanced Options > Settings > Restart
Upon restart, press on keyboard : key 7 - Disables drivers signature verification
After boot,
Start Flashtool Xperia Driver Pack 1.8,
check the Fastboot drivers, ADB and Xperia Z tablet drivers, start the installation and confirm the
forcing the driver installation. It ends by saying that everything was installed.
Restart Windows.
2bis, optionnal, FOR WARRANTY PURPOSE) Backup bootloader
Cannot help you precisely, didn't know about it at the time.
- Root. Follow Bin4ry root : http://forum.xda-developers.com/showthread.php?t=1886460
Download : http://forum.xda-developers.com/showthread.php?t=1886460
- Then Backup TA. https://github.com/DevShaft/Backup-TA
Unzip it in C:\
Make sure partition is saved.
3) IMEI NUMBER
On tablet, go to Menu > Settings > About tablet > Status > Information on the IMEI code
Note the IMEI. Store it.
4) GENERATE BOOTLOADER UNLOCK CODE
From your PC, go to : https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/
At the bottom of the page, in Select your device : Select Xperia Tablet Z (or Tablet Z Wifi).
Enter your IMEI and check both checkboxes.
Copy the unlock code on next page.
5) CONNECT TAB IN FASTBOOT MODE
Tablet powered off, hold "Volume up" while you plug the tablet in USB.
The blue light appears next to microSD cable, the drivers install in Windows.
6) UNLOCK BOOTLOADER
In Windows, copy the path to the "flash" folder you unziped earlier.
Open a Windows command prompt : Start menu > Command prompt > Start as administrator
Then type
Code:
cd /d thePathToFlashFolder
(ex: E:\root\Sony Xperia Tablet Z SGP321 Pollux\djibe Xperia pollux Pack\flash)
Type:
Code:
fastboot -i 0x0fce getvar Version
If a line is returned, drivers are correctly installed.
### Use fastboot and adb from my pack
Paste the following line (written at the end of the page issued by Sony) :
Code:
fastboot oem unlock 0xYOURUNLOCKKEY
confirm with Enter. After 2 seconds, it is displayed OKAY.
Bootloader is unlocked !
7) FLASH TWRP RECOVERY 3.4
Still in fastboot, type in console :
Code:
fastboot flash boot twrp-3.4.0-0-pollux.img
(or twrp-3.4.0-0-pollux_windy for Wifi model). Confirm with Enter.
Wait, then once the confirmed success,
type :
Code:
fastboot reboot
(confirm with Enter).
AND while it restarts, repeatedly click Volume+ AND Volume- buttons to access the recovery (can take a while).
8) BACKUP CURRENT ROM
You are now in TWRP recovery, swype to unlock changes.
Go to Backup, select all partitions.
In Storage, select microSD Card then OK.
Then swype to start backup (Well, hums, it failed on my tablet ;-) ).
Click the TWRP icon to return to home.
Go Wipe > Wipe Advanced > Select Dalvik, System, Cache, Data and swipe to confirm flash.
### If errors are displayed in red "failed to mount data (invalid argument)" appear (as I had),
### go to Wipe > Data Format, type yes and click OK.
9) FORMAT TO F2FS
INFO. F2FS is the fastest filesystem for read and write partitions on flash memories. Compared to EXT4, gain is from 15 to 280 %.
No need to format the /System partition because it is Read only and EXT4 is still faster.
Still in Advanced Wipe menu,
select the /Cache partition and tap Repair or Change File System > Change File System and select F2FS.
Confirm with a Swipe to Change.
Do it again for the /Data partition.
### Any partition problem ? Bootloop ? Format every partition back to EXT4, wipe all partitions and reflash Zips.
Go to Reboot > Recovery.
10) INSTALL ROM, GAPPS +/- ADDONSU ROOT
Back to TWRP home menu.
Go to Install > select lineage*.zip.
### If no file is visible, click Storage > select microSD Card.
### If you get an error and flash fails, go to Reboot > Recovery and wait for TWRP to reboot.
Add more zip > OpenGapps*.zip file,
(Optional) Add more zip > addonsu*.zip file.
Swype to confirm flash.
Wait while Install Zips are flashed.
At the end, select Wipe Dalvik and cache and then Reboot system.
Tab will reboot soon after first reboot.
Wait during both boots.
11) ROOT
Go to Settings > About tablet > Tap 7 times on Build number item.
Go to Settings > System > Advanced > Developer options.
Root > Applications and ADB.
12) PERMANENT TWRP RECOVERY AND TWEAKS
To keep TWRP recovery permanently, you need to flash it to a smart location: the FOTAkernel partition.
Now Settings > System > Advanced > Developer options.
Advanced restart switched ON (Hold power > Restart > Restart to recovery to access TWRP easily later)
Root access > ADB only
Android debugging switched ON
Windows animation scale yo Animation scale .5x
Same for Transition animation scale and Animator duration scale to improve reactivity
Connect tablet to PC.
Re-open a Windows command on my /flash folder.
Enter commands in order:
Code:
adb devices
On tab, grant ADB access
Code:
adb root
Code:
adb wait-for-device
Code:
adb push twrp-3.4.0-0-pollux.img /tmp/twrp.img
Command returns: 2600 KB/s (12103680 bytes in 4.544s)
and finally
Code:
adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
It will output
> 23640+0 records in
> 23640+0 records out
> 12103680 bytes transferred in 2.864 secs (4226145 bytes/sec)
You are done with flashing ! Congratulations.
13) OVERCLOCK (optional)
Open built-in Files app.
Open microSD folder.
Install Smartpack Kernel Manager app from my pack.
Launch app and grant root access.
Go to CPU menu > Apply on boot, CPU Maximum Frequency 1728 MHz
CPU min: 192MHz
Governor: ondemandplus
GPU: 487MHz
14) Others
For faster GPS fix, use GPS Status and Toolbox and download A-GPS data.
Your tablet is a rocket, enjoy ;-)
Thanks: LineageOS team, TWRP team, OpenGApps team, Flashtool Xperia Driver pack team, @CaHbKaUp, @CyberWalkMaN, @AdrianDC, Chippa_a, @Rootk1t
You forgot to mention about Backuping TA before bootloader unlock.
Also operation under numbers 4,5,7,8 can be done via Flashtool practically in one click, so it's much faster.
Also with frequent messages "can't post outside links" instruction is "half-done".
Your message
Rootk1t said:
You forgot to mention about Backuping TA before bootloader unlock.
Also operation under numbers 4,5,7,8 can be done via Flashtool practically in one click, so it's much faster.
Also with frequent messages "can't post outside links" instruction is "half-done".
Click to expand...
Click to collapse
XDA blocks my external links. What can i do about that ?
About flashtool, it is always more instructive to understand all the process rather than a tool you don't know the limits.
I'll look at TA partition backup, thx for your advice.
But this guide is made to help noobs like me. Everyone isn't good as you. Title is clearly written for noobs.
Direct links are finally available
Hi
Which version of stock are you using? Thanks!
Latest OTA from Sony. Looks like a 4.x.x with Sony Touch Interface
juanchinho said:
Hi
Which version of stock are you using? Thanks!
Click to expand...
Click to collapse
Latest OTA from Sony. Looks like a 4.x.x with Sony Touch Interface
Thanks a lot for this guide!
After installing CM13 on my Xperia Tablet the IR Blaster does not work, there is no signal coming out of it at all. What about you other guys here. Does IR Blaster work or not with you?
nicky-xda said:
Does IR Blaster work or not with you?
Click to expand...
Click to collapse
no.
IR Blaster not working: Good to know i'm not the only one with that issue
Who knows if this is considered as a bug and will some time in the near future be worked on and hopefully fixed?
Enhanced tutorial,
hope you'll like it !
Tutorial in 4th version available
YOU are a legend, you and a note stating that this device don't have a separate recovery so I had to use "fastboot flash boot ..." instead <3
So long since I last installed a custom rom that I forgot how and lost my how-to
PS: I still miss the IR-blaster since I had the stock ROM when the device was new :cyclops:
ettkatthej said:
YOU are a legend, you and a note stating that this device don't have a separate recovery so I had to use "fastboot flash boot ..." instead <3
So long since I last installed a custom rom that I forgot how and lost my how-to
PS: I still miss the IR-blaster since I had the stock ROM when the device was new :cyclops:
Click to expand...
Click to collapse
Hi,
sorry, i'm not sure I fully understand your message.
Do you need some help ? Is Something not clear in tuto ?
See you
djibe89 said:
Hi,
sorry, i'm not sure I fully understand your message.
Do you need some help ? Is Something not clear in tuto ?
See you
Click to expand...
Click to collapse
Guess I got a bit overwhelmed by it finaly working, it was just a long and confused thank you..:angel:
Jumped in at stage 7.
ettkatthej said:
Guess I got a bit overwhelmed by it finaly working, it was just a long and confused thank you..:angel:
Jumped in at stage 7.
Click to expand...
Click to collapse
Is there Something not clear in my tuto I could enhence ??
Not success in rooting sgp321 android 4.4.4 292 version, using the bin4try.，can somebody helps?
dickzoe said:
Not success in rooting sgp321 android 4.4.4 292 version, using the bin4try.，can somebody helps?
Click to expand...
Click to collapse
Use Easy Root Tool, KingRoot or Vroot.
thank you for your advice, I just rooted via kingroot. however, during unlocking bootloader process, after insert the unlock code via fastboot, it shown: failed (remote :command not allowed. ) Any clue?
dickzoe said:
thank you for your advice, I just rooted via kingroot. however, during unlocking bootloader process, after insert the unlock code via fastboot, it shown: failed (remote :command not allowed. ) Any clue?
Click to expand...
Click to collapse
service menu shown: bootloader unlock allowed: no
Any helps?
Greetings!
I'd like to present a TWRP recovery for the single-sim Xperia X. This release works on Xperia X F5121 and F5122
DISCLAIMER:
I'm not responsible for any damage done to your device. You have been warned.
REQUIREMENTS
Unlocked bootloader
Working ADB and Fastboot (You can get the latest version through Android Studio or by visiting this site)
FEATURES
MTP support
ADB Sideload
Backups and restores almost every partition
Full SELinux support
Working encryption. You can access /data within recovery
NEEDS TESTING
USB-OTG
DOWNLOADS
INSTALLATION
Unlock the bootloader
Download the file
Put the following code in CMD/Terminal:
Code:
fastboot flash recovery twrp-3.1.1-suzu-*.img
//Replace * with the version you want to flash
Unplug the cable
Press Volume Down + Power to activate the recovery. When installed properly, the device should vibrate funnily, purple LED should appear and after a couple of seconds you should see the TWRP screen.
Enjoy!
BUILD
You need to sync the OmniROM and vendor blobs from DonkeyCoyote. You can find my sources on GitHub.
android_device_sony_loire_common
https://github.com/omnirom/android_bootable_recovery/commits/android-7.1
Thanks:
@grayleshy - for initial TWRP
@AndroPlus for some of his flags
OmniROM team for sources
If you find my work useful, consider buying me a cup of coffee
[TWRP] TWRP 3.1.0 for Xperia X
Old OP below:
Team Win Recovery Project 3.1.0
REQUIREMENT:
- Unlocked bootloader
FEATURES:
- MTP support
- USB OTG storage support
- Covers most partitions for nandroid backups
- ADB root
- Full SELinux support
- Support for partition decryption
Download: Dropbox
Installation via the bootloader (Platform-tools (adb & fastboot))
Code:
fastboot flash recovery recovery.img
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
Special thanks kistigun for testing recovery on the device.
Changelog: twrp.me
TWRP was going on OmniRom 7.1 sources and XperiaDeveloper.
SOURCEs: Suzu; loire; Common.
Nice work! Finally no more decryption problems on the X!
Working well, thanks!
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)? When I've tried the phone boots normally instead.
baddesthad said:
One question ; is it possible to reboot the recovery via twrp reboot menu (or use an app like flashfire /flashify)?
Click to expand...
Click to collapse
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed. If I don't find how to fix that button will be removed.
samavar89 said:
Unfortunately the reboot Recovery does not work from the specifics of the section, but in the future maybe will be fixed.
Click to expand...
Click to collapse
Good to know, thanks for clarifying
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Oel said:
Is there a difference to the 3.1.0 TWRP recovery from the Poison thread?
Click to expand...
Click to collapse
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
Ah...
Ok, Thanks!
kistigun said:
Yes, this TWRP version has decryption problem fixed. So you can acces internal memory(and make a full backup) without the need of doing a full whipe & format /DATA
Click to expand...
Click to collapse
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
robby.pgn said:
No, don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
Click to expand...
Click to collapse
This problem is strange, please provide a log recovery.
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Kianush said:
I flashed this on my xperia x dual on nougat 7.0
I can go to recovery but when i try to turn on the phone normally it says "The phone is corrupt and cant be trusted bluh bluh..."
it says press power button to continue but when i press it screen turns off and nothings happens
what should i do?!
Click to expand...
Click to collapse
In Your kernel there is support for DM-Verity and Sony RIC?
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
robby.pgn said:
No,
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup...
someone knows a recovery that finally works?
Click to expand...
Click to collapse
Kianush said:
it's stock kernel man, I unlocked bootloader and flashed stock nougat for xperia X dual sim
I just wanna root it, if there is any other way pls help me out
-----
btw after this problem i used flashtool to flash system and kernel from stock rom to be able to use my phone again
Click to expand...
Click to collapse
use this tool/guide to make a rooted kernel(and edit DM-Verity and Sony RIC): https://forum.xda-developers.com/xp...oot-automatic-repack-stock-kernel-dm-t3301605
grayleshy said:
Team Win Recovery Project 3.1.0
Click to expand...
Click to collapse
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Thanks
robby.pgn said:
don't ask password but I can't access my internal memory.
I install zip file from my external sd card only.....no full backup.
Click to expand...
Click to collapse
This problem is almost resolved, just need to test, but I don't have time to compile recovery. In the test version recovery without decryption, problem solved.
juliompinheiro said:
I've installed and tried this TWRP in my Xperia X with MM. Very nice that it can access the data partition! I did not try to install any zip yet.
Some problems I've seen:
dmesg.log: no output
recovery.log: https://pastebin.com/EwbtuC9q
What is interesting in the output:
Code:
I:cmd: /sbin/exfat-fuse -o big_writes,max_read=131072,max_write=131072 /dev/block/mmcblk1p1 /external_sd
CANNOT LINK EXECUTABLE "sh": cannot locate symbol "__fwrite_chk" referenced by "/sbin/busybox"...
I:exfat-fuse failed to mount with result '', trying vfat
I:Unable to mount '/external_sd'
I:Actual block device: '/dev/block/mmcblk1p1', current file system: 'vfat'
Looks like something is not right with the busybox in the image. Maybe it is that what is causing the external sdcard (in my case in exfat filesystem) not being mounted?
Click to expand...
Click to collapse
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
grayleshy said:
Running TWRP: turn the phone off, wait 5 seconds, then pinch at the same time the power key and the volume down key until the device vibrates, release the keys. Recovery starts within 5-10 seconds.
Click to expand...
Click to collapse
For whatever reason I'm not able to boot into TWRP like I should be. I've used the poison version of TWRP before so I know what to do, and yet the phone will just boot normally despite holding volume down and power when off.
I know that TWRP is installed though as I am able to boot to it if I first boot to the bootloader using a USB cable but that is very cumbersome to do though.
grayleshy said:
This issue failed to reproduce, and yet there is no solution. You the problem is not in Busybox, and something else.
Click to expand...
Click to collapse
Clearly for the image available at your dropbox there are some libraries dependency errors, not only for the 'busybox', but also for other binaries that are in /sbin.
I do not know why this issue is only happening on my device since you said you can't reproduce this error. If there is anything I can do to help solve this strange behavior, count on me. I am an advanced linux user, but not too familiar with android specifics.
On latest 333 ROM for UK so that fingerprint scanner works on my Xperia X F5121.
I also modified by kernel/boot so that TWRP doesn't brick (actually boot loop) the device like it did the first time. After using these awesome instructions flashing TWRP recovery from here didn't kill the device any longer: https://forum.xda-developers.com/crossdevice-dev/sony/root-root-stock-firmware-modern-sony-t3558904
I was able to take an early nandroid backup before a bunch of Titanium restores, etc. Now I get stuck at "Backing up data" step and it literally doesn't move to the next file. Attaching an image of where I get stuck. FYI, I do use password encryption on the backup and I did disable MD5 creation... still just stuck.
Next tests are to:
see if the stall is on the same exact file number
try no encryption
do a check disk (fsck) type of repair just in case I have corruption --- on my brand new device
Any suggestions greatly appreciated!
UPDATED:
I only back up Boot, System & Data (the default)
On second attempt it stopped at file 18869 of 22065 --- so it does jump and not consistently stop at a certain file.
Dear all,
I finally got TWRP flashed onto my Le Max..
With TWRP, I backupped my phone and copied it to my PC.
I downloaded several roms to my Le Max, wich all went ok...
In the TWRP recovery menu, I choose Wipe All ( Dalvik, system, Cache, Data, Internal )...
But now, you guess, there is no OS on the phone...
When I enter TWRP recovey menu, advanced, sideload, I tried to copy a rom to the phone via " ADB SIDELOAD MAX.ZIP" but I get the message on the pc
loading : max.zip
* cannot read max.zip
Who can help? At the moment I dont have a USB stick....
if max.zip is your backup then do restore.
Max.zip is my rename of 23S Chinese...
My backup is " 2017-05-24--12-39-24_FIXNAOP5801607292S_release-keys"
It is more, how to get the files on my phone without a OTG USB stick...
Which commands and so...
ADB SIDELOAD xxxx.img works better, then xxxx.zip.
But I cant find any rom in .img format...
Bobenjanneke said:
Dear all,
I finally got TWRP flashed onto my Le Max..
With TWRP, I backupped my phone and copied it to my PC.
I downloaded several roms to my Le Max, wich all went ok...
In the TWRP recovery menu, I choose Wipe All ( Dalvik, system, Cache, Data, Internal )...
But now, you guess, there is no OS on the phone...
When I enter TWRP recovey menu, advanced, sideload, I tried to copy a rom to the phone via " ADB SIDELOAD MAX.ZIP" but I get the message on the pc
loading : max.zip
* cannot read max.zip
Who can help? At the moment I dont have a USB stick....
Click to expand...
Click to collapse
If you flash system off course you get No OS, because you deleted system partition.
And do not wipe Internal, phone has no sd card. When you flash internal you delete everything on the media partition which includes backup, music, photos, and the ROMs yo downloaded. When you flash a rom you only need to wipe cache, dalvik media and data. (System when u move from stock to custom, if you flash system and then try to flash another stock rom you will get error 7)
Now, I don't know what "max.zip" is. Try with other rom file or download cuoco92 fastboot version, then put your phone on fastboot mode, execute cuoco installation on PC and it will automatically flash the rom.
Edit: Install this driver https://drive.google.com/open?id=0By3XfnDvUFlAYXBZbFNhYTdCcjQ and then try to connect your phone to pc when in TWRP. It lets connect in MTP mode and it works for me
Enviado desde mi LEX829 mediante Tapatalk
max.zip = 23s Chinese ROM
While booted into TWRP. Connect your phone via the charging cable to your computer and copy rom + GApps to the internal storage of your phone.
Now install in TWRP.
Everybody allready thank you!
I don't know HOW to copy the files to my phone...
It is in recovery TWRP mode not recognized in Explorer, and the ADB command's I have found on Google, like ADB SIDELOAD and ADB PUSH don't work...
Does someone know if the USB cable witch came with the package, is OTG ready?
Bobenjanneke said:
Everybody allready thank you!
I don't know HOW to copy the files to my phone...
It is in recovery TWRP mode not recognized in Explorer, and the ADB command's I have found on Google, like ADB SIDELOAD and ADB PUSH don't work...
Does someone know if the USB cable witch came with the package, is OTG ready?
Click to expand...
Click to collapse
Copy the ROM to the ADB & Fastboot file path, then connect your Le Max 2 with your pc.
Now go in TWRP to Advanced and click on "ADB Sideload", type in ADB "adb sideload nameofthefile.zip", this will flash your ROM.
(It will not work with EUI but with every other ROM)
Or you push it with ADB push: "adb push /filepath/nameofthefile.zip/sdcard" after this click on Install, and install ist. ? Hope this helps your, and sorry for my bad english.
jufece said:
If you flash system off course you get No OS, because you deleted system partition.
And do not wipe Internal, phone has no sd card. When you flash internal you delete everything on the media partition which includes backup, music, photos, and the ROMs yo downloaded. When you flash a rom you only need to wipe cache, dalvik media and data. (System when u move from stock to custom, if you flash system and then try to flash another stock rom you will get error 7)
Now, I don't know what "max.zip" is. Try with other rom file or download cuoco92 fastboot version, then put your phone on fastboot mode, execute cuoco installation on PC and it will automatically flash the rom.
Edit: Install this driver https://drive.google.com/open?id=0By3XfnDvUFlAYXBZbFNhYTdCcjQ and then try to connect your phone to pc when in TWRP. It lets connect in MTP mode and it works for me
Enviado desde mi LEX829 mediante Tapatalk
Click to expand...
Click to collapse
What's the way to work when I want all of my 64gb ? ( If possible )
I read some about X829 has encrypted partition?
So when ( when all is fixed ) i am in the phone filemanager, I see total free space = 64gb -/- ROM = 60GB
Bobenjanneke said:
What's the way to work when I want all of my 64gb ? ( If possible )
I read some about X829 has encrypted partition?
So when ( when all is fixed ) i am in the phone filemanager, I see total free space = 64gb -/- ROM = 60GB
Click to expand...
Click to collapse
It's imposible to get 64 gb free...
And as far as I know the encryption problem is an issue fixed from 19S and above
Enviado desde mi LEX829 mediante Tapatalk
jufece said:
....
Try with other rom file or download cuoco92 fastboot version, then put your phone on fastboot mode, execute cuoco installation on PC and it will automatically flash the rom.
Click to expand...
Click to collapse
THE PHONE IS
****************************** ALIVE ******************************
THANK YOU very much!!!
( BTW, thank you all folks !!!! )
VC-34 said:
Copy the ROM to the ADB & Fastboot file path, then connect your Le Max 2 with your pc.
Now go in TWRP to Advanced and click on "ADB Sideload", type in ADB "adb sideload nameofthefile.zip", this will flash your ROM.
(It will not work with EUI but with every other ROM)
Or you push it with ADB push: "adb push /filepath/nameofthefile.zip/sdcard" after this click on Install, and install ist. ? Hope this helps your, and sorry for my bad english.
Click to expand...
Click to collapse
just wanted to say that I sideloaded Aurel EUI Rom.
but not recommended as it took me 2 tries.
What is best ROM for the Le Max 2?
I had vendor rom, which I turned on in the Chinese.
Now I have the Cuoco rom with some apps...
And "the best" rom is for everybody different, but I am curious at the thougths of other people about it...
I continiou that in another forum
( https://forum.xda-developers.com/le-max-2/development/best-stock-custom-rom-le-max-2-x829-t3612563 )
cy-rock said:
just wanted to say that I sideloaded Aurel EUI Rom.
but not recommended as it took me 2 tries.
Click to expand...
Click to collapse
It's because aurel EUI-ROM uses Aroma Installer.
jufece said:
It's imposible to get 64 gb free...
And as far as I know the encryption problem is an issue fixed from 19S and above
Enviado desde mi LEX829 mediante Tapatalk
Click to expand...
Click to collapse
What if I format my internal storage, and then repair the internal storage with cuoco92 fastboot version?
Whill that work?
Thank you already guys!
Bobenjanneke said:
What if I format my internal storage, and then repair the internal storage with cuoco92 fastboot version?
Whill that work?
Thank you already guys!
Click to expand...
Click to collapse
It doesn't matter because when u flash a rom with fastboot method it wipes everything.
Enviado desde mi LEX829 mediante Tapatalk