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

[nailyk]

507/5000
Is the WiFi and the camera stable?
No longer overheating and periodic restarts?
If this is so I point this mobile I use it for work and as in my country it is not very safe to load very good mobiles, only for certain occasions that I have free or give me vacations I occupy the rest of my mobiles, also I stole some of them Traveling to my work that's why my wife gave me the Z3 already a year ago and walks well besides that I take care of the battery quite hard all day and take some decent photos.

Read a bit the 14.1 thread to know what is remaining. I think it is mostly stable for DD.

 

[santeria27]

@nailyk hey buddy! I have trouble flash the new omni 7.1.2 for z3 /d6603 your twrp says error 7 i use lineage from your team! I would like test omni ar not working! Can me help??

Clean flash and verify the zip etc! Have same prob

Sent from my Xperia Z3 using XDA-Developers Legacy app

 

[nailyk]

@nailyk hey buddy! I have trouble flash the new omni 7.1.2 for z3 /d6603 your twrp says error 7 i use lineage from your team! I would like test omni ar not working! Can me help??

Clean flash and verify the zip etc! Have same prob

Sent from my Xperia Z3 using XDA-Developers Legacy app

Post your /tmp/recovery.log after error 7. In the last few lines you will have the real error.

 

[guma55]

i want to install rom base on stock rom, i revert my recovery to 3.02. and still got bootloop what i should do more?

 

[nailyk]

i want to install rom base on stock rom, i revert my recovery to 3.02. and still got bootloop what i should do more?

After reverting to 3.0.2 you need to ext4 format apps_log partition then you should be good with any stock based rom.

 

[guma55]

After reverting to 3.0.2 you need to ext4 format apps_log partition then you should be good with any stock based rom.

how i can do that?

 

[nailyk]

how i can do that?

You can also flash again full stock with emma software.
This will overwrite all the device, data included.

 

[jimmy123322]

Did this recovery work on Z3 Dual?

 

[Fa1n7]

Guys, can anybody let me know how to wipe the apps_log partition when coming from Nougat to stock Marshmallow? I can't find the setting anywhere in the recovery.

 

[nailyk]

Did this recovery work on Z3 Dual?

Mostly yes. But you will probably encounter problem to flash zip.

Guys, can anybody let me know how to wipe the apps_log partition when coming from Nougat to stock Marshmallow? I can't find the setting anywhere in the recovery.

Into wipe, advanced wipe.
Please ensure using 3.0.2 version.

 

[Knallkopp_on]

Hello, I’m new here. If this is the wrong place I post this, just tell me, I will delete it. I’m sorry form my bad English, just need some help.

Yesterday, I wanted to flash LineageOS 14.1 by nailyk on my Xperia Z3 (D6603).
Before that, my phone ran a rooted version of Android 6.01 by Sony. Bootloader locked.

First thing I did was to flash Android 4.4 (23.0.A.2.93) with flashtool. I used Giefroot, to root the device again and made simply a TA Backup. After this, I unlocked the Bootloader and flash the phone with Emma (the rom with .200 at the end). After flashing, I wasn’t able to access the Sony Recovery by pressing Volume-Down together with the Power Button. I don’t know why. Now, I tried to flash twrp in fastboot. Console said OK after 1.300s. But I can’t access twrp after this + bootloop (but I think bootloop is normal, because of the Sony image) --> flash twrp again --> the same. Flash .200 rom with Emma again + flash twrp recovery again --> the same situation. Flashing .575 Rom with Emma + flashing revovery, the same, too. Now I flashed Cyanogenmod 12.1, ran perfectly. I tried to flash twrp in fastboot again. I think, there was no Bootloop after flashing, but also no access to twrp recovery. Phone restart at boot process, while I tried to access recovery.

The good news: After I gave up, I flashed the device one last time with Emma, than I flashed the phone using flashtool on Sony Android Nougat Preview 4 (just to get any other Bootloader). Now, I flashed the good old Android 4.4 (23.0.A.2.93) with flashtool --> Giefroot --> Looked into *#*#7378423#*#* for the right Bootloader --> restore TA Partition. Now, I’m back on my rooted official Android 6.01 with Locked Bootloader.!

Bootloader after flashing .200 with Emma was S1_Boot_MSM8974AC_LA3.0_L_37

I'm sure, I did anything wrong. Would just like to know what.

 

[nailyk]

Hello, I’m new here. If this is the wrong place I post this, just tell me, I will delete it. I’m sorry form my bad English, just need some help.

Yesterday, I wanted to flash LineageOS 14.1 by nailyk on my Xperia Z3 (D6603).
Before that, my phone ran a rooted version of Android 6.01 by Sony. Bootloader locked.

First thing I did was to flash Android 4.4 (23.0.A.2.93) with flashtool. I used Giefroot, to root the device again and made simply a TA Backup. After this, I unlocked the Bootloader and flash the phone with Emma (the rom with .200 at the end). After flashing, I wasn’t able to access the Sony Recovery by pressing Volume-Down together with the Power Button. I don’t know why. Now, I tried to flash twrp in fastboot. Console said OK after 1.300s. But I can’t access twrp after this + bootloop (but I think bootloop is normal, because of the Sony image) --> flash twrp again --> the same. Flash .200 rom with Emma again + flash twrp recovery again --> the same situation. Flashing .575 Rom with Emma + flashing revovery, the same, too. Now I flashed Cyanogenmod 12.1, ran perfectly. I tried to flash twrp in fastboot again. I think, there was no Bootloop after flashing, but also no access to twrp recovery. Phone restart at boot process, while I tried to access recovery.

The good news: After I gave up, I flashed the device one last time with Emma, than I flashed the phone using flashtool on Sony Android Nougat Preview 4 (just to get any other Bootloader). Now, I flashed the good old Android 4.4 (23.0.A.2.93) with flashtool --> Giefroot --> Looked into *#*#7378423#*#* for the right Bootloader --> restore TA Partition. Now, I’m back on my rooted official Android 6.01 with Locked Bootloader.!

Bootloader after flashing .200 with Emma was S1_Boot_MSM8974AC_LA3.0_L_37

I'm sure, I did anything wrong. Would just like to know what.

Yes, your process is good. Your english too
1. unlock bootloader,
2. flash with emma the .200
2bis. reboot into fastboot mode
3. fastboot flash recovery twrp_z3.img
4. Shutdown without usb cable attached
5. power & vol down
5bis. Stay pressed until twrp splash came (~5 sec)
6. Flash any custom rom you want from twrp.

We have some known issues with this recovery, specially with replaced lcd panels. Maybe that was what you experienced. One way to check is screen keep being black but backlight is on.
Be sure you made 4. & 5. Without those exact steps you cannot go into recovery.
If you flashed cm-12.1 then 14.1 will be fine. Exact same rom (/boot process).

P.S.: welcome to xda

 

[Knallkopp_on]

Thank you nailyk. For your development and your quick reply.

You can be sure, I will try it again. I never give up until LineageOS runs on my phone (or it brick).
At the moment, I don't have much time. In one or two weeks, I will do it again.

 

[nailyk]

Thank you nailyk. For your development and your quick reply.

You can be sure, I will try it again. I never give up until LineageOS runs on my phone (or it brick).
At the moment, I don't have much time. In one or two weeks, I will do it again.

I can help you to brick (see my signature).
Joke aside, feel free to join (and stay) on freenode#freexperia and I will help you to install.

 

[mathorv]

@nailyk
Can we expect TWRP build 3.1.1 soon? (bug fixes are always welcome)
https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html

 

[nailyk]

@nailyk
Can we expect TWRP build 3.1.1 soon? (bug fixes are always welcome)
https://twrp.me/site/update/2017/05/19/twrp-3.1.1-0-released.html

Every request for an ETA will delay the release for 15 more days

Aren't you the person who help me to unbrick my device? I have no working device for now so cannot test before releasing.

 

[mathorv]

Every request for an ETA will delay the release for 15 more days
Aren't you the person who help me to unbrick my device? I have no working device for now so cannot test before releasing.

Come on it's obvious that I meant soon(tm)
http://www.urbandictionary.com/define.php?term=soon (tm)
https://gaming.stackexchange.com/questions/23112/where-did-soon-originate

Holding thumbs for you the first person that is on the verge of reviving first severely bricked Sony Xperia Z3!

 

[nailyk]

Come on it's obvious that I meant soon(tm)
http://www.urbandictionary.com/define.php?term=soon (tm)
https://gaming.stackexchange.com/questions/23112/where-did-soon-originate

Holding thumbs for you the first person that is on the verge of reviving first severely bricked Sony Xperia Z3!

Ah that is different!
Soon(tm) is only 8 days delays

Joke aside am working hard on unbricking my device but should be able to find some testers.
IIRC the build is ready. Also the 'old' 3.0.1 already some patchs included (some wipe problems, terminal, etc...)

 

[mathorv]

@nailyk
If there are twrp pre-betas before beta-production state I may sometime among other beta testers try these builds.

Formatting partitions in TWRP seem to be slow (maybe there is some check like -c or -cc?) What I mean compared to my Nexus 4 TWRP it is slow.
I know I may go for rm -rf and check if its slower or faster. Just pointing out that make_ext4fs seems to be slow.

 

[mathorv]

@nailyk

TWRP 3.1.1 alpha 20170523 worked ok.
Temperature was from around 50*C to 60*C when TWRP checking md5 of a backup.
(Used screen timeout 15s and lowest brightness in TWRP)
Made full backup with no errors 340sec, no errors, md5 generation
Restored data 240 sec, no errors, md5 check

Also tried to change Cache and Data Filesystem form Ext4 to f2fs in TWRP with success.
https://forum.xda-developers.com/showpost.php?p=72435316&postcount=1167
https://forum.xda-developers.com/xp...rial-migrate-filesystem-to-f2fs-ext4-t3004755

Regular users please don't ask for alphas this stuff may potentially cost you data loss and may break stuff.