Related
Hi people, here is a short instruction if you have a P or L version of the I8160 and want to update this (great) old phone. credits to xdas-e
for a while i thought that roms didnt work on the P version, because when installing roms i got the error that the rom was only for I8160, not I8160P. so yeah it is possible, maybe this is common knowledge, but i couldnt find out how before i found this information.
I have not tested this exhaustively but i believe they all should work, because i believe the only difference from the P version is that it has an NFC module.
]------- modify the rom for P version:
1.- Get the custom ROM.
2.- Get the /system/lib/tee folder contents from your GT-I8160P JB installation (from stock rom). You may need root access, although in my case I could simply move trough the hidden directories and copy the folder to my sd card.
3.- Swap the /system/lib/tee folder, and put what you got from step 2, into the zip file of step 1, same place, same everything. You may very well dispose the original /system/lib/tee folder in the zip file.
4.- Change /system/build.prop and introduce a P in every GT-I8160 entry (from GT-I8160 to GT-I8160P).
5.- (tricky one) look for the updater script file within the custom ROM zip file, and delete (or add a P) the first complete entry of the assert command (you shall see some GT-I8160 there). in my case it was located under META-INF\com\google\android\.
------- from here you have successfully modified the rom for the P version, these steps just show the installation:
6.- If you dont already have CWM, get yourself one (I used this one [JB] CWM Recovery 6).
7.- Put both zip files into your sd card; get a copy also of gapps (google apps, play store etc) for the android version of the rom.
8.- Back up all your data.
9.- Swicht off your phone and restart in recovery mode (up volume, home and power buttons pressed simultaneously).
10.- Load from the external sd card the CWM zip file.
11.- Make a full ROM backup to restore if things go wrong. Wipe data/factory reset; wipe cache partition; wipe dalvik cache (under advance options), format /system if needed (see rom instructions).
12.- Install from external sd card: a) custom CM rom; and b) gapps if you're for it.
13.- Restart.
14.- You shall be done!!! (first boot takes a long time)
good luck! my phone was crap with stock and now it works great, so basically it saved me from buying a new phone.. a big thanks to all the rom developers for this device .
I am making available the Nandroid backup of the Samsung Galaxy Tab 4 10.1 T530NN. I searched the net and did not find this available in any format. I have tested this and it will work if installed properly. This Backup will probably work in other Recovery packages, but has only been tested in TWRP 3.0.0-0. You're welcome to re-install any Recovery you wish afterward.
Instructions:
1) Install TWRP 3.0.0-0 (Use the Matisse variant for the T530NN) and boot directly into Recovery.
2) Backup your current configuration. This process WILL wipe everything!
3) Using Android File Transfer or ADB, upload the folder from the expanded Stock_5.0.2_Nandroid_LRX22G.T530NNUEU1BOJ3.zip file to the folder /TWRP/Backup/<your device's serial number>/ of either the Internal Storage, or SD Card, whichever you did your Backup to in step 2..
4) Select Wipe to wipe the Data, Cache and Dalvik partitions.
5) Still in TWRP Recovery, select Restore to restore the Stock_5.0.2_Nandroid_LRX22G.T530NNUEU1BOJ3 package. This will overwrite Everything! You can probably get by with selecting only the System, but I saved everything to be sure to get a full reset to stock.
6) Reboot into Recovery again to allow TWRP to make adjustments to the System to keep it rooted.
7) Reboot into System. This will take you through the initial setup to activate your Gmail account and such.
8) Install SuperSU from the Play Store to complete the Rooting. If you'd rather render the tablet un-rooted, that option is in SuperSU's Settings.
I hope I posted this correctly. If not, I welcome admins to properly chastise me.
I made TWRP backup of the most possible partitions if someone need it.
Backup of Stock ROM LDN-L21C432B139 (8.0.0.139)
Also made partition images of stock via DD command via ADB, or FF-ddumper app.
Since /data is encrypted, can not be backed up in current TWRP.
Data EMMC image (with internal sd) can be backed up via TWRP via DD/TWRP to SD/PC/USB-OTG with filesize about 25 GB.
TWRP with all partitions (no FBE nor MTP): https://www.androidfilehost.com/?fid=1395089523397910855
Stock ramdisk: https://www.androidfilehost.com/?fid=11410963190603879149
Stock recovery_ramdisk: https://mega.nz/#!9gAnjCoR!oaC3sCYdgbiia6RK6BemO0MxydhEAaJjSnkWLCS5kII
TWRP backup folder: https://mega.nz/#F!ApJjiSjC!yzX_aAgKdyHI91sXQmn-jg
Images backup folder: http://https://mega.nz/#F!lgYATKIY!dOXy5bmwoBzIGT9qjko96A
Backup of Stock ROM LDN-L21C432B142 (8.0.0.142)
Before any changes, please backup your /system, /vendor, /kernel, /ramdisk, /recovery_ramdisk for just in case in twrp.
For /data backup online copying of files or Migrate app or Titanium BackUp or something else method.
Extracted from update.app: https://www.androidfilehost.com/?w=files&flid=291939
Changes from original: Permissive /Kernel by @EzzUsesAndroid (repacked to 142), Magisk-patched /Ramdisk, Custom recovery, Removed DM-Verify + FileEncryption from /Vendor, Replaced bootanimation to walking fingers in /Product.
After restore, reboot to RECOVERY, not to system, and Data have to be formated! <--- This will remove encryption and set partition to encryptable=footer, so in the future you can backup and /Data (without internal storage). Since it is encryptable, Magisk Manager will shows turned on "Forced encryption" but it is not. You can encrypt it later (but I don't know how).
TWRP backup folder of main partitions: https://mega.nz/#F!ZgQxlSDD!s4eAEun2bC4MrIRL3mcgRA
If you want to keep encryption, flash this, after restore, (before reboot to twrp), but DO NOT format /data, just wipe.
If you just want to remove encryption for any rom, flash this, after restore, before reboot to twrp and format /data.
If you wipe/format data to remove encryption or use custom rom, flash /data/hm_init backup via TWRP: mega.nz
SE Linux permissive kernel by Ezz, needed for custom roms: this post
I have a question, when I want to go back to stock rom (currently running AOSP 9.0 GSI), do I only need to restore the two system.ext4 in the TWRP backup folder?
Proseph said:
I have a question, when I want to go back to stock rom (currently running AOSP 9.0 GSI), do I only need to restore the two system.ext4 in the TWRP backup folder?
Click to expand...
Click to collapse
Yes - you had to restore system.ext4 (splitted in 2 files), but also to format /Data and /Cache and restore backed apps/data later, after stock system successful boot.
If you had already remove "verity" and "fileencryption..." flags from /vendor/etc/fstab.qcom and recovery.fstab, I guess you only need to wipe /Data and /Cache, after restoring /System.
And you need to match stock rom versions in /system as in /kernel as in /version.
I made TWRP backup of stock 8.0.0.142 (feb-2019) with no verify, no forced encryption, with permissive kernel. You can use that or extract images from update.app.
stock rom in 3 files.
Update 1:
I saw that there is newer version 8.0.0.143 (march-2019) for LDN-L21B model, eu firmware C432. No need to restore /data/hw_init folder, just flash
update_data_full_public.zip and update_full_LDN-L21B_hw_eu.zip, ignore error 7 etc, works fine.
STOCK RECOVERY FOR HUAWEI Y7 Prime LDN-L21C185CUSTC185D1
I had flashed stock recovery of ldn-l21 c432 to my phone (LDN-L21 C185CUSTC185D1) now it is not working it is unable to reset my phone and install update from huawei Plz Provide ma stock recovery of Huawei LDN-L21 C185CUSTC185D1 (8.0.0.159)
lineage os
Could by any chances one assist on getting the lineage os for huawei y7 prime 2018
Arsam javed said:
I had flashed stock recovery of ldn-l21 c432 to my phone (LDN-L21 C185CUSTC185D1) now it is not working it is unable to reset my phone and install update from huawei Plz Provide ma stock recovery of Huawei LDN-L21 C185CUSTC185D1 (8.0.0.159)
Click to expand...
Click to collapse
Sorry for year late reply! Latest stock rom is 8.0.0.166.
Code:
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3004/g1650/v373698/f1/full/update.zip
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3004/g1650/v373698/f1/full/public/update_data_full_public.zip
http://update.dbankcdn.com/TDS/data/files/p3/s15/G3004/g1650/v373698/f1/full/LDN-L21B_hw_meafnaf/update_full_LDN-L21B_hw_meafnaf.zip
In update.zip, there is update.app, in update.app is named recovery.img.
There are kernel, ramdisk, recovery_ramdisk, recovery_vendor, eRecovery (all 3 files) @ mega.nz
Jack6617 said:
Could by any chances one assist on getting the lineage os for huawei y7 prime 2018
Click to expand...
Click to collapse
Hello. For Lineage 15/16/17, see this post. In short - you need to flash SE Linux permissive kernel to /kernel, wipe /system, /data and /cache and flash GSI image of custom rom to /system.
Backup of Stock ROM LDN-L21C432B151 (8.0.0.151) with few additions
WARNING: Do not flash any partition if you do not know what are you doing!
Spoiler: Changes from stock
Removed system apps
Google Duo, GMail2, Google Maps, Google Music, Google Search, Google Videos, SwiftKey (2 apps), M$ Exchange.
Updated/added system apps
Google Chrome, some keyboards, airplane mode apps and audio DSP app.
Removed user apps
TouchType configs, AsphaltNitro, AssassinCreed, Booking, DisneyMagicKingdom, DragonMania, eBay, Editor office apps, Facebook (2 apps), Instagram, Netflix (2 apps), PuzzlePets, SpiderManUltimatePower
Updated apps and moved to /data/hw_init (need to flash hwinit.zip) as can not fit to /cust
HiMovie (Huawei Video Player), Themes, HiCare, Smart Diagnosys, Files, Cloud, HMS, AppGallery
System partitions
ramdisk is magisk patched ..... (if prefer stock, flash RAMDISK.img)
kernel is updated to 3.18.140 and permissive ..... (if prefer stock, flash KERNEL.img)
recovery is custom (TWRP 3.1.1.0 with internal storage) ..... (if prefer stock, flash RECOVERY_RAMDISK.img)
vendor has removed dm-verity and removed forced encryption and updated OpenGL and Vulkan drivers!
product has custom bootanimation (walking fingers) ..... (if prefer stock, rename /product/etc/media/bootanimatiorigin.zip to bootanimation.zip)
LDN-L21B @ mega.nz
[GUIDE] f2fs for stock, developer and custom - roms
This is my first post in xda, im a silent reader since years.
Just registerd to post this because so many people always asks the thing with f2fs and if the rom have f2fs support.
Dont ask again, make it support on your own!
its not magic, its just format the partitions, editing two lines in fstab and flashing the right kernel.
Caution! You will lose all data from internal storage so please backup your files!
What you need:
1. unlocked android device, i´m on Redmi note 5 Global 4/64
2. pc or notebook with adb and fastboot
3. custom recovery solution, i use original latest twrp
4. off course a rom of your choice, in my case xiaomi.eu latest developer (MIUI 10.4 / 9.5.16)
5. a kernel that supports f2fs, i use KangarooX r4.4 with OC but ice cold etc. works also
6. a texteditor, i use the windows notepad
7. time
Ok, lets go:
All this things must be done in a row, without reboot!
1. remove fingerprint, face and pin unlock on your running device
2. boot into twrp by pressing vol up + power button
3. go to wipe > make a factory reset
4. go to wipe > advanced wipe > select Cache > repair or change file system > change file system > select f2fs
5. go to wipe > advanced wipe > select Data > repair or change file system > change file system > select f2fs
6. connect your device to pc
7. transfer your rom, kernel and all your files you need to internal storage or take your sd card (i prepared my sd card)
8. flash your rom
9. flash your kernel
10. flash your other stuff (i flashed magisk)
11. check your cache partition, it should be f2fs if not, change cache file system again (Point 4)
12. mount the vendor partition
13. on your pc, go to your adb folder and check in terminal if device is listed
14. type in terminal without quotes "adb pull /vendor/etc/fstab.qcom"
15. edit the fstab.qcom with your editor, search for the data and cache lines
16. edit the line for the cache partition that it looks like "/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait" without quotes
17. edit the line for the data partition that it looks like "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,background_gc=off,fsync_mode=nobarrier wait,resize,check,crashcheck,quota" again without quotes
18. save the file and push it to your device with terminal "adb push fstab.qcom /vendor/etc/" remember without quotes
19. set permisson of the file in terminal or twrp, i use terminal "adb shell" > "cd /vendor/etc" > "chmod 644 fstab.qcom"
20. now you´re ready to reboot the device and have a lag free gcam pixel3, etc.
After reboot, check your partitions with diskinfo or similar.
This guide should also work with other devices.
Happy flashing and i hope you enjoy
PS: my english is not so good as it can be
Remember: if you flash the vendor partition, you have to edit the fstab.qcom again!
its easier to convert to f2fs data and cache and flash datafix-fstabs cachefix-fstabs in twrp
JA
raptorddd said:
its easier to convert to f2fs data and cache and flash datafix-fstabs cachefix-fstabs in twrp
Click to expand...
Click to collapse
but not work for MIUI
RubenPCA said:
but not work for MIUI
Click to expand...
Click to collapse
yes it does. i am using in xiaomi .EU
Both methods work.
Let me explain why i posted this tiny Guide.
For people who are not familiar with operating systems in this case android, its allmost tricky to find the right solutions or files without any clue what they need.
If you do things from ground, you understand what you´ve done and are able to fix it or remove it by yourself.
I personally prefer the way to do things on my own and not spend many hours to search for the right files, to download and flash without any clue what they do or how they work.
When i decided to change the filesystem of my devices, i started to search and found fragmented solutions over the net.
Btw. doesn´t found the 2 zip files easy. Heard the first time as you commented this tiny Guide. So i started to search and found the hint in a different comment from you, it can be downloaded from a telegram group.
Anyway, i doesnt had this files but knowledge in linux, so i decided to change the lines quickly by myself. It isnt much work and its always the same so you can copy and paste the two lines.
To make the choice and search for the peoples easy, here ist the link to the thread where you can find the telegram group to download the files https://forum.xda-developers.com/redmi-note-5-pro/help/f2fs-miui-pie-roms-t3922370
raptorddd said:
yes it does. i am using in xiaomi .EU
Click to expand...
Click to collapse
Do you need to reflash cache and data fix after every rom update/dirty flash?
sushuguru said:
Do you need to reflash cache and data fix after every rom update/dirty flash?
Click to expand...
Click to collapse
it depends on the rom that you want to flash.
The file that needs to edit from hand or the two zip files is on the vendor partition.
In short, the file tells the System witch partition with attributs, names and filesystem is automatic mount during the startup process.
Gerr1 said:
it depends on the rom that you want to flash.
The file that needs to edit from hand or the two zip files is on the vendor partition.
In short, the file tells the System witch partition with attributs, names and filesystem is automatic mount during the startup process.
Click to expand...
Click to collapse
Xiaomi.eu in my case, wonder if the rom will replace the file has been fixed after flashing.
sushuguru said:
Xiaomi.eu in my case, wonder if the rom will replace the file has been fixed after flashing.
Click to expand...
Click to collapse
Dont know, try it out. If the phone doesnt boot, go to twrp and flash the zips again.
sushuguru said:
Do you need to reflash cache and data fix after every rom update/dirty flash?
Click to expand...
Click to collapse
yes. rom-kernel-datafix-cachefix.
Do I need to do steps 12 to 20 for HavocOS or AOSiP? (Both these ROMs support f2fs)
Also, do I need to do these steps again after I update the said roms?
devansh8 said:
Do I need to do steps 12 to 20 for HavocOS or AOSiP? (Both these ROMs support f2fs)
Also, do I need to do these steps again after I update the said roms?
Click to expand...
Click to collapse
Nope, just format data and cache partition to f2fs and you're good to go.
Gerr1 said:
[GUIDE] f2fs for stock, developer and custom - roms
This is my first post in xda, im a silent reader since years.
Just registerd to post this because so many people always asks the thing with f2fs and if the rom have f2fs support.
Dont ask again, make it support on your own!
its not magic, its just format the partitions, editing two lines in fstab and flashing the right kernel.
Caution! You will lose all data from internal storage so please backup your files!
What you need:
1. unlocked android device, i´m on Redmi note 5 Global 4/64
2. pc or notebook with adb and fastboot
3. custom recovery solution, i use original latest twrp
4. off course a rom of your choice, in my case xiaomi.eu latest developer (MIUI 10.4 / 9.5.16)
5. a kernel that supports f2fs, i use KangarooX r4.4 with OC but ice cold etc. works also
6. a texteditor, i use the windows notepad
7. time
Ok, lets go:
All this things must be done in a row, without reboot!
1. remove fingerprint, face and pin unlock on your running device
2. boot into twrp by pressing vol up + power button
3. go to wipe > make a factory reset
4. go to wipe > advanced wipe > select Cache > repair or change file system > change file system > select f2fs
5. go to wipe > advanced wipe > select Data > repair or change file system > change file system > select f2fs
6. connect your device to pc
7. transfer your rom, kernel and all your files you need to internal storage or take your sd card (i prepared my sd card)
8. flash your rom
9. flash your kernel
10. flash your other stuff (i flashed magisk)
11. check your cache partition, it should be f2fs if not, change cache file system again (Point 4)
12. mount the vendor partition
13. on your pc, go to your adb folder and check in terminal if device is listed
14. type in terminal without quotes "adb pull /vendor/etc/fstab.qcom"
15. edit the fstab.qcom with your editor, search for the data and cache lines
16. edit the line for the cache partition that it looks like "/dev/block/bootdevice/by-name/cache /cache f2fs nosuid,nodev,noatime,inline_xattr,flush_merge,data_flush wait" without quotes
17. edit the line for the data partition that it looks like "/dev/block/bootdevice/by-name/userdata /data f2fs nosuid,nodev,noatime,discard,background_gc=off,fsync_mode=nobarrier wait,resize,check,crashcheck,quota" again without quotes
18. save the file and push it to your device with terminal "adb push fstab.qcom /vendor/etc/" remember without quotes
19. set permisson of the file in terminal or twrp, i use terminal "adb shell" > "cd /vendor/etc" > "chmod 644 fstab.qcom"
20. now you´re ready to reboot the device and have a lag free gcam pixel3, etc.
After reboot, check your partitions with diskinfo or similar.
This guide should also work with other devices.
Happy flashing and i hope you enjoy
PS: my english is not so good as it can be
Remember: if you flash the vendor partition, you have to edit the fstab.qcom again!
Click to expand...
Click to collapse
Can you pls make tutorial for exynos chipsets also? Pls pls pls
Is there a way to know if a custom rom Support f2fs or not ?
Hello.
I have a problem: after downgrading my device from Magisk 24.1 back to Magisk 23 I can't unlock my device.
I can only see my wallpaper, but it doesn't respond to touch actions and may reboot.
When I reflash patched boot magisk file it is all the same thing.
Reflashing original boot makes only bootloop or message that data is incompatible.
It is Android 10, AP data file: 'AP_A515FXXU3BTF4_CL18770262_QB31913704_REV00_user_low_ship_meta_OS10'
The question is: how can I pull my /data and /sdcard from my phone?
The recovery is stock version, I've tried to flash TWRP, but TWRP sees only gibberish encrypted file names.
I made a copy of /data/unencrypted folder seems to be containing decryption keys. and entire sda32 containing data partition.
Please help me with ways to restore the system without data wipe or ways how to backup data before reinstalling firmware.
You could try to recover you data with Samsung Smart Switch, when IT doesn't work, there is a way top recover Data from a Phone with ADB tools and a PC.