Hi All,
After the adventure with the bricked phone I had to install clean rom, but unfortunately there is no such for RETCN. There is only version with weird and ugly 'ZUI' UI for chinese market. So after several trying I was able to install stock clean Z2 Force 8.0 ROM on my XT1789-05 RETCN 64GB/4GB from aliex. Here is guide:
1. Download RETCN Rom from HERE
2. Unpack zip, reboot to bootloader and run flashall.bat included in the directory
3. fastboot reboot and enjoy the ZUI experience until reflash
4. Now download RETEU version from HERE
5. Unpack and copy 'tools' directory from RETCN to RETEU catalog
6. Download attached 'flashaponly.txt', rename extension to '.bat' and move to RETEU directory
7. Reboot to bootloader, run flashaponly.bat (it flash only system part, without radio/baseband/bootloader)
8. fastboot reboot. Now You have clean stock 8.0 Rom
Above method works for me, but You can also try to replace system.img and oem.img files from RETEU to RETCN and modify 'flashall.bat' (there is difference with oem.img files) and install just one rom.
Edit: I've noticed some bad impact of RETCN radio on battery life, so I reflashed also baseband/radio part. Now battery is ok. I've updated .bat file
Related
share my process and trouble shooting for upgrading rooted note fe from nougat to oreo without re-install. I eventually got a solution
my nougat installation had data encryption enabled during setup, not sure if it made difference, or the cause of my trouble below.
the process references the post [SM-N935F/DS] How to flash TWRP & Root with Magisk (Int. Ver.) [Oreo Updated] and mostly used files provided there.
start with rooted nougat with TWRP
1. download latest OREO ROM from sammobile. Mine has CSC code XME
2. unzip to five .tar.md5 files
3. flash BL/AP/CP/HOME_CSC via Odin, turn off auto-reboot
4. exist download, and re-enter download immediately without letting it to boot up (press home+volume down+power immediately)
5. flash TWRP in odin
6. reboot into recovery
7. install in TWRP RMM-path
8. install in TWRP no-verty-opt-encrypt. This is required for me as my data is encrypted
9. reboot and let android complete the update process
--- note, I did not install the /data partition patch mentioned in original thread for OREO, as it led to boot loop and I had to re-flash stock rom --
10. reboot back to TWRP and install magisk to root
This should be it. BUT --
system boots up ok, but I noticed that CSC was not installed. there is not even /system/csc folder. somehow, the csc was not installed during the installation process. I tried multiple time, same results. here is how I got over it
1. from stock rom 's HOME_CSC_xxx.tar.md5 file, remove ".md5" to turn it to a tar file, and use 7zip to unzip it and take cache.img.lz4
2. use lz4 tool to covert cache.img.lz4 to cache.img
3. use SVAImgUnpack to covert cache.img to cache.ext4.img
4. use ext2explore.exe included in SVAImgUnpack to open cache.ext4.img and extract the sec_csc.img (ext2explorer.exe needs to run with admin)
5. use TWRP to install the extracted sec_csc.img
6. open a terminal in TWRP or use adb shell to run the following command cp -dpfr /system/csc/XME/system/* /system
that is it. and it should work.
If you need to enable VoLTE for Verizon or T-Mobile. extract customer.xml file from Galaxy S8 rom CSC's VZW or TMB folder, and copy it to overwrite customer.xml file under /system/csc.
Thx For informations This phones community is quiet silent :/
If you need to enable VoLTE for Verizon or T-Mobile. extract customer.xml file from Galaxy S8 rom CSC's VZW or TMB folder, and copy it to overwrite customer.xml file under /system/csc.
Click to expand...
Click to collapse
Anyone have the T-mobile CSC file to upload here?
prozo said:
Anyone have the T-mobile CSC file to upload here?
Click to expand...
Click to collapse
I need this as well
Don't forget -d: lz4 -d [input] [output]
Hi everyone,
How can I get the boot.img (either patched with magisk or clean) for the 13.0.8.0.SKDEUXM (11TPro vili - EEA)?
I've performed an OTA update, patched with magisk 24.1 with the option to "install to inactive slot (after OTA)" and now I can't boot into the device.
This is the process I've followed in previous updates, but this time it hasn't worked.
I've tried changing active slots (A/B) and trying to boot, without any luck.
Many thanks!
FYI, i've extracted boot.img from the recovery file:
https://bigota.d.miui.com/V13.0.8.0.SKDEUXM/miui_VILIEEAGlobal_V13.0.8.0.SKDEUXM_5142aa18f5_12.0.zip
Using those instructions: https://www.droidwin.com/extract-pa...The_Need_to_Extract_payload_bin_File_using_PC
If someone needs the untouched boot.ini 13.0.8.0.SKDEUXM (11TPro vili - EEA) file, just let me know.
I have seen that there are problems after updating to miui 13 with the option to "install to inactive slot (after OTA)". How to do it in good way? I have last time almost bricked my device and i don't want to have same ****ty feeling again...
Did you manage to patch with Magisk and install SafetyNet?
shr3kull said:
FYI, i've extracted boot.img from the recovery file:
https://bigota.d.miui.com/V13.0.8.0.SKDEUXM/miui_VILIEEAGlobal_V13.0.8.0.SKDEUXM_5142aa18f5_12.0.zip
Using those instructions: https://www.droidwin.com/extract-pa...The_Need_to_Extract_payload_bin_File_using_PC
If someone needs the untouched boot.ini 13.0.8.0.SKDEUXM (11TPro vili - EEA) file, just let me know.
Click to expand...
Click to collapse
ciao, i am not able to extract boot.img 13.0.8.0 dispitee i follow the procedure above, could you put the boot.img uou extract here. thanks in advance
Just download a fastboot rom(tgz) the boot img is inside the img folder.
https://xiaomifirmwareupdater.com/miui/vili/stable/V13.0.8.0.SKDEUXM/
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
blocky3321 said:
I did as I usually do I updated my system and then reflashed vbmeta and root but for the latest update it didn't work.
Click to expand...
Click to collapse
Because the ota cancel magisk robot. U have to repatch new boot.img and reflash magisk
PhotonIce said:
If you're using magisk to root (and twrp), then after flashing the latest version (24.1 right now), boot into you system, open the apps drawer then close it and wait a little while. sometimes it takes a minute to load in that shortcut for installing the magisk app. if you managed to install the app, but you dont have root, open the app and make sure that you have both options on the home page installed (i believe its magisk, and magisk app). You need the top one for root, the bottom one is the one you just installed. Also make sure they are up to date, as sometimes outdated versions dont work. Or maybe the opposite is happening, and the newer version of magisk doesnt work for you, if thats the case then download the version you used before and flash that.
Click to expand...
Click to collapse
with the older versions i get suck in a boot loop and with the new version there is no root
blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
wetito said:
Look into how to root discussion. I have uploaded boot.img patched from new 12.5.4
Open your eyes
Click to expand...
Click to collapse
i tried the boot and vbmeta it didnt work got stuck in a boot loop
It you have 12.5.4 firmware working 100% I have flashed on my device
wetito said:
It you have 12.5.4 firmware working 100% I have flashed on my device
Click to expand...
Click to collapse
tried again and got suck on the miui screen on fastboot reboot
blocky3321 said:
with the older versions i get suck in a boot loop and with the new version there is no root
Click to expand...
Click to collapse
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
PhotonIce said:
i just tried rooting my phone with magisk 24.2 (latest at the moment). just follow the steps i listed in my first post and you'll have root.
Click to expand...
Click to collapse
use magisk 24.1, because 24.2 it's a beta. it's buggy. my files are patched with 24.1
blocky3321 said:
tried again and got suck on the miui screen on fastboot reboot
Click to expand...
Click to collapse
1. Download the fastboot version of your rom here:
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
I prefer 12.5.4 as it's not buggy, laggy as MIUI 13 and it has navigation button shortcuts, a new cool feature. Remind again, you must download Type fastboot, not Type recovery
2. Unzip downloaded rom, look for [rom name] folder -> images -> boot.img file
3. Copy that boot.img to your phone storage, any phone is fine
4. Run Magisk 24.1 on the any phone that got the boot.img file
5. Press Install
6. Choose Select and Patch a file
7. Navigate and choose the copied boot.img
8. You'll get something like this in your phone storage: magisk_patched-24100_VDv7z.img
9. Copy magisk_patched-24100_VDv7z.img to your PC
10. Install ABD 15 seconds installer, if not already done so
11. Get phone to fastboot mode
12. Use this command to enter fastbootd
Code:
fastboot reboot fastboot
13. Flash empty vbmeta.img:
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
fastboot flash vbmeta_b vbmeta.img
Where is this vbmeta.img from? Check downloaded rom folder, look for [rom name] folder -> images -> vbmeta.img file
14. Use this command to flash your Magisk patched img:
Code:
fastboot flash boot magisk_patched-24100_VDv7z.img
Reminder: Each time Magisk patches an img file, it changes name randomly, so don't blindly input this command, you must change name too: fastboot flash boot [magisk patched boot name].img
15. Reboot to your phone's rom:
Code:
fastboot reboot
Hey, my 9 power has an NVT-TS touch panel. All android 11 based ROMs seem to work such as Pixel Blaster and Lineage. However, when we talk about Android 12, my touch seems to only work on Evolution X.
I tried installing PixelPlusUI and PixelOS, however my touch does not work in them. If I try installing a custom kernel with those two, the OS does not boot and the phone gets stuck on the Redmi boot logo.
I have tried many fixes from various threads but nothing seems to work.
Anybody with a workaround or suggestion?
Update: Only a previous version of EvoX works. The latest version does not boot.
Hi. What kernel and recovery did you used for a12 rom ? Can you put here links to twrp/kernel and roms used in process ? Thanks. I have the same model with nvt touch and nothing worked for me and now i'm back to stock miui 12.5.11 global.
I used PitchBlack Recovery but also tried 2 different TWRP and Orange Fox Recoveries. I tried flashing various kernels but none worked. In the end, the kernel within the evox rom itself had to be used.
Hello,
I'm actually running fine a CrDroid on android 12 without issue.
Here's how i flashed it :
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
From another XDA Post : https://forum.xda-developers.com/t/...onsive-with-custom-roms.4342665/post-86009079
Except i didn't fhashed an old CrDroid release, but the latest. Android 12 work just fine on my Juice with the same screen as yours
uzurka said:
Hello,
I'm actually running fine a CrDroid on android 12 without issue.
Here's how i flashed it :
FOR JUICE!
1. Reflash the Firmware using MiFlash (From clean all and lock, change it to clean all Only)
2. Boot your device to Fastboot mode and Connect your device again to the PC
3. Download Minimal ADB and Fastboot and Install it, as follow the Instructions.
4. Download the OrangeFOX Recovery, download the Xiaomi.eu Rom, and download your Favourite Custom Rom.
5.Go to the Directory of Minimal ADB and Fastboot ----> C:\Program Files (x86)\Minimal ADB and Fastboot
and paste the recovery.img from the Archive in the Directory of Minimal ADB and Fastboot
6. Launch the Minimal ADB and Fastboot.exe Shotcut from the Desktop and type these commands:
1. Fastboot flash recovery recovery.img
2. If you want to reboot the device Fast type Fastboot reboot
7. Boot the device to the OrangeFOX Recovery, go to the Menu and open the Settings
8. From the Settings select General and uncheck Mount system and vendor read-only
9. Important! To install Successfully the Rom u need first to format the Data, go to Wipe section, select Format Data, type yes and Confirm.
10. Disconnect the Phone, connect it again to the USB and drag the Xiaomi.eu rom zip and the Custom Rom zip to the Phone
11. First u need to Install the Xiaomi.eu Rom zip this is Important!
12. When the flashing of the Xiaomi.eu Rom zip is Complete, u can flash your Favourite Custom Rom
13 Final Step: Format the Data with typing Yes again and Reboot the device, Enjoy!
From another XDA Post : https://forum.xda-developers.com/t/...onsive-with-custom-roms.4342665/post-86009079
Except i didn't fhashed an old CrDroid release, but the latest. Android 12 work just fine on my Juice with the same screen as yours
Click to expand...
Click to collapse
Hi. What type of screen do you have ? Can you put the link here to download what rom you installed ? Thx.
I have the exact same type of screen than you, NVT-TS
I downloaded the rom from the official website of CrDroid : https://crdroid.net/juice/8
For the stock zip (step 11), i used this one : https://sourceforge.net/projects/xi...i_HMNote94G_HM9T_21.11.24_v12-11.zip/download
Btw, use crdroid 8.6 for juice. ATM 8.7 don’t work with touchscreen afaik. I did have to reinstall 8.6 after update
uzurka said:
Btw, use crdroid 8.6 for juice. ATM 8.7 don’t work with touchscreen afaik. I did have to reinstall 8.6 after update
Click to expand...
Click to collapse
Thank you, crdroid 8.6 worked. However, I wanted to use ROMs like Pixel Experience and PixelPlus but they touch does not work on them.
Atm, PixelPlusUI or PixelExperience are A12 AOSP with integrated Gapps (probably others differences but no matter), use flamegapps to get full gapps package and there you go!
Atm, i tried a lot of roms, and with A12, only CrDroid8.6 works...
REQUIREMENTS - BL UNLOCKED
You need to be on VERSION : RMX3312_11.C.12_IN_202304230924
If not on RMX3312_11_C.12 version - download the entire OTA PACKAGE from the above link & LOCAL INSTALL
Reboot to Bootloader adb reboot bootloader or Power + Volume Down
Take the ROOT BOOT image from the zip file given below and PASTE it in platform tools folder
FLASH the ROOT BOOT IMAGE fastboot flash boot RMX3312_11.C.12_ROOTBOOT.img
Type - fastboot reboot
Finished - Now your Realme GT2 - RMX3312 is now ROOTED!
P.S. : FLASH ON BOTH SLOTS
To keep ROOT when you receive an OTA update
DOWNLOAD THE OTA UPDATE
Let it UNZIP
When it shows - INSTALL / REBOOT TO INSTALL option, put to recents - Open MAGISK
There in MAGISK - SELECT THE INSTALL OPTION on the TOP RIGHT
& then select INSTALL TO INACTIVE SLOT (AFTER OTA) OPTION
Click on OK on the POP-UP MENU in MAGISK
NOW THE DEVICE WILL REBOOT - UPDATE TO THE LATEST OTA & STILL KEEP ROOT!
DOWNLOADS : Both STOCK & ROOT boot images are attached below in one ZIP FILE!
Each Boot Image is 192MB & the compressed ZIP FILE below is 72.6MB.
NOTE : I'm NOT RESPONSIBLE FOR BRICKS, STONES, BLASTS, WIPES etc. of RMX3312
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
gx7x said:
Thank you of the guide.
Just questions, what is meant by "P.S. : FLASH ON BOTH SLOTS"?
and What is the SafetyNet status?
Click to expand...
Click to collapse
He means you need to run the flash boot command for each slot
for instance your system runs on a slot, as soon as you type the
fastboot flash boot [boot image]
if it shows writing boot_a
then you need to type
fastboot flash boot_b [boot image]
to flash in the b slot also
if it shows writing boot_b
then you need to type
fastboot flash boot_a [boot image]
to flash in the a slot also
and you can pass the safteynet easily even when in root, u can use zygisk and magiskhide to pass the safteynet and you can run any banking app you want
Please do not use the boot images provided if you have not updated to the current latest version
Note: EU version boot image might be different so don't try
p.s you can extract boot images yourself from any version you want!
Stano36 said:
How to extract images from OTA zip files:
Extract the OTA zip file
Download and extract payload-dumper-go
Drag and drop payload.bin on payload-dumper-go executable
Spoiler: Video instructions
Click to expand...
Click to collapse
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
b0nb0n3v said:
HIGHLY recommend to extract boot for your version, tnx to Stano36 we have well prepared collation of update. Thanks to Prajwal_Beast for this guide!
I have some questions about "a" and "b" partitions, where can I found some information why we have two partitions and all have two or some of them and etc..
Click to expand...
Click to collapse
We have two partitions so that if one fails the other can safely boot however most of us are careless and flash on both partitions so it's not really helpful for us
How to root gt 2 running on pixel os?
_PsyDuck_ said:
How to root gt 2 running on pixel os?
Click to expand...
Click to collapse
extract the pixel os file & patch the boot image using magisk & flash the magisk patched boot image
Thanks