How to flash xenon hd? Its showing error on my mi3 ,cwm c7 furniel, kindly send details of perfect installation procedure
Usual procedure (for clean flash) is as follows :
- Download the latest build
- Download Gapps
- Take a nandroid backup (in case something goes wrong)
- Full wipe/factory reset
- Flash ROM using recovery (TWRP works flawlessly)
- Flash Gapps
- Wipe Cache/Dalvik
- Reboot
I flashed it few days back after using Cancro by Bitti09 on stock partition for more than 2 months. Process I followed :
1. Download Latest TWRP recovery (flashable one would be better) + CWM R11 (this is required if you are on previous CWM version) + 1.2GB repartition script + Xenon HD + TkGapps + Stuxnet latest + any other add-on flashable script.
2. Reboot to recovery.
3. Flash CWM R11.
4. Reboot to recovery (Now, you will be in CWM R11).
5. Flash 1.2 GB partition script.
6. Flash TWRP recovery.
7. Reboot to recovery (Now, you will be in TWRP recovery)
8. Wipe data + cache + dalvik- cache + system.
9. Install Xenon Zip.
10. Install TKGapps zip.
11. Install Stuxnet zip.
12. Clear Cache + dalvik - cache.
13. If any addon flashable zip (I flashed viper).
13. Reboot to System.
A lengthy process but at the end you will have a stable ROM. Make sure to tweak kernel settings in Kernel Auditor and then @Audahadi's Rom will let your Mi3 fly.
I hope this process helps you.. I followed the exact process explained above and you can get the zips from Xenon's thread/repartition thread, just search a little bit.
THANKS FOR GIVEN PROCEDURE , but Repartitioning only struck , any body explain re-partitioning ????????????????????:victory:
sahafdeen said:
THANKS FOR GIVEN PROCEDURE , but Repartitioning only struck , any body explain re-partitioning ????????????????????:victory:
Click to expand...
Click to collapse
http://forum.xda-developers.com/xiaomi-mi-3/general/howto-resize-extend-partition-capacity-t3011918 everything you need to know, plus the script-procedure to do it.
In short, the Mi3 comes with system1 and system2 partitions, each of 600MB. Nice idea, devs with other devices spend a lot of effort in building a multi-boot option. However, 600MB is not much for a ROM + Gapps, plus all the stuff that ends up in system partition. This is why often a ROM+Gapps combo will not flash successfully into those 600MB - there is insufficient space so it fails.
So the script changes the size of the 2 partitions: system 1 get 1.2GB, and system 2 a testimonial 5MB (since you are not ever going to use system 2 with this config).
CWM identifies and works with system 1 & 2, so you run the partitioning script from CWM. Once you have your system 1 partition as 1.2GB, you can use TWRP if you want to.
As a basic principle, if you are not comfortable with what you are reading, don´t do it
First off you will completely lose all of your data. I highly recommend backing up all of your internal storage because it will all be gone.
Also I recommend investing in a good quality USB-C OTG drive. It comes in very handy with any TWRP encryption issues. You can always use ADB if needed, but the drive makes it 10x easier.
Things to download
1. OOS Full zip. Do not use an incremental update. - https://forum.xda-developers.com/showpost.php?p=78026655&postcount=2
2. Latest TWRP Installer - https://forum.xda-developers.com/on...overy-unofficial-twrp-touch-recovery-t3861482
3. Magisk - https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Steps.
1. Reboot to Recovery
2. Perform an Advance Wipe (Dalvik/Art Cache, System, Vendor, & Data)
3. Factory Reset
4. Flash OOS Full Zip on slot A
5. Flash TWRP
6. Reboot to Recovery - You should now be on Slot B
7. Flash OOS Full Zip again on slot B
8. Flash TWRP
9. Reboot to Recovery
10. Flash Magisk
11. Format Data
12. Boot to OOS
Thank you for the details.
What do you mean by step 3 "Factory Reset" ?
Isn't step 2 is a factory reset through TWRP ?
Or......
https://forum.xda-developers.com/oneplus-6t/how-to/rom-stock-fastboot-roms-oneplus-6t-t3862516
Hello, last night I have unlocked the bootloader flashed twrp -0 official build and magisk it was all good and was working then i wanted to install the last eu beta and flashed but flashing it always corrupting the file system, to solve it I have flashed stock rom via fastboot
Problem here I do not wipe /system directory but whenever I try to flash a custom rom the file system directory is corrupting and consequently the device is stucking on twrp. Is there an idea?
MertFatih said:
Hello, last night I have unlocked the bootloader flashed twrp -0 official build and magisk it was all good and was working then i wanted to install the last eu beta and flashed but flashing it always corrupting the file system, to solve it I have flashed stock rom via fastboot
Problem here I do not wipe /system directory but whenever I try to flash a custom rom the file system directory is corrupting and consequently the device is stucking on twrp. Is there an idea?
Click to expand...
Click to collapse
1. It must to be in QUESTIONS & ANSWERS and not in GUIDES, NEWS, & DISCUSSION.
2. What exactly corrupted? There is system partition which is not file system And there is a data partition which you can call a file system
3. If the problem was in system partition you would be stuck in fastboot.
4. What steps did you make after flashing stock rom via fastboot?
For flashing eu beta ROM after flashing stock rom via fastboot, the steps are:
1. FORMAT (not wipe) data.
2.Wipe cache/dalvik cache (don't wipe system or flash a ROM without reboot).
3.Flash eu ROM.
You can try another TWRP for example: https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825 , official TWRP is based on it or from Chines team: http://files.mi-room.ru/files/twrp/cepheus/3.3.1-1030/recovery.img . Both very good.
g_seva said:
1. It must to be in QUESTIONS & ANSWERS and not in GUIDES, NEWS, & DISCUSSION.
2. What exactly corrupted? There is system partition which is not file system And there is a data partition which you can call a file system
3. If the problem was in system partition you would be stuck in fastboot.
4. What steps did you make after flashing stock rom via fastboot?
For flashing eu beta ROM after flashing stock rom via fastboot, the steps are:
1. FORMAT (not wipe) data.
2.Wipe cache/dalvik cache (don't wipe system or flash a ROM without reboot).
3.Flash eu ROM.
You can try another TWRP for example: https://forum.xda-developers.com/Mi-9/development/recovery-unofficial-twrp-xiaomi-mi-9-t3905825 , official TWRP is based on it or from Chines team: http://files.mi-room.ru/files/twrp/cepheus/3.3.1-1030/recovery.img . Both very good.
Click to expand...
Click to collapse
Update: after format, it stucks on twrp(directories are not encrypted), and rom is not flashing at all I mean it is not writing to /sdcard (loading screen says it successfully flashed but not in the reality )and there are only 'obb' and 'TWRP' directories in the /sdcard also the twrp version is not even change by fastboot or flashing img after a reboot it recovers itself to build -0
I will try it with the Chinese teams's twrp build for this time
Solved with another twrp version
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.