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

gubacsek

Senior Member
Jun 18, 2010
260
308
93
Any help can I get
I/O error usually means your partition is full (most probably /system). You need to free up some space by deleting not needed packages (apk files) from /system/app or /system/priv-app and then re-flash the ARISE zip.
But this thread is not about ARISE... Please post your problems in the ARISE thread, and let this one be about TWRP recovery!
If you manage to boot into recovery, and decrypt the data partition, then my work is done. From here, it is about your system and the mod that you are trying to flash.

Thanks!
 
  • Like
Reactions: rockingondrums

kiran8631

Senior Member
Oct 3, 2015
227
49
48
I/O error usually means your partition is full (most probably /system). You need to free up some space by deleting not needed packages (apk files) from /system/app or /system/priv-app and then re-flash the ARISE zip.
But this thread is not about ARISE... Please post your problems in the ARISE thread, and let this one be about TWRP recovery!
If you manage to boot into recovery, and decrypt the data partition, then my work is done. From here, it is about your system and the mod that you are trying to flash.

Thanks!
Thanks bro got it working
 

gubacsek

Senior Member
Jun 18, 2010
260
308
93
@gubacsek could you upload the device tree recovery files so people can see what was changed? :confused:

Sent from my Pixel using XDA Labs
I was thinking a lot about this :)
I will of course do it, because I would like to help the TWRP guys to include these changes in their next release.
But right now it is a kind of a big mess :) I added some debug lines which are not needed, I was acting out of rage, and the script copies the entire system and vendor lib folders instead of what is really needed so it is not at all professional :)
I will clean it up a bit, then I'll push my changes.
For now please check /sbin/pulldecryptfiles.sh, /etc/recovery.fstab, and the init rc files. Those are the biggest changes. There is also one option in Boardconfig.mk, to enable FBE (file based encryption) instead of vold decrypt.
 

glyphsays

New member
Apr 13, 2016
2
0
0
I made the mistake of updating to DP4 while expecting TWRP and everything to work as normal. All I want is to flash back to purenexus, but this update isn't making it easy. Can I flash PN using this TWRP mod, or should I just wait until an official release?
 

piperx

Senior Member
Nov 22, 2011
1,201
847
143
Cheektowaga, NY
I made the mistake of updating to DP4 while expecting TWRP and everything to work as normal. All I want is to flash back to purenexus, but this update isn't making it easy. Can I flash PN using this TWRP mod, or should I just wait until an official release?
You can't downgrade like that.

Just flash stock image to both slots, then flash pure nexus

Sent from my Pixel using XDA-Developers Legacy app
 

gubacsek

Senior Member
Jun 18, 2010
260
308
93
I made the mistake of updating to DP4 while expecting TWRP and everything to work as normal. All I want is to flash back to purenexus, but this update isn't making it easy. Can I flash PN using this TWRP mod, or should I just wait until an official release?
In my opinion the way for you to go is to make a backup of everything (internal sd, pictures, music, everything, best the whole internal SD as it is) because this method will reformat your phone and you will loose everything. Download and then flash the stock android N factory image via fastboot (that should flash back your old bootloader, and reformat your phone as it should be for android N), and finally install the stock TWRP recovery, flash purenexus, and restore back your stuff from backup to internal SD.

This would be the cleanest approach, not the easiest... You could start with only flashing a few partitions, flashing purenexus, or even keep the /data partition, but this way god and google only knows what will happen...

After the factory image flash via fastboot, you could try to use my modded recovery, but I never tested it under android N. Theoretically it should work, but I can't be 100% certain it will..... If you dare to test it, please report back, so I know :D

Thanks!
 
Last edited:

glyphsays

New member
Apr 13, 2016
2
0
0
In my opinion the way for you to go is to make a backup of everything (internal sd, pictures, music, everything, best the whole internal SD as it is) because this method will reformat your phone and you will loose everything. Download and then flash the stock android N factory image via fastboot (that should flash back your old bootloader, and reformat your phone as it should be for android N), and finally install the stock TWRP recovery, flash purenexus, and restore back your stuff from backup to internal SD.

This would be the cleanest approach, not the easiest... You could start with only flashing a few partitions, flashing purenexus, or even keep the /data partition, but this way god and google only knows what will happen...
You can't downgrade like that.

Just flash stock image to both slots, then flash pure nexus
Unfortunately after upgrading to DP3/4 any time I flash the factory N image (ANY factory N image) and try to boot TWRP, TWRP always sends me to a black screen that forces me to hard reset. After the upgrade I'm unable to downgrade and boot TWRP, even after flashing factory images.
 

mngdew

Senior Member
Aug 17, 2010
606
96
0
Los Angeles
What did you do?
Follow the step below.
1. Rename "audio.effects.conf" in /system/vendor/etc to "audio.effects.conf.bak"
2. Download ARISE 3.09. https://www.androidfilehost.com/?fid=529152257862712061 and save it to "Internal Memory"
3. Donwload "arise_customize.prop" https://drive.google.com/file/d/0B-0lMNJzHcabRFc3SHYxclFYNlk/view?usp=sharing, and save it to "Internal Memory". This is my prop, and it only flashes the V4A core only. If you want to flash additional stuff you can modify the prop further before you flash.
4. fastboot to TWRP to flash ARISE 3.09.
5. Upon reboot, make sure the access to the storage is enabled for V4A.

Hope this works for you, too.
 

piperx

Senior Member
Nov 22, 2011
1,201
847
143
Cheektowaga, NY
Unfortunately after upgrading to DP3/4 any time I flash the factory N image (ANY factory N image) and try to boot TWRP, TWRP always sends me to a black screen that forces me to hard reset. After the upgrade I'm unable to downgrade and boot TWRP, even after flashing factory images.
Flash the n factory image

Download TWRP 3.0.2- rc1 zip & image

https://dl.twrp.me/sailfish/

Fastboot the twrp image and install the zip

Install pn



Sent from my Pixel using XDA-Developers Legacy app
 

maflin18

Senior Member
Apr 4, 2015
431
124
0
Iowa City
plus.google.com
Follow the step below.
1. Rename "audio.effects.conf" in /system/vendor/etc to "audio.effects.conf.bak"
2. Download ARISE 3.09. https://www.androidfilehost.com/?fid=529152257862712061 and save it to "Internal Memory"
3. Donwload "arise_customize.prop" https://drive.google.com/file/d/0B-0lMNJzHcabRFc3SHYxclFYNlk/view?usp=sharing, and save it to "Internal Memory". This is my prop, and it only flashes the V4A core only. If you want to flash additional stuff you can modify the prop further before you flash.
4. fastboot to TWRP to flash ARISE 3.09.
5. Upon reboot, make sure the access to the storage is enabled for V4A.

Hope this works for you, too.
Tried this and got stuck on Google boot logo for 20+ mins. ADB reboot and got stuck again. Flashed modified flashall, back to normal now. Still no viper :(
 

bbender716

Senior Member
Sep 11, 2014
790
230
63
Chicago
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...
Hmm yeah arise gets mine frozen on the boot screen. Is that an issue with space on /system?
 

imaverik

Senior Member
May 17, 2010
275
67
48
audio not working?

This is probably something with "selinux" being on. Most of the arise and v4a versions ive ever seen need the selinux enforce=1
 

gubacsek

Senior Member
Jun 18, 2010
260
308
93
Hmm yeah arise gets mine frozen on the boot screen. Is that an issue with space on /system?
Don't think so. I had 400+mb free in system, still frozen.
Which version did you flash? For me, Deuteronomy 309 is working. Fastboot flash system and vendor back, and then try to flash that in recovery!
But again: if you can boot my modded recovery, and it can decrypt your data partition, then my work is done. This is what I made possible. The rest is up to your rom, and what you try to flash....
 
Last edited:

gubacsek

Senior Member
Jun 18, 2010
260
308
93
Great job on this! DP4 on Pixel Xl. Booted into Twrp just fine. Flashed Twrp RC2 in recovery and so far no issues.
I'm glad you like it :D Can you please let me know if you can still boot into recovery after booting Android once, or after flashing Supersu (if you intend to flash it anyway :D) ? Just asking, because right after flashing my modded TWRP, I could reboot into recovery from the fastbooted one, but after booting the OS once, I couldn't anymore. I will take some time to check things later, I just would like to get a confirmation if it is the same for others too...
And to be honest, I don't understand why the normal TWRP RC2 would work if you flash it :D
 

cjkacz

Inactive Recognized Developer
May 11, 2013
1,310
2,053
153
Sardinia
www.teamoctos.com
I'm glad you like it :D Can you please let me know if you can still boot into recovery after booting Android once, or after flashing Supersu (if you intend to flash it anyway :D) ? Just asking, because right after flashing my modded TWRP, I could reboot into recovery from the fastbooted one, but after booting the OS once, I couldn't anymore. I will take some time to check things later, I just would like to get a confirmation if it is the same for others too...
And to be honest, I don't understand why the normal TWRP RC2 would work if you flash it :D
I first fastboot booted this modded Twrp. Once Twrp booted I flashed RC2, rebooted recovery and saw that it worked. I booted into DP4 and it was fine. Went back into bootloader menu and selected recovery. It booted me into RC2 just fine. I made a backup of Android O. I then tried flashing magisek for Pixel. Rom boots fine but no root exists. I may try SuperSU at some point but I do not really have a need for root atm