• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[togari] TWRP Recovery 3.0.0

Status
Not open for further replies.
Search This thread

alia5

Senior Member
Apr 24, 2011
208
271
Regensburg
TWRP 3. for Xperia Z Ultra aka togari

Up-to-date TWRP with new looks and functional display/brightness settings, and mountpoints like in sony-aosp marshmallow.

Code:
#include <std_disclaimer.h>
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

Download: AndroidFileHost

Sources: Github

Make sure you have installed the new bootloader and have flashed the latest stock Sony ROM at least once since.

Then, erase the recovery partition and flash TWRP using fastboot.
Code:
fastboot erase recovery
fastboot flash recovery twrp-3.0.0-togari.img

Enter recovery:
Switch off the phone
Hold Vol-Down & Power button simultaneously until the phone vibrates
Release the power button and keep holding Vol-Down until the Sony logo appears

Thanks to @Dees_Troy for twrp
Thanks to Sony AOSP for basic device trees

XDA:DevDB Information
TWRP 3.0.0, Tool/Utility for the Sony Xperia Z Ultra

Contributors
alia5
Source Code: https://github.com/omnirom/android_bootable_recovery/tree/android-6.0


Version Information
Status: Snapshot

Created 2016-02-13
Last Updated 2016-02-13
 

pTeronaut

Senior Member
May 28, 2012
708
217
Lafayette, IN
C6806

Device goes into reboot loop when trying to enter. Need instructions on how to capture logcat as ADB LOGCAT cannot find device until OS or recovery is loaded.
 
  • Like
Reactions: teeve

alia5

Senior Member
Apr 24, 2011
208
271
Regensburg
I'm guessing you also don't have a recovery.log anywhere on your phone?

Anyway I had some problems by just applying the TA-update with EMMA with some custom-roms, by flashing the newest stock version that whole song and dance got solved (C6833)
But as you stated in some other thread, just applying the TA update doesn't work for you on the C6806, and you already have had flashed the newest stock fw, so...
I guess I'm going to ask some people and see...

BTW: what happens if you "fastboot boot PATH_NAME_OF_RECOVERY.img" ?
 
  • Like
Reactions: teeve

TimeTurn

Senior Member
Dec 5, 2010
282
50
Berlin
AFAIK the C6806 is the Google Play Edition - that has a completely different boot method. Don't try this on the GPe.

Why has this thread been opened? We already have a TWRP 3 thread here.
 
Last edited:

jimmkind

Senior Member
Jun 20, 2010
122
39
Stockholm
In previous versions it was possible to reboot into recovery from rom. cm12.1 in my case. with yours and the others in the forum it results into bootloop. only way to enter recovery is to hold power+volume down.
 
  • Like
Reactions: teeve

alia5

Senior Member
Apr 24, 2011
208
271
Regensburg
AFAIK the C6806 is the Google Play Edition - that has a completely different boot method. Don't try this on the GPe.
There also is a non-GPE C6806 (afaik) and I'm guessing @pTeronaut would've said if he has a GPE, if he has, well... then why does he even try since this is not the gpe section

Why has this thread been opened? We already have a TWRP 3 thread here.
The other TWRP 3 has a missing symlink in the init.rc script, which causes problems when trying to flash marshmallow roms

In previous versions it was possible to reboot into recovery from rom. cm12.1 in my case. with yours and the others in the forum it results into bootloop. only way to enter recovery is to hold power+volume down.

That's because the most roms (all of them available here?) don't support booting to recovery on the separate recovery partition. The roms need to have a patch in order to be able to boot to recovery on separate recovery partition.
When the marshmallow roms finally arrive (aka. ready to be shared in public) this will no longer be a problem
 
Last edited:

pTeronaut

Senior Member
May 28, 2012
708
217
Lafayette, IN
AFAIK the C6806 is the Google Play Edition - that has a completely different boot method. Don't try this on the GPe.

Why has this thread been opened? We already have a TWRP 3 thread here.
You know incorrectly, The GPE is based on the original North American LTE version of the Xperia Z Ultra C6806, the only difference being the storage's partitioning, 'Xperia' being removed from the device's branding and '_gpe' being tagged onto the model code.
 
Last edited:

jimmkind

Senior Member
Jun 20, 2010
122
39
Stockholm
There also is a non-GPE C6806 (afaik) and I'm guessing @pTeronaut would've said if he has a GPE, if he has, well... then why does he even try since this is not the gpe section


The other TWRP 3 has a missing symlink in the init.rc script, which causes problems when trying to flash marshmallow roms



That's because the most roms (all of them available here?) don't support booting to recovery on the separate recovery partition. The roms need to have a patch in order to be able to boot to recovery on separate recovery partition.
When the marshmallow roms finally arrive (aka. ready to be shared in public) this will no longer be a problem
the recovery by Saatvik Shukla had this function working. the version of that recovery was 2.8.7.0.
 

pTeronaut

Senior Member
May 28, 2012
708
217
Lafayette, IN
I'm guessing you also don't have a recovery.log anywhere on your phone?

Anyway I had some problems by just applying the TA-update with EMMA with some custom-roms, by flashing the newest stock version that whole song and dance got solved (C6833)
But as you stated in some other thread, just applying the TA update doesn't work for you on the C6806, and you already have had flashed the newest stock fw, so...
I guess I'm going to ask some people and see...

BTW: what happens if you "fastboot boot PATH_NAME_OF_RECOVERY.img" ?
The recovery boots.
I'm beginning to think that the C6806 never got the recovery partition, and that Saatvik Shukla (who's TWRP works) & championswimmer (whose CWM works) have done something strange to get theirs working.

No recovery.log. :(
 
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    TWRP 3. for Xperia Z Ultra aka togari

    Up-to-date TWRP with new looks and functional display/brightness settings, and mountpoints like in sony-aosp marshmallow.

    Code:
    #include <std_disclaimer.h>
    /*
     * Your warranty is now void.
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    Download: AndroidFileHost

    Sources: Github

    Make sure you have installed the new bootloader and have flashed the latest stock Sony ROM at least once since.

    Then, erase the recovery partition and flash TWRP using fastboot.
    Code:
    fastboot erase recovery
    fastboot flash recovery twrp-3.0.0-togari.img

    Enter recovery:
    Switch off the phone
    Hold Vol-Down & Power button simultaneously until the phone vibrates
    Release the power button and keep holding Vol-Down until the Sony logo appears

    Thanks to @Dees_Troy for twrp
    Thanks to Sony AOSP for basic device trees

    XDA:DevDB Information
    TWRP 3.0.0, Tool/Utility for the Sony Xperia Z Ultra

    Contributors
    alia5
    Source Code: https://github.com/omnirom/android_bootable_recovery/tree/android-6.0


    Version Information
    Status: Snapshot

    Created 2016-02-13
    Last Updated 2016-02-13
    1
    C6806

    Device goes into reboot loop when trying to enter. Need instructions on how to capture logcat as ADB LOGCAT cannot find device until OS or recovery is loaded.
    1
    I'm guessing you also don't have a recovery.log anywhere on your phone?

    Anyway I had some problems by just applying the TA-update with EMMA with some custom-roms, by flashing the newest stock version that whole song and dance got solved (C6833)
    But as you stated in some other thread, just applying the TA update doesn't work for you on the C6806, and you already have had flashed the newest stock fw, so...
    I guess I'm going to ask some people and see...

    BTW: what happens if you "fastboot boot PATH_NAME_OF_RECOVERY.img" ?
    1
    In previous versions it was possible to reboot into recovery from rom. cm12.1 in my case. with yours and the others in the forum it results into bootloop. only way to enter recovery is to hold power+volume down.