Was this already known ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
raystef66 said:
Was this already know ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Ey buddy I need your help , magisk keep forgetting my rooted apps ... I forgot whats the command I have to run on terminal emulator can you please help me !
luisaet82 said:
Ey buddy I need your help , magisk keep forgetting my rooted apps ... I forgot whats the command I have to run on terminal emulator can you please help me !
Click to expand...
Click to collapse
if it's this what you're referring too...
In terminal :
Code:
su
reboot disemmcwp
or adb :
adb shell reboot disemmcwp
raystef66 said:
if it's this what you're referring too...
In terminal :
or adb :
adb shell reboot disemmcwp
Click to expand...
Click to collapse
The first one ... Thank you so much .. great night
So its about twrp and first reaction is off topic...why you dont pm him?!!
Predatorhaze said:
So its about twrp and first reaction is off topic...why you dont pm him?!!
Click to expand...
Click to collapse
Big deal...that's called helping someone out you know.
You could have pm me or him too you know
And really? All those exclamation marks too? I suggest to ease down (and I know you already a bit longer then yesterday...) your comments are from time to time most inappropriate. I leave it with that
Can i flash the latest version when i have the treble recovery from nfound?
@BaamAlex the version 3.2.3.0 has as far as I could see that on my axon 7 no treble support
Chris axon 7 said:
@BaamAlex the version 3.2.3.0 has as far as I could see that on my axon 7 no treble support
Click to expand...
Click to collapse
Have you installed this here?
Yes
raystef66 said:
Was this already known ? Thought not, right ?
Anyway look for source : https://dl.twrp.me/ailsa_ii/
Click to expand...
Click to collapse
Wow. This completely flew past me (and probably most of the xda community lol). Gonna check it out later. Thanks for telling us
Was this the same release that Nfound said was using older sources than his custom release?
This version boots as it should even with a fully loaded f2fs data partition. Finally the f2fs bug in TWRP has been solved!!!!!
Oki said:
This version boots as it should even with a fully loaded f2fs data partition. Finally the f2fs bug in TWRP has been solved!!!!!
Click to expand...
Click to collapse
Can we use that TWRP on treble? It will be better if we format all partitions to f2fs?
Aviver said:
Can we use that TWRP on treble? It will be better if we format all partitions to f2fs?
Click to expand...
Click to collapse
This TWRP works perfectly with treble roms. The main limitation is the inability to wipe, format, backup and restore the vendor partition using the menu system. You can always use the terminal to manage all that. For integrated vendor management, your only option so far is TWRP 3.2.1-8 Treble.
F2FS is a filesystem aimed to ssd storage devices. It provides an efficient and elaborated write policy that takes advantage of the flash memory. Reads are not specially efficient, this is why ext4 is used for read only partitions and f2fs for read/write partitions. So, system and vendor are ext4 while data and cache should be f2fs.
Related
Hello everyone,
I've managed to make a build that boots with the latest versions of ubuntu touch and I wanted to share it with you because I've also been following this thread eager to install ubuntu touch on my phone, although the method to install still might be complicated for some at the moment.
So first off you need to be using Linux, as I don't think project rootstock works on Windows
To install it you must follow the instructions I found here which are, in a terminal:
sudo apt-get install android-tools-fsutils qemu-user-static bzr
android-tools-adb
bzr branch lproject-rootstock-ng
cd project-rootstock-ng
Click to expand...
Click to collapse
then to get the rootfs with the mir fixes
./rootstock-touch -p pps:rsalveti/ppa
Click to expand...
Click to collapse
which takes a little while or you can download the tar.gz from here
but once the screen turns off it takes a while or a reboot to get it back on
Once that part is finished download all the files at the end of the post and put them in the project-roostock-ng directory to make things easier
then in the same terminal with your device connected to bootloader:
sudo fastboot flash boot ./boot.img
sudo fastboot flash recovery ./recovery.img
Click to expand...
Click to collapse
Reboot your device to recovery and do a full wipe, once that's done, with your device still connected to usb, in the same terminal type:
./rootsotck-touch-installer ./out-XXXXXXXX/ubuntu-touch.rootfs-armhf.tar.gz ./system.img
Click to expand...
Click to collapse
your device should reboot on its own, once you get to the black screen type:
adb shell
mount /dev/loop0 -o remount,rw
exit
adb push 70-m7ul.rules /usr/lib/lxc-android-config
adb push m7ul.conf /etc/ubuntu-touch-session.d
adb reboot
Click to expand...
Click to collapse
and your device should load the ubuntu lockscreen
Here are the files for m7ul:
system.img
boot.img
recovery.img
70-m7ul.rules
m7ul.conf
for m7spr (not tested):
boot.img
recovery.img
system.img
and download the 70-m7ul.rules and m7ul.conf but replace m7ul with m7spr
What works:
UI
camera
auto-rotation
Wifi (tested only on at&t version)
Audio (I've managed to get audio to work if the headphones are plugged in but not all the way, you really gotta find the sweet spot so it's not really useable yet but it's still progress.)
What doesn't work:
GSM
etc
it should run more smooth and the phone should get less hot
Backup file - http://www.mediafire.com/download/2xnfez828442k3l/2014-06-17--17-26-37.zip
I also found a way to have the same kind of dual boot setup canonical made for the nexus 4 by flashing the boot.img (the newer one can be found here http://www.mediafire.com/download/i9kmmwvc3gmb0kb/boot.img) on the recovery partition and keeping the internal rom's boot on the boot partition, so in theory if you flash a rom without wiping after flashing the backup and you flash the boot.img I provided on the recovery partition it should also work and then to get ubuntu you reboot in recovery and to get android you just boot normally, the problem is you lose your recovery temporarily and you have to reflash it if you want to use it until canonical finds a different way or I manage to get it to work with multirom.
delete
Sent from my HTC One_M8 using Tapatalk
ModestMouse1312 said:
He told me to post this here?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
could you please upload the backup of your rom so that we can install. I don't have linux installed on my laptop.
Great JOB! Thank You very much lots of people are waiting for working ubuntu touch rom and this is another big step forward!
https://www.dropbox.com/s/zz6xlm30ffskcol/2014-06-12--03-27-15.zip here is the twrp backup. just unzip it
ModestMouse1312 said:
https://www.dropbox.com/s/zz6xlm30ffskcol/2014-06-12--03-27-15.zip here is the twrp backup. just unzip it
Click to expand...
Click to collapse
may be you should update OP but wifi actually works
saketh91 said:
may be you should update OP but wifi actually works
Click to expand...
Click to collapse
wifi works? not for me? i have at&t
ModestMouse1312 said:
wifi works? not for me? i have at&t
Click to expand...
Click to collapse
i have at&t too and it works pretty well for me. I was playing with some settings and suddenly wifi networks popped up and got connected. I then tested if the internet is working by using both facebook and browser. It is working pretty fine for me. Will post screenshots if needed
saketh91 said:
i have at&t too and it works pretty well for me. I was playing with some settings and suddenly wifi networks popped up and got connected. I then tested if the internet is working by using both facebook and browser. It is working pretty fine for me. Will post screenshots if needed
Click to expand...
Click to collapse
my backup wont show up in twrp? any help? lol (nevermind didnt copy to the right place xD)
ModestMouse1312 said:
my backup wont show up in twrp? any help? lol
Click to expand...
Click to collapse
backup should be something like this.
/TWRP/BACKUPS/HT34CW900897/2014-06-12--03-27-15.
what I mean by this is that the backup folder should be in sub folder of backups not in backups itself. I already had a backup of my android rom and now I pasted your backup folder in HT34CW900897 folder not in BACKUPS
saketh91 said:
backup should be something like this.
/TWRP/BACKUPS/HT34CW900897/2014-06-12--03-27-15.
what I mean by this is that the backup folder should be in sub folder of backups not in backups itself. I already had a backup of my android rom and now I pasted your backup folder in HT34CW900897 folder not in BACKUPS
Click to expand...
Click to collapse
what did you do to get wifi working?
ModestMouse1312 said:
what did you do to get wifi working?
Click to expand...
Click to collapse
Is it still not working for you? Trust me I did not touch anything. I just restored ur backup file and it worked. If you still dont believe i can post screenshots for you. Btw i am using the oldest firmware. Hboot 1.43. Just for your info(if that really matters)
saketh91 said:
Is it still not working for you? Trust me I did not touch anything. I just restored ur backup file and it worked. If you still dont believe i can post screenshots for you. Btw i am using the oldest firmware. Hboot 1.43. Just for your info(if that really matters)
Click to expand...
Click to collapse
ah, it finally started working after about 30 minutes.
ModestMouse1312 said:
ah, it finally started working after about 30 minutes.
Click to expand...
Click to collapse
finally it worked. now getting gsm and audio working would be a great achievement. I am learning things now and if I am of anyway useful to this project I would gladly contribute.
saketh91 said:
finally it worked. now getting gsm and audio working would be a great achievement. I am learning things now and if I am of anyway useful to this project I would gladly contribute.
Click to expand...
Click to collapse
go for it man, if you can develop it first just take over
ModestMouse1312 said:
go for it man, if you can develop it first just take over
Click to expand...
Click to collapse
when I try to execute this command "./rootstock-touch -p pps:rsalveti/ppa" I get this error. please help me with this
saketh91 said:
when I try to execute this command "./rootstock-touch -p pps:rsalveti/ppa" I get this error. please help me with this
Click to expand...
Click to collapse
you need to install the debootstrap utility , I guess a sudo apt-get install debootstrap will do it
cuyo11 said:
you need to install the debootstrap utility , I guess a sudo apt-get install debootstrap will do it
Click to expand...
Click to collapse
thank you that worked like a charm. I should have double checked the dependencies installed
Error 509 on link, can someone please mirror it?
Q&A for [Kernel] [12/1] FIRE-ICE [R14]
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 [Kernel] [12/1] FIRE-ICE [R14]. 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!
flashed ok on new factory image
5.0.1 stock / flashed cf autoroot/flashify/twrp ... flashed your rom/su/gapps/ set up the tablet and then flashed fire/ice. Tablet seems smooth and zippy . also of note previous to flashing your rom I also flashed the new factory image unencrypted if that matters. Thanks for your efforts on the rom.
fazbender said:
5.0.1 stock / flashed cf autoroot/flashify/twrp ... flashed your rom/su/gapps/ set up the tablet and then flashed fire/ice. Tablet seems smooth and zippy . also of note previous to flashing your rom I also flashed the new factory image unencrypted if that matters. Thanks for your efforts on the rom.
Click to expand...
Click to collapse
Cheers
ROM? What ROM
posted in the wrong thread : - / . meant to post in the lollipolosa rom thread. so in my previous post just swap out the word rom and insert kernel ,,,,hmmm still doesn't work .
lol - ty for your efforts with the kernel.
Just a quick heads up for those that don't know.
Since some of the terminal emulators don't seem to work and the one that I was able to get working doesn't allow copy and paste.
ROM toolbox pro, and I'm sure plenty of other apps allow you to make the value changes a lot easier and quicker than typing it all out.
jaben2 said:
Just a quick heads up for those that don't know.
Since some of the terminal emulators don't seem to work and the one that I was able to get working doesn't allow copy and paste.
ROM toolbox pro, and I'm sure plenty of other apps allow you to make the value changes a lot easier and quicker than typing it all out.
Click to expand...
Click to collapse
You need to copy it to clipboard
What is the "lite version of the Nexus 9"?
Sent from my Nexus 9 using Tapatalk
TriadX1 said:
What is the "lite version of the Nexus 9"?
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
The nexus 9 with data
Encryption still enabled
First off, I'd like to say that I love your kernel, as it has solved my main issue of overheating on my tablet.
My problem is that despite my best efforts, it still says that the tablet is encrypted. I'm currently on the latest Lollipopalooza running the latest Fire and Ice Kernel and the your modified TWRP recovery (I've tried both R1 and testR2). Doing a factory reset displays the message that it was successfully decrypted, but it still shows up as encrypted under Security settings. I'm also unable to perform a factory reset from adb because it says that the file system f2fs is not supported, and it shows this message despite the fact that I had formatted it back to ext4 through TWRP in a previous attempt to get things in working order. I've attached some screen shots of my security settings as well as the output from fstab.flounder and fstab.flounder64, both showing that it is encryptable. I apologize if this has been posted before, but for the life of me I was not able to find anything that could help. I appreciate any help
JackTheRipper1891 said:
First off, I'd like to say that I love your kernel, as it has solved my main issue of overheating on my tablet.
My problem is that despite my best efforts, it still says that the tablet is encrypted. I'm currently on the latest Lollipopalooza running the latest Fire and Ice Kernel and the your modified TWRP recovery (I've tried both R1 and testR2). Doing a factory reset displays the message that it was successfully decrypted, but it still shows up as encrypted under Security settings. I'm also unable to perform a factory reset from adb because it says that the file system f2fs is not supported, and it shows this message despite the fact that I had formatted it back to ext4 through TWRP in a previous attempt to get things in working order. I've attached some screen shots of my security settings as well as the output from fstab.flounder and fstab.flounder64, both showing that it is encryptable. I apologize if this has been posted before, but for the life of me I was not able to find anything that could help. I appreciate any help
Click to expand...
Click to collapse
Ok hmm
do this
in Recovery
enter adb
and do
cat /proc/version
Give me the output
You know what
screw it I make a flashable zip I would do the same thing
as a factory reset
USBhost said:
Ok hmm
do this
in Recovery
enter adb
and do
cat /proc/version
Give me the output
You know what
screw it I make a flashable zip I would do the same thing
as a factory reset
Click to expand...
Click to collapse
I appreciate the speedy response . Anyway, here is the output I got from recovery:
Code:
/ # cat /proc/version
I:Actual command is: 'cd "/" && cat /proc/version 2>&1'
Linux version 3.10.40[FIRE-ICE]RECOVERY ([email protected]) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 4.9-2014.11) ) #1 SMP PREEMPT Fri Dec 5 20:58:57 PST 2014
JackTheRipper1891 said:
I appreciate the speedy response . Anyway, here is the output I got from recovery:
Code:
/ # cat /proc/version
I:Actual command is: 'cd "/" && cat /proc/version 2>&1'
Linux version 3.10.40[FIRE-ICE]RECOVERY ([email protected]) (gcc version 4.9.3 20141031 (prerelease) (Linaro GCC 4.9-2014.11) ) #1 SMP PREEMPT Fri Dec 5 20:58:57 PST 2014
Click to expand...
Click to collapse
Hmm dont know why it does not work
But any way
In about 5min the flashable zip will be ready
---------- Post added at 04:19 PM ---------- Previous post was at 03:56 PM ----------
ok just boot this recovery
like
fastboot boot test.img
then go to install
and move to /res
then you will see a zip called
factory reset.zip
then flash
note i have not tested it so its up to you
to flash it
https://drive.google.com/file/d/0B1cOHQ70J9vlNEN3bHpyVmkzb3M/view?usp=sharing
USBhost said:
Hmm dont know why it does not work
But any way
In about 5min the flashable zip will be ready
---------- Post added at 04:19 PM ---------- Previous post was at 03:56 PM ----------
ok just boot this recovery
like
fastboot boot test.img
then go to install
and move to /res
then you will see a zip called
factory reset.zip
then flash
note i have not tested it so its up to you
to flash it
Click to expand...
Click to collapse
I get an error
Code:
E:Mount: Unable to find partition for path '/res'
Error flashing zip '/res/factory reset.zip
JackTheRipper1891 said:
I get an error
Code:
E:Mount: Unable to find partition for path '/res'
Error flashing zip '/res/factory reset.zip
Click to expand...
Click to collapse
Hmm ok
1 sek
But in the mean time
manually format data to ext4
then back to f2fs
USBhost said:
Hmm ok
1 sek
But in the mean time
manually format data to ext4
then back to f2fs
Click to expand...
Click to collapse
Alright I'll give it a try when I return home in a few hours. Thank you for the help so far
JackTheRipper1891 said:
Alright I'll give it a try when I return home in a few hours. Thank you for the help so far
Click to expand...
Click to collapse
ok i feel so stupid now lol
just format data to f2fs
and your awesome
USBhost said:
ok i feel so stupid now lol
just format data to f2fs
and your awesome
Click to expand...
Click to collapse
I really don't want to be a bother, but it's still encrypted
I even tried manually changing it to ext4 and back again to f2fs, but no change
JackTheRipper1891 said:
I really don't want to be a bother, but it's still encrypted
I even tried manually changing it to ext4 and back again to f2fs, but no change
Click to expand...
Click to collapse
NP at all
Thats one stubborn nexus 9
You know what
I will edit my kernel to
Not support encrypted data
To see if that does it
Also can you give me the output of
su -c mount
USBhost said:
NP at all
Thats one stubborn nexus 9
You know what
I will edit my kernel to
Not support encrypted data
To see if that does it
Also can you give me the output of
su -c mount
Click to expand...
Click to collapse
Thanks for the help
Ive attached a screenshot of the output.
JackTheRipper1891 said:
Thanks for the help
Ive attached a screenshot of the output.
Click to expand...
Click to collapse
ok lets get this on the shell lol
ok download force format data.zip && boot.img
then move force format data.zip to /cache
then boot to recovery
then flash it
then format cache to f2fs
then boot to bootloader
then do
fastboot flash boot boot.img
then reboot
lets hope this does it lol
CM11 M for d605
it is based on Varcain kernel and device tree, much thanks for your work and releasing source code!
Just woke up from my slumber, because I realized, that my domain expired and links get broken.
Sorry, but nothing new, only links fix
Kernel
what is new:
More free ram, over 35MB
Screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=3146159&d=1422877546
Added new cpu governor - Interactive, default scheduler is noop
Kernel modules for zRam, usb storage, gamepads, and others
Support for USB-OTG with external charger, based on ziddey's work for Mako
Source: http://forum.xda-developers.com/nexus-4/orig-development/usb-otg-externally-powered-usb-otg-t2181820
Fixed offline charging
zRam control
what is that:
Very simple app, setup zram by yourself and watch stats. zRam settings won't survive reboot!
After creation zram device, for short time, one value in stats is temporally broken because no data .
Screenshot: http://forum.xda-developers.com/attachment.php?attachmentid=3146160&d=1422877546
Framework
patched framework and settings for usb flashdisk
few UI colors changes
Install
Wipe data and cache. Then just flash archive in recovery.
Download: http://46.28.109.28/cm.zip
Source
Somehow stable source code is on my github, PM me for questions.
https://github.com/puresoul
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU Affero General Public License for more details.
OTG will work only with external charger. So you need something like that.
shall I wipe something after installation? if something goes wrong, will cmw recovery start anyway(i've installed v3 today)?
You may wipe cache and dalvik cache, but it is not needed to wipe something. Nope, installation process will not touch recovery partition.
cescom said:
shall I wipe something after installation? if something goes wrong, will cmw recovery start anyway(i've installed v3 today)?
Click to expand...
Click to collapse
Puresoul_CZ said:
You may wipe cache and dalvik cache, but it is not needed to wipe something. Nope, installation process will not touch recovery partition.
Click to expand...
Click to collapse
It works perfectly also without any wipe (i was too happy to try this that i forgot to wipe), thanks! :fingers-crossed:
No problem, thanks.
Puresoul_CZ said:
No problem, thanks.
Click to expand...
Click to collapse
Great work for RAM:good:, but i've gone to the gallery and sdcard is not recognised anymore
I have the same problem. Where I can find zRam settings?
Could you include rtl8192cu driver with your build?
edit: everything is now bundled together as a whole rom.
dundee81 said:
I have the same problem. Where I can find zRam settings?
Click to expand...
Click to collapse
Ok, thx What about mounting sdcard?
please send me dmesg log
immediately after reboot type in terminal, su; dmesg > /cache/dmesg.log
and send me that file
Thanks
Puresoul_CZ said:
please send me dmesg log
immediately after reboot type in terminal, su; dmesg > /cache/dmesg.log
and send me that file
Thanks
Click to expand...
Click to collapse
where can i send it?
Using terminal emulator, shall i use adb? because terminal emulator takes a lot to start
yes, adb is way batter
cescom said:
where can i send it?
Using terminal emulator, shall i use adb? because terminal emulator takes a lot to start
Click to expand...
Click to collapse
i suspect kernel modules, but for sure need to check log.
this may be the case, i forgot to add the permision file. Update: http://frame.jailbrake.cz/boot_v2.zip
boot_v2
I don´t read sd card
Puresoul_CZ said:
this may be the case, i forgot to add the permision file. Update: http://frame.jailbrake.cz/boot_v2.zip
Click to expand...
Click to collapse
set perm:some changes failed (cwm)
did you flash boot.zip or boot_v2.zip?
sinnombrexxl said:
I don´t read sd card
Click to expand...
Click to collapse
check please file handheld_core_hardware.xml
if exists at /system/etc/permissions/handheld_core_hardware.xml
here is that file: http://frame.jailbrake.cz/hch.zip
cescom said:
set perm:some changes failed (cwm)
Click to expand...
Click to collapse
[RECOVERY] TWRP 3.5.0-0 - TeamWin Recovery Project
Introduction:
Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It's 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.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Easy selection of internal/external storage
In addition to the above new features, TWRP features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe, and run a backup.
We are looking for other talented developers, themers, and device maintainers if they are interested in helping with a free, open source project.
Source Code:
GitHub - https://github.com/TeamWin/android_bootable_recovery
Gerrit Instance - http://gerrit.twrp.me
If you have made your own TWRP build for an unsupported device, please let us know. We might add your build to the list of unofficial builds. Bear in mind that we are working hard to add more devices and we may add your device to our official build list later.
flame Device Config: https://github.com/bigbiff/android_device_google_coral
DOWNLOAD:
Please go to https://twrp.me to download the device image.
A11 Testing:
https://build.twrp.me/test/flame/twrp-3.6.0-0-test1-flame.img- updated for lineage-18.1 booting
Old info:
Hello, this is a test build for flame users (will work on coral crosshatch/blueline later). The image is pretty safe for backing up now.
So far I have decryption working, touch, adb and backup and restore seems to work. Super partition volumes can be mounted, and the super partition can be backed up.
Not working: sideload and fastbootd
May FW Date https://build.twrp.me/test/flame/twrp-3.3.1-0-test1-flame.img
June FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test2-flame.img
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test4-flame.img
- fix super partition restore
- fix persist partition restore
July FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test5-flame.img
- allow repacking of TWRP boot.img
- magisk currently doesn't work
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test6-flame.img
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test7-flame.img
- fix repacking TWRP with magisk
August FW Date https://build.twrp.me/test/flame/twrp-3.4.0-0-test8-flame.img
- multiuser decryption support
- fastbootd support
3.5.0-0: Android 11 bringup
https://build.twrp.me/test/flame/twrp-3.5.0-0-test1-flame.img
https://build.twrp.me/test/flame/twrp-3.5.0-0-test2-flame.img
- Titan M Wipe working on Format Data
- Apex fixes for flattened directories
- Credit to @Freak07 https://github.com/freak07/FLORAL - using his kernel as a Coral/Flame TWRP base
http://twrp.me
What to backup
* super
* data
* persist
* boot
* any other partition desired
What to restore
* super
* data
* boot - depending on ROM support
Please just restore persist if you have a failed partition. I do not recommend restoring backups from phone to phone unless you know what you are doing.
Repacking TWRP into Boot partition
To repack TWRP into the boot partition to override stock recovery when rebooting to recovery, perform the following steps
1. adb push <latest_boot.img> /sdcard/
2. reboot to bootloader and fastboot latest boot.img of TWRP
3. Go to Install
4. Touch Install Image
5. Select your boot.img from /sdcard
6. Swipe to confirm flash
7. Reboot to recovery and android to verify installation
TWRP won't Boot?
Make sure you have a kernel that supports the R DTBO and LZMA ramdisk starting with test5 such as https://forum.xda-developers.com/pi...nel-kirisakuraq-1-0-0-pixel-4-xl-aka-t3992213
Is this just for flame? Or both coral and flame? Reason I ask is because the 2 devices have significant differences, and if it's just for flame, you'll want to throw it in the regular Pixel 4 subforum
This is for flame as described. I will work on coral next.
They share the same device tree btw.
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
bigbiff said:
Weird I thought I chose pixel 4 forum. Asking for this thread to be moved.
Click to expand...
Click to collapse
Ah man lol got me all excited!
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Can confirm this works for flashing. Booted the image and then ADB pushed magisk and kernel and both flashed successfully!
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Great work to see, we are finally not tied to magisk for flashing things now
Mrcactuseater said:
Will try removing lockscreen security next attempt to gain access to internal storage which should likely work.
Click to expand...
Click to collapse
wont work to @my end
2WildFirE said:
Thanks long awaited :good:
Will try later..
ok fastboot boot boots fine to TWRP but decryption wont work for me
https://paste.omnirom.org/view/e9536f05
Click to expand...
Click to collapse
Can you paste logcat output too?
Please guys don't just say it doesn't work. I need recovery.log and logcat so I can debug issues.
2WildFirE said:
wont work to @my end
Click to expand...
Click to collapse
Can you please post recovery.log and logcat?
bigbiff said:
Can you please post recovery.log and logcat?
Click to expand...
Click to collapse
Yep
Is ADB logcat -l the correct one?
2WildFirE said:
Yep
Is ADB logcat -l the correct one?
Click to expand...
Click to collapse
I usually do in adb shell
logcat > /tmp/logcat.txt
Then adb pull /tmp/logcat.txt
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
2WildFirE said:
OK here logcat https://paste.omnirom.org/view/9caa8b33
And recovery.log https://paste.omnirom.org/view/3c26a706
hope it helps
Click to expand...
Click to collapse
Can you tell me your android build version?
bigbiff said:
can you tell me your android build version?
Click to expand...
Click to collapse
qq3a.200605.001
just to thank you a lot bigbiff for putting so much work and efforts on this, you are great. hope you can sort this out, best luck!! (a p3 user) :fingers-crossed::good: sorry for the ot
2WildFirE said:
qq3a.200605.001
Click to expand...
Click to collapse
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
bigbiff said:
There was an update to the platform version, please test https://build.twrp.me/test/flame/twrp-3.4.0-0-test1-flame.img
Click to expand...
Click to collapse
Thanks will try :good:
@bigbiff
yeah decryption works fine now
@bigbiff
Sorry for dump questions, but if I want to backup, is it enough to backup super and data partition?
Yea I tried to follow this Hovatek but it didn't work...
Honestly I'm to finished trying to port this recovery someone help me..
hi i found yr new thread
jjgvv said:
hi i found yr new thread
Click to expand...
Click to collapse
yup I just tried twrp builder, but I where is internal and emulated storage?
maybe I can port to you soon I use Android image studio on my tab to extract
hellofriendlymanveriosns said:
yup I just tried twrp builder, but I where is internal and emulated storage?
Click to expand...
Click to collapse
?
please elaborate
jjgvv said:
?
please elaborate
Click to expand...
Click to collapse
Well when it says to back up image I only brings up two directories :
emulated (which im assumin is sd card)
and
Internal (which I assume is the actual phone storage)
but my image dosn't show up for either
hellofriendlymanveriosns said:
Well when it says to back up image I only brings up two directories :
emulated (which im assumin is sd card)
and
Internal (which I assume is the actual phone storage)
but my image dosn't show up for either
Click to expand...
Click to collapse
In TWRP or What?
jjgvv said:
In TWRP or What?
Click to expand...
Click to collapse
No I don't have twrp yet, the apk of "TWRP BUILDER"
I thought I would get somewhere with it but it just wouldn't detect anything...
To get things work TWRP Builder needs to create a copy of phone's stock recovery.img - what's a bootable image that is written to the /recovery partition on an Android device.
If your phone has A/B-partition layout, then TWRP Builder can''t find a partition named /recovery this because such a partition simply doesn't exist. Resume: TWRP Builder in this case isn't useful for you, you've to create TWRP at your own ( DIY ) .
To find out whether your phone has an A/B-partition-system Android installed, or not, run
Code:
adb devices
adb shell "getprop ro.build.ab_update"
If TRUE is returned, Android is a A/B-partition-system one.
BTW:
TWRP requires device's bootloader got successfully unlocked.