Related
Hello hello,
this will be my "live" thread of bringing AICP 13.1 to my xperia z1c, I found some Guide's that I will follow and I will share with you all the links and knowledge I gained as a newbie that I used to understand and fix my problems on the way.
Maybe this will help you, too.
Main Tutorial: LINK
Target of all this: LINK
My Device:
Sony XPERIA Z1C, 14.6.A.1.236 , Lollipop 5.1.1
My best hint: read carefully, take your time to understand what you're trying to do and do your own research!
Hopefully you will get a aicp custom rom out of it.
_____________________________________________
_____________________________________________
General information: Android 5.1.1 cannot be rooted due to its high security standards, therefore we will downgrade to a lower security stock rom and create root access there. Root access will be needed as well as an unlocked bootloader to install real recovery (TWRP) which is the tool to flash custom roms like aicp. But the aicp custom rom will not have a good working camera, don't ask me why, but the camera seems to be a really difficult thing from the point of developer's view, let's accept this. Aside of that disadvantage, this custom rom is a very nice software and it makes my z1c kind of new. I don't use my camera anyway often at all.
During all this flashing thing I had a very big ??? while implementing real recovery. I was able to flash the .236.ftf but not the openbootloader.ftf as described in section 5 in the main tutorial. The result was twrp boot failed.
Error description:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
boot stock rom works
My solution:
I restarted from scratch and finally with the kind of messed up secquenceI got it:
flash .236.ftf works
flash openbootloader fails
flash twrp works
boot twrp fails
flash openbootloader works
flash twrp works
boot twrp works
UPDATE 06.12.2018 as a solution for REAL RECOVERY with working camera <<< RECOMMENDED
0. boot into rom works
1. flash openbootloader works
2. boot into rom works
3. flash .236.ftf works
4. boot into rom & check camera works
3. flash twrp ( business as usal ) works
4. boot twrp ( First boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
5. full wipe, flash aicp-rom, flash gapps, flash magisk-root, boot system works
6. enjoy Oreo 8.1 & camera check !!! works !!!
This routine worked straight forward for me where I started from scratch with my second device.
Flashing aicp was pretty easy, good to know for flashing the rom was full wipe = advanced wipe and select everything except of micro sd
To complete my aicp 13.1 Oreo 8.1 device the camera problem has to be fixed ( Saving the taken picture fails, display goes into freeze, no chance to solve this with camera mods, camera apps )
But @lm089 gave me the right hint, and finally this was my solution! Thanks again @lm089!!
Have fun with your new >> SONY XPERIA Z1 COMPACT <<
How to update TWRP
1. Turn Off your device
2. Start device in fastboot mode by connecting via usb cable to your pc and press Vol- until blue led tuns on
3. use fastboot flash recovery twrp.img to flash it
4. boot twrp ( This first boot is damn important, don't miss it! Press Vol- & Power, wait for vibration, release Power & keep Vol- until twrp boots up ) works
How to update to aicp 14.0 pie 9.0
starting with the running and latest aicp 13.1 oreo 8.1 rom above I just followed the Instructions here. As a specialty I had to install the Magisk Manager App manually into the rom to get root. Downloading supersu.apk from www.supersuroot.org works fine as well.
Your fastboot connection doesnt work for some reason though u had this workin fine in the past? maybe u had a windows update. install your drivers again.
>> LETS KEEP THIS DEVICE ALIVE <<
_____________________________________________
_____________________________________________
More helpful links that I used:
Debug apps by creating logs
what is adb? an xda tutorial
ADB working Download Link and ADB Article on xda
xda flashtool error during setup: click
[NOOBIE] Basic adb commands and device partition overview
Latest TWRP 3.2.3-0 for z1c
root solution using flash tool
Restore DRM functionality after UB
If TA Backup dry restoration restoration fails: Solution and Download *.dll
Boot into recovery or fastboot mode
How to install TWRP
Magisk beats superSU
How to Install Custom ROM using TWRP for Android!
change boot animations
[TUTORIAL] Design Your Own Bootanimation
Backup & Restore Your ROM With TWRP
Terminology: odex and deodex
If the camera goes into freeze or saving the picture fails: This was my solution! /// But you better go straight with the steps of my update 06.12.2018, field tested!
THANKS A LOT TO @colaigor for his [BEGINNERS GUIDE]
Ok. So i dont have much time now but i can give some short directions.
1. Get unlock codes from sony for bootloader unlock
2. Instal adb and fastboot at your system(PC)
3. Instal z1c drivers
4. Instal flashtool
5. Unlock bootloader,root,flash recovery(search forum for "real recovery" ),flash root solution
6. Flash wanted rom,gaps
P.P. On second thought u dont need flashtool. All can be done with adb and fastboot commands from terminal
There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?
derjango said:
There is one thing I don't understand:
what is the difference between FLASHING REAL RECOVERY and FLASHING FAKE RECOVERY?
What I read is, that in both cases I get TWRP but on different partitions (real = Recovery Partition, fake = Boot partition) but do I need both or do I choose just on of them?
Click to expand...
Click to collapse
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.
Ok thank you :good:
flashtool log of openbootloader.ftf failed:
01/015/2018 13:15:58 - INFO - Device connected in flash mode
01/017/2018 13:17:19 - INFO - Selected Bundle for Sony Xperia Z1 Compact(D5503). FW release : 1. Customization : openbootloader
01/017/2018 13:17:19 - INFO - Preparing files for flashing
01/017/2018 13:17:19 - INFO - Please connect your device into flashmode.
01/017/2018 13:17:19 - INFO - Using Gordon gate drivers version 3.1.0.0
01/017/2018 13:17:20 - INFO - Opening device for R/W
01/017/2018 13:17:20 - INFO - Device ready for R/W.
01/017/2018 13:17:20 - INFO - Reading device information
Click to expand...
Click to collapse
solved, I skipped step 5.2, flashing the .236.ftf in advance
but how can I start TWRP?
doesnt work with POWER + Vol-, vibrate & release power
I tried to flash the following recovery solution using this command:
smartphone in fastboot mode (blue LED enabled)
fastboot flash recovery recovery.img
TWRP from step 5.1 of the GUIDE
TWRP 3.0.2
My formerly flashed .236.ftf rom works fine, but I cant start TWRP the device goes directly to my rom
zlata said:
Real recovery have its own partition(after that update to bootloader). Custom recovery dont have that and its stored somewhere else(FOTA,onetime boot image , etc). Choose real recovery. New stuff works good with it.
Click to expand...
Click to collapse
Thats where I'm stuck right now, any ideas how to fix?
okay got it, basically i do not know what the problem is but:
after BLU
flash .236 :good:
flash openbootloader
flash twrp :good:
--> failed to install openbootloader and probably thus twrp failed
solution: I skipped to flash .236 as recommended by the author of the GUIDE (step 5.2)
flash open bootloader :good:
flash twrp :good:
--> failed to start twrp, though it was installed successfully
flash .236 :good:
flash openbootloader (failed again, but it's already on the device and I guess I could have skipped this here)
flash twrp :good:
first boot of twrp is successful :good:
And basically the author explained it in his text, FIRST INSTALL OPEN BOOTLOADER BEFORE WRITING STH TO RECOVERY PARTITION
I think you should use Aicp 14 pie instead of 13.1 Oreo
I feel Aicp 14 PIE is very stable and flash port camera stock this link https://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/port-stock-camera-nougat-roms- t3628791
Nice thread, thank you! Wish I had that when I started rooting and flashing
@lm089 Haha it's quite some work to get into it, right? I just saw that we are running on the same device & custom rom, how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj
derjango said:
how did you solve the issue with the not working camera? I'm still reading stuff about some mod, but I'm curious and open for tested solutions on z1c
best, dj
Click to expand...
Click to collapse
Had this situation twice with 2 different oreo ROMs. Both times I solved it following a rather strange sounding suggestion I found on the AICP 13.1 discussion thread. The basic idea is to go back to a stock Sony ROM. Boot into it and make sure the camera is working which for me was the case both times. Then - if necessary - re-root your phone (on first occasion I flashed a pre-rooted .236 version but that caused some extra trouble so next time I decided to flash an unrooted version). And from then on it's the standard way as you described it in your OP.
Good luck!
Okay, thanks a lot for your hint! Unfortunately the camera mod didn't fix the problem, my android-task for this evening is defined:
AICP 13.1 Oreo 8.1 on z1c, root, ulb, magisk 17.1
1. backup my system (done)
2.0 flash stock rom lollipop 5.1.1 (14.6.A.1.236.ftf) with flashtool via usb (done),booting the os for the first time takes quite long (~10m), check camera in the os (done)
interesting fact: recovery is deleted by flashing the rom via flashtool - I thought I can go the lazy way and skip the step of installing twrp again into recovery
2.1 okay, let's do it: install twrp (done) and boot into twrp, NOT into ROM!! (done) (Vol- & Power, wait for vibration & release Power but keep Vol- until TWRP starts up)
3. flash aicp 13.1 following this (full wipe as an advanced wipe: select all EXCLUDING THE SD STORAGE)
Again here, I recognized the first boot of the rom takes quite longer.
4. check camera (done)
!!!! IT WORKS !!!!
(I did it two times)
alright, lets start flashing my second device - now I know how to do it
Thanks guys!!
derjango said:
!!!! IT WORKS !!!![/SIZE]
Click to expand...
Click to collapse
Weird, isn't it?
lm089 said:
Weird, isn't it?
Click to expand...
Click to collapse
Totally But hey, it's a solution
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too
derjango said:
btw @lm089, boots your ota-updater directly into twrp and start the flashing procedure? In my case I had to boot twrp manually and flash the zip manually, too
Click to expand...
Click to collapse
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?
lm089 said:
No, updater is booting into recovery, doing a nandroid backup and wiping caches (because I told it to), then flashing and finally rebooting into system. All by itself :good:
I remember having trouble with that in the past though. Do you by any chance have an SD card formatted as adoptable storage?
Click to expand...
Click to collapse
Yes, its used as an external storage
derjango said:
Yes, its used as an external storage
Click to expand...
Click to collapse
ok, that's something different; adoptable storage means that your SD or part of it is setup to extend internal storage. If you can access all of your SD from TWRP then it is indeed formatted a external storage.
1) How to unlock bootloader:
https://developer.sony.com/develop/...ed/unlock-bootloader/how-to-unlock-bootloader
2) Download Platform-tools (adb & fastboot) r.26.0.2 as latests version does not work (or just for me):
https://xiaomifirmware.com/downloads/download-platform-tools-adb-fastboot-r-26-0-0/
3) Download TWRP 3.2.3-0 https://androidfilehost.com/?fid=11410963190603854057 and place file in Platform Tools folder on PC
4) Restart in fastboot mode and flash revovery:
fastboot flash recovery Z1C_twrp_3.2.3-0.img
fastboot reboot
5.1) Download AICP Oreo 8.1 http://dwnld.aicp-rom.com/device/amami/WEEKLY/aicp_amami_o-13.1-WEEKLY-20181204.zip and place file in Platform Tools folder on PC
5.2) Download Gapps Pico https://opengapps.org/?download=false&arch=arm&api=8.1&variant=pico and place file in Platform Tools folder on PC
5.3) Download stable Magisk 17.1 https://github.com/topjohnwu/Magisk/releases/download/v17.1/Magisk-v17.1.zip place file in Platform Tools folder on PC
6.1) Load TWRP. Advance>ADB Sideload (for Oreo)
adb sideload aicp_amami_o-13.1-WEEKLY-20181204.zip
(do not restart)
6.2) Repeat Advance>ADB Sideload (for Gapps)
adb sideload open_gapps-arm-8.1-pico-2018XXXX.zip
(do not restart)
6.3) Repeat Advance>ADB Sideload (for Magisk)
adb sideload Magisk-v17.1.zip
(restart)
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
IO13 said:
I'm trying to install magisk on MiA2Lite with january update but I fail.
I've tried
- Zip installation (Magisk Manager -> download .zip) but when I reboot on TWRP i don't find zip, all folders seems empty
- upgrade boot image: the upgrade semmes works well but when I restart MiA2Lite and I open Magisk Manager I alway see "Magisk is not installed" ed if I tap on INSTALL Magisk Manager propose: "download zip or upgrade boot img"..
the option "direct install (recommended)" dosn't apear to me
Click to expand...
Click to collapse
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
marstonpear said:
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
I assure you that if I would have preferred to find the information myself rather than wait for some kind user to answer me. Unfortunately it is not so simple, there are many double posts with information missing (you imagine a new user who wants to try to install the GCam, there are several posts on the subject with redundant or sometimes opposite information, there are two posts on how to install Magisk without losing the OTA, they are almost identical but in one there is written that with Pie no longer works, in the other no ..). Look for an info here with the search function is anything but simple so thank you for answering me so exhaustively!
marstonpear said:
If you want to install magisk from TWRP:
-Put the magisk.zip on your fastboot folder,
-Boot to TWRP and connect the phone to your PC, then use this code :
Code:
adb push ./magisk.zip /sdcard
-Now, you will be able to see magisk.zip on the Install section of your TWRP. Make sure to rename the magisk installation zip to "magisk.zip"
If you want to install without TWRP:
-Get patched_boot.img for 10.0.3.0 here: https://forum.xda-developers.com/mi...hed-boot-img-v10-30-0-january-update-t3891331
-Put the img in your fastboot folder, shutdown your phone.
-Go into fastboot mode on your phone (hold Vol- and Power)
-Connect phone to PC and write this on ADB:
Code:
fastboot boot patched_boot.img
-Let it download the img to the phone then unplug and wait for it to boot.
-Install Magisk Manager and tap Install->Direct Install
Next time, before you open a thread, please try reading other threads. Because this is explained pretty much all over the forum. :good:
Click to expand...
Click to collapse
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
bla.tiga said:
Bro.. i'd like to ask
So the diffrence/concept is , if
- with twrp we dont need patched boot.img
- without twrp (we need patched boot img)
Are we can flash stock rom via twrp? So dont need fastboot anymore? At least fastboot for emergency case only
And last why right now is so much step in order doing mod, last time i doing mod with my samsung galaxy grand 2, the key is only how to install custom recovery (cwm or twrp) , from that recovery if we want to install custom rom or root , just download zip , flash from custom recovery, enjoy.... Simple
Why in this phone not like that, especially install GSI rom ( which still im not clearly about GSI and difference with custom rom)
Click to expand...
Click to collapse
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
marstonpear said:
You can't flash stock ROM with TWRP, unless you use a backup of your own stock ROM, then you can recover your backup to install stock. Also you're talking about 6 yr old phone. Many things have changed since then on Android lol. GSI means Generic System Image which means that these roms should be able too boot on every device with treble support. Instead of creating a rom from scratch for every device, they just make a GSI and that can be installed on every GSI supported (project treble enabled) phone. You can still install TWRP and flash what you want. But beware you might have issues and Mi A2 Lite doesn't have any custom ROMs yet, because it is project treble enabled. You can use GSIs for now but most of them lag so I stick with stock. You can try modding the stock rom with magisk etc. :good:
Click to expand...
Click to collapse
Oh i see.. thanks for the explanation... Gathering information in xda is bit confusing lol
Okay one more thing to be clear, right now im on oreo august security patch V 9.6.6.0 ODLMIFF
I want to install twrp and flash magisk (do i need downgrade to 9.6.4.0?) , if i succeed install both of that, and i want upgrade rom to pie or upper version via fastbot flash, i need to remove twrp and magisk, or just directly flash with mi flash??
Today the unlock time for bootloader to unlock will complete and I Intend to install TWRP. I have found the latest officially supported twrp-3.6.1_11-0-alioth.img at https://eu.dl.twrp.me/alioth/. How does it compare to TWRP-3.5.1 https://forum.xda-developers.com/t/recovery-unofficial-twrp-3-5-1-20210702.4300189/.
Can anyone guide me what are the pros and cons of using twrp-3.6.1_11-0-alioth.img and its limitations as compared to TWRP-3.5.1 as I can not find any documentation on twrp-3.6.1_11-0-alioth.img. Any help will be appreciated.
Also does the following limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0-alioth.img ?
KNOWN LIMITATIONS:
The following are some known limitations due to either the design nature of Virtual A/B or a problem with ROM themselves. Please read carefully :-
You cannot format data after flashing a ROM zip (Limitation of Virtual A/B). If you want to format, then reboot recovery after flashing ROM. Additionally, if you are encrypted, the newly flashed ROM must be able to decrypt your device. If not, then you have to format data before flashing the ROM It appears, you can actually format data after reboot even if the new ROM cannot decrypt.
You can flash only one ROM in one boot. If you wanna flash another ROM, you must boot to system once. This is again a limitation of Virtual A/B.
Once you have rebooted after flashing a ROM, you cannot write to the data partition until you boot successfully to the new ROM. Android seals the data partition after a ROM flash to prevent any accidental brick since the newly flashed ROM is actually stored in /data. Only data format is allowed in this case. Once you successfully boot to the new ROM, your storage becomes ready for writing again.
Ideally, after flashing a new ROM, you should only need to wipe your data rather than format. But, due to a problem in the device trees current ROMs are using, you will have to format data if you are currently on miui and want to switch to a custom ROM. Specifically, the roms need this commit and to set vendor security patch level to fix this issue. Switching between custom ROMs should not need format, except for hentai OS.
If you are currently on hentai OS, then before using TWRP, you must flash vendor_boot from the link provided in every hentai OS release. Otherwise, you will get black screen. This is only needed when you boot to TWRP for the first time. Do not repeat this step again. Also, do not try this with beta version of the ROM. Use it only with stable.
If you reboot to older slot after flashing new ROM, the new ROM will be cancelled and you will have to reflash again. This is because of how Virtual A/B works.
If you must flash magisk via recovery (it's not recommended now), please uncheck "Inject TWRP after install" else TWRP will remove magisk.
Do not flash magisk after flashing a ROM before reboot. Magisk's zip detects slot in a different way that will cause issues.
Backuptool (used to persist magisk and gapps across ROM updates) will also not work in recovery due to A/B. You will have to flash gapps (or any other zips) everytime after flashing a ROM.
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
hofi01 said:
you dont search enough...
this is latest A12 TWRP....
https://dl.akr-developers.com/?dir=skkk/TWRP
Installation:
activateUSB DEBUGGIN and OEM unlocked on Poco
(copy all files in Adb folder) rename the long TWRP file to twrp.img
Disable all security settings like PIN, pattern, fingerprint
start Poco in fastboot
fastboot boot twrp.img"
copy twrp.img to Poco or "adb push twrp.img /sdcard/"
TWRP Menü -> Advanced -> Flash Current TWRP or Install Recovery Ramdisk -> you must test it... both should work
TWRP Menü -> Reboot -> recovery
Magisk and safety net working great...
see also....
Xiaomi devices on Android 12 via Fastboot only:
- Download our ROM zip file
- Unpack downloaded zip file in the PC using WinRAR
- Reboot your device to fastboot mode (press volume down + power)
- Connect to PC via USB cable
- Run fastboot installation script from unpacked zip according your PC operating system:
--- For Windows OS - windows_fastboot_update_rom.bat
--- For Linux - linux_fastboot_update_rom.sh
--- For MacOS - macos_fastboot_update_rom.sh
greeting
Click to expand...
Click to collapse
I know where the lastest TWRP for Poco F3 is and how to install it as I have already installed it. That was not the question. The question was that "does limitations of TWRP-3.5.1 also apply to twrp-3.6.1_11-0'? Limitattions like being forced to reboot TWRP after flashing a every single zip file and other limitations like it as mentioned above. Thanks for your reply anyways.
so for me, TWRP does not start again, after installing a file.
I install TWRP, boot into TWRP again and install Magisk. after that I boot into the ROM.
TWRP does not restart itself
So, still no decryption on A12?
I wanted to test new custom roms but i dont want to have to reinstall everything from scratch if i go back to my current rom (.EU).
Can twrp make a full backup and restore it despite not having decryption?
If it cant, can I make a full back up of my phone from cmd in fastboot mode? (so i can just flash it from fastboot to restore everything as it is now)
Here's the steps on how to fix it, because Samsung's treble implementation is kinda crap.
(note: might not work for everyone, steps must be done correctly)
These steps assumes that you have your phone bootloader unlocked, rooted,flashed with a custom Recovery, and encryption removed.
Method 1 (easy, no need to download large flash files)
- Go to your custom recovery and then wipe
- Flash the boot.img file given below (note: Flash only on A71 4G. I am not responsible if your device bricked because you flashed this img on A71 5G or other devices. EVEN IF IT IS SIMILAR, IT WON'T WORK!)
- Reboot to recovery (important)
- Your device might boot to a stock recovery as of now. Don't panic if it does. Power off then boot to download mode
- Select "reboot to download"
- Use Odin to flash twrp-3.6.2_11-3_afaneh92-a71.tar (AP slot) that is given below.
- When the device reboots, immediately boot into the custom recovery by pressing volume up + power button.
- Flash Multidisabler, file given below
- Flash your GSI of choice (select install image then flash as system image)
- Flash any fix zips that need to be flashed (if there are any)
- Wipe again just to make sure
- Reboot
Bugs: This TWRP build's encryption/decryption not fully working. Make sure your device storage is already decrypted, as formatting data will not decrypt your device storage.
Method 2 (hard, but almost guaranteed will work)
Thank you @Zainullahk1234 for this fix
install Stock ROM (4 files, search on Samfw or Sammobile for the flash firmware for the A71. I recommend to flash the latest binary, as flashing older builds will not work sometimes) boot into the stock rom and then change date to 3 months from now
check for updates, make sure you're connected to the internet for this
boot into download mode
flash twrp 3.6.2 (file given above) and vbmeta tar file
boot into twrp
do format data
flash multidisabler
flash GSI ROM
flash GSI Fixes (if there are any)
do factory reset
reboot
if it boots you into fastboot again, shutdown then reboot to recovery, flash twrp 3.6.2 via Odin and try another factory reset and reboot (In twrp)
Credits: @ShaDisNX255 for the stock boot.img, extracted from RayOS
@afaneh92 for the TWRP recovery.
Thread - https://forum.xda-developers.com/t/recovery-unofficial-twrp-for-galaxy-a71-snapdragon.4350893/
@ianmacd for the multidisabler
TigerLake said:
Here's the steps on how to fix it, because Samsung's treble implementation is kinda crap.
(note: might not work for everyone, steps must be done correctly)
These steps assumes that you have your phone bootloader unlocked, rooted,flashed with a custom Recovery, and encryption removed.
- Go to your custom recovery and then wipe
- Flash the boot.img file given below.
- Reboot to recovery (important)
- Your device might boot to a stock recovery as of now. Don't panic if it does. Power off then boot to download mode
- Select "reboot to download"
- Use Odin to flash twrp-3.6.2_11-3_afaneh92-a71.tar (AP slot) that is given below.
- When the device reboots, immediately boot into the custom recovery by pressing volume up + power button.
- Flash Multidisabler, file given below
- Flash your GSI of choice (select install image then flash as system image)
- Flash any fix zips that need to be flashed (if there are any)
- Wipe again just to make sure
- Reboot
Bugs: This TWRP build's encryption/decryption not fully working. Make sure your device storage is already decrypted, as formatting data will not decrypt your device storage.
Credits: @ShaDisNX255 for the stock boot.img, extracted from RayOS
@afaneh92 for the TWRP recovery.
@ianmacd for the multidisabler
Click to expand...
Click to collapse
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
afaneh92 said:
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
Click to expand...
Click to collapse
Okay, I'll link your TWRP thread.
afaneh92 said:
It was simple if you linked my twrp thread, and please drop the image and direct link to my host.
Click to expand...
Click to collapse
Also btw, TWRP 3.7 caused my phone to not boot, so I reflashed twrp 3.6.2 and this build is what I put here.
TigerLake said:
Also btw, TWRP 3.7 caused my phone to not boot, so I reflashed twrp 3.6.2 and this build is what I put here.
Click to expand...
Click to collapse
Thanks, will try to fix it soon
How to flash miui14 Chinese dev recovery rom in mipad 5
?
1. You download the CN Stable dev build from here
2. A. It's a recovery ROM zip, so you can only directly flash it in MIUI Updater, or MIUI Stock Recovery, if you are already on the same branch (CN Stable dev)
2. B. otherwise (you are on a different ROM variant, like Global or Stable non-dev) you have to unlock your tablet and then flash the recovery ROM zip via custom recovery (TWRP) or flash a fastboot ROM (which is not the same as the zip above) and flash it via MiFlash Tool, or adb from a computer.
Am in stable indian rom
Cant update through miui updater ?
Because last time changing China fastboot rom my device got bricked
Any other possible way ?
Twrp guide ?
underlines said:
1. You download the CN Stable dev build from here
2. A. It's a recovery ROM zip, so you can only directly flash it in MIUI Updater, or MIUI Stock Recovery, if you are already on the same branch (CN Stable dev)
2. B. otherwise (you are on a different ROM variant, like Global or Stable non-dev) you have to unlock your tablet and then flash the recovery ROM zip via custom recovery (TWRP) or flash a fastboot ROM (which is not the same as the zip above) and flash it via MiFlash Tool, or adb from a computeram i
Click to expand...
Click to collapse
drmagesh7 said:
Am in stable indian rom
Cant update through miui updater ?
Because last time changing China fastboot rom my device got bricked
Any other possible way ?
Twrp guide ?
Click to expand...
Click to collapse
WARNING: If you don't know how this stuff works, I recommend not to do it. This will install CN Stable Dev ROM, only English and Chinese will be available. Mi Flash gives an error but the Tablet reboots and MIUI 14 CN will be properly flashed without losing user-data. But to be sure, make a backup and learn how to fix a soft-bricked device BEFORE you start. If you soft-brick, don't ask questions here but google and learn through youtube tutorials.
unlock your device. Apply here
download the latest MIUI 14 chinese stable dev fastboot tgz file
extract the tgz with winRAR or 7zip into a folder
download and extract Mi Flash Tool into another folder
run XiaoMiFlash.exe inside the extracted Mi Flash Tool folder
Install the drivers when asked inside the Mi Flash Tool, if it gives an error then install the driver manually
Turn off your Mi Tab 5, then reboot it by pressing POWER + VOLUME UP until the Fastboot screen appears
Connect your Mi Tab 5 to your computer via USB.
Click the "refresh" button in Mi Flash Tool. In the table below the "select" button a new row should appear with an id and device. If not you have a USB driver problem, cable problem, your tablet is not in fastboot mode or other issue. Use google to fix your problem or watch a youtube video to learn how to do it.
in Mi Flash Tool click the "select" button and navigate to the folder where you extracted the tgz file, click OK. (Make sure you navigate and select the "nabu_images_V14.0.22.12.21.DEV_13.0" folder, and not the one inside it called "images")
At the bottom of Mi Flash Tool select "Save user data"and in the drop down next to it select "Flash all except storage"
Click the "flash" button in Mi Flash Tool and wait until it's done.