Related
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
(short) Tutorial in getting your Xiaomi Mi MIX2 encrypted with latest Android 9 (Pie) ROM released by xiaomi.eu (and propably also with the beta ROMs released by Xiaomi/miui.com)
Preparations:
- your phone is unlocked
- a custom recovery is installed on your phone already
- download OrangeFox recovery 9.0-1 or later (others may work too but had not tested for this tutorial / TWRP 3.3.0-0 may produce errors)
- download force-enryption script for Mi MIX2 Android Pie
- download NO enryption restore script for Mi MIX2 Android Pie (reverts fstab config to default - wipe of data needed)
- download latest Android 9 Pie based MIUI ROM (tested only with the modified ROM from xiaomi.eu - official beta ROM may work too)
- optional: download latest Magisk to receive root (may needed by your backup/recovery app to restore your apps within android)
CAUTION!
When folliging this procedure you will loose all current data on your device! DO A APP-BASED BACKUP IN ANDROID FIRST!!! (TWRP or OrangeFox recovery based backups won't work for this procedure!)
Have done your Backup? No? DO IT NOW! really!
Let the phone boot and encrypt itself after flashing the scipt linked in HowTo.
Up to now (bug has been reported) it is to be mentioned that encrypting Xiaomi.EU rom via setting/privacy/encrypt leads direct to PHONE RESET.
FORMAT DATA is required then to get it back to life. @lolo9393 thanks for that hint!
Exact proceedings:
1. you've done a backup eh? - good
2. ... did you save that backup on a other device than your phone? Remember you'll loose all data stored on the phone!!!
3. reboot your phone in your currently installed recovery
3.1 copy the OrangeFox recovery to your device
3.2 select "Install" and choose the OrangeFox recovery .zip file to install (replace your current recovery)
3.3 OrangeFox installer will reboot the recovery after its install
4. Select "Wipe"
4.1 Select "Advanced Wipe"
4.2 Select every Partition exept USB-OTG
4.3 Swipe to Wipe
5. reboot your recovery to recovery again
6. Select "Wipe"
6.1 Select "Advanced Wipe"
6.2 Select "Format Data"
6.3 type in "yes" and confirm that step
7. reboot your recovery to recovery again
8. copy the latest Android 9 Pie based MIUI ROM to your phone
9. copy the latest version of the force-enryption script to your phone
10. Select "Install" and select the Android ROM first then "Add to queue" and select the force-encryption script as second item to flash
10.1 Swipe to Install
11. reboot to system
11.1 go to "Settings"
11.2 scroll down to "SYSTEM SETTINGS" area
11.3 select "Additional settings"
11.4 select "Privacy"
11.5 scroll down to "ADVANCED" area
11.6 check the status of "Encryption & credentials" - it should state "Encrypted"
12. now continue in setting up your system (e.g. enable developer mode, enable advanced power menu, usb debugging if needed, ...)
13. DONE ...
... ok, maybe you're missing your apps and settings - here is a possible way to restore them ... (i personally prefer Titanium Backup)
Root & how to restore apps & app data
14. copy Magisk installer to your device
14.1 reboot your device to recovery
14.2 select "Install" and choose the Latest Magisk-vXX.X.zip file to install (in the log you should read something about "keep forced encryption" - this is good )
14.3 when done - reboot to system again
15. Install Titanium Backup (from a store or as APK from file)
15.1 copy your Titanium Backup or TWRP backup (that could be restored by Titanium Backup Pro) to insternal storage
15.2 restore apps & app data with Titanium Backup (for a detailed HowTo please visit official Titanium Backup Website: https://www.titaniumtrack.com/kb/titanium-backup-kb/titanium-backup-user-guide.html#restore)
15.3 Profit!
That guide may has helped you ...
... say thanks and/or donate for my massive Whiskey consumption -> https://forum.xda-developers.com/donatetome.php?u=496297 :fingers-crossed:
FAQ
Q: Is that procedure ROM update safe? / What if xiaomi.eu releases an ROM update or my ROM has to be reinstalled?
A: When Xiaomi.eu releases an update you have to flash that script right afterwards that update in your favorite recovery. - No further actions should be needed. This procedure has to be repeated for every ROM update or reinstall.
Procedure is verified as working with update 9.5.9 up to 9.6.27Q: Does TWRP recovery work also?
A: There is feedback that TWRP 3.3.0-0 does not work as intended (THX @mguz on post 11 for the feedback)
Maybe TWRP 3.3.1-0 that was released short ago solves that problem ...
How to update later?
cineq said:
How to update later?
Click to expand...
Click to collapse
... hmm sorry did not get what you like to do - could you please describe in detail what you mean/like to achieve?
When there will be next build of xiaomi.eu what is the procedure to update it? Just install new in recovery without any wipes? Is force-encryption script needed when updating?
cineq said:
When there will be next build of xiaomi.eu what is the procedure to update it? Just install new in recovery without any wipes? Is force-encryption script needed when updating?
Click to expand...
Click to collapse
When Xiaomi.eu releases an update you have to flash that script right afterwards that update in your favorite recovery.
No further actions should be needed.
Thanks for the hint - will update the guide with that question/answer
raupe said:
When Xiaomi.eu releases an update you have to flash that script right afterwards that update in your favorite recovery.
No further actions should be needed.
Thanks for the hint - will update the guide with that question/answer
Click to expand...
Click to collapse
Procedure is verified as working with update 9.5.9 -> 9.5.16
raupe said:
(short) Tutorial in getting your Xiaomi Mi MIX2 encrypted with latest Android 9 (Pie) ROM released by xiaomi.eu (and propably also with the beta ROMs released by Xiaomi/miui.com)
@raupe
VERY good work.
Very useful for people having security concern when using a TWRP.
My comments:
-This procedure is valid with any latest 3.3. TWRP version that can decrypt now. (?)
- This is applicable to all XIAOMI phone under PIE. (Fstab must be exchanged in the zip tool in order to fit with the phone model)
- NOTE :
Up to now (bug has been reported) it is to be mentioned that encrypting EU rom via setting/privacy/encrypt leads direct to PHONE RESET and FORMAT DATA required.
Regards
Click to expand...
Click to collapse
Hi,
- download force-enryption script for Mi MIX2 Android Pie
- download NO enryption restore script for Mi MIX2 Android Pie
both links are down, re-upload possible ?
EDIT: Links are working now
Help out a noob. Why would one need to have phone encrypted? Whats the purpose of encryption?
I'd like to update to 9.5.x Xiaomi.eu Pie but hear complaints of GCam, SuperSU, FindDevice, fingerprint, etc not working. Would encryption help these issues?
stoshie said:
Help out a noob. Why would one need to have phone encrypted? Whats the purpose of encryption?
I'd like to update to 9.5.x Xiaomi.eu Pie but hear complaints of GCam, SuperSU, FindDevice, fingerprint, etc not working. Would encryption help these issues?
Click to expand...
Click to collapse
Its not about encr. Problems.Pie uses vendor for most stuff now and for gcam is needed additional line in build prop to make it work.magisk 19 can root it without problems
Hi,
thank you for this helpful tutorial.
First time I tried with TWRP 3.3.1-0 and it did not work (Bootloop).
With OrangeFox Recovery it works as described.
Regards
On official TWRP-3.3.1-1 works as intended, thanks!
Hi, here's a guide on how install crDroid 7.5 (A11) on Redmi 8
UPDATE: THERE'S 7.5 VERSION AVAIABLE, IF YOU ARE USING 7.4 FOLLOW THIS STEPS TO UPDATE WITHOUT LOSING DATA (NEW ROM IS IN MEGA FOLDER, ):
1- Reboot in recovery
2- Go to Wipe -> Avanced wipe -> wipe dalvik, cache and system
3- Go to Reboot -> Recovery
4- Now follow the normal guide from the flashing of the .img file as system image
VERY IMPORTANT: DON'T FORMAT DATA AFTER FLASHING GSI FIXER OR YOU WILL LOST ALL YOUR DATA
Features:
- All functions of the phone work (face unlock, fingerprint, voLTE, voWIFI, hotspot, bluetooth, fast charge, DT2W, ...)
- Magisk safetynet passed without flash nothing (screenshot at the bottom)
- Permissive Selinux by default (in settings is writing disabled, it's wrong) but you can switch to enforcing with
SelinuxModeChanger app, apk at the bottom
What doesn't work
- Nothing if you use fixes below
Note 1: You may have problems with the brightness or sim calls/sms, there are solutions:
- For brightness: Open settings -> Go in "Phh Treble Settings" -> "Misc Features" -> Scroll until you are in backlight menu -> Select "Force alternative backlight scale" and "Enable auto-brightness overlay" -> then deselect both and reboot
- For sim calls: Open settings -> Go in "Network and internet" -> "Mobile network" -> Tap on "Preferred network type" and select "GSM/WCDMA/LTE" or "Global" (try which is better for you) and then reboot
Note 2: If you fing bugs tell me in comments, maybe I could help you (I'm not the developer of the rom)
IMPORTANT ADVICE:I am not responsible for any damage caused to your device by not following the steps, all the steps were tested on my personal device and are confirmed, my device is Redmi 8 4/64
Installation Steps - All the files you need are HERE
Note 3: I did the installation coming from Mui 12.0.1 stock (flashed in fastboot with Mi Flash) and there was no problem in the installation process or in the boot process, YOU NEED THIS ROM IF YOU WON'T PROBLEMS
1- First make a backup of all the necessary information in case something goes wrong you can easily recover, Charge the battery at least 80%
All your data will be deleted during the process
2- Unlock the Bootloader if you have not already done it or do not know how to, follow this post: http://en.miui.com/unlock/
3- Before continue following steps estract on pc "crdrom-v302-210315-arm64-bvZ.img" from "crdrom-v302-210315-arm64-bvZ.img.xz" and activate USB debug in phone settings
4- Reboot in fastboot and connect the phone to the pc with cable
5- Install on pc minimal adb tool (zip at the bottom), flash the TWRP recovery typing " fastboot flash recovery ", now drag twrp file near the command, then vbmeta typing " fastboot --disable-verity --disable-verification flash vbmeta " and drag vbmeta file near the command. Finished the procedure type " fastboot reboot " and hold volume + on the phone until you see the recovery screen
6- Scroll on the slider at the bottom of the phone screen to access in the TWRP
7- Go to Wipe -> Format data -> type "yes"
8- Go to Reboot -> Recovery
9- Go to Wipe -> Avanced wipe -> wipe dalvik, data, cache and system
10- Go to Reboot -> Recovery
NOW YOU HAVE TO TRANSFER ALL OTHER FILES OR IN THE INTERNAL STORAGE OF THE PHONE OR IN SD/USB WITH OTG CABLE
11- Go to Install -> Select the storage where you have files -> Install img -> select "crdrom-v306-210425-arm64-bvZ.img" (Extracted from the .xz file) -> select "system image" and flash
12- Wait and then go to Reboot -> Recovery
13- Wipe -> Advanced wipe -> select "system" and click on "Repair or change file system" -> Resize system
14- Wait and then go to Reboot -> Recovery
15- Install -> Select the storage where you have files -> Flash "GSI-BUGS-FIXER_11_Q.zip"
16- Wipe -> Format data -> type "yes"
17- Wait and then go to Reboot -> Recovery
18- Install -> Select the storage where you have files -> Flash "BiTGApps-arm64-11.0.0-R19_signed.zip"
19- Wait and then go to Reboot -> System
20- Configure phone and enjoy your new rom
Note 4: I reccomend you to flash magisk after you have configured the rom to avoid problems, I leave you the zip to flash in recovery below
Note 5: I reccomend you the best gcam I've found for Redmi 8, everything works except slow motion, link HERE
Thanks for the attenction
-Estatè
Happy that many GSI roms are under develment. I hope this phone will die due to hardware, as there are lots of options in future to keep the software updated.
Anyway, if someone intends to try, following is the link of all GSI Roms.
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
Can i flash vbmeta through recovery
Naulels said:
Can i flash vbmeta through recovery
Click to expand...
Click to collapse
Hey
I'm not using crDroid yet, but I've already installed TWRP.
It is advertised that you should flash vbmeta when you're installing TWRP.
I hope I can help you
Hey !
I wanna try this but I have rooted my phone so here is my question : do I need to remove the root to install this GSI ?
Thx a lot
Volume doesn't work correctly, I cannot increase or decrease the volume. And I plugged my headphone not play through headphone, it play through speaker. Sorry my English
Naulels said:
Can i flash vbmeta through recovery
Click to expand...
Click to collapse
No, you have to flash it with ADB like twrp
letouvetpierre said:
Hey !
I wanna try this but I have rooted my phone so here is my question : do I need to remove the root to install this GSI ?
Thx a lot
Click to expand...
Click to collapse
I recommend you to remove it from the magisk app to avoid problems but I think that would be the same
Naulels said:
Volume doesn't work correctly, I cannot increase or decrease the volume. And I plugged my headphone not play through headphone, it play through speaker. Sorry my English
Click to expand...
Click to collapse
I haven't this problem, have you flashed the gsi fixer? Did you start the installation from miui 12.0.1? It's really important, anyway, you can try to do again the procedure
Does VoLTE and VoWIFI works ? It's a GSI so I'm not thinking it works...
letouvetpierre said:
Does VoLTE and VoWIFI works ? It's a GSI so I'm not thinking it works...
Click to expand...
Click to collapse
Yes, all work fine becouse you flash the gsi fixer for gsi roms on redmi 8
Estatè Mosconi said:
I haven't this problem, have you flashed the gsi fixer? Did you start the installation from miui 12.0.1? It's really important, anyway, you can try to do again the procedure
Click to expand...
Click to collapse
I have reinstalled and fixed it, thanks
Hey !
I'm so happy !
Everything works on that GSI rom, but I haven't the certification on SafetyNet.
With the covid-tracing app, there is a little problem but it's with all the custom roms so...
Thanks a lot for your guide !
letouvetpierre said:
Hey !
I'm so happy !
Everything works on that GSI rom, but I haven't the certification on SafetyNet.
With the covid-tracing app, there is a little problem but it's with all the custom roms so...
Thanks a lot for your guide !
Click to expand...
Click to collapse
Hi, I'm happy for you, for safetynet try the magisk module, I didn't have this problem, anyway, try the rom and than leave a feedback, it could be useful for other people who want to try this rom
I can't get this rom to work correctly. Did the steps as described, but it has SELinux not enforced and Google play isn't certified. Tried multiple times.
EDIT: seems my phone is soft bricked now (Can't install any rom). Going back to xaomi stock to try again.
I tried again and got it to work. The certificate patch throws an error but Google apps are working.
I get an SE Linux not enforcing error. though.
Is there anything I can do about that?
I lost the treble-overlay-xiaomi-redmi8.apk file ,I should problems with the brightness
ndduc said:
I lost the treble-overlay-xiaomi-redmi8.apk file ,I should problems with the brightness
Click to expand...
Click to collapse
There is the solution for brightness in the guide, you don't need that file
Estatè Mosconi said:
There is the solution for brightness in the guide, you don't need that file
Click to expand...
Click to collapse
thanks you, i fixed
ndduc said:
thanks you, i fixed
Click to expand...
Click to collapse
Ok good
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.
Hey!
I unlocked the phone (LLD-L31) with PotatoNV and installed TWRP 3.2.1-0 (from this page: https://ministryofsolutions.com/2020/03/honor-9-lite-emui9-1-twrp-and-root-lld-l31-l21-l22-al10.html), so far so good.
Now I found LOS 18 and 19 (testing) for this device: https://sourceforge.net/projects/andyyan-gsi/
But the sideload doesn't work.
Error: insufficient permissions for device.
I can see the phone via 'adb devices' (in the main menu of the TWRP)
BUT if I start adb sideload in TWRP I get no permissions.
tried sudo, but with the same result.
best regards
lay
#Edit1:
I restarted the adb server with as sudo
adb kill-server
sudo adb start-server
Now it shows Total xfer: 0.00x and breaks.
I think it has something to do with the img.xz files.
I just deleted the xz and tried to sideload it as img.
#Edit2:
ok, the ISOs are compressed.
'unxz blabla.iso.xz'
But the same result: Total xfer: 0.00x and breaks
Simply flash image in fastboot
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
-Alf- said:
Simply flash image in fastboot
https://forum.xda-dlinelineage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgeveloplineage-19.1-20220410-UNOFFICIAL-arm64_bvS.imgers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/
Click to expand...
Click to collapse
THANKS!
so it works via 'sudo fastboot flash system blabla.img'
So... LineageOG 19 (testing) gets 'invalid sparce file format at header magic' while flashing, but installes then everything, after that, it's hanging.
After that I tried this step from the link above:
"4. Run command fastboot reboot, unplug your phone, when appears on screen yellow warning, press and hold for 3 sec Volume Up . In eRecovery select 'Wipe data/factory reset'.Reboot ."
Now it does not start the system, but the TWRP (without touchscreen), So i can not use it. Even if I flash LineageOS 18. If I now flash TWRP again and restart, I get to eRecovery and have no TWRP. If I reboot then in eRecovery, I get to LineageOS 18. For my understanding.... VERY strange!
The LineageOS boots and boots and boooooots now...
#Edit1:
tried now the ROMs from your link.
18.1 shows 'invalid sparce file format at header magic' and fails on install.
17.1 without GAPPS succeeds the flashing, but did not reboot in eRecovery, but the TWRP. There I did the same (wipe data, cache, davlik / factory reset) with the error 'unable to wipe cache'.
and it also does NOT boot the system, but TWRP without touchscreen
#Edit2:
I think the phone is dead
maby because of the TWRP wiping the data
The strange thing is, I can still write to the system partition and flash another LineageOS. But it never reboots to system, just to TWRP (in TWRP I can not mount 'system')
#Edit3:
I can not even reboot to fastboot. It always boots the TWRP
#Edit4:
formated (repaired) system in ext4 again
Now it can be mounted, but I can not get to fastboot-mode and get no device via adb.
I can just boot to eRecovery now. So I try the only one thing, that is there: recovery via wifi. It's downloading now the EMUI 9.1. So we'll see.
It's just crazy!
layalala said:
Now it does not start the system, but the TWRP (without touchscreen), So i can not use it. Even if I flash LineageOS 18. If I now flash TWRP again and restart, I get to eRecovery and have no TWRP
Click to expand...
Click to collapse
Your problem is that you don't read carefully.
Why do you have TWRP installed???
layalala said:
It's just crazy!
Click to expand...
Click to collapse
Indeed!
the problem was, that I first followed enother tutorials and then swiched to yours
so the TWRP was already there.
The point is, I got it!!!
After downloading new EMUI via wifi in eRecovery, I got everything back. Meanwhile my VM in the QubesOS did not want to accept the USB-Controller I used for adb-fastboot. So i switched to Windows and followed your tutorial. BUT with the ROMs from Andy Yan (https://4pda.to/forum/index.php?showtopic=896420&st=10780#entry100487186). And everything works! Even the testing LOS 19! Android 12 on that old phone, yeah! but it works rather good.
Your ROM (LOS 18.1) did not work for me. It showed error in header while flashing and broke the process. The ROM from Andy Yan (LOS 19) also showed an error in header while flashing, but the process worked after that.
now I'll try to root it and hope that this will work well
layalala said:
now I'll try to root it and hope that this will work well
Click to expand...
Click to collapse
did rooting succeed?
epicmann24 said:
did rooting succeed?
Click to expand...
Click to collapse
yes!
layalala said:
yes!
Click to expand...
Click to collapse
may i ask which gsi image and which magisk zip did you flash? as for me rooting does not work.
epicmann24 said:
which magisk zip did you flash
Click to expand...
Click to collapse
Running EMUI 9.1 you have to flash magisk_patched recovery_ramdisk (on EMUI 9.1 ramdisk is included in the recovery_ramdisk).
Also you can follow this guide:
https://forum.xda-developers.com/t/losq-lir-lineageos-17-1-18-1-unofficial-gsi.4219291/post-84305543
You can use files linked in this post, recovery_ramdisk and erecovery are the same for ANE and LLD devices. Use TWRP linked on this post (important!).
Edit: you can get root rights also via SuperUser:
1. In TWRP flash Zip.file
2. Install Phh Superuser apk .(if needed)
https://mega.nz/file/A4sWFYxZ#9KMkvKRgzU7oCvgThPFQOpv_wKAnLZcZVWcJ03HDyNE
layalala said:
the problem was, that I first followed enother tutorials and then swiched to yours
so the TWRP was already there.
Click to expand...
Click to collapse
Hello,
Everything worked; even to the Lineage 19 rom, but, I couldn't install OpenGapps 12l (error 70).
I tried to replace the system "LOSQ - LineageOS 17.1-[10]-unofficial-GSI" via TWRP (system install) and I had the same problem, in addition to not being able to boot by eRecovery to download EMUI by Wi-Fi.
also, on TWRP, I don't have the option to mount "system"
How did you do?
[2022/07/06 - EDIT]
--> eRecovery done
--> Download in progress
--> EMUI 9 Install done
--> go test lineage 18.1 first
Rahinsoo said:
I don't have the option to mount "system"
Click to expand...
Click to collapse
This option is only on GSI vndk-lite version
Keep in mind, that on the Honor 9 lite, in the latest firmwares, the system partition is only 2312 Mb, if I'm not mistaken (on ANE-LX1, the system is 3270 Mb). So those GSI ROMs that work on ANE (Losq, LiR, PE+ etc.) probably won't work on LLD.
https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/post-87085313
-Alf- said:
This option is only on GSI vndk-lite version
Keep in mind, that on the Honor 9 lite, in the latest firmwares, the system partition is only 2312 Mb, if I'm not mistaken (on ANE-LX1, the system is 3270 Mb). So those GSI ROMs that work on ANE (Losq, LiR, PE+ etc.) probably won't work on LLD.
https://forum.xda-developers.com/t/kernel-emui-9-p20-lite-phenix-kernel.4241503/post-87085313
Click to expand...
Click to collapse
That's right, I managed to install open gapps pico in some instance, especially on the bvs_vndklite versions.
What is the difference between bvs version and bvs_vndklite version?
Rahinsoo said:
That's right, I managed to install open gapps pico in some instance, especially on the bvs_vndklite versions.
What is the difference between bvs version and bvs_vndklite version?
Click to expand...
Click to collapse
Very simplistically written:
generally, vndk-lite build are designed for vndk-lite vendors, vndk for vndk vendors.
But on Phhusson AOSP based GSI ROMs there is one change from v300 version (or so): A/B non-lite builds are read-only (due to new phh patches),
A/B vndk-lite builds are in r/w mode, i.e. allow mount system and system modifications.
-Alf- said:
Very simplistically written:
generally, vndk-lite build are designed for vndk-lite vendors, vndk for vndk vendors.
But on Phhusson AOSP based GSI ROMs there is one change from v300 version (or so): A/B non-lite builds are read-only (due to new phh patches),
A/B vndk-lite builds are in r/w mode, i.e. allow mount system and system modifications.
Click to expand...
Click to collapse
Can I use this version without particular problems on my honor 9 lite?
Rahinsoo said:
Can I use this version without particular problems on my honor 9 lite?
Click to expand...
Click to collapse
Read carefully.
Oh, I'm sorry, I misunderstood ^^'
my question was for the vndklite version because I'm having a hard time figuring out the difference.
Rahinsoo said:
my question was for the vndklite version
Click to expand...
Click to collapse
I answered you, didn't I?
Currently I tested several roms. Only certain Andy Yan roms in the version without Gapps work correctly and allow the installation of Gapps.
OK test:
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite
+ Open Gapps pico OK
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img --> OK
+ Gaaps --> pico OK ---> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lineage-19.1-20220613-UNOFFICIAL-arm64_bgS-vndklite.img --> OK
+ Gaaps --> pico OK --> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lir-v316-220325-arm64-bgZ-lite.img --> OK
+Gaaps --> pico OK --> play store OK --> factory reformat impossible (automatic boot on TWRP)
What is the procedure for factory reformatting to work normally without booting to TWRP?
Rahinsoo said:
Currently I tested several roms. Only certain Andy Yan roms in the version without Gapps work correctly and allow the installation of Gapps.
OK test:
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite
+ Open Gapps pico OK
- lineage-18.1-20220616-UNOFFICIAL-arm64_bvS-vndklite.img --> OK
+ Gaaps --> pico OK ---> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lineage-19.1-20220613-UNOFFICIAL-arm64_bgS-vndklite.img --> OK
+ Gaaps --> pico OK --> play store does not start --> cannot factory reformat (automatic boot on TWRP)
- lir-v316-220325-arm64-bgZ-lite.img --> OK
+Gaaps --> pico OK --> play store OK --> factory reformat impossible (automatic boot on TWRP)
What is the procedure for factory reformatting to work normally without booting to TWRP?
Click to expand...
Click to collapse
Why do you have TWRP there? You don't need it to install GSI. And if you have TWRP installed instead of Recovery, then it should be clear...