[RECOVERY][flo | deb][UNOFFICIAL] -> [TWRP] [3.1.1-0]

r.west0813 · Mar 14, 2017

Don't know if anyone else is having this issue, but while in recovery if you reboot into bootloader or back into recovery my device gets stuck on the Google loading screen.

followmsi · Mar 14, 2017

r.west0813 said:
Don't know if anyone else is having this issue, but while in recovery if you reboot into bootloader or back into recovery my device gets stuck on the Google loading screen.

Just tested it .. twice.

Reboot recovery .. reboot bootloader ... Choose recovery .. TWRP again ..And again.

No, don't have this problem on flo.

shantam3108 · Mar 15, 2017

followmsi said:
Do you have F2FS filesystem ?
It takes some time to boot if you have /data partition on f2fs.

Pls wait a bit longer ... Need more infos to be able to fix it.

Here it was booting fine..at least
https://xdaforums.com/showpost.php?p=71346241&postcount=31

Are you able to grab recovery.log from /tmp folder - maybe via adb ?

Thanks

Yes i am running f2fs. I tried all methods via fastboot, flashify and even through twrp but I can't get past the twrp logo in any case.

Could you tell me how to grab a log and will provide you with It.

Thebear j koss · Mar 15, 2017

shantam3108 said:
Yes i am running f2fs. I tried all methods via fastboot, flashify and even through twrp but I can't get past the twrp logo in any case.

Could you tell me how to grab a log and will provide you with It.

http://lmgtfy.com/?q=How+to+grab+a+logcat+using+adb?

To all the amazing, smart, strong females that continue to change the world... Thank you.

gangrenius · Mar 15, 2017

Is this a political forum now? What's this have to do with recovery?

Bumpn gums from my vzw DROID Turbo xt1254

Thebear j koss · Mar 15, 2017

gangrenius said:
Is this a political forum now? What's this have to do with recovery?

Bumpn gums from my vzw DROID Turbo xt1254

He asked how to grab a logcat. No idea where you get political forum from. Click the link and it shows you how to go about grabbing a log.

To all the amazing, smart, strong females that continue to change the world... Thank you.

followmsi · Mar 15, 2017

shantam3108 said:
Yes i am running f2fs. I tried all methods via fastboot, flashify and even through twrp but I can't get past the twrp logo in any case.

Could you tell me how to grab a log and will provide you with It.

How long did you wait while seeing the splash screen ?
Are you encrypted ?

Anyway .. pls connect PC via abd.

When you see the splash screen are you able to get ADB connection ?

Device is online:
adb devices

Grab the log:
adb pull /tmp/recovery.log

Which TWRP version did you use before ?

Need more infos here .. can't replicate your issue.
My F2FS cache partition works as it should..

shantam3108 · Mar 15, 2017

followmsi said:
How long did you wait while seeing the splash screen ?
Are you encrypted ?

Anyway .. pls connect PC via abd.

When you see the splash screen are you able to get ADB connection ?

Device is online:
adb devices

Grab the log:
adb pull /tmp/recovery.log

Which TWRP version did you use before ?

Need more infos here .. can't replicate your issue.
My F2FS cache partition works as it should..

Umm my data partition is f2fs too along with cache . I was on official 3.0.2.0 recovery before. Will provide you logs by tomorrow as I don't have my laptop along with me for now .
I waited for almost 3 to 4 minutes on the splash screen. I am not encrypted.
Thanks I just needed the command to pull log. Will give you one tomorrow

followmsi · Mar 15, 2017

shantam3108 said:
Umm my data partition is f2fs too along with cache . I was on official 3.0.2.0 recovery before. Will provide you logs by tomorrow as I don't have my laptop along with me for now .
I waited for almost 3 to 4 minutes on the splash screen. I am not encrypted.
Thanks I just needed the command to pull log. Will give you one tomorrow

As I understood, F2FS will be checked differently on file system mount as ext4 partitions.

You may need to wait longer ... pls wait for 10 minutes on the splash screen.
Just to verify ...

shantam3108 · Mar 15, 2017

followmsi said:
As I understood, F2FS will be checked differently on file system mount as ext4 partitions.

You may need to wait longer ... pls wait for 10 minutes on the splash screen.
Just to verify ...

Sure will give it a shot and keep you posted
Thanks

followmsi · Mar 15, 2017

shantam3108 said:
Sure will give it a shot and keep you posted
Thanks

Look here .. other device - same problem ..

https://xdaforums.com/oneplus-3t/help/twrp-stuck-splash-screen-t3541037

"Remember that it takes a while to boot up TWRP if you're using f2fs, the more files on the*data*partitions the longer it takes."

How many files do you have on data ?

Cheers

followmsi · Mar 16, 2017

3.1.0-1

New version arrived ... 3.1.0-1

Update.ZIP_TWRP_flo_3.1.0-1.zip -> to be installed via TWRP
TWRP_flo_3.1.0-1.img -> to be installed via fastboot or flashify .. etc.

Update.ZIP_TWRP_deb_3.1.0-1.zip -> to be installed via TWRP
TWRP_deb_3.1.0-1.img -> to be installed via fastboot or flashify .. etc.

Changes:
3.1.0-1
- Added NTFS-3G for NTFS R/W support -> USB-OTG
- Used new kernel with changed F2FS config -> to speed up F2FS boot time a bit !

Enjoy ..

SHABBYLEA · Mar 16, 2017

followmsi said:
New version arrived ... 3.1.0-1

Update.ZIP_TWRP_flo_3.1.0-1.zip -> to be installed via TWRP
TWRP_flo_3.1.0-1.img -> to be installed via fastboot or flashify .. etc.

Update.ZIP_TWRP_deb_3.1.0-1.zip -> to be installed via TWRP
TWRP_deb_3.1.0-1.img -> to be installed via fastboot or flashify .. etc.

Changes:
3.1.0-1
- Added NTFS-3G for NTFS R/W support -> USB-OTG
- Used new kernel with changed F2FS config -> to speed up F2FS boot time a bit !

Enjoy ..

Hello MSI,

Just checked your drive, and can't find the latest Twrp update for Flo. Is it because I'm browsing using Flo?

Many thanks.

rajsris · Mar 16, 2017

So I don't think TWRP 3.1.0-1 boots unfortunately. Stuck at Google logo for a long time. I reflashed TWRP 3.1.0-0 from your OLD folder in Google Drive, and booted up fine and normal speed.

EDIT: I'm on flo with f2fs if that matters. I tried both fastboot flash and update.zip

incognito369 · Mar 16, 2017

Twrp 3.1.0-1 doesn't boot for me either, stuck at google logo.

I have flo with data and cache formated to f2fs.

Twrp 3.1.0-0 boots mostly fine for me. With USB cable plugged into computer it takes ~20 seconds from the moment the twrp splash appears to boot, if it's not plugged in it takes ~3 minutes to boot.

Will try to take logs when I have some free time.

followmsi · Mar 16, 2017

Pls install v2 version ..

Update.ZIP_TWRP_flo_3.1.0-1-v2.zip -> to be installed via TWRP
TWRP_flo_3.1.0-1-v2.img -> to be installed via fastboot or flashify .. etc.

Update.ZIP_TWRP_deb_3.1.0-1-v2.zip -> to be installed via TWRP
TWRP_deb_3.1.0-1-v2.img -> to be installed via fastboot or flashify .. etc.

Changes:
3.1.0-1-v2
- Changed back from ElementalX kernel to Google MSM kernel -> same F2FS config.

Pls report ..

Thx

followmsi · Mar 16, 2017

SHABBYLEA said:
Hello MSI,

Just checked your drive, and can't find the latest Twrp update for Flo. Is it because I'm browsing using Flo?

Many thanks.

Yes, like written before, pls use Chrome and and enable "request desktop version" to download from mobile device.
Can't change the link .. it' google.

followmsi · Mar 16, 2017

Made some further tests and converted my data partition to F2FS as well

Now /cache and /data are on F2FS.

The new converted F2FS data partition takes approx. 2 minutes booting time until TWRP has fully started. (approx. 4GB data)

The ElementalX kernel has already the config we want -> the "CONFIG_F2FS_CHECK_FS" kernel setting is disabled too.
But this kernel is slightly bigger as the msm kernel binary and as we come close to the max partition size of recovery partition this is could be an issue.
No more space left on recovery partition

Strange issue .. If you boot into recovery via power button and vol button it works on initial release. (3.1.0-1)

Now in 3.1.0-1-v2 version we use the google msm kernel (lineageos) again .. with the same F2FS config - but smaller kernel binary.
To prevent any strange issues in the future we will keep google msm kernel for the next TWRP versions ..

Cheers

brewer75 · Mar 16, 2017

followmsi said:
Made some further tests and converted my data partition to F2FS as well
Now /cache and /data are on F2FS.

The new converted F2FS data partition takes approx. 2 minutes booting time until TWRP has fully started. (approx. 4GB data)

The ElementalX kernel has already the config we want -> the "CONFIG_F2FS_CHECK_FS" kernel setting is disabled too.
But this kernel is slightly bigger as the msm kernel binary and as we come close to the max partition size of recovery partition this is could be an issue.
No more space left on recovery partition

Strange issue .. If you boot into recovery via power button and vol button it works on initial release. (3.1.0-1)

Now in 3.1.0-1-v2 version we use the google msm kernel (lineageos) again .. with the same F2FS config - but smaller kernel binary.
To prevent any strange issues in the future we will keep google msm kernel for the next TWRP versions ..

Cheers

I just flashed your newest build. I'm using F2FS and my boot time in recovery seemed much quicker than on the previous TWRP build...Thanks!

followmsi · Mar 16, 2017

To have proper naming standards and one last fix for the deb version only ...

Update.ZIP_TWRP_flo_3.1.0-2.zip -> to be installed via TWRP
TWRP_flo_3.1.0-2.img -> to be installed via fastboot or flashify .. etc.

Update.ZIP_TWRP_deb_3.1.0-2.zip -> to be installed via TWRP
TWRP_deb_3.1.0-2.img -> to be installed via fastboot or flashify .. etc.

Finish - done

[RECOVERY][flo | deb][UNOFFICIAL] -> [TWRP] [3.1.1-0]

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts