[TWRP][Z3][UNOFFICIAL] twrp 3.2.1-2 for z3 [2018-03-28]

nailyk · Oct 27, 2017 at 12:55 PM

maxi16 said:
Ok I tested the command.

Don't come in the recovery. The phone did a reboot after I send the command and trys to come into the recovery. No success.
A few seconds after that it makes a second reboot straight to the system. So I will ask the maintainer.

this seems to be the fix for that issue (on omnirom).
Please highlight me into your rom thread while posting it.

vikivegito · Oct 27, 2017 at 5:12 PM

@nailyk why twrp new versions are not available for d6633?

nailyk · Oct 27, 2017 at 6:17 PM

vikivegito said:
@nailyk why twrp new versions are not available for d6633?

as we are working on unification, my sources cannot build single or dual independently. Releasing this will cause most breaks than fixes.
A bit more patience is needed

jrkb · Nov 7, 2017 5 1 0

doesn't really work

I love this development, but unfortunately I cannot successfully boot into twrp.
I have a D6603, when I flash, it gives no errors

Code:

$ fastboot flash recovery twrp_leo_2017-10-02.img
sending 'recovery' (13624 KB)...
OKAY [  0.431s]
writing 'recovery'...
OKAY [  0.901s]
finished. total time: 1.332s

but then it just boots into normal rom, whatever I try

I remembered that once (with another phone) I could directly boot into twrp from fastboot like that:

Code:

$ fastboot boot twrp_leo_2017-10-02.img
downloading 'boot.img'...
OKAY [  0.429s]
booting...
OKAY [  0.056s]

but now when I do this, the screen is black (with backlight) and nothing goes.

I just updated my build with the latest available via Emma for me (23.1.A.1.28).

What am I doing wrong?
I know there should be a newer build (.291), but Emma doesn't show it. Could that be the issue?
I also got FlashTool, but I don't couldn't find proper .291 ftf files (I guess you shouldn't trust files which end in *.img.exe

)

maxi16 · Nov 7, 2017

Did you try the on/off and vol- hardware button?

Because Nailyk mentioned that the function boot to recovery through fastboot/App is function that the rom maintainer handled.

I using also this recovery and Carbon Rom 5.1 and the only way to get in the recovery in my case are the hardware button.

I think the stock Rom doesn't support the fastboot function.

jrkb · Nov 7, 2017 5 1 0

thx for your reply.
yes, I tried all variations:
(1)
- flash recovery
- turn off phone
- push power
- push vol- repeatedly
-> boots into stock rom
(2)
- flash recovery
- turn off phone
- push power
- push vol+ repeatedly
-> always boots into stock rom
(1)
- flash recovery
- turn off phone
- push power
- push vol- and vol+ repeatedly
-> always boots into stock rom

you may be right, that it doesn't work with fastboot, because when i try

Code:

(sudo) fastboot reboot recovery

it only shows me the manpage of fastboot.... not sure where to go on here

brianpee · Nov 7, 2017 at 5:52 PM

jrkb said:
...

Try power off, hold volume down, and then press power button.

maxi16 · Nov 7, 2017

brianpee said:
Try power off, hold volume down, and then press power button.

I hold always both buttons after I turn off. For me I came to the recovery, too.

If is vibrate twice it should be go in the recovery. By me the light changes to purple when the recovery started.

nailyk · Nov 7, 2017

jrkb said:
thx for your reply.
yes, I tried all variations:
(1)
- push vol- repeatedly
(2)
- push vol+ repeatedly
(1)
- push vol- and vol+ repeatedly

No need to flash on each attempts

On emma you need to setup something to display all the available rom. See the 'boot pain' guide.
Only using this way (flashing >.200 with emma) you will get the new bootloader.
With the new bootloader, you can boot straight to recovery: shut down (without USB), then hold vol- & power *at the same time*.

If you cannot have the new bootloader (some device did not receive marshmalow, thanks to the mobile operator, you still can use the "old" way:

This 2nd way is not recommended because, for any reason of corrupted boot partition (mod flashing for example), you won't be able to boot into recovery anymore.

P.S. (we choose to disable vol+ long time ago, at the beginning of lineage 14.1, so vol+ while led is up will not work anymore, but still can produce vibrate on some devices).
P.S.2: you will never be able to boot into FOTAKernel recovery with stock rom without replacing the boot.img.

jrkb · Nov 8, 2017

nailyk said:
No need to flash on each attempts

guess i was a bit paranoid

thx for your elaborate answer!

It appears I have this bootloader:
LA3.0_L_15.4

Also, my device seems to not have received Marshmallow, so it must have been branded before I bought it.
I followed the bootpain guide, but still 23.1.A.1.28 is the newest I can select.

I'm flashed OmniRom 8.0 following your instructions.
first boot.img, then twrp
(btw, the md5sum is 3df6806c9fcee4b356d7def1b601930d for omni-8.0.0-20171101-z3-nailyk.zip, I hope - it's missing in your guide

)

My notification light is unfortunately broken by a Media Markt "repair" guy, so i'm not sure I press vol- at the right time...
Now it only boots until the sony logo shows up and that's it.

It's not surprising that my rom doesn't boot, but recovery would be nice... did I miss something?

can I just flash omnirom with fastboot as well like

Code:

fastboot update omni.zip

?

nailyk · Nov 8, 2017 at 1:09 PM

jrkb said:
guess i was a bit paranoid

thx for your elaborate answer!

It appears I have this bootloader:
LA3.0_L_15.4

Also, my device seems to not have received Marshmallow, so it must have been branded before I bought it.
I followed the bootpain guide, but still 23.1.A.1.28 is the newest I can select.

I'm flashed OmniRom 8.0 following your instructions.
first boot.img, then twrp
(btw, the md5sum is 3df6806c9fcee4b356d7def1b601930d for omni-8.0.0-20171101-z3-nailyk.zip, I hope - it's missing in your guide )

My notification light is unfortunately broken by a Media Markt "repair" guy, so i'm not sure I press vol- at the right time...
Now it only boots until the sony logo shows up and that's it.

It's not surprising that my rom doesn't boot, but recovery would be nice... did I miss something?

can I just flash omnirom with fastboot as well like

Code:

fastboot update omni.zip

?

No you cant. Rom need to be installed into TWRP, specially omnirom because of the variant script support.
Forget to say one thing into previous post (no idea how to translate this).
With the 'old' boot way (with BL 15.4), while led popup you need to push multiples times on the vol- button, not keep pressed.
As your device do not have light anymore please do:
1. Fash recovery,
2. Flash boot from omni.zip,
3. fastboot reboot
4. As soon as sony logo come keep pushing/releasing volume buttons.
5. Device should vibrate then enter recovery.

P.S. as you do not have the new bootloader, use fastboot flash FOTAKernel twrp.img. The recovery<->FOTAKernel should not exist on your device.

jrkb · Nov 8, 2017

nailyk said:
5. Device should vibrate then enter recovery.

awesome!!! I got into twrp, and was able to flash omni + gapps! yesssss

and it booted without issues.

you made my day,
thank you!!!

hertsjoatmon · Nov 8, 2017 at 10:04 PM

unlocked the bootloaded then flash this. now stuck in a bootloop

Dobsgw · Nov 9, 2017 at 9:45 PM

hertsjoatmon said:
unlocked the bootloaded then flash this. now stuck in a bootloop

Did you upgrade the bootloader?

If not then you need to also flash a kernel that supports FOTA boot to recovery.

Try Nailyks Omni ROM

gsausalito · Jan 14, 2018

Hi:

Can't enter into recovery mode using this recovery (2017-10-02) on a 6603 variant.
I flashed 2017-09-28 (works fine), also flashed 2017-07-27 (works fine too) so there is no hardware button problem.
I can't figure out what's going on.

On version 2017-09-28 (twrp 3.1.1-3) i turn off the phone, push vol- button and, without
releasing it, push power button (phone vibrates) until pink light shows
(phone vibrates again), then enters recovery.

On version 2017-07-27 i do the same and although there is no second vibration, i keep
pressing vol- and power buttons and the phone enters recovery.

On version 2017-10-02 i do the same but there is no second vibration; if i release
buttons, CarbonRom boots, if i keep pressing buttons (no release) CarbonRom boots.

So i do not know what i am doing wrong.

Anyone whith similar issue?

Thanks for your time.

Dobsgw · Nov 13, 2017 at 9:08 AM

gsausalito said:
Hi:

Can't enter into recovery mode using this recovery (2017-10-02) on a 6603 variant.
I flashed 2017-09-28 (works fine), also flashed 2017-07-27 (works fine too) so there is no hardware button problem.
I can't figure out what's going on.

On version 2017-29-28 (twrp 3.1.1-3) i turn off the phone, push vol- button and, without
releasing it, push power button (phone vibrates) until pink light shows
(phone vibrates again), then enters recovery.

On version 2017-07-27 i do the same and although there is no second vibration, i keep
pressing vol- and power buttons and the phone enters recovery.

On version 2017-10-02 i do the same but there is no second vibration; if i release
buttons, CarbonRom boots, if i keep pressing buttons (no release) CarbonRom boots.

So i do not know what i am doing wrong.

Anyone whith similar issue?

Thanks for your time.

If I'm right in the latest versions of Carbon ROM you have to boot to recovery from power off on the new bootloader.

Strangest thing is that you are able to get the functionality back by reverting to older TWRP versions.

Maybe try it one more time?
Start with an older version flashed with fastboot, if that works then update it with fastboot and try to boot to TWRP again.

Would be interesting to know if it works normally with Omni ROM as it has been for me. If you don't have time or don't want to then don't worry the main aim is getting it to work with your ROM

tinynja98 · Sep 11, 2015 28 3 0

Why was it updated on the single but not on the dual sim z3? Or is the updated "single" recovery going to work on my dual z3?

gsausalito · Nov 23, 2017 at 3:27 AM

Hi

Dobsgw said:
If I'm right in the latest versions of Carbon ROM you have to boot to recovery from power off on the new bootloader.

Strangest thing is that you are able to get the functionality back by reverting to older TWRP versions.

Maybe try it one more time?
Start with an older version flashed with fastboot, if that works then update it with fastboot and try to boot to TWRP again.

Would be interesting to know if it works normally with Omni ROM as it has been for me. If you don't have time or don't want to then don't worry the main aim is getting it to work with your ROM

Tried again, as you advised with the same bad results, last recovery (2017-10-02) does not work in my 6603 phone nor my wife's 6603.
Tried Linage 14.1 and Cyanogenmod 5.1.1 flashed in my phone and Resurrection Remix v5.8.3 in my wif'es phone.
It does not work, at least i think it doesn't work (because i can't enter recovery), using the same combo buttons i use at 2017-09-28 recovery version.
I do not know what to do so i give up.

Thanks for your time.

vikivegito · Dec 1, 2017 at 11:30 AM

@nailyk I can't find my bootloader version using this command

getprop ro.boot.s1boot

it gives me a blank output :crying:

nailyk · Dec 1, 2017 at 12:16 PM

vikivegito said:
@nailyk I can't find my bootloader version using this command
it gives me a blank output :crying:

gimme the result of
adb shell cat /proc/cmdline
should be in it.

[TWRP][Z3][UNOFFICIAL] twrp 3.2.1-2 for z3 [2018-03-28]

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member