Database Develop

Xposed Installer destroyed my Toshiba AT300SE rooted

I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.

Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk

kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
i'll try this

kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Seems that disabler zip did not work.
Any other brilliant ideas................

Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk

kingvortex said:
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.

Rooks said:
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Click to expand...
Click to collapse
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.

Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Only brilliant idea here was flashing something before backing up your rom.
Sent from my Nexus 5 using Tapatalk

GermainZ said:
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Click to expand...
Click to collapse
I did not mean to be rude or ANY disrespect.
So guys, PLEASE point me to right direction so that i can bring back my device.

rovo89 said:
In case you get into a boot loop:
First, try using the safemode by pressing any hardware key repeatedly. You can find a short explanation how it works here.
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

rovo89 said:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Where can i find disabler zip file?
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.

Rooks said:
Where can i find disabler zip file?
Click to expand...
Click to collapse
From the linked post:
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
Rooks said:
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse

GermainZ said:
From the linked post:
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
Click to expand...
Click to collapse
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.

Rooks said:
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Click to expand...
Click to collapse
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.

Rooks said:
Yes i've tried three different files, all failed to install.
Click to expand...
Click to collapse
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?

Rooks said:
Where can i find disabler zip file?
I downloaded some file from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.

GermainZ said:
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Click to expand...
Click to collapse
I'll try to get logcat for this issue.
rovo89 said:
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Click to expand...
Click to collapse
Yes, it's the stock recovery and i've tried several times with hardware keys but safe mode did not work in my scenario.
esgie said:
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
Click to expand...
Click to collapse
I've tried three different file with different sizes (143kb, 121kb and 145kb), all these files include the same script ("updater-script" file) by Tungswenty.
ui_print("");
ui_print("");
ui_print("------------------------");
ui_print(" Xposed disabler tool ");
ui_print(" by Tungswenty ");
ui_print("------------------------");
ui_print("");
ui_print("Mounting system partition");
ifelse(!is_mounted("/system"),
run_program("/sbin/busybox", "mount", "/system"));
assert(is_mounted("/system"));
ifelse(run_program("/system/bin/sh", "-c", "test -f /system/bin/app_process.orig") == 0,
(
ui_print("Restoring the original app_process file");
assert(run_program("/sbin/busybox", "cp", "-a", "/system/bin/app_process.orig", "/system/bin/app_process"));
set_perm(0, 2000, 0755, "/system/bin/app_process");
ui_print("Restore complete.");
ui_print("You should now be able to boot normally and remove all traces of Xposed from within the Installer app.");
),
(
ui_print("No backup found for app_process, nothing to be performed!");
));
ui_print("");
ui_print("Done.");
ui_print("");
Click to expand...
Click to collapse

Rooks said:
Yes, it's the stock recovery
Click to expand...
Click to collapse
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).

rovo89 said:
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
Click to expand...
Click to collapse
I've stock rom and recovery, there is no custom rom or recovery available for my device (Toshiba Excite 10 SE aka AT300SE).
So with stock rom and recovery it won't accept any zips and i can't format system partition with stock recovery. And about adb, i don't know where to start. In recovery there is an option to push a file through adb but when i connect my device while this option, my pc does not recognize the device, neither i can update the adb drivers.

Rooks said:
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Click to expand...
Click to collapse
HOW YOU ROOT...???!!!
PLEASE TELL ME
I CANT FIND IN WEB....
Give me a links if you can ....
THANKS

[Q&A] Rom Lollipop AOSP 5.1.0 (Released 2015-03-13) port for ZR testing

Q&A for Rom Lollipop AOSP 5.1.0 (Released 2015-03-13) port for ZR testing
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Rom Lollipop AOSP 5.1.0 (Released 2015-03-13) port for ZR testing. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Thanks for your post
tonytee said:
@uncomment : Did u test it? How about battery and free ram?
Click to expand...
Click to collapse
I just Flash the rom , its smooth , free ram is 1.3 GB thanks a lots
but there is no battery percentage , cant change drawable shortcuts , i need clipboard too could u help me to bring this item ?

Xperia zr said:
I just Flash the rom , its smooth , free ram is 1.3 GB thanks a lots
but there is no battery percentage , cant change drawable shortcuts , i need clipboard too could u help me to bring this item ?
Click to expand...
Click to collapse
Its AOSP, cause that no much options. Waiting xposed for 5.1 release
Sent from my Xperia ZR using XDA Free mobile app

Hi Dear
uncomment said:
Its AOSP, cause that no much options. Waiting xposed for 5.1 release
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
I have another problem ,after i turn airplane mode on , i have to reboot my phone to detect sim card, how can i fix it ?
sorry for my bad english

Xperia zr said:
I have another problem ,after i turn airplane mode on , i have to reboot my phone to detect sim card, how can i fix it ?
sorry for my bad english
Click to expand...
Click to collapse
Its a known bug from Z noticed here:
http://forum.xda-developers.com/showpost.php?p=59458446&postcount=17
Sent from my Xperia ZR using XDA Free mobile app

anyone know when we will have a update to lol 5.0 original ?

Cant Flash Rom
Omni Rom 5.1 - Cant Flash zip through TWRP.
The error i get is failed Sym link. Some Simlinks failed.??

Shray said:
Omni Rom 5.1 - Cant Flash zip through TWRP.
The error i get is failed Sym link. Some Simlinks failed.??
Click to expand...
Click to collapse
It say symlinks fail or it say script updater fail ?
Try install my twrp from RR rom v5.4.0 CM5.1 base
Let me check about 2days cause im not near my copmputer
Sent from my Xperia ZR using XDA Free mobile app

uncomment said:
It say symlinks fail or it say script updater fail ?
Try install my twrp from RR rom v5.4.0 CM5.1 base
Let me check about 2days cause im not near my copmputer
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
Okay, so this is what it says.
Symlink: Some symlinks failed
E: Error executing updater binary in zip.
Used TWRP from RR rom v5.4.0 and got the same error.
I also tried flashing with old Twrp. It didn't work.

Fixed for Rom zip
Shray said:
Okay, so this is what it says.
Symlink: Some symlinks failed
E: Error executing updater binary in zip.
Used TWRP from RR rom v5.4.0 and got the same error.
I also tried flashing with old Twrp. It didn't work.
Click to expand...
Click to collapse
I checked: my zip upload is old script-updater
TO fixed:
- download script-updater below and rename it by delete .zip
- Use 7zip on your PC to open rom zip and follow path:
omni-5.1-20150330-dogo-EXPERIMENTAL.zip\META-INF\com\google\android\
- Replace updater-script in zip by: Drag new updater-script from Explorer to zip
- Done!
Sorry for my fault! :angel:

uncomment said:
I checked: my zip upload is old script-updater
TO fixed:
- download script-updater below and rename it by delete .zip
- Use 7zip on your PC to open rom zip and follow path:
omni-5.1-20150330-dogo-EXPERIMENTAL.zip\META-INF\com\google\android\
- Replace updater-script in zip by: Drag new updater-script from Explorer to zip
- Done!
Sorry for my fault! :angel:
Click to expand...
Click to collapse
Its all okay, mate. Its how things progress.
Also, thank you for providing the steps for the fix.
I tried them just as you mentioned (exactly word to word) and this is what i got.
Formatting /system
Mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: device or resource busy
Symlinking
Symlink: some symlinks failed
E: Error executing updater binary in zip
Tried with some variations and still got the same message.

Shray said:
Its all okay, mate. Its how things progress.
Also, thank you for providing the steps for the fix.
I tried them just as you mentioned (exactly word to word) and this is what i got.
Formatting /system
Mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: device or resource busy
Symlinking
Symlink: some symlinks failed
E: Error executing updater binary in zip
Tried with some variations and still got the same message.
Click to expand...
Click to collapse
Enter twrp and tick mount system. Try it again. I did it before show you how to fix
Sent from my Xperia ZR using XDA Free mobile app

uncomment said:
Enter twrp and tick mount system. Try it again. I did it before show you how to fix
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
I tried it, again.
Checked that the system is mounted and flashed the Rom.
This time its able to extract the system but some symlinks still fail and the error is still the same (E: error executing UPDATER BINARY in zip)
I deleted the extension (.zip) from the file you uploaded before using 7zip to replace it.

Shray said:
I tried it, again.
Checked that the system is mounted and flashed the Rom.
This time its able to extract the system but some symlinks still fail and the error is still the same (E: error executing UPDATER BINARY in zip)
I deleted the extension (.zip) from the file you uploaded before using 7zip to replace it.
Click to expand...
Click to collapse
Oh, it like as be crazy! I check script again and see it call mount program from sbin but not found
Forget it! Hope you enjoy with resurrection remix 5.4.0
Olivier release new omni 5.1 with video fix. I will do it later.
Thank you for testing!
Sent from my Xperia ZR using XDA Free mobile app

uncomment said:
Oh, it like as be crazy! I check script again and see it call mount program from sbin but not found
Forget it! Hope you enjoy with resurrection remix 5.4.0
Olivier release new omni 5.1 with video fix. I will do it later.
Thank you for testing!
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
Anytime.
Thanks again for RR.

uncomment said:
Oh, it like as be crazy! I check script again and see it call mount program from sbin but not found
Forget it! Hope you enjoy with resurrection remix 5.4.0
Olivier release new omni 5.1 with video fix. I will do it later.
Thank you for testing!
Sent from my Xperia ZR using XDA Free mobile app
Click to expand...
Click to collapse
I'm not sure if it was my mistake or TWRP had problems while installing.
I flashed TWRP 2.8.5.0 (Uploaded by you previously) and tried flashing again Omni 5.1.
This time it worked.

Shray said:
I'm not sure if it was my mistake or TWRP had problems while installing.
I flashed TWRP 2.8.5.0 (Uploaded by you previously) and tried flashing again Omni 5.1.
This time it worked.
Click to expand...
Click to collapse
Thank for testing.
I will not upload AOSP rom more. For me it less bug but not much options for me like CM base rom.

[CLOSED] flash Xposed | "cp: write error: No space left on device"

Hello, I have a Problem while flashing Xposed.
I have the current TWRP and Firmware Version
Yesterday I had install the custom Rom ViperOne on my device.
Then i want to flash Xposed. But every time TWRP shows : "cp: write error: No space left on device",
but my storage have more than 10GB free space.
Please help

xXZaretXx said:
Hello, I have a Problem while flashing Xposed.
I have the current TWRP and Firmware Version
Yesterday I had install the custom Rom ViperOne on my device.
Then i want to flash Xposed. But every time TWRP shows : "cp: write error: No space left on device",
but my storage have more than 10GB free space.
Please help
Click to expand...
Click to collapse
Xposed is flashed to the /system partition not in /data so make sure there is enough space in /system.

alray said:
Xposed is flashed to the /system partition not in /data so make sure there is enough space in /system.
Click to expand...
Click to collapse
Thank you for this information. How i can clean my /system ?

xXZaretXx said:
Thank you for this information. How i can clean my /system ?
Click to expand...
Click to collapse
/system is your OS partition so be extra careful if you delete anything form it. I would only recommend deleting pre-loaded apps that you doesn't use (apps that came with the rom). You might want to ask in the viperone thread, probably someone else got the same issue since both Xposed and Viperone are popular.

alray said:
/system is your OS partition so be extra careful if you delete anything form it. I would only recommend deleting pre-loaded apps that you doesn't use (apps that came with the rom). You might want to ask in the viperone thread, probably someone else got the same issue since both Xposed and Viperone are popular.
Click to expand...
Click to collapse
Thank you, now i can install xposed

xXZaretXx said:
Thank you, now i can install xposed
Click to expand...
Click to collapse
Glad it worked and thanks for adding (closed) :good:

LOCKED: How to Reset Pattern? (Urgent)

Hello,
My Device: Oneplus 3T
I have installed multirom on my mobile with Resurrection and MIUI installed ROMs. Although i insert the correct pattern, some how both the OS not accepting the pattern after reboot and my phone is locked . Please help me to unlock/reset the pattern.
Note: I have TWRP 3.0.3 (Multirom) installed in my device and the phone is rooted.

Amitshahc said:
Hello,
My Device: Oneplus 3T
I have installed multirom on my mobile with Resurrection and MIUI installed ROMs. Although i insert the correct pattern, some how both the OS not accepting the pattern after reboot and my phone is locked . Please help me to unlock/reset the pattern.
Note: I have TWRP 3.0.3 (Multirom) installed in my device and the phone is rooted.
Click to expand...
Click to collapse
Boot into TWRP and go to the file manager under advanced. From here cd to data/system/ and delete the 2 .key extension files along with the lockscreen.db files. This will remove your lockscreen from your primary rom. You can do the same with secondary. This is a known MultiROM bug and a quick search in the thread would have provided you with the answer.

cmbdom said:
Boot into TWRP and go to the file manager under advanced. From here cd to data/system/ and delete the 2 .key extension files along with the lockscreen.db files. This will remove your lockscreen from your primary rom. You can do the same with secondary. This is a known MultiROM bug and a quick search in the thread would have provided you with the answer.
Click to expand...
Click to collapse
Thanks for your reply, but i already found those solutions and tried too.
But still the Resurrection OS is locked. while the internal OS which points to MIUI is unlocked and not asking anything. should i reinstall the 2nd OS of Resurrection?
Now there are no .key files or lockscreen.db files in /data/system.

Amitshahc said:
Thanks for your reply, but i already found those solutions and tried too.
But still the Resurrection OS is locked. while the internal OS which points to MIUI is unlocked and not asking anything. should i reinstall the 2nd OS of Resurrection?
Now there are no .key files or lockscreen.db files in /data/system.
Click to expand...
Click to collapse
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.

cmbdom said:
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.
Click to expand...
Click to collapse
Thanks, this seems something would have worked if I didn't had deleted and reinstalled the OS. sorry I can't wait so reinstalled it. I will try to follow this next time if I face the same issue. thanks...

cmbdom said:
You now need to travel to your secondary rom's install location (ex. Internal Storage). I'd assume you installed it to the userdata partition so travel to sdcard/MultiROM/ then continue to data/system/. If it is not in this location then take a quick Google search for the partition you installed it to.
Click to expand...
Click to collapse
[Solved] :good:
Thanks, this one really worked for me.. the path was sdcard/multirom/roms and then data/system.

Amitshahc said:
[Solved] :good:
Thanks, this one really worked for me.. the path was sdcard/multirom/roms and then data/system.
Click to expand...
Click to collapse
This happens whenever you set a lockscreen pattern while using MultiROM on any of the installed ROMs.

[MOD][RECOVERY] Working TWRP recovery for Pixel on Android O

EDIT:
My mod is not needed anymore!
Everything is fine now, the TWRP guys made the decryption in their latest version (3.2.1 at the time of this post) possible, even with android 8.1.
Go ahead and download it from twrp.me. and don't forget to thank them, because it was a LOT of hard work! Google made big changes under the hood, and it took a lot of patience and endurance to adapt.
Big up to @Dees_Troy and the rest of the team!
Hey People! It seems, that after weeks of trying, hundreds of reboots, countless tests, I can present you a working version of TWRP 3.1. for the Pixel with Android O Developer Preview 4.
Edit: and it also works on the final Android O.
But let's not rush into things.. First of all a DISCLAIMER:
This is a TEST release, you are using it at your own risk. If your phone gets damaged in any way, nobody else but you can be held responsible. If you do not agree, stop reading and don't use this mod!
I would like to give credits to the people who helped me, and made all this possible:
First of all, @Chainfire, who did more then you would think Among other things, he was the one who showed me how to use tune2fs and reset quotas on /data, which makes it possible to mount it. Without this , I couldn't even start. So thank you very much!
Of course where would we be without @Dees_Troy and the other TWRP guys (i.e.: CaptainThrowback, nkk71, steadfasterX, _that...), who created and maintain TWRP, and demonstrated some serious patience on IRC , where I was asking them for help. For days. For weeks Thank you guys! You helped a lot!
What is this "mod"?
This is stock, normal TWRP 3.1 compiled from source, for the Google Pixel (sailfish) with some small tweaks to make it possible to mount /data, and decrypt it.
Can you use it on the Pixel XL (marlin)?
I don't know... I don't have a Pixel XL to test. If you want, you can buy me one and I'll be glad to compile, prepare, and test it for you.
EDIT: Chainfire "tested a few zip installs" and those were working for him on the Pixel XL, so maybe it is worth a try guys! - thanks for this CF! -
What happens behind the curtains?
I made some modifications to a script that prepared stuff to make the decryption of /data possible. Now it does a bit more... It copies libraries and binaries from /system and /vendor partitions to /system and /vendor folders, so they can be un-mounted (needed for backup). Basically, the recovery uses the real files/commands of the currently installed android os to prepare and mount /data partition (to make it ready for decrypting).
I updated the fstab file, so TWRP knows what to mount where.
I also changed a few things in the order how services are started during TWRP boot.
This is mostly everything. I was only changing external parts/files/tools of TWRP. The original code, the core is left intact.
How well was it tested?
I have only 1 phone, the pixel. I have only tested on this one phone, and it works for me. Of course I can't be certain it will for you, but you will see if you try it
I tested decrypting of /data, flashing a zip file, making a backup. Didn't dare to test restore yet
How can you try it?
This is not a flashable zip, this is a bootable image. So to use it, you have to put the phone into fastboot mode, and fastboot boot the image.
1. reboot the phone into fastboot mode
- if you have adb: adb reboot bootloader
- if you don't, then turn off the phone and press volume down while turning it on
2. open a terminal and issue the following command:
Code:
fastboot boot <path to your twrp image here>
(for example: fastboot boot /home/you/twrp-3-1-pixel-bootable-mod.img)
What about a flashable zip?
I had some quick test runs only for now, and it was working for me (flashing the zip, rebooting to recovery) until I flashed supersu, or rebooted the phone to android. I will need some more time to work on this, and see what is going wrong. So please be patient, I will try to do something, but can't guarantee it will work. Soon. Anytime.
Enough of the talk, you can download the image file from here:
https://www.androidfilehost.com/?fid=745425885120753892
Good luck and don't forget to report back!
I will try to do my best to help you, but I have a family and I inted to spend most of my time with them. Please be patient!
If you like my work, you can buy me a beer, it is damn hot here right now, and I would love to drink one
Edit: Because I'm a noob and couldn't push my changes to the gerrits, I created a diff file with all my changes.
If you are checking it, please take into account, that I was in a hurry, and there was a point where I said "F*** it!" and I copied ALL the libs and bins from /system and /vendor
Anyway, here it is : https://www.androidfilehost.com/?fid=817550096634795329

reserved...

I've only tested installing a few ZIPs but that seems to work fine (on Pixel XL).
I've looked at your modified script and I see the tune2fs commands and copying /system and /vendor files, but I don't see where you actually mount/decrypt /data. Or is this still handled by the TWRP binary?

Chainfire said:
I've only tested installing a few ZIPs but that seems to work fine (on Pixel XL).
I've looked at your modified script and I see the tune2fs commands and copying /system and /vendor files, but I don't see where you actually mount/decrypt /data. Or is this still handled by the TWRP binary?
Click to expand...
Click to collapse
Hi Chainfire!
I'm happy to hear, that it works on the Pixel XL
Thanks for the confirmation!
Yes, decrypting the data partition is still being handled by TWRP. I added some debug lines to the C code, you can see it in /tmp/recovery.log.
The main issue was mounting /data first, and I had to enable file based encryption instead of vold...

Thanks, I'll have to make time in the very near future to prep my phone for a fresh install.
I haven't had a need to host Android files since I moved on from LG devices before my HTC 10 and Pixel, but I highly recommend Android File Host with optional FTP access on request.
If you prefer a regular cloud service, I recommend Mega. They give 50GB for free and they have an Android app as well as Windows. Possibly others (Mac?), not sure.

My God this is amazing. Thank you so so much.

bbender716 said:
My God this is amazing. Thank you so so much.
Click to expand...
Click to collapse
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy

roirraW "edor" ehT said:
Thanks, I'll have to make time in the very near future to prep my phone for a fresh install.
I haven't had a need to host Android files since I moved on from LG devices before my HTC 10 and Pixel, but I highly recommend Android File Host with optional FTP access on request.
If you prefer a regular cloud service, I recommend Mega. They give 50GB for free and they have an Android app as well as Windows. Possibly others (Mac?), not sure.
Click to expand...
Click to collapse
Ahh I haven't thought of Android File Host! Although I downloaded gigbytes of roms, and mods from there already
Thanks for the tip!

is my path is cd/adb what command i write before twrp.img
gubacsek said:
Hey People! It seems, that after weeks of trying, hundreds of reboots, countless tests, I can present you a working version of TWRP 3.1. for the Pixel with Android O Developer Preview 4.
But let's not rush into things.. First of all a DISCLAIMER:
This is a TEST release, you are using it at your own risk. If your phone gets damaged in any way, nobody else but you can be held responsible. If you do not agree, stop reading and don't use this mod!
I would like to give credits to the people who helped me, and made all this possible:
First of all, @Chainfire, who did more then you would think Among other things, he was the one who showed me how to use tune2fs and reset quotas on /data, which makes it possible to mount it. Without this , I couldn't even start. So thank you very much!
Of course where would we be without @Dees_Troy and the other TWRP guys (i.e.: CaptainThrowback, nkk71, steadfasterX...), who created and maintain TWRP, and demonstrated some serious patience on IRC , where I was asking them for help. For days. For weeks Thank you guys! You helped a lot!
What is this "mod"?
This is stock, normal TWRP 3.1 compiled from source, for the Google Pixel (sailfish) with some small tweaks to make it possible to mount /data, and decrypt it.
Can you use it on the Pixel XL (marlin)?
I don't know... I don't have a Pixel XL to test. If you want, you can buy me one and I'll be glad to compile, prepare, and test it for you.
EDIT: Chainfire "tested a few zip installs" and those were working for him on the Pixel XL, so maybe it is worth a try guys! - thanks for this CF! -
What happens behind the curtains?
I made some modifications to a script that prepared stuff to make the decryption of /data possible. Now it does a bit more... It copies libraries and binaries from /system and /vendor partitions to /system and /vendor folders, so they can be un-mounted (needed for backup). Basically, the recovery uses the real files/commands of the currently installed android os to prepare and mount /data partition (to make it ready for decrypting).
I updated the fstab file, so TWRP knows what to mount where.
I also changed a few things in the order how services are started during TWRP boot.
This is mostly everything. I was only changing external parts/files/tools of TWRP. The original code, the core is left intact.
How well was it tested?
I have only 1 phone, the pixel. I have only tested on this one phone, and it works for me. Of course I can't be certain it will for you, but you will see if you try it
I tested decrypting of /data, flashing a zip file, making a backup. Didn't dare to test restore yet
How can you try it?
This is not a flashable zip, this is a bootable image. So to use it, you have to put the phone into fastboot mode, and fastboot boot the image.
1. reboot the phone into fastboot mode
- if you have adb: adb reboot bootloader
- if you don't, then turn off the phone and press volume down while turning it on
2. open a terminal and issue the following command:
Code:
fastboot boot <path to your twrp image here>
(for example: fastboot boot /home/you/twrp-3-1-pixel-bootable-mod.img)
What about a flashable zip?
I had some quick test runs only for now, and it was working for me (flashing the zip, rebooting to recovery) until I flashed supersu, or rebooted the phone to android. I will need some more time to work on this, and see what is going wrong. So please be patient, I will try to do something, but can't guarantee it will work. Soon. Anytime.
Enough of the talk, you can download the image file from here:
(If you know a good file hosting service, please let me know):
https://drive.google.com/open?id=0BycCshQzwZmBaUtialo5Y01Dc3c
Good luck and don't forget to report back!
I will try to do my best to help you, but I have a family and I inted to spend most of my time with them. Please be patient!
If you like my work, you can buy me a beer, it is damn hot here right now, and I would love to drink one
Click to expand...
Click to collapse
Any help don't want reistall all again!!!!
is my twro .img is on cd/adb what command i write to flash this beauty?

Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.

gubacsek said:
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy
Click to expand...
Click to collapse
Hilariously, the ARISE sound mod is exactly why I had flashed back from DP4. I'm close with those guys and they know their stuff for sure.

mngdew said:
Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.
Click to expand...
Click to collapse
Same here

I just tried ARISE. This one installs, but failed to update the driver.

mngdew said:
I just tried ARISE. This one installs, but failed to update the driver.
Click to expand...
Click to collapse
Interesting. I also tried side loading the v4a apk packaged in WETA, granted root permissions and it attempted to install drivers but failed.

mngdew said:
Well, I was able to boot to TWRP, and successfully flashed WETA audio mod. However, upon rebooting, the V4A app wasn't there.
Click to expand...
Click to collapse
maflin18 said:
Same here
Click to expand...
Click to collapse
mngdew said:
I just tried ARISE. This one installs, but failed to update the driver.
Click to expand...
Click to collapse
maflin18 said:
Interesting. I also tried side loading the v4a apk packaged in WETA, granted root permissions and it attempted to install drivers but failed.
Click to expand...
Click to collapse
Guys! Check the free space on /system! On Android O DP4 I had about 100MB free space, and I had to remove some **** before flashing anything. Try /system/app and Pinyin input, Chinese input apks....
The recovery is fine...

What? I don't know what I did differently this time, but the the app keeps asking to install the driver again and again everytime I open the app even though there was a successful driver installation notification.

gubacsek said:
You are welcome! Try to imagine how happy I was when I first succeeded At that time I had to issue 5 commands after boot, and restart it twice to make it work
But I was already able to flash ARISE sound mod and I almost cried of joy
Click to expand...
Click to collapse
Can u pls send link for arise which u have flash...

kiran8631 said:
Can u pls send link for arise which u have flash...
Click to expand...
Click to collapse
It was this one:
https://drive.google.com/file/d/0BycCshQzwZmBRFRJSXAwTDhHcm8/view?usp=drivesdk

At last! I got it working.

gubacsek said:
It was this one:
https://drive.google.com/file/d/0BycCshQzwZmBRFRJSXAwTDhHcm8/view?usp=drivesdk
Click to expand...
Click to collapse
Facing this issue...