yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] Sc4r3Crow:
Little Problems

Hey guys, I flashed AOSIP some days ago and the rom is running very fine. But I have a problem concernig TWRP, everytime I boot to recovery it displays a screen where I can allow modifications of system partitition. I think that occurs because I'm decrypted, to whatever reason. But I want to be encrypted.

So far I've tried several flashing orders:

1. complete wipe, format data, flash firmware, flash rom, flash gapps, wipe dalvik/cache, reboot system...

2. format data, complete wipe, flash firmware, flash rom, flash gapps, wipe dalvik/cache, reboot system...

3. format data, restart recovery, complete wipe, flash rom, flash gapps, wipe dalvik/cache, reboot system...

4. format data, restart recovery, complete wipe, restart recovery, flash rom, flash gapps, with and without wiping dalvik/cache, reboot system...

But the problem still exists, and I'm sure it's only a little detail I'm doing wrong.

Can someone please give me an exact step by step manual (for dummies)?

Thank in advance :good:
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] gtpitch:
Have you tried just checking or unchecking (forget what the default is) the box in TWRP to not show the dialog again?

If your end goal is to end up encrypted, the best way is to flash OOS OB4, set it up, then fastboot install twrp again, then wipe (don't format) system, data, cache and flash ROM + GAPPs.
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] Sc4r3Crow:
Yes, I check the box everytime...but the display keeps displaying when I boot to recovery.

The other problem is that when I try to flash anything else e.g. Magisk, TWRP tells me Data can not be mounted.

After formatting data I check the box one time and the message doesn't appear anymore...it appears after rom flash...
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] David:
nnnnnoooooooo uuuuuuuuu brettt
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] TrOjAnUK:
Hey bud, thanks for your work on this, my favorite rom :) can you tell me, do you do anything to the rom before you build, Ive been building from source but my roms are coming in at a different size and also my battery sucks..

BTW, Im learning this building stuff as I go so kindly cut me some slack :D

TrOjAn
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] gtpitch:
Upgrade to latest twrp. Recommend codeworkx universal
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] gtpitch:
No I assume you're just syncing aosip oreo-mr1 manifest and using the lunch command to sync the device tree?

The only thing I add for release builds are the ims and subs commits from review.aosiprom.com.

Those work for op5 but aren't ready to be merged yet.
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] TrOjAnUK:
Ok cheers... yes Im just syncing then running lunch, I`ll look in to the reviews and see about pulling them in.. thankyou for the reply :good:

TrOjAn
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] gtpitch:
Once you have build/envsetup.sh you can easily grab those two topics but running:

repopick -t ims && repopick -t subs-sysserv-mr1

Should both pick cleanly and take a little to run (a lot of commits).

Oh, actually don't pick ims. It takes other repos and if you're not having phone issues with your builds I wouldn't worry about it until we merge them.
[OnePlus 5 ROMs, Kernels, Recoveries, & Other Devel] red5pade:
I tried the 1/21 build and when unlocking the phone, it's not instantly like oos. Am I doing something wrong? Should I use another kernel? Was that fixed in 1/28? I'm decrypted with magisk. Sorry for the questions... I want to use the Rom but that annoys me too much
[P3300, MDA Compact III ROM Development] lbendlin:
In the past I have successfully re-added the BT DUN profile to various WM5 and WM6 versions of my Orbit. But now, with WM6.1, after installing the .Mun. hack, other device still don't see the DUN service of the Orbit. Anyone had a similar problem?
[P3300, MDA Compact III ROM Development] cesconoa:
WM6.1 has btdun service included, have you tried to add BT dun profile without .mun. hack? It's possible it coflicts with microsoft drivers...
[P3300, MDA Compact III ROM Development] lbendlin:
Silly me. Removed the .Mun. package and all is working well. Anyone wants to throw eggs?
[Xperia Tablet Z Original Android Development] CyberWalkMaN:
WARNING!

TWRP builds version 3.2.1-0 and higher are not compatible with Android Lollipop (5.0/5.1.1) due to SELinux rejection

OFFICIAL DOWNLOADS FOR POLLUX/POLLUX_WINDY :

https://dl.twrp.me/pollux/ ,

https://dl.twrp.me/pollux_windy/

twrp-3.x.x-x-pollux.img , twrp-3.x.x-x-pollux_windy.img : Official TWRP image

How to install : All informations available on TWRP.me

DEVELOPMENT DOWNLOADS FOR POLLUX/POLLUX_WINDY :

https://www.androidfilehost.com/?w=files&flid=202356

twrp-3.2.x-x-pollux.zip , twrp-3.2.x-x-pollux_windy.zip : Flashable TWRP 3 to FOTA installer

twrp-3.2.x-x-pollux.img , twrp-3.2.x-x-pollux_windy.img : Fastboot bootable TWRP 3 image

cleaner-fota.zip : Flashable FOTA formatter (optional)

HOW TO INSTALL EASILY TO FOTA :

* (Optional) : Download the TWRP bootimage and flash it to boot

fastboot flash boot twrpfilename.img

* Boot to recovery : Enter the Recovery as usual

* Flash to FOTA : Install the TWRP FOTA zip

* (Optional) : Flash the ROM you want

HOW TO INSTALL MANUALLY TO FOTA :

* Bootimage : Download the TWRP bootimage you want to flash

* File storage : Adapt the path and push the file to the device this way :

adb root
adb wait-for-device
adb push FullPathToTheRecovery.img /tmp/twrp.img

* Flash : Extract the TWRP image to the FOTA partition

adb shell dd if=/tmp/twrp.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

* Reboot to recovery : adb reboot recovery

ADDITIONAL LINKS :

* Easy ADB and Fastboot for unexperienced users :

https://xdaforums.com/showthread.php?p=48915118

Thanks to the TWRP Team​

Current local manifest of the TWRP build

<?xml version="1.0" encoding="UTF-8"?>
<!-- https://github.com/fusion3-common/twrp_development_sony -->
[Xperia Tablet Z Original Android Development] ze7zez:
Oreo needs TWRP 3.2.x.x.

Does the appearance of this thread mean that there are ongoing work on Oreo for Tablet Z?
[Xperia Tablet Z Original Android Development] CyberWalkMaN:
Yes, we are working on android 8.1.0 for all fusion3 devices :)
[Xperia Tablet Z Original Android Development] phillipssat:
For me links are dead. Here i found it

https://androidfilehost.com/?fid=673791459329066468

Anyone installed 3.2.1.0 on windy ? Is it OK ?
[Xperia Tablet Z Original Android Development] ric84:
To me it works pretty well, don't see any difference. Running now the unofficial OREO LineageOS.
[Xperia Tablet Z Original Android Development] phillipssat:
Does anyone know why original links are dead ? Any problems with the 3.2.1.0 at link from first post ?
[Xperia Tablet Z Original Android Development] Lycidias:
Thank you Very much for your efforts for this device! Great!!!
[Xperia Tablet Z Original Android Development] CyberWalkMaN:
All the download links work, I checked them.
[Xperia Tablet Z Original Android Development] ripee:
[MENTION=5405613]CyberWalkMaN[/MENTION], are you planning on eventually submitting your 3.2.1-0 builds for official support? I'm asking because I built my own TWRP for both pollux and pollux_windy (see the BasketBuild link in my signature) from my dedicated device trees, not directly from Lineage source repos. I was thinking of creating my own thread and submitting my repos to TeamWin, given enough positive feedback, especially since only pollux_windy has an official TWRP page and it's most recent official version is 3.0.2-0. I've built TWRP for a number of devices since version 3.2 was released and submitted them for official support.
[Xperia Tablet Z Original Android Development] CyberWalkMaN:
Yes, I plan to do it this week. I think that our device trees are cleaner and more relevant for this -

https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux

https://github.com/fusion3-common/twrp_development_sony/tree/device_sony_pollux_windy
[Xperia Tablet Z Original Android Development] ripee:
Great! Hey, whatever works best is what's most important ;)
[Xperia Tablet Z Original Android Development] CyberWalkMaN:
Please test first official builds:

pollux - http://build.twrp.me/twrp-3.2.1-0-pollux.img

pollux_windy - http://build.twrp.me/twrp-3.2.1-0-pollux_windy.img
[Xperia Tablet Z Original Android Development] Rootk1t:
What is a difference between unofficial and official builds?
[Xperia Tablet Z Original Android Development] ze7zez:
Is already out of date?

I do not see any TWRPs for pollux*
[Xperia Tablet Z Original Android Development] ripee:
Before official builds come out, TeamWin runs official preview builds to make sure that the images their Jenkins builder churns out are actually functional and true to the code submitted by the developer, relative to the developer's own unofficial builds.

Once everything is confirmed to be working the same as unofficial builds, TeamWin runs the actual official builds, which get linked on their site and made available on the official TWRP app. Official support also ensures that future version of TWRP will be attempted to be built using existing repos without the need for the developer's further input unless and until the source repo become too outdated, at which point a new branch would need to be created with code that follows a more recent android API.
[Xperia Tablet Z Original Android Development] CyberWalkMaN:
TWRP for pollux/pollux_windy is now officially maintained by me -

https://twrp.me/sony/sonyxperiatabletzlte.html (pollux),

https://twrp.me/sony/sonyxperiatabletzwifi.html (pollux_windy) :)
[Xperia Tablet Z Original Android Development] merrymeal:
There must be something wrong with my pollux_windy. :crying: :D

Flashing v3.2.1.0 causes a TWRP boot looping.

The only way to boot LineageOS 14.1 was flashing again TWRP-3.1.1-pollux-FOTA-20170928.zip from CaHbKaUp.

Any idea what's going on?

BTW, thanks for updating TWRP! :good:

Edit:

Finally solved the problem.

Downloaded TWRP 3.2.1.0 from official page and I've followed the dd Install Method even though my tablet is not rooted (su command wasn't recognized -su: not found- but dd worked in TWRP Terminal).
[Xperia Tablet Z Original Android Development] amritansh singh gautam:
Help-as written I cant flash this twrp on 5.1.1 right so i hve to downgrade it to 4.2.2 and then flash it

Can I flash it with Flashtool?

What is FOTA?? Can I flash it from Flashtool if yes then how
[Xperia Tablet Z Original Android Development] djibe89:
Hi,

any version for TWRP 3.2.2-0 ???

Thx
[Xperia Tablet Z Original Android Development] Rootk1t:
images are available on official site.
[Xperia Tablet Z Original Android Development] djibe89:
Hi,

thanks for reply but I forgot to be more precise, is there a 3.2.2-0 TWRP FOTA version flashable from recovery ?

Thx
[Xperia Tablet Z Original Android Development] Rootk1t:
i did it for myself. It's not that difficult if you have recovery image.
[Xperia Tablet Z Original Android Development] okumobile73:
Is this stable?

Are there no error in this build?
[Xperia Tablet Z Original Android Development] lm089:
Just got rid of Xperia Stock ROM on my SGP311, following instructions on LineageOS's pages. Everything worked nice including the installation of TWRP 3.2.3-0 like that from my Linux terminal:

adb shell
dd if=/sdcard/twrp-x.x.x-x-pollux_windy.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel

I then flashed LOS 15.1 Official + OpenGapps pico + Magisk V 18 from recovery. Finally booted into system, and all appears to be well.

There are only some things that are confusing me:

[Solved] every time I boot into recovery all settings like language, timezone, 24hr clock etc. are forgotten; this is unlike my other Xperia (Z1c), running 3.2.3-0 as well

when I try to create a Nandroid backup on my Z1c I can also select a recovery partition to be included in the backup; here on my SGP311 however this option is missing

Is there a way to tell which partition twrp has been installed to? I know that I told system to install twrp*.img to FOTAKernel so I assume it's there. But not so sure in regards to my Xperia phone (Z1c); it's been a while that I installed twrp there, and from then on I applied updates from within recovery flashing the .img file

[Solved] the standard key combinations upon boot (power + Vol-down) is booting up some (very basic) LineageOS recovery instead of tarp. Power + Vol-up just boots into system. Only way to boot into recovery is through the extended restart menu

(although I'm running this from a Linux installation I'm far from being an expert re: this OS, so please be a bit patient....)

EDIT: #1 just solved itself; after re-booting into recovery for the umpteenth time "suddenly" all settings are remembered; the other 2 questions remain, though

EDIT: #4 apparently solved as well, power + Vol-up now boots into twrp now. No clue why it wasn't working first... So basically everything's working now as expected.

Just for curiosity reasons I'd still would love to learn an answer to q #3
[Xperia Tablet Z Original Android Development] Rootk1t:
As sony devices from that era (2012-2013) don't have separate recovery partition, it it installed in dev/block/platform/msm_sdcc.1/by-name/FOTAKernel partition, which is used for OTA updates on stock ROM and is not used on custom ones.

P.S: official LOS 15.1 is not a bad choice, but i would stick to unofficial one from this forum, because it has built-in recovery in kernel, and some features that are not allowed, and i suppose will never be present in official builds, though it is a matter of taste.
[Xperia Tablet Z Original Android Development] PedroDexplorer:
can someone please help me out after I install magisk v19.3 twrp recovery is gone every time I go to recovery its all just black.
[Xperia Tablet Z Original Android Development] lm089:
Known bug / incompatibility of Magisk v19+ with many xperia devices. Only known solution at the moment is to stay at Magisk 18.1.
[Xperia Tablet Z Original Android Development] jeromelec:
Magisk 19.3 doesn't work with recovery

You must flash twrp with fastboot command and reinstall last Lineage. Don't flash magisk 19.3 then magisk 18.2 who works perfectly. Don't update it.
[Xperia Tablet Z Original Android Development] Rootk1t:
well, the latest unofficial JUNE builds of LOS 15.1 and 16.0 have fixed for this incapability intergrated.

Stay away from Magisk v19 if using official LOS nightlies 15.1 or use fixed unofficial builds.
[Xperia Tablet Z Original Android Development] L.F.B.:
Just a little doubt here... How to update Twrp wen new version?

Flash to boot or flash to recovery? Im on 16 pie ?

Edit.. Hey Master [MENTION=5292989]Rootk1t[/MENTION] where is your RR pie Rom from your signature? Im curious ??
[Xperia Tablet Z Original Android Development] Rootk1t:
TWRP 3.4.0-0 was released.
[Xperia Tablet Z Original Android Development] csoller:
Wow, still going...
[Xperia Tablet Z Original Android Development] DanOccupanther:
Hi, I'm trying to install LineageOS for the first time on Xperia Tablet Z SGP311 but I'm stuck trying to install TWRP.

I've been able to unlock bootloader, have USB debugging available, and can get into adb and fastboot through PowerShell

I'm following the instructions here: https://wiki.lineageos.org/devices/pollux_windy/install but when I get to:

fastboot flash boot twrp-x.x.x-x-pollux_windy.img

I get the error message:

error: Couldn't parse partition size '0x'.

I'm not sure if this is because I'm currently running Android 5.1.1, or to do with the recovery-in-boot arrangement of xperia devices, but i'm stuck.

Could anyone help with a fix?
[Xperia Tablet Z Original Android Development] hathesput:
TWRP boot issues

Hello everybody,

I face issues while booting TWRP.

Device:

Xperia Tablet Z pollux windy SGP312, Android Version 4.3, Build Number 10.4.1.B.0.109

So far done:

Device is routet with towelroot and the bootloader unlocked.

"adb device", reboot into bootloader and "flashboot device" are responding correct.

After "flashboot boot twrp.img" it shows flash successful, but after that nothing happens. LED is blue, screen black.

I tried with TWRP 2.6.3, 2.8.5, 3.2.1, 3.3.1, 3.4.0.

Is this a compatibility problem?

What happens when I use flashboot flash boot twrp.img?

Can I "destroy" the recovery partition, if the TWRP version is the wrong one for Android 4.3?

I couldn´t find a detailed explanation for that anywhere.

Please advise. Thanks a lot in advance

Philip
[Xperia Tablet Z Original Android Development] Rootk1t:
Your command is wrong.

fastboot flash boot twrp.img
[Xperia Tablet Z Original Android Development] jokerni:
Thought I'd have a go on my xperia tablet z sgp321. Looking at:

Install LineageOS on pollux_windy | LineageOS Wiki

wiki.lineageos.org

Under option 7 rooting status my tablet reports Bootloader unlock allowed: No

Do I have a dead duck?
[Xperia Tablet Z Original Android Development] Rootk1t:
If you have operator device like O2 or T-mobile or Docomo, then yes, those device bootloaders can't be unlocked.
[Xperia Tablet Z Original Android Development] 4everer:
I had the same problem but later found it was due to fastboot command changed.

fastboot flash:raw boot twrp-x.x.x-x-pollux_windy.img

worked for me. I found it when reading this article https://www.droidwin.com/fix-fastboot-error-couldnt-parse-partition-size-0x/
[Xperia Tablet Z Original Android Development] Rootk1t:
TWRP 3.5.0-0 was released.
[Xperia Tablet Z Original Android Development] lm089:
Working great, appears to be a bit slower than 3.4.0, e.g. loading the reboot menu. But no issue.

Had a bootloop right after flashing the image from the previous Twrp where after showing the lineage boot animation for a few minutes the tablet suddenly would reboot to twrp. Solved by restoring nandroid
[Xperia Tablet Z Original Android Development] Rootk1t:
TWRP 3.5.1 was released.
[Xperia Tablet Z Original Android Development] Rootk1t:
TWRP 3.5.2 was released.
[Xperia Tablet Z Original Android Development] Rootk1t:
TWRP 3.6.2 was released.
[Xperia Tablet Z Original Android Development] Rootk1t:
TWRP 3.7.0 was released.
[Upgrading, Modifying and Unlocking] Witzker:
Hi I am new want to upgrade my tablet

Flashing Root in Odin(Odin3 v3.12.7.exe) was ok with:

CF-Auto-Root-picassolte-picassoltexx-smt525.tar

then tried to install TWRP to load the image

[6.0.x] [SM-T525] LineageOS 13.0 UNOFFICIAL Nightlies for the Tab Pro 10.1 LTE

In Odin (Odin3 v3.12.7.exe) I load:

twrp-3.1.1-0-picassoltexx.img.tar

I get:

<ID:0/004> Added!!

<ID:0/004> Odin engine v(ID:3.1207)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> NAND Write Start!!

<ID:0/004> SingleDownload.

<ID:0/004> recovery.img

<ID:0/004> RQT_CLOSE !!

<ID:0/004> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

also tried the App from Playstore

Flashing......

not successful

I got the tablet from Provider 1und1 in Germany.

Is it possible that there is some lock for updating?

What could be the problem?

regards

Witzker

P.S: main Target is to get newer version of Android on my tablet.

i found: [6.0.x] [SM-T525] LineageOS 13.0 UNOFFICIAL Nightlies for the Tab Pro 10.1 LTE

maybe there is an other way to get this done?

Is there an other image for it? to use with Odin?

or other roms with newer Android?
[Upgrading, Modifying and Unlocking] Ibuprophen:
I don't have this device but, the following threads may be helpful for what you need and, if needed, post your question within one of them.

https://xdaforums.com/showthread.php?t=2679825

https://xdaforums.com/showthread.php?t=3087451

Good Luck!

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Xiaomi Redmi Note 3 Guides, News, & Discussion] SpawnX1200:
Okay as the title suggests, my post is all about whether the prime of our phone is behind it and it's time to cash on the phone and move to a new beast where development is very much active be it from the community with cust roms or the creators and their stock rom. I mean if I look at the pace of how things are going on Oreo compared to how things went on Nougat, there's a world of a difference. Besides our specs are starting to lag behind, so is it still worth to hold on the Redmi Note 3 SD or it's time to move onto a new beast?!
[Xiaomi Redmi Note 3 Guides, News, & Discussion] emime12:
I'm still in love with my Redmi Note 3, I never had problems with it. It was always easy to remove the Bootloop, the battery after almost 2 years is still perfect, I have no lags, I can change ROM whenever I want. I would not change it for anything.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] vaseto96:
Specs are starting to lag behind? How come? Most of the devices in this price range still use snapdragon 625 or even less if it's from some manufacturer like Samsung, Nokia and so on. Don't be ridiculous... Redmi Note 3 was ahead of its time when it comes to price to performance ratio and it still holds up today pretty well. Samsung a8 which is brand new and more expensive has the exact same Antutu score as redmi note 3 and redmi note 3 is from 2016. I would choose Note 3 every day of the week.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] dustmalik:
OP, Can you mention any device that has more Oreo custom roms than Kenzo/Kate? Because i haven't really found any.
[Xiaomi Redmi Note 3 Guides, News, & Discussion] harif_p:
No, i'm not agree with you. Kenzo still beast.

Until Xiaomi starting to use 660 or it successors for redmi, i don't think to upgrade my device. I just not really care about SD 61x, 62x, or 63x series. That what i'm thinking about..

(Or maybe its time to thinking xiaomi's flagship then, coz think it impossible to xiaomi using 66x or it successor for redmi series.. ?)
[Xiaomi Redmi Note 3 Guides, News, & Discussion] adizz4:
NO

/thread
[Amazfit] gswolf:
When I went through the threads in the forum I thought it is not possible to use the tracking data on the watch as GPX data without the help of the mobile or other external Apps.

In fact it is quite easy to do this with the watch only thus you can re-use already tracked trails or routes and redo them. The integrated Sport App will show always if you are on track.

Steps to Do within Sport App:

Open Sport App

Got to "Activities" and select a specific trail track and open (with a left swipe) the "Route" and push "Export"

Now your formerly tracked route is stored in gpx format in directory /Internal Storage/gpxdata (on the watch)

Go to "Settings" and select "Sport Trail" and select the trail you want to show in your activity

Now you can start a new activity e.g. "Trail Run" and it will show inline the selected gpx route

Of course if you have gpx routes downloaded from web you can put them directly, e.g. via explorer from PC, to /Internal Storage/gpxdata too.

It looks like below when you are on running track following the GPX route and you never get lost again ;)

bb img

Using firmware 1.3.5 with included Sport App.

PS: I like the Sports App in specfic the GPS tracking on the watch very much. It would be even greater if the Zoom (+/- buttons) good be configured or at least set in smaller steps. Currently it jumps form 50m, 200m, 2km, 5km More intermediate steps would be very helpful e.g. 50m, 100m, 200m, 500m, 1km, 2km, 5km, 10km
[Google Pixel XL Questions & Answers] AnitaMedic:
I've switched to ElementalX kernel for a few reasons, including the hopes that it had a way to control the charging amperage, but so far the closest I've gotten was tricking my device into thinking it was getting a different current. I've been looking in /sys/class/power_supply, but for all I know it's just not possible with this kernel. Any help is appreciated! :D
[Google Pixel XL Questions & Answers] isssaputra:
May i know why you need to control charging rate?