Hello,
I need help for TWRP on my Samsung Galaxy A20e. My device is rooted for a while and TWRP is newly installed. But the problem is when I try to backup something, I got an error while creating the folder TWRP with the mension of operation not permited. I also have a problem when I touch the Install button, I see a list of folders with random generated names like in the photo. Can anybody help me to solve this problem? I can give more informations if needed.
Thanks for helping !
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
your device is encrypted. you must disable encryption and factory reset device in order to become TWRP functional, as TWRP cannot handle samsung encryption. or use other backup method such as Migrate.
Ok I tried what you wrote but it works only while I don't boot my device after factory reset it. If it happens, the encryption enables automatically and I can't backup anymore. Do you have a solution for this ?
you must disable encryption in /vendor/etc/fstab.samsungexynos7884
(can maybe done with zip)
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-4-0-0-for-galaxy-a20e-a202f.4141767
How am I supposed to do that ? I tried everything with this file. There is a mount option for /data "filencryption=ice". I tried to delete this with a file editor in the stock system but when I reboot my phone it reappears. When I this this in TWRP the system can't boot.
https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-4-0-0-for-galaxy-a20e-a202f.4141767
Click to expand...
Click to collapse
This link cannot help me because it is just a tutorial and when I do exactly like in i get the same results. I don't unerstand why my phone has this problem and not others. If you have other ideas i would be good
there is download for Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip flashable zip which is supposed to patch fstab (last step in tutorial). you must mount system/vendor writeable (checkbox in TWRP)
aIecxs said:
there is download for Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip flashable zip which is supposed to patch fstab (last step in tutorial). you must mount system/vendor writeable (checkbox in TWRP)
Click to expand...
Click to collapse
I tried installing this zip file from the SD card but it didn't boot (locked on samsung logo) so I did a factory reset with TWRP and after configuring, I got the same results than before.
- in TWRP double check your vendor partition is separate partition (or directory inside system partition)
- in TWRP terminal make sure partition is mounted rw
Code:
mount /system w
mount /vendor w
mount
- install Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
- in TWRP terminal double check fstab.samsungexynos7884 file fileencryption= flag is gone
Code:
cat /vendor/etc/fstab.*
- in TWRP - wipe - format data - type yes
Thanks for the instructions. It works perfectly ! I am just an idiot because I didn't wipe /data in TWRP but I just swiped to factory reset. Thank you a lot !
maybe I was misleading you with factory reset. might be that TWRP factory reset just behaves like simple wipe, where only files are deleted excluding /data/media
formatting whole partition is required for removing encryption.
edit: Please note if you're interested in undo the patch, you must restore vendor partition. you can of course add the fileencryption= flag back with text editor yourself. However that requires linux line endings (LF) so you can't use Windows text editor (CRLF) that's why you should use Notepad++ and enable view for invisible chars with (π) button. Do not simply copy file back into /vendor you will lose file permissions. Do not use sed you still would lose secontext. only copy content of file into old existing file like this.
Code:
cat /tmp/fstab.new > /vendor/etc/fstab.samsungexynos7884
Btw if you're running custom ROM (such as LineageOS) it's possible to break samsung encryption and use AOSP encryption as fallback by deleting keystore.mdfpp.so and keystore.msm8953.so from /vendor/lib/hw. This way you can use TWRP on encrypted device.
Related
Hi,
here comes Recovery for Play of Team FreeXperia.
Download here: (Beta1 - Update 20.06.2011 - 18:28h GMT+1)
http://www.multiupload.com/VC3JRZ74H0
Broken:
Cannot backup&restore boot partition (kernel related)
To test use this command:
fastboot boot recoveryPLAY.img
Button mapping: (thanks Logseman)
Back- Back
Home/Vol UP - Up
Menu/Vol DOWN - Down
Search - OK
Please DO NOT FLASH! This recovery is designed to work just as recovery, if you flash it to your device it will NOT boot system anymore!
Please test and report functions. If there are errors please include EXACT outpot of errormessage.
Thanks to Blagus for his Xperia Play Kernel!
To gain root on every ROM (Stock ones too) just flash the attached RootXperia.zip via Recovery
Regards
Bin4ry & Team FreeXperia
I assume we need to install the custom kernel first?
No! You have NOT to install custom kernel to use this.
Just issue the command i wrote on your windows console. Then phone boots into recovery!
Regards
Logseman said:
I assume we need to install the custom kernel first?
Click to expand...
Click to collapse
The recovery image is structured exatcly as boot.img, with the difference in executable files - regular boot.img boots Android system from /system partition, while recovery boots into... well, recovery
So, since it's structured just as boot.img, you have to pack kernel inside as well. That's where, in this case mine, zImage comes in handy instead of unpacking SE's special boot.img structure, it was easier to take zImage from standard boot.img.
ive just tried it now, boots into CWM fine, im going to try a nandroid and report back
It looks weird in this DDMS capture, but in the phone it looks all right (black background, orange text). I've had no error messages of any kind.
Button mapping:
Back- Back
Home/Vol UP - Up
Menu/Vol DOWN - Down
Search/Power - OK
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This capture looks funny
But important is how it looks on device. I doubt that ddms cannot capture 32bit framebuffers
Regards
Bin4ry
Ok, i did a nandroid, rebooted, booted back into bootloader and fastboot erased /system/, pushed the recovery back and tried to restore /system/ but i get the error " Error formatting system " i also get the same error in the mounts & storage menu can i flash the nandroid image from fastboot?
*edit* no it wont let me flash it from fastboot, it tells me the image is too large lol probably because i moved some widgets and lwp's to /system/, no worries i'll flash the image in the development section.
Recovery booted fine, did a nandroid backup worked fine, not sure i want to follow suit and delete a load of stuff and try restore. will wait to see what androhero and bin4ry can figure out first with andro's issue
mehmehmen said:
Recovery booted fine, did a nandroid backup worked fine, not sure i want to follow suit and delete a load of stuff and try restore. will wait to see what androhero and bin4ry can figure out first with andro's issue
Click to expand...
Click to collapse
try and clear cache, see if you get the same error? if the action works it wont matter if cache gets formatted
I hope you can help me figure this out, because right now I am astonished at least.
I've been poking around with ClockworkMod, and getting a couple of errors. I know there is an error reporting utility inside CWM, "Report Error" in "advanced" so I made use of it. However, the log would save to "/sdcard/clockworkmod/recovery.log".
Since I'm using the custom kernel, I'm not able to use the sdcard as it seems to be improperly mounted. It shows as mounted in CWM, I unmounted it and remounted it again to no avail... though it can be mounted on the computer properly.
However, that's not the point. I thought I'd do a search on "recovery" with Root Explorer, wanting to find the Recovery.log somewhere else. And boy, did I find it. I found the two recovery logs I saved inside the folder /data/system/dropbox . I happen to have DB installed in my Android. But not only that, I found my kmsg logs, and boot logs, registered there as well.
Hereby I attach the two recovery logs. Does it make sense that these kinds of logs are saved in such a folder? Am I worrying unnecessarily?
this is one of the reaons why google take root access off us in the first place isnt it?
Thanks for the logs.Dunno why they was stored in DB folder
@AndroHero:
Yes just restore the img files from backup via fastboot flash.
Regards
Bin4ry
where excatly do i put the play recovery.img?
crispyduckling said:
where excatly do i put the play recovery.img?
Click to expand...
Click to collapse
just put it in the same folder as fastboot.exe
When backing up the progress bar doesn't work and it can take some minutes, so just be patient when doing a back-up.
Are their any specific options you like us to play with?
AndroHero said:
just put it in the same folder as fastboot.exe
Click to expand...
Click to collapse
cheers mate
okay so i formatted the cache and it comes back
Cach wipe complete.
E:Can't Mount /cache/recovery/log
E:Can't Open /cache/recovery/log
E:Cant mount /cache/recovery/last_log
E:Cant Open /cache/recovery/last_log
it wiped cache ok but is this error something i need to be worried about in away before attempt wipe and restore of system with my nandroid?
Do not bother trying to restore a nandroid backup: the /system partition won't get formatted and the operation will be cancelled.
The back-up made a cache.img, data.img, system.img and a .android_secure.img
I assume I can flash the system.img with fastboot like I used to do when rooting through fastboot? Could safe me the bloatware removal trouble after I get into a bootloop (yet again ).
Hi!
Story goes like this. I have here clone Samsung S4 that I wanted to update the software trough CWM. Unfortunately phone died at some point and now is dead. But, I made backup of the flash with MTKDroidTools and with SP flash tool... and here comes the problems... I can not flash backup back to phone because yaffs2 files are not good page/spare ratio. Thanks to members rua1 and Alex1948 now it is more clear how to change spare ratio on yaffs2 files. Unfortunately I'm not very good with Linux, last night I boot Mint 16 from USB stick and was trying to repair my files but without success.
So, my question is: is someone willing to repair my files in Linux (who understand Linux terminal better)?
Here are some details from phone
View attachment 2574910
View attachment 2574911
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I only have problem with flashing yaffs2 files and secro.img all other are OK. If I try to flash those files I get this error
In attachment is mtd, dumchar_info, MTKDroidTools log and Sp flash tool log so you can see my file structure.Log from MTKDroidTools is from version 2.5.2 because I was using this version when I was making backup from my original phone (you will see other phones data just scroll down to MT6575)
I'm uploading original yaffs files to google drive so later I will update this post with some links.
Thank you all in advance.
Best regards
P.S. INFO FROM MTKDroidTools IS TAKEN FROM SAME PHONE LIKE MINE (FRIENDS PHONE) YES, SAME ONE HARDWARE AND SOFTWARE IS 100% SAME.
Files on Google drive link
https://drive.google.com/file/d/0Bx8Xjd1q6dr3YnFISVJBZFZPSUU/edit?usp=sharing
Little update (memory type)
View attachment 2575196
from guide:
Аttention! Yaffs2 type blocks from this backup can't be Downloaded to phone, they aren't correct! Use backup on 9th step if phone have yaffs2 type blocks!
Click to expand...
Click to collapse
files from archive is wrong
from your log:
10/02/14 11:43:23 Free space: system- 113.7M; data- 54.3M; sdcard- 16.7M; D:\ 170861M
10/02/14 11:43:46 - ERROR - tar: write error: No space left on device
Click to expand...
Click to collapse
it was necessary to release the free memory on SD card before
Hi!
First, thank you for your reply.
Yes , I did figure it out that my files are not OK. I was trying to make them manually in "yafey" for windows (software to create and edit yaffs2 images) but this software have to much bugs so one time it create system.img with full lib folder second time only half of lib files are there and also there is no option for spare ratio change.
So, MTKDroidTools did make my system backup in a folder on my PC but I can not make yaffs2 file from it because there is no software for windows that works fine (I don't use Linux). On Linux it is easy to do (at least for someone who understand Terminal commands).
So, I can send you my backuped system folder if you are willing to make yassf2 file from it (in Linux). Data and Cashe files I have create in yafey and thay are ok.
In yafey if I make new yaffs2 file and insert lib,etc,app,framework... it will not create all files in folders... and after that when I try to flash that created system.yaffs2.img I have error from BROM s_ft_readlen_not_page_aligment (4017) again problem with spare ratio.
I still have here my friends phone so if you have any idea what to do and how to do please tell. I made backup from my friends phone but same thing data,cache,system,secro files are not created correctly. I don't know why is this is it because of the MTKDroiTools or is it because of the phone?
Aaaaaaaaaarghh!!!!!
You wouldn't beleive what I just discover I just try to put my friends phone in recovery so I give a try to make backup.
NORMALY my friends phone don't want to go in recovery (just light on screen), so I have call my friend to ask him does he do something with phones recovery and he said YES i flash some recovery from net trough CWM and after that he can not go in the recovery.
CAN YOU BELEIVE HOW UNLUCKY I AM????????
If someone have any idea???
Basically, there are 3 types of flash method for K900
SDFUSE
OTA Recovery
MFT (Manufacturing Flash Tool)
There is a lot of question, asking about why same version of VIBEROM_V1.0_1411_ST_K900 have so many method of flashing.
There are too many information from the general thread. so I create new thread here for beginner to understand more about flashing.
From my understanding, there are only one version ROM (eg. VIBEROM_V1.0_1411_ST_K900).
But there are a few format for different flashing method.
1) SDFUSE
This format usually flash by create sdfuse folder in internal SD. Normally for update ROM
Copy files system.img.gz, boot.bin, dnx_firmware.bin, etc. (or .inb file which is the one and only one file) into sdfuse folder.
Shutdown and boot up by pressing power + volume up for couple of seconds
select SDUpdate and press power to start.
After done select power off, then power on again. (direct reboot may cause boot loop)
2) OTA Recovery
The format of rom is in ZIP. The zip is signed and there will be checksum (SHA1 and MD5) during flash. so the zip is unable to modified before flashing.
this method normally for update ROM too.
Copy update.zip file into sd card (recommended is at root of SDCard) and shutdown.
Boot up by pressing power + volume up for couple of seconds, then select recovery.
wipe data / Factory reset and wipe cache partition ( optional, which will wipe all data in sdcard)
apply update from internal storage and select update.zip
system will reboot after done.
This does not works for me to upgrade to 4.3 where I am on Qubex Vibe ROM v4.
But there are a lot of K900 user able to flash original Vibe ROM v7 and follow the above method and upgrade successfully.
Refer this http://forum.xda-developers.com/showpost.php?p=51069544&postcount=3142 or
http://forum.xda-developers.com/showpost.php?p=51128922&postcount=3199
if you are using official Vibe Rom v7. There are a easier way to flash.
copy the downloaded OTA zip file into SD Card.
Go to System upgrade, swipe left get menu, and select tools.
Touch Install specified update package and browse for OTA Zip file in sd card.
Touch install Now.
3) MFT
This method require computer with driver and software installed and USB cable for sure.
Refer this http://forum.xda-developers.com/showpost.php?p=51162040&postcount=3245
I got this method successfully when I am on non-official Vibe rom.
Please correct me if I am wrong.
Thanks to Onesjy at lenovo forum.
http://bbs.lenovo.com/forum.php?mod=viewthread&tid=154595&extra=page=1
Edited:
From my experience, the MFT method is always succeed.
Url for latest 1418_DEV MFT : http://forum.xda-developers.com/showpost.php?p=52500023&postcount=3745
MFT
i know how to use it but where can i find Manufacturing Flash Tool 6.0.2??
As far reported to me by QuBeX the ADB mode is not working on that device... I guess for the issue we have with MFT, it is the only solution we can look for also because I haven't forum (and have to open it) a thread where to speak about the recovery of a stock ROM.
About the Method N.3, most of the compatibility issues are related to the OS you are working on.
For the Settings you have to apply what you see below...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
... about the libraries, instead, download that packages and replaces (if so) the files already present in the 32 / 64bit Windows' system folders: https://drive.google.com/file/d/0B282FXce0kggSHpHSDRROFNZaEU/edit?usp=sharing
You can find the Applications as well the Drivers you need directly starting from that shared folder: https://drive.google.com/file/d/0B282FXce0kggSHpHSDRROFNZaEU/edit?usp=sharing
imei changed to null
i tried to flash viberom using sdfuse method but after flashing imei changed to null how to retore it
help
TWRP Alpha build for MT2-L05(LianTong) TeamWin Recovery Project
Not working:
Could not handle Internal Storage properly, i.e., Wipe data will wipe internal storage as well.
Most of the text and even the config/build itself is copied from Modding.MyMind work on US version MT2L03. Thanks, Modding.MyMind
****ALPHA Version WARNING *** IMPORTANT *** MUST READ ****
Please note, due the structure of this phone storage, the Internal Storage (/storage/emulated/0 size 12GB) is actually shared with /data partition, and the mount point is /data/share, this is not same as google recommended value /data/media, and current TWRP code could not handle this properly. Also Modding.MyMind has PM'ed me that he probably will spend less and less time on XDA/development work, and I really lack of expertise/time on this one, so This build didn't resolve this issue. That's why I labeled this as ALPHA version.
Internal Storage /data/share /storage/emulated/0 size 12GB
External SDcard: /mnt/media_rw/sdcard1/ An SDCard is required to use this TWRP build and recommended 32GB or bigger.
For more information about this issue, please check TWRP article http://teamw.in/DataMedia, and please noted that it mentioned "A stock AOSP recovery would format data including the "sdcard" but TWRP will use its regular factory reset setup that leaves the internal storage intact" is not working in this TWRP alpha build., i.e., This TWRP will wipe your internal storage when you wipe data.
So, using this TWRP recovery, fact is:
. The backup target must select External Storage.
. Backup /data will include the internal storage, and this partition size will be ~12GB if uncompressed.
. Restore /data will override internal storage area.
. Wipe data (Factory Reset) will wipe internal storage as well.
Please read above carefully, and understand the risk of using this alpha build.
Recommended approach:
In your daily usage of the phone, try to save everything to external SDCard, or manually backup internal storage to external SDCard frequently.
When using TWRP, back/restore following partition is safe:
/boot
/recovery
/system
And always take caution when backup-restore /data, also, it is recommended check the compress option when do the /data backup.
Again, Many application may save files into Internal Storage including the pictures you taken, and files/songs you downloaded. So be aware of the risk of using this TWRP that may wipe the internal storage. If you are not clear/comfortable of this risk, please do not install this TWRP.
****ALPHA Version WARNING *** IMPORTANT *** MUST READ ****END****
Disclaimer: You are responsible for insuring you keep a backup of your stock recovery!
Steps for Backing up Stock Recovery:
within a terminal using dd (aka Data Destroyer);
Code:
su
dd if=/dev/block/mmcblk0p18 of=/mnt/media_rw/sdcard1/stockrecovery.img
TWRP for MT2-L05
Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. Its a fully touch driven user interface no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Installation (PC):
- You MUST have an unlocked Bootloader!
- Download TWRP Recovery
- Boot to your Bootloader
- Plug your device to your PC
- Open Command Window
- Type, then Enter:
Code:
fastboot flash recovery /path/to/TWRP.img
Download:
- TWRP 2.8.0.0
File name: TWRP_MT2L05_Alpha.img
File size: 11,040,768
md5sum: b8832fc6dfd5d6e47e63ba7f7e047518
CONTRIBUTORS
@Modding.MyMind
@xordos
And thanks @4L0M for the testing that is dangerous due to the nature of twrp
SOURCES
- Recovery built in a OmniRom 4.4.4 environment using device trees/kernel
- Stock Kernel
- TWRP source from Omnirom
- MT2-L05 Device Configuration Folder - My Github
VERSION INFORMATION
- Status: ALPHA
- Created 2014-10-03
- Last Updated 2014-10-29
//reserved
Great work. If anyone could help finish this project off, I am more than happy to keep testing. If we can get this recovery fully working, then I think we would be far closer to understanding how to port kitkat to the MT2-L03 devices.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Yes, I do have an idea/workaround for this issue, and hopefully open this discussion thread can get more idea/evaluation going on.
The /data/share folder is treated as internal storage, but twrp is hard coded /data/media in many many places. So maybe we can rename 'share' to 'media' when boot into twrp, then rename back before reboot. But the 2nd part may not easy to guarantee. If it get into normal OS booting, it may cause confusion even damage.
So I am not like this workaround even myself.
disregard...
I think B606 breaks recovery. After I update to B606 and reinstall TWRP, it just hangs on splash screen every time I try to enter recovery.
Hi, i flashed the recovery using fastboot and then i tried to reboot into recovery but the phone just reboot after 1 try. here is my bootloader screen. Plz tell me how to root this phone. Its unlocked but i'm unable to root it.
Jolla SailfishOS 3.2.0.12 linux
IT IS NO ANDROID!
There's no guarantee nothing, don't use it if you don't know what you're doing!
SAVE your DATA before!
Make sure you have a custom recovery installed (TWRP is the preferred recovery. [I'm not using Fox recovery, I'm not going to give you advice.])
The full install tested with Official ugglite 3.3.1 TWRP.
Download LineageOS 14.1 & SailfishOS.
NEED FREE INTERNAL STORAGE SPACE ~2GB!!!!!!
NEED UNSECURE EXT4 /data Partition!
Boot into recovery.
Wipe data, cache,system partitions.
(If your /data partition secured, you need format /data to ext4 if you want to use this ROM.)
Flash LineageOS 14.1 ugglite ROM in TWRP (sideload or copy any storage)
Reboot, start LineageOS 14.1 (If TWRP warn that there is no system, it doesn't matter, go reboot.)
First boot may take up to 2 minutes.
Restart to TWRP again.
Flash SailfishOS 3.2 ugglite in TWRP (sideload or copy any storage)
Reboot
First boot may take up to 1 minute.
ssh: [email protected] (change password: settings - developer menu)
Dual boot: flash with TWRP or 'fastboot boot' Lineage boot.img, or flash with TWRP or 'fastboot boot' hybris-boot.img, from zip files.
Sailfish OS workig from /data partition, if you wipe data, deleted Sailfish OS
BACKUP, before wipe data.
Bugs:
No bootsplash.
Boot time 50-60 sec. Power off charge animation ~50 sec. Reboot, and power off time 15-20 sec.
I could only create a Jolla account on a PC.
Some video types are not playable (Jolla license).
DOWNLOAD ROMS SF
DOWNLOAD ROMS AFH
Known issues: don't know
I'm not going to give you support for privat upgrades and other changes, fix it for yourself. Sorry.
*
Screenshots: LINK
ROM OS Version: 14.1 & 3.2.0.12
ROM Kernel: Linux 3.18-31-szancso & 3.18.140-szancso
ROM info: Lineage-14.1, system partition, Android quota no.
If you have previously used Android 9.x or 10.x ROM which has a quota set on the data partition, you can remove the quota in TWRP, and not need format the data partition (this method tested, working was for me, but no guarantee for by all means)
commands:
Code:
tune2fs -O ^quota /dev/block/bootdevice/by-name/userdata
tune2fs -Q ^usrquota,^grpquota /dev/block/bootdevice/by-name/userdata
If you then use a ROM that configures quota (fstab.qcom), you can start over, if do not want quota. Or cleaning from fstab: "quota".
Created 2020-03-08
Last Updated 2020-03-08
I am not aware that it contains malicious code in the ROM, I have never put it in. This is a ported ROM, all its elements come from the Internet.
Test update and alien-dalvik Android support:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to update ?
ByHorvyCZ said:
How to update ?
Click to expand...
Click to collapse
I do not support the update.
There may be a problem with WiFi, sounds, lights, etc.
If you want to upgrade, you have to solve it yourself, because if you can't upgrade it yourself, you can't fix problems.
Alien-dalvik is not going to be with upgrade, a separate thing, and to my knowledge warez. Anyway, it's almost uselessly bad. (At least the version I tried.)
I do not support this too. Sry.
Yes you're right. I tried to make a force update through the terminal.
Now Wifi doesn't work. Otherwise, I put it into operation.
I upgraded the system just to make sure other accounts were working.
Warning, do this at your own risk.
!!You can ruin the system or worse the whole phone !!
So, okey, open your terminal. :angel:
Code:
devel-su
Then you enter the root password, :good:
Code:
ssu release 3.2.1.20
This sets up what you want the system to update
Code:
version --dup
This will start the process of updating.
You should never close the terminal when you're running this command.
After all, restart phone, and you are done ! :silly: