Hi! I followed the steps here to build stock CAF Android for my device.
I made the factory images and OTA zip, and it said everything was successful.
When I flash the factory images, it says that it's looking for a "QC Reference Phone" and my phone identifies as either msm8996 or oneplus3 (can't remember) so it won't flash.
When I flash the OTA zip, it says that this phone is a "oneplus3" and it needs "msm8996" so it wouldn't flash either, but I got around that by removing the checks in the updater script.
So I've got it flashed onto my device, but I'm facing a problem:
Once it's flashed, it boots, but then says Encryption Unsuccessful, and to factory reset my phone. However, if I do that, I get the same error.
Also, I noticed that when I run fastboot commands like "fastboot format userdata" it tells me
Code:
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Could anyone help with this? I can even pay like 20$ if I get a good solution
Thanks
Have you tried completely wiping your data from TWRP? That is erasing everything from the "Format Data" option under "Wipe". You need to enter "yes" from the keyboard to confirm. This basically does the same thing as fastboot format user data. Try this, and let us know what happens.
thes3usa said:
Have you tried completely wiping your data from TWRP? That is erasing everything from the "Format Data" option under "Wipe". You need to enter "yes" from the keyboard to confirm. This basically does the same thing as fastboot format user data. Try this, and let us know what happens.
Click to expand...
Click to collapse
Do I do this before or after flashing the zip file?
Thanks, Nate
Follow these steps.
Wipe System/Data/Cache
Flash Zip
Reboot back into Recovery
Wipe all data as I've mentioned in the above post
Reboot.
thes3usa said:
Follow these steps.
Wipe System/Data/Cache
Flash Zip
Reboot back into Recovery
Wipe all data as I've mentioned in the above post
Reboot.
Click to expand...
Click to collapse
Thanks for the help. I flashed it, rebooted back to recovery, and chose Format Data - "yes" and it says:
Code:
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount storage
I rebooted anyways just to see, and it goes like normal on the OnePlus logo, then the boot animation, and then I get the same screen. https://imgur.com/a/hD8Zm
Rebooted again back to recovery and did the same format, and that time it worked successfully. I rebooted back into the OS, and same error.
NateDev said:
Thanks for the help. I flashed it, rebooted back to recovery, and chose Format Data - "yes" and it says:
Code:
Failed to mount '/data' (Device or resource busy)
Failed to mount '/data' (Device or resource busy)
Unable to recreate /data/media folder.
You may need to reboot recovery to be able to use /data again
Updating partition details...
Failed to mount '/data' (Device or resource busy)
...done
Unable to mount storage
I rebooted anyways just to see, and it goes like normal on the OnePlus logo, then the boot animation, and then I get the same screen. https://imgur.com/a/hD8Zm
Click to expand...
Click to collapse
Seems like your data partition is completely corrupt. You may want to try the Unbrick tool, to get your device back working. "Fastboot Format Userdata" was the last thing you could do, and it doesnt work.
Are you sure the build compiled correctly? I've never seen something like this happen, and it's quite weird. It's happened to me, but under completely different circumstances.
Are you on the recommended TWRP? That is Acuicultors TWRP for the 3/3T? It is bug free.
thes3usa said:
Seems like your data partition is completely corrupt. You may want to try the Unbrick tool, to get your device back working. "Fastboot Format Userdata" was the last thing you could do, and it doesnt work.
Click to expand...
Click to collapse
What's weird though is when I was trying this before and got this issue, I went back and flashed OxygenOS and it booted fine. This attempt now was straight off of OxygenOS and it doesn't work.
Do you think it's still worth trying the Unbrick tool, as OOS worked fine inbetween? idk but maybe it could be more of an issue with the ROM, but I built it with no modifications straight from OnePlus' GitHub.
EDIT: Didn't see your second post, about the build compiling.
It looks like it compiled correctly, didn't show any errors, and the final message was green, not red.
I'm on the TWRP from twrp.me, is that the reccomended one?
EDIT2: Tried this TWRP https://androidfilehost.com/?fid=746010030569948067, I flashed the ROM and when I go to format data, it says:
Code:
mkfs.f2fs -t 0 -r 16384 /dev/block/sda15 process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption
That line about encryption is interesting, is there a way to disable encryption on the 3T? I saw this https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748 but idk if it would as it says its only for OOS.
Then I just tried this https://android.stackexchange.com/questions/98228/removing-encryption-from-recovery to remove encryption but the boot just gets stuck on the boot animation, even after setting it to on and reflashing, so I'm going to hope I didn't brick my phone and am going to try the unbrick tool if flashing stock does nothing.
Thanks for your help
NateDev said:
What's weird though is when I was trying this before and got this issue, I went back and flashed OxygenOS and it booted fine. This attempt now was straight off of OxygenOS and it doesn't work.
Do you think it's still worth trying the Unbrick tool, as OOS worked fine inbetween? idk but maybe it could be more of an issue with the ROM, but I built it with no modifications straight from OnePlus' GitHub.
EDIT: Didn't see your second post, about the build compiling.
It looks like it compiled correctly, didn't show any errors, and the final message was green, not red.
I'm on the TWRP from twrp.me, is that the reccomended one?
EDIT2: Tried this TWRP https://androidfilehost.com/?fid=746010030569948067, I flashed the ROM and when I go to format data, it says:
Code:
mkfs.f2fs -t 0 -r 16384 /dev/block/sda15 process ended with ERROR: 1
Unable to wipe Data.
Unable to format to remove encryption
That line about encryption is interesting, is there a way to disable encryption on the 3T? I saw this https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748 but idk if it would as it says its only for OOS.
Then I just tried this https://android.stackexchange.com/questions/98228/removing-encryption-from-recovery to remove encryption but the boot just gets stuck on the boot animation, even after setting it to on and reflashing, so I'm going to hope I didn't brick my phone and am going to try the unbrick tool if flashing stock does nothing.
Thanks for your help
Click to expand...
Click to collapse
Sorry for the late reply, got a little busy there.
Did you flash OOS after flashing the Custom Build? If you did so, and it worked, it may not be the device, it may be the build.
thes3usa said:
Sorry for the late reply, got a little busy there.
Did you flash OOS after flashing the Custom Build? If you did so, and it worked, it may not be the device, it may be the build.
Click to expand...
Click to collapse
Yea I flashed OOS after my custom build, which does point to the build being the problem.
That's weird because everything completed with no errors, and I used the source straight from OnePlus.
And, seeing how inactive they are on GitHub, doesn't look like I'll be getting a solution from them anytime soon
Is there a similar ROM source code that I could use? I'm looking for barebones CAF, basically. I saw this: https://github.com/AOSP-CAF but I don't even know if it's possible to configure that for the 3T without extensive work, as it looks to just be a generic build.
NateDev said:
Yea I flashed OOS after my custom build, which does point to the build being the problem.
That's weird because everything completed with no errors, and I used the source straight from OnePlus.
And, seeing how inactive they are on GitHub, doesn't look like I'll be getting a solution from them anytime soon
Is there a similar ROM source code that I could use? I'm looking for barebones CAF, basically. I saw this: https://github.com/AOSP-CAF but I don't even know if it's possible to configure that for the 3T without extensive work, as it looks to just be a generic build.
Click to expand...
Click to collapse
You should try LineageOS's source, if you're looking for barebones. Can't say it's similar to CAF though. If you're an Amateur at these stuff, use Sources that are already readily built for the 3T, so you can do your own customizations without having to worry about the build failing.
thes3usa said:
You should try LineageOS's source, if you're looking for barebones. Can't say it's similar to CAF though. If you're an Amateur at these stuff, use Sources that are already readily built for the 3T, so you can do your own customizations without having to worry about the build failing.
Click to expand...
Click to collapse
Is LineageOS CAF based or AOSP? I searched but couldn't find a clear answer. If it's indeed CAF I will probably go ahead and try that.
Sucks that OnePlus's own GitHub for building for the 3T fails, and I kinda would have liked the experience of bringing up the system from the most barebones it could get, but if I can't even get an initial build to boot up with no modifications whatsoever, then I'll have to do Lineage.
I'll keep my OSS sources on my PC for the next week or 2 and resync and rebuild in the hopes that they change something that fixes it.
Thanks for your help
NateDev said:
Is LineageOS CAF based or AOSP? I searched but couldn't find a clear answer. If it's indeed CAF I will probably go ahead and try that.
Sucks that OnePlus's own GitHub for building for the 3T fails, and I kinda would have liked the experience of bringing up the system from the most barebones it could get, but if I can't even get an initial build to boot up with no modifications whatsoever, then I'll have to do Lineage.
I'll keep my OSS sources on my PC for the next week or 2 and resync and rebuild in the hopes that they change something that fixes it.
Thanks for your help
Click to expand...
Click to collapse
LineageOS is AOSP based, but has one of the most trusted sources, that are confirmed to be working.
It's OnePlus. Obviously their sources are going to be messed up. Look at their absolutely horrible Camera2 API Implementation. It's the reason why we need so many add-on fixes for HDR+ and other features to be working on the front camera.
Try resyncing the Repo, or completely start the sync over from scratch. Who knows, maybe your saved sources are messed up, and that's what causing the build error.
Good luck with the building!
thes3usa said:
LineageOS is AOSP based, but has one of the most trusted sources, that are confirmed to be working.
It's OnePlus. Obviously their sources are going to be messed up. Look at their absolutely horrible Camera2 API Implementation. It's the reason why we need so many add-on fixes for HDR+ and other features to be working on the front camera.
Try resyncing the Repo, or completely start the sync over from scratch. Who knows, maybe your saved sources are messed up, and that's what causing the build error.
Good luck with the building!
Click to expand...
Click to collapse
"It's OnePlus. Obviously their sources are going to be messed up. Look at their absolutely horrible Camera2 API Implementation. It's the reason why we need so many add-on fixes for HDR+ and other features to be working on the front camera." Haha yep you're right lol.
Thanks, I'll try LOS and keep trying OnePlus's sources, and I will resync as well incase that's the issue.
Thanks so much for all your help
Related
TWRP 2.8.2.0Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
This is not an official TeamWin TWRP build. I used TWRP sources found HERE, device tree that I created for TWRP that can be found HERE.
Changelog:
CHANGELOG for 2.8.2.0 - From TWRP webiste...
-Pull in all changes from Android 5.0 lollipop into TWRP
-Add decrypt support for Android 5.0 lollipop encrypted partitions including automatic decrypt when the default_password is in use
-Revert some changes to exFAT that were breaking exFAT support on some devices
-Other minor fixes and updates
Note: At this time we do not have a GUI representation for pattern unlock. You can still decrypt patterns though by translating the pattern dots to numbers. The pattern dots correspond to numbers in the following pattern:
1 2 3
4 5 6
7 8 9
So an upper-case L would translate to a password of 14789 entered on the keyboard. Eventually we plan to add a proper pattern unlock to TWRP but it is a relatively low priority at this point.
More info and changelog can be found on the official TWRP website HERE
Install Instructions:
With custom recovery already installed.
Download
Place zip file on phone
Reboot into recovery
Flash zip file through recovery
Reboot
With stock recovery - Need ADB installed.
Download zip file
Extract recovery.zip to a folder on your computer. Example c:\recovery
Open terminal window/command prompt, browse the the c:\recovery folder to execute following commands
adb reboot bootloader
fastboot flash recovery recovery.img
use vol +/- to scroll through menu to select recovery mode
press power button to reboot into updated recovery
profit!
Download:
Download HERE
Credits:
@Dees_Troy
TeamWin
Everyone involved with TWRP.
PS...Working on CM12 for V510 now
Thanks!
It doesn't seem to ask for a password to decrypt /data for encrypted devices though like it does on my N5.
Having some difficulty getting this to push through on the V50020d build. Thoughts?
apvikes28 said:
Having some difficulty getting this to push through on the V50020d build. Thoughts?
Click to expand...
Click to collapse
This is only for GPE 510 devices. There is another thread for your device.
NHLWil said:
Thanks!
It doesn't seem to ask for a password to decrypt /data for encrypted devices though like it does on my N5.
Click to expand...
Click to collapse
Can you flash the latest build, has today's date in it and see if it works now?
Thanks!
AndroidUser00110001 said:
Can you flash the latest build, has today's date in it and see if it works now?
Thanks!
Click to expand...
Click to collapse
It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.
AndroidUser00110001 said:
Can you flash the latest build, has today's date in it and see if it works now?
Thanks!
Click to expand...
Click to collapse
NHLWil said:
It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.
Click to expand...
Click to collapse
@AndroidUser00110001, maybe you need to have fstab.palman in the ramdisk, as described in this commit message: https://github.com/omnirom/android_bootable_recovery/commit/4eca40d7d8ff6968ed68a24686093cfb6f5f6373
NHLWil said:
It still didn't ask for a password, nor could I mount /data manually due to encryption. I even took out my SD card for giggles, thinking since TWRP was able to mount that, it could've been skipping trying to mount /data, but no dice.
Click to expand...
Click to collapse
Try twrp-2.8.2.0_v510-20141209.zip
AndroidUser00110001 said:
Try twrp-2.8.2.0_v510-20141209.zip
Click to expand...
Click to collapse
Still no change.
NHLWil said:
Still no change.
Click to expand...
Click to collapse
What exactly is going on because I am able to mount and do whatever I need to do.
AndroidUser00110001 said:
What exactly is going on because I am able to mount and do whatever I need to do.
Click to expand...
Click to collapse
And your device is encrypted running Lollipop?
With my N5, TWRP prior to 2.8.2.0 was not able to decrypt the /data partition on Lollipop. It would simply ask for the password, but would always fail. 2.8.2.0 fixed this.
However, with 2.8.2.0 on palman, it never even asks for the password . . . it just says it's unable to mount /data. The decryption routine doesn't appear to be working at all for me.
NHLWil said:
And your device is encrypted running Lollipop?
With my N5, TWRP prior to 2.8.2.0 was not able to decrypt the /data partition on Lollipop. It would simply ask for the password, but would always fail. 2.8.2.0 fixed this.
However, with 2.8.2.0 on palman, it never even asks for the password . . . it just says it's unable to mount /data. The decryption routine doesn't appear to be working at all for me.
Click to expand...
Click to collapse
Can you get a log? Is your data partition encrypted? I am guessing you are running the stock ROM?
I can mount data and wipe data. Not sure what issue you are having unless I am not understanding what you are trying to explain.
AndroidUser00110001 said:
Can you get a log? Is your data partition encrypted? I am guessing you are running the stock ROM?
I can mount data and wipe data. Not sure what issue you are having unless I am not understanding what you are trying to explain.
Click to expand...
Click to collapse
Yes, my data partition is encrypted. TWRP 2.8.2.0 on the N5 supports decrypting data. TWRP 2.8.2.0 on the N5 will ask for your password as soon as it boots, and when you input the proper password, it will decrypt data so it can be mounted.
TWRP 2.8.2.0 on palman does not ask for the password as soon as it boots, thus data is not decrypted. The exact error is:
"Could not mount /data and unable to find crypto footer"
AndroidUser00110001 said:
TWRP 2.8.2.0PS...Working on CM12 for V510 now
Click to expand...
Click to collapse
OMG if you can get CM12 out for the V510 GPE device I am sure you would become an instant hero to thousands of users...
jk8260 said:
OMG if you can get CM12 out for the V510 GPE device I am sure you would become an instant hero to thousands of users...
Click to expand...
Click to collapse
invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.
I would say CM12 for the v510 in a week.
AndroidUser00110001 said:
invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.
I would say CM12 for the v510 in a week.
Click to expand...
Click to collapse
Awesome news! That will open up a whole new world for kernel development too. Really looking forward to it. Thank you for your hard work. Takes hours/days to get there.
AndroidUser00110001 said:
invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.
I would say CM12 for the v510 in a week.
Click to expand...
Click to collapse
This would definitely be great for the GPE! Looking forward to updates...
Any news on getting CM12 out for the V510 GPE, fingers crossed…
The device tree page won't come up. The link is broken.
AndroidUser00110001 said:
invisiblek will be working on it with me. I have CM11 booting but with some hardware issue and I cannot get my CM12 build to boot yet. I am actually giving him my v510 so he can finish up the build. I am maintaining the d850 and just don't have enough time right now to continue with the v510.
I would say CM12 for the v510 in a week.
Click to expand...
Click to collapse
Bump: Any Status or Beta's??
Disclaimer: Usual disclaimer applies. I've tested this recovery but it might not work due to a different ROM / device / moon phase / etc. Use at your own risk.
Introduction
After working with upstream TWRP developers and fixing some bugs (in TWRP itself and in this port) this device finally has an official port
There were various builds available at different times (some with bugs) but most of them should now be fixed.
Features
Works
backup/restore
installing zips
ADB
MTP
Screen turns off
Basically the rest of this list
format /data
Adoptable storage
Decrypt /data
Doesn't work (please ask if you need this)
Encrypted backup (set password for /data/data)
USB-OTG
Untested
Backup/restore of stock system / data.
Installation instructions
Warning: only use it on the G800F/M/Y, NOT on the G800H! I only tested the G800F, but think G800M/Y will also work. G800H will most likely NOT work, as it is based on a different SoC (Qualcomm).
Download the recovery image from twrp.me. It also includes some installation instructions.
There are more extensive installation instructions over at the LineageOS ROM installation instructions.
I personally prefer using Heimdall, but you can also use Odin. Commands in Download/Odin mode (power off, then press home+Volume-Down+power):
Code:
heimdall flash --RECOVERY recovery.img
If you're using the stock ROM, use:
Code:
heimdall flash --RECOVERY recovery.img --no-reboot
When you come from the stock ROM you have to make sure the stock ROM doesn't overwrite TWRP: Pull the battery, wait 5 seconds, insert it again, and press home + volume up + power to enter TWRP and replace the stock ROM from there.
If you already have TWRP or LineageOS, it's much easier to install from there, see twrp.me.
Another method is using ADB (from your computer). I used it a lot during testing:
Code:
adb root
adb push twrp-3.1.1-1-kminilte.img /dev/block/mmcblk0p10
Changelog
Code:
2017-07-10:
* fix formatting /data while the partition is encrypted
(device is not encrypted by default)
* add support for adoptable storage
* accept kminiltexx etc. for flashing basebands
2017-06-20:
* ADB
* MTP at the same time as ADB
* Screen turns fully off
* fix for restoring backups made using `adb backup --twrp`
Source code
Kernel: https://github.com/TeamWin/android_kernel_samsung_kminilte/tree/cm-14.1
Device: https://github.com/TeamWin/android_device_samsung_kminilte/tree/cm-14.1
This recovery is built using a LineageOS tree. Instructions are similar to the instructions for building LineageOS for the S5 mini. Differences are: you don't need to patch the source (skip that step) and the last step is mka recoveryimage instead of mka bacon - this only builds the recovery resulting in much faster builds. Also see the official build instructions.
Thanks
Other people who have worked on this project:
Team Win, of course, for the recovery itself! In particular bigbiff which has worked with me to make this device official.
hennymcc
RVR
---
Note to moderators: this is my first DevDB thread started on XDA so I may have made mistakes.
XDA:DevDB Information
Team Win Recovery Project, ROM for the Samsung Galaxy S5 Mini
Contributors
ayke, hennymcc, RVR
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Version Information
Status: Stable
Current Stable Version: 3.1.1
Stable Release Date: 2017-06-20
Created 2017-06-24
Last Updated 2017-07-09
Thanks!
OFFICIAL TWRP...I can't believe it
Great work on this one...many thanks.
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
P.S. Is it possible to add support for adopted storage, that would be awesome!
Nevertheless - thanks for making this device officialy supported!
Friedensfurz said:
Thanks a million @ayke ! However, I found some bugs I'd like to submit some bugs I discovered:
- Recovery is not SEANDROID enforcing" message when booting TWRP, didn't cause any trouble for me but still - it was fine in your previous unofficial build
Click to expand...
Click to collapse
The current kernel used upstream is somewhat older and hasn't enabled SELinux yet. I don't see why you would want enforcing SELinux in TWRP, though.
Friedensfurz said:
- Some zip files (tested with latest modem flashable zip) report "This package is for kminiltexx devices; this is a kminilte", so it doesn't flash and fails with ERROR:7
Click to expand...
Click to collapse
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Friedensfurz said:
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
Click to expand...
Click to collapse
Nice!
Friedensfurz said:
P.S. Is it possible to add support for adopted storage, that would be awesome!
Click to expand...
Click to collapse
I might look into it. I don't use it at the moment but am considering it.
EDIT: I have fixed it, it will be included in the next build.
any chance for g800h support?
sasukesama said:
any chance for g800h support?
Click to expand...
Click to collapse
Not from me. The G800H is a completely different device. I have a G800F so I can't test it.
ayke said:
I think I have a fix for that, please test https://aykevl.nl/download/2017-06-25-recovery-fix-ota-asserts.img (not tested by me)
Click to expand...
Click to collapse
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Friedensfurz said:
Sorry, but the build doesn't fix the wrong device id issue - still throws error " This is for kminiltexx your device is kminilte. Anyway - maybe the next build will fix it[emoji6]
Click to expand...
Click to collapse
Can you give a link to where you downloaded this zip? Then I can test it myself.
I also get the device error with latest official and 2017-06-25-recovery-fix-ota-asserts.img.
Tried to flash one of Spookcity's kernels, you can find it here (search for "test9" that is what I used lately).
https://github.com/Spookcity/ROMS-G800F/issues/10#issuecomment-301915315
The latest pre-official TWRP 3.1.1-0 works (says kminiltexx).
ayke said:
Can you give a link to where you downloaded this zip? Then I can test it myself.
Click to expand...
Click to collapse
This file causes problems with the device id: http://pt.tapatalk.com/redirect.php...1_22.05.2017_DRE-flashable.zip&au_id=13587482
It is a TWRP flashable baseband file, hope this helps
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
ayke said:
@Friedensfurz @Pat750
I couldn't find a (still online) kernel from Spookcity and I'd rather not flash a new modem unless I know why I should do that. So I haven't verified it.
But here's another build you can try. My previous attempt was incomplete.
https://aykevl.nl/download/2017-06-27-recovery-fix-ota-asserts-2.img
On my device I've verified it has a ro.product.device property of kminiltexx.
Click to expand...
Click to collapse
Yeah,I removed all of my test build links from my google drive, but have a thread on here. I already sent you this though. I will test your new build and see if it helps.
Edit:
Yep,fixed. Good work Ayke!
Sent from my SM-G800F using Tapatalk
Friedensfurz said:
...
I can confirm that decrypting a File-Based encrypted /data partition works, I didn't test the backup tool though.
...
Click to expand...
Click to collapse
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I have the same problem
Here also this message in unofficial builds, don't tried it, but I think its still present in this version.
fidoedidoe said:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):
I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.
Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)
Many thanks!
Click to expand...
Click to collapse
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/data ext4 /dev/block/mmcblk0p21 length=-16384
...
fidoedidoe said:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:
Code:
Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.
What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.
Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.
EDIT
Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.
I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :
Code:
...
/dataext4/dev/block/mmcblk0p21length=-16384
...
Click to expand...
Click to collapse
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually
Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):
https://aykevl.nl/download/2017-07-03-recovery.img
This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).
If it fixes the issue for you, I'll push the change for inclusion in the next official build.
I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.
ayke said:
https://aykevl.nl/download/2017-07-03-recovery.img
Click to expand...
Click to collapse
Can someone test this change? Then I'll integrate it in the official build.
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...
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.
ashyx said:
Format (not wipe) DATA and if that doesn't work FORMAT the system partition.
If neither works then maybe you should use an updated twrp.
Click to expand...
Click to collapse
Thank you for the advice, I will update to the latest TWRP and then format the data and try that. Will report back with results.
After formatting the data and updating to the latest TWRP, 3.2.3-1, I come across the same error 7.
Have updated the script filed to make certain no trace of verification exists for the ROM and still receive the error.
Have now attempted at least five different ROMS all with the same results.
The following is a summarized look at the details it gives.
Installing zip file 'lineage.zip'
Checking for Digest file...
Skipping Digest check: no Digest file found
Warning: No file_contexts
detected filesystem ext4 for /dev/block/platform/15540000.dwmmc0/by-name/SYSTEM
Patching system image unconditionally...
E1001: Failed to update system image.
Updater process ended with ERROR: 7
Error installing zip file '/lineage.zip'
Updating partition details...
Failed to mount '/hidden' (Invalid argument)
...done
Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.
TheBigby said:
Update: I have now wiped data but have not yet formatted it. I believe I will need to install Magisk for that.
However based on other recommendations I have come to find out about the encryption on the Samsung storage and that it might be causing the issue.
I have tried to circumvent this by formatting the data into ext2 then back to ext4 and restarting recovery, but so far this has not worked. The error 7 message persists regardless.
Will come back with further updates.
Click to expand...
Click to collapse
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.
ashyx said:
You didnt read my previous post correctly.
You don't need Magisk to FORMAT DATA.
The FORMAT DATA button is right there under the wipe options.
However what you did would have formatted DATA anyway.
Now do the same for the system partition after formatting DATA.
Do not reboot just check DATA and SYSTEM can be mounted then try and install the zip again.
Click to expand...
Click to collapse
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.
TheBigby said:
Formatted the data and the system. Verified they were both mounted. Then attempted to flash the ROM.
Error 7 message still appearing. As does the unable to mount hidden.
Click to expand...
Click to collapse
What device is the ROM intended for?
ashyx said:
What device is the ROM intended for?
Click to expand...
Click to collapse
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.
TheBigby said:
Have tried multiple ROMs, all intended for either the t810 or the t815. They include Lineage, Resurrection Remix, Paranoid Android, AOSP, and a couple more besides.
Click to expand...
Click to collapse
It may be that the system partition sizes are different?
Unknown. I have tried reflashing the stock firmware and that still failed in Odin.
I have given up at this point and restored from a backup. Thanks for the help however.
Same issue with Lineage 15.1
TheBigby said:
I have a rooted SM-t817t and have been attempting to flash Lineage 14.1 to it through TWRP 3.1.0-1_ashyx.
I have tried to flash with the gts210ltexx and the gts210wifi and the results are the same, receive the Error 7 message.
After reading up on other threads I attempted to alter the script to either tell it that the ROM is for the gts210ltexx or just remove it entirely and still getting the error.
Also attempted to run it without authentication.
I have read that the t817x tablets can be flashed with the t810 ROMs but have had zero success with doing so at this time.
I am unsure how to proceed from this point.
Click to expand...
Click to collapse
Can you share root procedure for the sm-t817t my roommate has one for sale, I'll only buy it if I can root it though.
This is a TWRP fully Treble-ready with "Treble enabler" option in order to repartition safely the device.
Features:
TWRP fully Treble-ready;
Maintained with latest TWRP version;
Fully compatible with non-Treble devices - can be used as normal without Treble partitioning;
USB-OTG fixed
Has 'TWRP survival' function for automatically re-installing TWRP recovery when installing ROMs and kernels;
Adds a "Treble enabler" option that allows you to repartition your device in order to support Treble.
Has the option to shrink userdata to create Vendor partitions. All relevant partitions will be resized and formatted in one go.
If you shrink Userdata, it will ERASE DATA AND INTERNAL STORAGE COMPLETELY - but your device will stay compatible with all existing non-Treble ROM's
Instructions
Flash the recovery.
Reboot Recovery
Optional - Use the "Advanced > Treble enabler" option for repartition option.
If you opted to repartition for Treble, you are ready to flash a Treble ROM/Vendor pack.
About TWRP survival
TWRP survival is a simple hook that detects if a boot.img will be installed and restores TWRP after it's flashed. This only works if you have booted TWRP with Tissot Manager 2.0 from a real recovery boot - NOT from a recovery 'hot boot' (fastboot boot method).
You will see in the install log if a TWRP survival attempt is successful in the flash text output.
Automatic TWRP survival works when:
Flashing a ROM ZIP (or AIO) with TWRP
Flashing a boot.img in TWRP "Install Image" mode
Automatic TWRP survival does NOT work when:
Flashing a boot.img via fastboot
Restoring boot in a TWRP backup
Any other way of flashing a boot.img
In these cases, be sure the use the TWRP Installer immediately after flashing or restoring a backup - otherwise you may get the device into a confused state (especially if you restore a non-TWRP boot then try to install an AIO ROM without installing a new TWRP first).
Download
https://zenfone3-dev.gitlab.io/recovery/twrp-treble/
FAQ
Q) After I flash TWRP, I get kicked into fastboot when trying to boot the ROM!
A) Your kernel is not Treble-compatible.
Q) How do I update TWRP?
A) Just flash the ZIP installer again, then Reboot Recovery. Note that this will erase Magisk on BOTH slots if you have it installed to either, requiring you to reflash it to one/both slots. See my Treble guide FAQ section for more info on Magisk interaction.
Q) My PC can't see the MTP (storage) device from TWRP!
A) For dualboot compatibility, MTP is automatically disabled at various points. Just enable it manually in the Mounts menu to get access.
Q) If I shrink Userdata for Treble, will stock and OTA work?
A) I have heard varying results on this. It does for some, not for others. Please assume that this will NOT work.
Q) Can I restore a non-Treble TWRP backup after I repartition for Treble? And the other way around?
A) Yes!
Q) I see "Failed to mount '/system' (Device or resource busy)" red error in TWRP after flashing a ROM
A) You can safely ignore it. You just need to reboot recovery before you can flash anything else (like Gapps) to this ROM.
Thanks to:
@CosmicDan for his files for Tissot Manager & this thread template
@makorn645, @planet9, @Oki for Party
XDA:DevDB Information
TWRP Recovery for Zenfone 3, Tool/Utility for the Asus ZenFone 3
Contributors
Giovix92, makorn645,
Source Code: https://github.com/Giovix92/android_device_asus_zenfone3/tree/twrp-8.1
Version Information
Status: Stable
Current Stable Version: 20190312
Stable Release Date: 2019-03-12
Created 2019-03-12
Last Updated 2019-03-12
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
dVinsmoke said:
@Giovix92 Does this mean I can use any ROM that is Treble? Or have some restrictions.
Click to expand...
Click to collapse
Just the treble los16 zenfone3 on our forum for now
iamROOTX said:
Just the treble los16 zenfone3 on our forum for now
Click to expand...
Click to collapse
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
dVinsmoke said:
But then I see no difference from a "normal" ROM ported specifically to a device. Should not Treble support be able to use them on several different devices?
For example, should not I be able to go to the AEX Treble download area and use it on ZF3? If it would not be the same as having to wait for a dev port AEX to ZF3.
I'm really confused lol
Click to expand...
Click to collapse
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
makorn645 said:
What do you expect? It's still in an early stage of porting. Some device specific bits still run from /system. GSI's may work but I doubt anything will work properly.
And I don't plan of supporting GSIs anyway.
Click to expand...
Click to collapse
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
dVinsmoke said:
Being sincere I did not expect anything, since I did not understand anything lol This Treble left me was confused lol
So what's the difference of the Lineage Treble for a Lineage normal running in ZF3?
Click to expand...
Click to collapse
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
makorn645 said:
Currently nothing much ( updated proprietary bits + vendor image taken in place )
Maybe in the near future when everything is in place. I'll seperate Vendor image from builds ( noticable smaller updates )
Click to expand...
Click to collapse
Also, when vendor img will be split from the ota package, with (if necessary) some adjustments we can flash GSI ROMs easily.
Great work guys!! Waiting for vendor partition, for some tests!
Williknot said:
Great work guys!! Waiting for vendor partition, for some tests!
Click to expand...
Click to collapse
Well, repartition works fine. After repartition a new /vendor partition of 1024mb will be made.
Although, you'll loose your data (apps+personal). So make sure to do a full backup of your device.
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
[QS said:
;79165451]Works fine for me, data is correctly resized even with multiple changes from normal to treble and back...
Can't seem to wipe /cache partition.
Anyone knows why?
Click to expand...
Click to collapse
A bugfix release will be coming along with the next LineageOS build.
fcbn98 said:
Feedback:
* HAVE A BACKUP. This tool messes with your partition table and is still unstable. Your data partition can be resized to the wrong size.
Will come back after a few months to provide more feedback. Appreciate the work guys.
Click to expand...
Click to collapse
Well, that's normal.
Since you're going to make a new /vendor partition of about 1024mb, /data should be deleted & recreated in order to give some space to the new partition.
Also, what do you mean with "can be resized to the wrong size"?
The tool is pretty stable tho. Can you give more info such as model (ex. ZE552KL 4/64), script version (ex. 4.3b) & other?
Thanks.
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Kaisogen said:
I've successfully installed this tool, although attempting to install the new LOS 16 Android 9 ROM we have on this forum results in an error: 7, "Failed to mount '/vendor' (Invalid argument)"
From what I've perused so far in my research, that error mostly crops up on non-treble builds of TWRP, yet I definitely used the latest version from your website. I also redownloaded the latest version of LOS just to recheck, and yep, nothing's changed.
Any clue about what's going on here? I don't know much about Treble ROMs, or custom ROMing to be all honest.
EDIT: I have found the enable Treble option. Even when enabled and installed, after reboot, the /vendor partition cannot be read. It seems that after doing this too, I can't load files over USB, or mount my SD Card. I'm getting pretty confused as to what's happening. I can't boot into system, and fastboot won't connect to my PC.
Click to expand...
Click to collapse
Did you follow these steps properly?
https://zenfone3-dev.gitlab.io/tutorials/repartition
can i flash android q gsi images using treble recovery.
Switching back to stock rom
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Avinash007 said:
If I have made the treble partition using this recovery is there any way to go back to stock rom?
Click to expand...
Click to collapse
Wipe vendor, data, cache, dalvik partition and flash any ROM normally.
Can i flash android Q gsi image using this recovery on ze520kl