yashsingh1/xdaforums huggingface dataset:
[Galaxy S5 Mini Original Android Development] fidoedidoe:
I'm having a few issues with TWRP 3.1.1 where "wipe / format data" (where you have to key "yes") generates the following error msg (I posted a similar msg in Slim Rom 7 thread):

Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.

I'm now wondering whether decrypting the data partition from within TWRP will address my format data issue reported above.

Can I ask how you did this? I've dug around the TWRP menus but nothing has jumped out at me (maybe it's something you need to run from the terminal?)

Many thanks!
[Galaxy S5 Mini Original Android Development] :
I have the same problem
[Galaxy S5 Mini Original Android Development] MikeT.:
Here also this message in unofficial builds, don't tried it, but I think its still present in this version.
[Galaxy S5 Mini Original Android Development] fidoedidoe:
I still haven't found a method to decrypt the /data volume from within TWRP (a reference earlier in the thread implied it was possible)..the hope being this would mitigate the "wipe / format data" error:

Error:unable to wipe /data unknown file system 'auto'
unable to format encryption.

What I did discover was that when reverting to an older version of TWRP (2.8.x) using Odin, " format data" (where you have to type "yes" to proceed) didn't error. I'm not sure whether that cured the issue, but after that I updated TWRP image back to 3.1.1.0 and installed my ROM as normal.

Still looking for a recognised method to wipe encrypted /data volume from within latest stable TWRP if anyone has any experience of that.

EDIT

Another thread suggests (to my untrained eye) that "unknown file system 'auto" may be related to how twrp.fstab is configured.

I'm very much out of my here ( so apologies for the crude suggestion), but could it be that another build of a TWRP image is needed where twrp.fstab is changed to allow "format data" to work, ie substitute "fstype" from "auto" to "ext4" as outlined below :

...
/data	ext4	/dev/block/mmcblk0p21	length=-16384
...
[Galaxy S5 Mini Original Android Development] Friedensfurz:
I got it to work by formatting/repairing/changing filesystem in TWRP. Just try some combinations, it will work eventually ;)
[Galaxy S5 Mini Original Android Development] ayke:
Yes, I think it's because of the 'auto' in the fstab. I've set it to ext4 in this build (for data and cache):

https://aykevl.nl/download/2017-07-03-recovery.img

This build also contains the previous fixes (adoptable storage, fixing the kminiltexx error).

If it fixes the issue for you, I'll push the change for inclusion in the next official build.

I didn't see any negative consequences of changing the FS type in fstab. Even setting the fstab entry to 'f2fs' mounts /data as usual (as ext4) so I think it's safe.
[Galaxy S5 Mini Original Android Development] ayke:
Can someone test this change? Then I'll integrate it in the official build.
[Galaxy S5 Mini Original Android Development] Pat750:
I'm a little confused now. Last issue here was to find a way to format encrypted data partition, but I can't remember that data was ever encrypted. Is that only on stock MM ROM? I never flashed that and used KK and LP only for a couple of minutes. Since then it's AOSP ROMs I'm using, but there data isn't encrypted...or is it??? I never formatted data partition before...so when is that necessary to do?:confused:
[Galaxy S5 Mini Original Android Development] spookcity138:
I believe, but could be wrong as I have never messed with encrypting my data, but in most (all?) ROMs in settings -> security there is an option to encrypt your phone. If this is not what people are talking about then I'm also clueless on this.
[Galaxy S5 Mini Original Android Development] Pat750:
Yes, I think you're right. Forgot about that option cause I never used it...thanks for the enlightenment.
[Galaxy S5 Mini Original Android Development] ayke:
A new build has been released:

https://twrp.me/devices/samsunggalaxys5miniexynos.html

Fixes:

support adoptable storage

support kminiltexx, kminiltedv, kminilteub so basebands can be flashed

fix wiping /data while the device is encrypted

Note: by default, the device isn't encrypted. It's only encrypted when you manually encrypt it in Settings -> Security -> Encrypt phone (a process that takes a while and wasn't very stable in my experience). Most people won't need to worry about it, and most people shouldn't format /data anyway (as it will clear internal storage).

When you wipe /data, TWRP will log some errors, but it will work anyway. Reboot TWRP (Reboot -> Recovery) to be able to mount /data inside TWRP.

I haven't tested this build myself but I hope it'll work (my test builds worked fine).
[Galaxy S5 Mini Original Android Development] ffoucault:
I tried to install a zip OTA update with the latest TWRP but it abort with errors. This is the log

Any clue?
[Galaxy S5 Mini Original Android Development] ayke:
Which ROM?

Most likely the ROM needs to be patched to check for all variants of this device: kminilte, kminiltexx, kminiltedv, kminilteub.

Maybe with such a line in BoardConfig.mk, but I'm not sure:

TARGET_OTA_ASSERT_DEVICE := kminiltexx,kminiltedv,kminilteub,kminilte

If you need a fix now, the older build (3.1.1-0) should work.

Oh and thanks a lot for providing the log, it makes it a *lot* easier to see what went wrong. If only everyone did it ;)
[Galaxy S5 Mini Original Android Development] ffoucault:
Thanks for you answer, I installed the previous TWRP version and the assert_device was not a problem any more but now I got this:

I'm on a rooted stock 6.0.1 and I'm trying to install an official OTA update.
[Galaxy S5 Mini Original Android Development] ayke:
This ROM isn't overwriting the recovery? Is it a customized ROM? AFAIK Samsung ROMs all overwrite the recovery on boot if there is a custom recovery (like TWRP) installed.

Please read https://twrp.me/faq/officialota.html

TL;DR: it's not supported, sadly. Maybe you should install the stock ROM in a more conventional way (KIES? Odin?). I don't know how it works, I've only been running stock for a month after purchasing the phone.

Edit: or try installing a stock recovery (again, I don't know how this works)
[Galaxy S5 Mini Original Android Development] Friedensfurz:
You need to use an app like FlashFire to flash OTAs ;)
[Galaxy S5 Mini Original Android Development] RicSou:
Someone checked if it works Backup / restore of stock rom system / data?

Enviado desde mi SM-G800M mediante Tapatalk
[Galaxy S5 Mini Original Android Development] Pat750:
Sorry, but for me your question is not clear.

But when you run an AOSP ROM and want to restore your TW Rom that does work.
[Galaxy S5 Mini Original Android Development] RicSou:
In previous versions of TWRP, ROM stock backups fail to recover them

Enviado desde mi SM-G800M mediante Tapatalk
[Galaxy S5 Mini Original Android Development] Pat750:
Well, I only did that once and it worked with 3.1.1-1. I used an AOSP ROM, recovered stock and then recovered to AOSP again with no issues.
[Galaxy S5 Mini Original Android Development] CostasGr:
i cant find a link working for latest build
[Galaxy S5 Mini Original Android Development] spookcity138:
https://twrp.me/samsung/samsunggalaxys5miniexynos.html
[Galaxy S5 Mini Original Android Development] Panzerknakker:
Looks like build of 3.2.1 is broken on kminilte.

Edit: 3.2.1 is now available.
[Galaxy S5 Mini Original Android Development] MikeT.:
Don't know why, but I couldn't download a correct 3.2.0.img with my device (hash fails) so I used the Odin version at least.

What's the problem with 3.2.1?
[Galaxy S5 Mini Original Android Development] bothered:
twrp-3.3.0-0-kminilte

https://dl.twrp.me/kminilte/

usb otg still not functional but fine otherwise I think
[Galaxy S5 Mini Original Android Development] RolfW:
OTG not enabled/included/not working

Is there a possibility to enable OTG?

By now I' using twrp-3.3.1-0-kminilte.

Thank you,

Rolf
[Galaxy S5 Mini Original Android Development] SethGeckoXDA:
Bug report for twrp-3.4.0-0-kminilte : full wipe (including internal storage) + clean flashing lineage-16.0-20201015-UNOFFICIAL-kminilte fails with

mkdir "/cache/recovery/<LONGSTRINGWITHRANDOMCHARACTERS>/" failed: No such file or directory

Workaround as per user DoubleNegative: manually create the missing directory /cache/recovery.
[Galaxy S5 Mini Original Android Development] Panzerknakker:
twrp-3.5.2_9-0-kminilte too big?
[Galaxy S5 Mini Original Android Development] 1Maxnet1:
Same issue happens to me. It seems like there is already some work ongoing, as the repository got its first commit for over 3 years: https://github.com/TeamWin/android_device_samsung_kminilte/commits/cm-14.1
[Galaxy S5 Mini Original Android Development] 1Maxnet1:
Seems to be fixed now, new images are available on the twrp homepage
[Galaxy S5 Mini Original Android Development] nutpants:
twrp-3.5.2_9-0-kminilte fails to flash modem files or is it just me?

tried latest ctk1 (2021) img with no love.

also cant root with magisk v23 on latest oem rom ctk1, no errors with flash so maybe its the recovery
[Galaxy S5 Mini Original Android Development] 1Maxnet1:
I didn't had any issues with 3.9.2 twrp image and didn't heard of others.
[Oppo R7 Plus] gangamiin:
Hi all,

My phone is currently an Oppo R7SF, it has the "Team Win Recovery Project 3.0.2-2" (should be latest version) installed and currently no image installed so it is just the recovery.

Every time I boot up the phone it just automatically boots into recovery, tried to install some zips but it doesn't work, sometimes it says 'error 7' and sometimes it installs but it just automatically boots back to recovery.

Any help is appreciated.

Regards,
[Android Head-Units] Wolvessoulz:
Hey,

I have this Morrivoe 6.5" Android headunit, it has Android 5.1.1 on it and I can't find any information on it anywhere or any roms.

Is there a way to update or edit the Equalizer to include subwoofer control on these units?

Here's a shot of the info of the unit ; (Remove space)

i.imgur .com/aVeuUuQ.jpg

Thanks !
[LG G6 Questions and Answers] RoyalD:
Hi,

I unlocked the bootloader of my H870, installed TWRP 3.1.1.0 and SUPERSU. Everything was working great untill I decided to restore my system defaults to make a fresh start with my G6. After choosing the option to restore system defaults, my phone rebooted and it booted into TWRP. I rebooted my phone and it kept doing this all the time.

I decided to look for a stock ROM and flash that ROM.

I succesfully flashed the "LG-H87010f-Flashable.COMPLETE.zip" ROM (from autoprime's post) trough TWRP. But this did not work. I even wiped all the data from my phone (even system) and flashed the ROM again; still nothing.

Before having this issue, I had the same Baseband version, Kernel version, Build number. Only the dates and the Software Version are different.

I had the V10b-EUR-XX Software Version installed on my phone. I see this is the 10f version. I guess this should not be a problem right?

After this I took these steps solve this issue:

1. Downloaded new LG Mobile Drivers (LGMobileDriver_WHQL_Ver_4.2.0)

2. Downloaded and installed LGUP. LGUP doesnt recognize my phone as a LG G6 and this method did not work for that reason.

Fastboot mode is working on my phone; I can reboot my phone trough the commandline on my PC and things like that . However, my PC is not recognizing my phone as a LG G6 device in Fastboot mode.

My PC recognices my phone as a H870 when in TWRP. In Fastboot mode it recognices my phone as Android Device.

3. Installed LG Bridge for more drivers; did not work either

4. Downloaded Uppercut, but it doenst work without LGUP.

4. Looked all over the internet to find a Stock ROM in .zip or .img format; found nothing :(

5. Downloaded WindowsLGFirmwareExtract-1.2.6.1 and tried to extract the H87010d_00_OPEN_EU_OP_0327.kdz file. I extracted it into .bin files, but they were not usable. After that, I combined these .bin files into a system.img file. But that .img file was bigger then 5 GB and for that reason it was not usable to flash trough Fastboot or TWRP.

7. Looked for other methods to obtain a H870 Stock Rom, including another extraction method, but I cant figure out how to do this.

I have spend countless hours on this problem, but I cant find an usable H870 stock rom to flash my phone with.

Is there someone that can help me out with this problem? Im willing to donate some € if someone helps me to get my phone working again.

Really hoping for a kind person to help me out and provide me solution for this issue.

Thanks in advance ;)
[LG G6 Questions and Answers] autoprime:
Try formating data in TWRP(not factory reset) then flash the 10f complete zip. Trying to perform a factory reset from within Android could have possibly messed up your data (due to TWRP being installed instead of stock recovery) so a full data format is needed.

Lgup most likely doesn't detect the phone because you wiped system. But flashing the complete zip should have restored system.

In the future make backups in TWRP to restore later.. or flash a kdz with lg bridge or lgup without wiping system first.
[LG G6 Questions and Answers] RoyalD:
Thanks for your reply. I have already formatted data in TWRP, but im still having this problem :(. It seems like something is preventing my device from starting up. I have flashed several ROMS on other devices, but never experienced something like this. Is there something else I can try? Can I flash the stock recovery and flash the stock ROM? I got the feeling TWRP is causing this issue.

If its possible to flash stock recovery, where can I find it?
[LG G6 Questions and Answers] autoprime:
Flash the complete zip then boot into download mode and flash kdz. Lgup should see the device as a g6 now instead of unknown device. If lgup isn't seeing any device at all (including unknown device) then your setup is off.. missing drivers or something. If that doesn't work.. idk.
[LG G6 Questions and Answers] Swizzle82:
Don't factory reset using the in phone option. You can only do this through twrp's option. To fix this you'll need to boot through the hard side, using power and volume down until the lg logo appears then release power for 1 sec and then repress keeping volume down pressed. Confirm yes twice on the white screens to get to twrp. Once in twrp then reset again and reflash the system. Then using twrps img installer flash your twrp img(make sure it is on ext sd) again. Then reboot.
[LG G6 Questions and Answers] RoyalD:
Ohhh F*** YEAHH!!! :victory: Booting the "hard side" fixed the problem!! It was the first thing I tried this morning. I just booted this way and rebooted my phone without resetting or flashing anything. Im so damn happy lol. I still dont understand what happened and why my device was actling like this. But I learned a hard lesson; backup, backup and once again: BACKUP. And dont Factory reset in Android!

Thanks a lot for your help guys! I really apreciate it! :victory::victory:
[LG G6 Questions and Answers] RoyalD:
Thanks a lot for taking your time to help me out. The combination of your ROM/tips and Swizzle82's tip made me fix my phone. You're the man! :victory:
[LG G6 Questions and Answers] Swizzle82:
Probably because you already did all the flashing prior to. Glad it worked. This happened when I first got my V20 and was stoned not thinking. I reset using the in phone option and it caused twrp bootloop. I too learned the hard way.
[LG G6 Questions and Answers] ASW1:
Had the same issue, fixed it, thanks.
[LG G6 Questions and Answers] matthew33:
My phone kept doing this booting into recovery no mattery what ROM I installed.

I got into twrp by holding volume down and selecting yes on next 2 white screens....but now this message appears all the time.

please can someone help??

Here is message:

"Encryption Unsuccessful

The password you entered is correct, but unfortunately your data is corrupt.

To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset , you'll have an opportunity to restore any data that was backed up to your Google Account."

Matt.
[LG G6 Questions and Answers] Killua96:
Flash a firmware trough LGUp, or flash again the last TWRP available trough fastboot.
[LG G6 Questions and Answers] jjfgsyg:
Please help, i have the same problem and nothing, what exactly is a boot to the hard side? I ve tried to power off the phone, press vol down and power, realase power 1 sec, press again...but nothing...still boot on twrp...

Well, I finally solved it with lgup and uppercut... what a nightmare.
[LG G6 Questions and Answers] ZinX09:
Flash stocl .kdz with uppercut and lg up
[LG G6 Questions and Answers] MaxBPL:
Saved my G6!

Great tip [MENTION=5619709]Swizzle82[/MENTION]! It allowed me to restore my LG G6 after bootloop. It had not been detected by PC, and this hardware reset helped!
[LG G6 Questions and Answers] JackSparreau:
Hi, all

If I understand, and to sum up :

I rooted my LG-G6 few weeks ago, and intall TWRP. When OTA wants to install official update, the reboot stops in TWRP mod, so ... failed :-/

Is the solution to flash through Uppercut/LGUP with a .kdz file, without risk of brick the phone ?

Thx
[Moto Z Play Questions & Answers] nikhiljoshi97:
when i restart device verification failed and may not work properlyshows up although i havent rooted or unloacked the boot loader it shows oem loacked when checked . due to this apps keeps on crashing randomly

device is xt 1635-02

also i checked forums same problem occured to many people bt there was no slution available last hope is xda is plz guyz help

moto z and z force had same issues bt company provided fix for them bt not for moto z play

also resetting and updating didnt helped

plz help guyz
[Moto Z Play Questions & Answers] MiBan82:
I have the same issue. I sideload 7.1.1 with ADB but failed for the first time. Second time it passed but this message remain.

But I don't have any crashes or lags.

Can you name some apps that crashes ?

I know that some benchmark apps crashes with 7.1.1 but it is problem of app optimalization not ID error.
[MTCB Android Head Units Q&A] spirosme:
Hello friends after upgrading to last 5.1.1 malaysk the B / T adapters lost its settings and refused to connect up to the blue with MTCB 1024x768 RK3188 23 Rom of malaysk I had no problem both the mobile phones and the ODB They had impeccable connectivity.

Trying to downgrade to Kit Kat 4.4 23 malaysk again it is not possible to have functional B / T incredible. :confused:

Please give me a help thank you

Edit: The problem was solved was clean install a 5.1 factory Rom and was again operating Bluetooth
[LeEco Le Max 2 Questions & Answers] OneDiablo:
Hi guys i want to flash custom rom but i try 3 custom rom but offline charge no work

when i use cocuo92 rom or stock rom offline charge work

plss help me i need nougat

its only me?
[LeEco Le Max 2 Questions & Answers] jufece:
That's normal, if it doesn't work there is nothing you can do.

Anyway why would you want to charge your phone turned off? Use airplane mode instead.

Enviado desde mi LEX820 mediante Tapatalk
[LeEco Le Max 2 Questions & Answers] OneDiablo:
0% BATTERY on custom rom = bootloop = bye bye eco max 2
[LeEco Le Max 2 Questions & Answers] jufece:
That's fake bro, it happened to me many times. When it goes to 0% it power off, then when u plug in the charger it shows a black screen with a battery and automatically turn on after 2 mins charging.

Enviado desde mi LEX820 mediante Tapatalk
[LeEco Le Max 2 Questions & Answers] OneDiablo:
me too man i flash rr rom but now When it goes to 0% it power off, then when u plug in the charger it shows a black screen with a battery and automatically turn on after 2 mins charging

how to fix
[LeEco Le Max 2 Questions & Answers] kkcheong:
Why need to fix? Means it's good. Maybe you need to fix your understanding. LoL
[Android Q&A, Help & Troubleshooting] dark_lord:
OH developers please port a rom to oppo a57

its an awsome device its got 3gb ram snapdragon 435 and 720 p display please guys port it colour os sucks help needed :rolleyes::rolleyes::rolleyes::rolleyes:
[Android Q&A, Help & Troubleshooting] jboywonder:
OP, I know you posted this in the find5 thread as you wanted them to port the rom from this phone but since it's for the a57 I assume this technically isn't the right place to do it, anyhow:

From what I can tell Oppo has restricted access to the bootloader on these phones and we still don't have a working root method. Until either one of these circumstances changes it is unlikely that any development can begin for these phones.

If any senior devs out there have skills in reverse engineering, I would be more than happy to donate to the cause or maybe even flash your betas because at this stage what I have is a well spec'd phone that's as useful as a brick thanks to Oppo's abhorrent ColorOS. I just want root or an unlocked bootloader. :(

I'm offering $25aus as a starting point and I'm sure others would get on board with me since we all spent the equivalent of $300aus for a P.O.S phone.
[Android Q&A, Help & Troubleshooting] ECKSGK:
Oppo a57 working root

https://xdaforums.com/chef-central/android/oppo-a57-root-t3637799
[Android Q&A, Help & Troubleshooting] jboywonder:
Can confirm rooting method works but it seems like it corrupts your NV partition. Make sure you've taken a backup of yours before proceeding. Check back as we nut out a solution.

I currently have my phone rooted and TWRP installed but the bootloader still needs to be unlocked or a tool similar to magictricks.zip needs to be made to enable/install fastboot binaries on this device.

Anyone here familiar with doing this?

I can provide you with backups of the file system.

Let's get these phones free, next stop roms.
[Android Q&A, Help & Troubleshooting] dark_lord:
Phone you are using?sir

Sir

Which phone are you currently using a57 or find 5
[Android Q&A, Help & Troubleshooting] Rsugar:
I can unlock the bootloader by a software on the phone.but that software is Chinese.Would you like me to translate it into English?
[Android Q&A, Help & Troubleshooting] jboywonder:
Oppo a57

Yes please :) that would be amazing. Thank you very much!
[Android Q&A, Help & Troubleshooting] dark_lord:
Awsome development has started budding here #waiting for initial release of lineage os
[Android Q&A, Help & Troubleshooting] sagarhanchate:
Great Guys; eagerly waiting for a custom ROM that run's on this device. :good:
[Android Q&A, Help & Troubleshooting] dark_lord:
If you guys need beta testing i can help

:o
[Android Q&A, Help & Troubleshooting] dark_lord:
hows the transalating going

Bro hows the translating going
[Android Q&A, Help & Troubleshooting] Rsugar:
Tool translate worked out

mega+nz/#!GVJUwZCB

!bwRoamHnbapHtTnvZc0rF6ecPQxfcS9eHBtdrP3oVLs

I was so busy that I have no much time.sorry

TURN + INTO.
[Android Q&A, Help & Troubleshooting] dark_lord:
Nice brooh next step is porting Lineage os
[Android Q&A, Help & Troubleshooting] dark_lord:
Link not working:rolleyes::rolleyes::rolleyes:
[Android Q&A, Help & Troubleshooting] Rsugar:
It doesn't make sense:confused:

Try this:

mega+nz/#!GVJUwZCB!bwRoamHnbapHtTnvZc0rF6ecPQxfcS9eHBtdrP3oVLs
[Android Q&A, Help & Troubleshooting] dark_lord:
See the screenshot
[Android Q&A, Help & Troubleshooting] dark_lord:
Tried typing in url bar and redirecting to this
[Android Q&A, Help & Troubleshooting] Rsugar:
You should turn + into .

mega.nz not mega+nz
[Android Q&A, Help & Troubleshooting] dark_lord:
Whats the use in unlocking if you cant go to fastboot mode:(:(
[Android Q&A, Help & Troubleshooting] jboywonder:
From what I've read, there isn't a high likelihood of us getting fastboot. The main reason bootloader unlocking was possible with previous models was due to Oppo's release of 'project spectrum' firmware.

Our best approach is to make our voices heard on the Oppo forums and/or learn about reverse engineering bootloaders to create a solution.

I'm grateful that we have root (at a cost of signal), it's an excellent starting point at least. Have patience.
[Android Q&A, Help & Troubleshooting] dark_lord:
:angel: you
[Android Q&A, Help & Troubleshooting] Rsugar:
but they never mind you.As you know,oppo and vivo phones are all P.O.S phone.