Hi, everyone! I decided to make this post, containing the stuff from the name.
*I AM NOT THE AUTHOR OF ANY CONTENT BELOW. ALL CREDITS GO TO THE DEVELOPERS FROM RUSSIA*
Root and recovery
How to install TWRP 3.0:
1. Open m4twrp.zip
2. Install recovery.img using SP Flash Tool, scatter file inside the archive
3. When leaving TWRP, it will ask you to choose to install root. Agree
4. Profit
Custom ROMs
BACKUP YOUR STOCK MODEM BEFORE FLASHING!!!
GApps: http://opengapps.org/ (ARM64, 5.1 or 5.0, Pico)
AOSP 5.0
Download: https://yadi.sk/d/GmxF8cBTrtu74
Installation:
1. Put the zip to your SD card
2. Wipe Dalvik/ART Cache, System, Cache, Data with TWRP
3. Install the zip
4. After booting go to SuperSU and disable "Mount namespace separation"
5. Profit
First boot about 3-4 minutes
Author: iwewni
AOSP 5.1
Download: https://yadi.sk/d/2WorFxgFrvPKi
Installation:
1. Put the zip to your SD card
2. Wipe Dalvik/ART Cache, System, Cache, Data with TWRP
3. Install the zip
4. Not leaving TWRP, install Fix_compass.zip and patch51.zip
5. After booting go to SuperSU and disable "Mount namespace separation"
6. Profit
First boot about 3-4 minutes
Author: iwewni
CyanogenMod 12.1 (Android 5.1.1)
Download: https://yadi.sk/d/3UtQPP8aspLaE
Installation:
1. Put the zips to your SD card
2. Wipe Dalvik/ART Cache, System, Cache, Data with TWRP
3. Install the zip
4. Profit
First boot about 3-4 minutes
Author: iwewni
Flyme OS BETA (Android 5.1)
NOT WORKING: TORCH, RECENTS KEY, MANUAL FOCUS, PROXIMITY SENSOR
Download: https://cloud.mail.ru/public/42EC/dgtRh2EFM
Download patched core: https://yadi.sk/d/YVB08GsbsfrcN
Installation:
1. Put the patched core zip to your SD card
2. Wipe Dalvik/ART Cache, System, Cache, Data with TWRP
3. Install the zip with Flashtool
4. Not booting, go to TWRP and install patched core
5. Profit
Author: ruslan_3_
Patched core author: Artttech
M4 Stock Deodex (Android 5.0)
Download: https://yadi.sk/d/GmxF8cBTrtu74
Installation:
1. Put the zip to your SD card
2. Wipe Dalvik/ART Cache, System, Cache, Data with TWRP
3. Install the zip
4. Profit
Author: Artttech
BLU Studio Energy 2 Stock (Android 5.0)
Download: https://yadi.sk/d/swWgAQ9tsKvb7
Installation:
1. Put the zip to your SD card
2. Wipe Dalvik/ART Cache, System, Cache, Data with TWRP
3. Install the zip
4. Profit
Author: acstudio
I spent two hours making this post...
Camera quality????
josepgreg said:
Camera quality????
Click to expand...
Click to collapse
Aosp 5.1 and flyme don't have autofocus, everything else is same as stock
Thank you bro any chance to get masmellow
---------- Post added at 08:15 PM ---------- Previous post was at 08:10 PM ----------
4. Not leaving TWRP, install Fix_compass.zip and patch51.zip
Where is link
cm 12.1 sim card not detected
i install cm 12.1 sim card not detected plzz tell me how to fix this problem ??
rohitsahota said:
i install cm 12.1 sim card not detected plzz tell me how to fix this problem ??
Click to expand...
Click to collapse
the OP says with a huge font: backup your stock modem. now restore it.
Gershik said:
the OP says with a huge font: backup your stock modem. now restore it.
Click to expand...
Click to collapse
How does one backup their stock modem?
Thank you.
how to backup the modem files? pls help....
how to backup the modem files? pls help....
Gionee m4
Which one is best?
Thanks Gershik
Thanks Gershik i have rooted my this but I'm facing problem in flashing xposed framework..its show error executing updater binary in zip in TWRP.. do u have any idea what to do?
Link flyme os beta gionee m4 die
Hi
Today I get my OnePlus 3T. So I did that, what I do with any new phone = TWRP and Root. So I...
1. Boot, download and install Oxygen OS 4
2. Fastboot unlock bootloader, flash TWRP (latest official build)
3. Reboot in TWRP and TWRP ask for password (never set any password for this phone, nothing! just start without sim and set nothing, only wifi for the first step)
4. Download SuperSU .zip and try to root - 0MB when I try to install SuperSu
5. TWRP > Wipe > Format data
6. Reboot and now I see (when I click on install) internal Storage (52100 MB). After that (dont flash SuperSU) just boot in TWRP
7. With OTG and USB stick I flash Oxygen OS 4.0 (full ROM with 1,4GB) > phone just reboot in TWRP.
When I go to
Wipe > Advanced Wipe > check Internal Storage > click on Repair or Change File System I get "invalid partition selection"
This also happen, when I check Dalvik/ART Cache. With System, Data and Cache no problems.
I have no idea what I can do. Over Google I only find some thread from Huawei and Samsung device, something with PIT file. Nothing to OnePlus (not One, not Two and not Three).
Klanac89 said:
Hi
Today I get my OnePlus 3T. So I did that, what I do with any new phone = TWRP and Root. So I...
1. Boot, download and install Oxygen OS 4
2. Fastboot unlock bootloader, flash TWRP (latest official build)
3. Reboot in TWRP and TWRP ask for password (never set any password for this phone, nothing! just start without sim and set nothing, only wifi for the first step)
4. Download SuperSU .zip and try to root - 0MB when I try to install SuperSu
5. TWRP > Wipe > Format data
6. Reboot and now I see (when I click on install) internal Storage (52100 MB). After that (dont flash SuperSU) just boot in TWRP
7. With OTG and USB stick I flash Oxygen OS 4.0 (full ROM with 1,4GB) > phone just reboot in TWRP.
When I go to
Wipe > Advanced Wipe > check Internal Storage > click on Repair or Change File System I get "invalid partition selection"
This also happen, when I check Dalvik/ART Cache. With System, Data and Cache no problems.
I have no idea what I can do. Over Google I only find some thread from Huawei and Samsung device, something with PIT file. Nothing to OnePlus (not One, not Two and not Three).
Click to expand...
Click to collapse
This question seems to keep repeating itself due to missing information on TWRP post about the latest official version being incompatible with OOS 4 encryption method, but that is the explanation. There is a beta release of TWRP in post 550 in that thread that is supposed to fix this.
Here's some spoon feeding for you
https://forum.xda-developers.com/showthread.php?t=3507308
Lookup post numbered 550 and it has a link to the unofficial TWRP update
What to do? Boot in beta1 and looks like the same... can flash OOS 4 but still the same problem.
Gesendet von meinem MI 5s Plus mit Tapatalk
This series of roms is focused tu gain more performance for this series and add some other features to the rom, all of them are based in latest firrmware for each
How To install:
1) install TWRP for your device
2) enter in advance wipe and wipe dalvik, system,data,internal storage and cache
3) format data partition
4) flash the rom
5) 4) flash DM-verity
6) enjoy!!
A70:
to boot it must format data after install the rom
Download:mediafire
ROM OS Version: 10
ROM Kernel: Stock
ROM Firmware Required: Stock Android 10
Status: Stable
Created 31-08-2020
Last Updated 11-12-2020
In orden to boot the rom you need to flash DM-Verity after install the rom
Telegram Group for support and updates
wrong instruction for a705FN or this for a70MN only
MHMD NZMY said:
wrong instruction for a705FN or this for a70MN only
Click to expand...
Click to collapse
Wdym? All variants doesn't matter lmao
I'm on A705MN running latest TWRP and your instructions are not very clear. Here is what I am doing and get a bootloop
I advanced wipe cache, dalvik, data, system, internal storage
I format data and type "yes".
install add files for zip of rom, then add second zip of DM-verity
Both flash fine; do not reboot, but go to TWRP home and format data again per your instructions, type "yes"
then reboot system...and I get boot loop.
If my order is wrong please clarify.
Any prints?
gaderderian said:
I'm on A705MN running latest TWRP and your instructions are not very clear. Here is what I am doing and get a bootloop
I advanced wipe cache, dalvik, data, system, internal storage
I format data and type "yes".
install add files for zip of rom, then add second zip of DM-verity
Both flash fine; do not reboot, but go to TWRP home and format data again per your instructions, type "yes"
then reboot system...and I get boot loop.
If my order is wrong please clarify.
Click to expand...
Click to collapse
2.1 after format data, you need to reboot recovery
Anyone with A70? I installed Android 10 Stock Rom to install this Tutibreaker rom and the phone never started, the phone was in bootlogo and I repeated the process and instructions and the phone never started so I had to go back to Stock Rom and I got frustrated
Hello, I have a Samsung Galaxy A6+ with latest fw installed.
(italian version)
A605FNXXU7CUD4
The phone is totally useless after the update to android 10, it takes AGES to perform any action, even open the Camera or open a Message.
Already tried to wipe everything, hard reset, reinstall fw. Still useless.
Since I’d like to downgrade to Android 9 to have back a useful phone, I tried to install the latest Android 9 fw with Odin.
A605FNXXS5BTB1
But it fails, saying SW REV CHECK FAIL : [aboot] Fused 7 > Binary 5
What can I do?
Is there any chance to downgrade this phone?
Thank you
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
nqnxev said:
1. Unlock your bootloader.
2. Flash custom recovery for your device.
3. Go to custom recovery (TWRP) and flash any downloaded custom rom (for your device), GSI or save stock firmware as flashable zip with tool like ClassyKitchen.
4. Flash Magisk or RMM-bypass-v3 in TWRP to protect your bootloader from getting locked again.
Backup your personal data at first, of course.
Click to expand...
Click to collapse
Almost done, but I can't find any custom rom available for download. Can someone help? Since wwith twrp I cannot install a stock rom. Thanks in advance.
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Ecto1000 said:
I managed to flash a so called Ari's rom, but I think the phone is now bricked. It is on bootloop on the first screen of Samsung (with phone name and so on) and with SET WARRANTY BIT : KERNEL at top left. I think it is time to trash it or does someone have any hint? Thanks
Click to expand...
Click to collapse
I proposed three different options: custom rom, GSI (generic system image) or conversion stock firmware to flashable form. If there's no good custom rom for A6+, then don't worry - you can still try another options. Try playing with Generic System Images:
1. Flash your current stock firmware as usual in Odin.
2. Unlock bootloader and flash TWRP.
3. Go to TWRP.
4. Wipe partitions cache, dalvik, data, system (don't wipe vendor partition - it's needed).
5. Flash GSI image (recommended will be at first phhusson's AOSP (Android 9 or 10)) as "system image". You always need to choose and download "arm32_binder64" variant of img file.
6. Reboot to your new system.
Second option is to convert stock Android 9 firmware into flashable form.
1. Download ClassyKitchen tool.
2. Import downloaded Android 9 stock firmware (for your phone) into it and save it as flashable zip.
3. Go to TWRP.
4. Wipe cache, dalvik, data, system and vendor.
5. Flash your previously done zip with Android 9 as any other flashable zip in TWRP.
6. Flash Magisk or RMM-state-bypass-v3 in TWRP to prevent your bootloader from getting locked again.
7. Reboot.
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Success, success also for RMM-state-bypass-v3.
I rebooted but I'm again stuck in the same loop described in my previous reply.
When I selecr REBOOT in twrp, do I have to flag anything? For example System?
Regarding the first option, if I go there:
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
exactly which file do I have to download among ASSETS of any release?
Thank you very much
Ecto1000 said:
I went for the second option, in Classykitchen I loaded the stock android 9 rom and selected
BUILD ZIP ROM (for recovery).
Then installed with TWRP following your wipe indications.
Success.
But when I went to install RMM-state-bypass-v3 I got the error impossile to mount /system.
So I rebooted twrp and before anything I manually mounted SYSTEM in twrp in the dedicated MOUNT menu, and I did everything again from wipe to install.
Is this procedure correct?
Click to expand...
Click to collapse
Yes, it's correct. If RMM bypass or Magisk.zip was flashed without any errors in TWRP then everything is okay. Just reboot to system in TWRP after that - there is option to reboot directly to system. First boot always can take a bit longer than next boots.
Ecto1000 said:
exactly which file do I have to download among ASSETS of any release
Click to expand...
Click to collapse
You always need to get any "arm32_binder64" (always AB) image. Gapps or vanilla is just your choice. Just get Android 9 or 10 image and flash it as "system image" (but wipe at first partitions specified in my previous post - don't wipe only Vendor partition, because it contains important things). Android 12 GSI still aren't stable. Android 11 - maybe will work properly. Android 9 and 10 should work fine. There is even short article about GSI on Galaxy A6+ with some fixes for that device attached:
Samsung Galaxy A6 Plus (2018)
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
You can try of course other GSI's as well:
Generic System Image (GSI) list
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Ecto1000 said:
Thank you very much, appreciated.
But something weird happens: I install the ROM with success. If then I try to install Magisk (or Rmm) it fails with error 7.
And twrp says No Os installed if I reboot.
But if I try to install Magisk after rebooting into twrp after installing the ROM it goes without errors.
But anyway I have the issues of No Os installed.
Click to expand...
Click to collapse
You need to reboot to recovery after flashing new system, because just after flashing TWRP doesn't recognize it - that is why you see that "no OS installed". Just reboot your phone to recovery again (you have such option in TWRP). In case of GSI (except maybe CAOS, LineageOS Q/R mod) Magisk or RMM bypass is not needed.
Btw, in case of any problems with hardware support on GSI flash also that patch in TWRP (it may be needed to mount "Vendor" partition in TWRP before flashing that fixes):
Fixes.zip
drive.google.com
Thank you again for your help.
I already rebooted to recovery and twrp keeps saying NO OS.
I'm using twrp 3.5.2_10-0.
I'm starting to suspect that this behaviour is due to the fact that this version of twrp could be too much new and unstable for my phone.
So I'd like to install an older version of twrp with Odin, as explained here:
TWRP for SM-A605FN Samsung Galaxy A6+
How to Install TWRP 3.2.3-1 on Galaxy A6+ SM-A605FN Android 8.0.0 Oreo. Once you installed TWRP recovery on your Samsung Galaxy A6+ SM-A605FN, you can customize it, Rooting or installing custom ROM
www.recovery-mode.com
But I cannot manage to go into download mode again, even from REBOOT menu of twrp it doesn't work, I keep staying in the loop explained before.
Moreover your first option of GSI need me to go into download mode to install the latest stock ROM with Odin.
I just manage to get into the attached screen.
Any idea?
Thank you again
It's not possible to ignore that message and just flash latest stock firmware via Odin? Odin refuses flashing latest stock firmware?
Other builds of TWRP for your devices you'll find here:
Releases · roynatech2544/TWRP_device_samsung_a6plte
Contribute to roynatech2544/TWRP_device_samsung_a6plte development by creating an account on GitHub.
github.com
But don't use TWRP older than 3.4.0, because it doesn't have support for "Vendor" partition.
Yes, I managed to ignore that screen and go in download mode again.
I tried to follow your first option since the second one was not successful.
Installed latest stock and then twrp 3.5.0-1.
Wipe as you explained, I flash the Gsi
system-quack-arm32_binder64-ab-gapps.img
The flash is very fast, but no errors, is it normal?
After that I reboot to recovery in order to flash
Disable_DM-Verity_ForceEncrypt_11.02.2020
it goes but just at the end it gives the error
failed to mount /odm no such file or directory.
And if I reboot to system the phone loops as always.
I'm losing all hope...
Ecto1000 said:
system-quack-arm32_binder64-ab-gapps.img
Click to expand...
Click to collapse
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Ecto1000 said:
The flash is very fast, but no errors, is it normal?
Click to expand...
Click to collapse
If you flashed it as "System Image" and it was successful then yes - should be fine. DM-Verity isn't needed for GSI - only RMM bypass v3 is sometimes needed (on CAOS, Lineage Q/R mod and maybe in case of some other images). On usual A600FN RMM bypass is not needed on phhusson AOSP. Just format "Data" partition (format, not only wipe) - it will remove encryption for you.
Procedure of flashing should be like that:
1. Wipe: cache, dalvik, data, system ("Vendor" partition leave untouched, because it's important for GSI - that is why you needed to flash stock firmware at first, because it adds vendor files for your phone, but it's needed only once, just don't wipe "Vendor").
2. Flash your GSI as "System Image".
3. Reboot phone (to recovery again).
4. Mount your "data", "vendor" and "system" partition.
5. Flash your zips: RMM bypass v3 (optionally Magisk).
5. Reboot to your new system now.
In case of any hardware support problems, reboot to TWRP again, mount "Vendor" partition and flash that fixes:
Fixes.zip
drive.google.com
Try to boot Android 10 or Android 9 images. If it will succeed, then you can try flashing Android 11 images and check what works, and what not. According to that article
nqnxev said:
It's okay, but it's possible that you'll always need "vndklite" images for working camera.
Click to expand...
Click to collapse
I don't know what are those images. Can you explain better?
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Can this be related to the hardware support problems you mentioned?
I tried with different versions of Twrp already and with Havoc Os too.
Should I try with flashing a different ROM ?
Thanks again
Ecto1000 said:
I don't know what are those images. Can you explain better?
Click to expand...
Click to collapse
Just look at filename of system images. But as I see, it's apparently important on Android 11 and newer. For now, try to boot Android 10 or 9. Let's try with that image:
https://github.com/phhusson/treble_experimentations/releases/download/v222/system-quack-arm32_binder64-ab-vanilla.img.xz
1. Decompress that image.
2. Copy to SD card or to internal storage.
3. Wipe cache, dalvik, data, system.
4. Format data partition (it's needed only once).
5. Flash downloaded and extracted file as "System Image".
6. Reboot phone to recovery (again).
7. Select in TWRP: Mount -> system, data, vendor.
8. Flash RMM bypass v3 (or Magisk).
9. Reboot now to system.
10. In case of some things not working, go back to TWRP and mount vendor partition (Mount -> tick "Vendor" -> go back to flashing zips) and flash that:
Fixes.zip
drive.google.com
11. Reboot to system again and check if now everything works properly.
Ecto1000 said:
When I proceed with RMM bypass V3 I see the errors in the attached image. It seems like there is a problem in writing to /system.
Click to expand...
Click to collapse
Yes, because you need to mount that partitions in TWRP:
Mount -> tick "system", "vendor" and "data" - and now flash whatever you want.
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Maybe I have to try with sideload ?
Ecto1000 said:
The only "receipt" which isn't giving installation errors is following your last instructions but avoiding to reboot to recovery after ROM flash (used Vanilla), and using Magisk v22 with unticked the line called "skip digest check" . See attached images.
Anyway, still no success to get into android.
Also tried fixes.zip.
Click to expand...
Click to collapse
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
nqnxev said:
Everything seems to be okay in your photos. What happens when you press "Reboot System"?
Click to expand...
Click to collapse
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Ecto1000 said:
The phone goes into loop with the attached screen and black screen alternatively.
On the top you can see SET WARRANTY BIT: KERNEL, it should be normal right?
Do I have to set something inside MOUNT of twrp before rebooting to system?
Click to expand...
Click to collapse
I've never had such problem, but according to that thread it seems that it's a fault of modified kernel (so don't flash Magisk with GSI, because it patches kernel).
Try to flash stock firmware, unlock bootloader, flash TWRP, format "data" partition, wipe partitions (cache, dalvik, system, data) and flash GSI image as "system image". And reboot to system.
Don't flash RMM and Magisk for now - and check if system will run properly.