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)
hi i am using note 5 ai 6/64 gb with stable chinese rom miui 10.2.1..now i want to shift to global rom..after unlocking bootloader what are the steps i should follow?
download the global rom version of 10.2.1 from
https://forum.xda-developers.com/redmi-note-5-pro/how-to/received-9-5-17-ota-update-t3813192
if you boot is unlocked (finally) (after many days of waiting period)
put the 1.6gb rom in sdcard or otg
then using any good recovery ( i am using orange fox 8.3-2) https://sourceforge.net/projects/orangefox/files/whyred/
extract it and there will be recovery.img file
connact Rn5p in fastboot mode and boot recovery from minimal adb and fastboot window
fasboot boot (& drag drop recovery.img in the terminal window from extracted folder) and press enter ,
device will show MI logo, if your 1.6gb rom is in OTG drive then NOW is the time to connect you OTG before ORANGEFOX logo appear, otherwise it won't read properly.
for clean flash wipe /data /system /cache /internalstorage /delvik etc
then come back to install and from sdcard' or OTG flash the 1.6gb globalrom of 10.2.x once done
reboot atleast till MIUI setup screen
if you wana ROOT
boot back into recovery ( same steps) and
1. take BACKUP OF YOUR BOOT SECTOR, it may backup in your sdcard or OTG drive
and now flash the following
1. lazyflasher.zip (search for Redmi5 / note5A / Note5Pro on XDA) (its a small zip file)
2. flash magisk 17.1 (i dont recomend 18.0 since they have changed the script, and later no rcovery can extract RAMDISK folder from boot sector unless you RE-FLASH the whole rom.
first couple of boots may goto reboot but it should come to miui setup again.
if anything goes wrong,
reboot in to recovery again! and restore the BOOT sector, it will UNDO the lazyflash and Magisk
now, magisk 17x does say that it tries to disable DMvarity so try flashing ONLY MAGISK. for root.
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
thanks so much for this! Been flashing since andriod 1.6 but couldnt wrap my dumb head around these dual partitions.
And is the same for miui.eu ?
raphae34 said:
And is the same for miui.eu ?
Click to expand...
Click to collapse
No. Follow the instructions in the OP there. They work.
Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?
Snjeky said:
The 1st method for Pixel Experience does not work for me, after following all the steps carefully, if i boot into system it boots me to fastboot everytime, or if I dont reboot to system (in TWRP after flashing everything) it only says no OS installed are you sure you want to continue, so any help?
Click to expand...
Click to collapse
the "no os installed" is normal, dont worries.
The installation method for pixel experience worked when I installed the old version, it was updated multiple times so probably the process changed, I will update the thread later
This dual slot fuking my mind up.
TWRP asking for password to decrypt data. while first boot in recovery.
also *unable to decrypt FBE device* error while formating data.
"couldnt able to flash Any ROM "unable to partition path/cache" error.
ps. flashed in slot a.
When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same
ManuMan99 said:
When I install twrp on fastboot it stuck there, I have Android 10 stock, is anything that I can do ? I try like 3 times and always the same
Click to expand...
Click to collapse
downgrade to android 9. apparently android 10 got some issues.
pradie said:
downgrade to android 9. apparently android 10 got some issues.
Click to expand...
Click to collapse
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it's booted correctly.
---------- Post added at 12:37 PM ---------- Previous post was at 12:37 PM ----------
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
I apologize for not being precise. i had the same issue. downloaded and flashed android 9 Stock global ROM with mi flash tool. now it booted correctly.
Sapper Morton said:
Indeed, it's not as straight forward, but it's possible without losing Widevine L1 security level; read my experience here, I explained the steps I took ; so far, I came back to v11.0.8.0 QFQMIXM from v10.3.17.0 PFQEUXM after the downgrade, with no issues whatsoever (no format/wipe data); my DRM Keys and sensors remains intact.
Click to expand...
Click to collapse
Thank you I wouldn't have guessed that would work it seems too easy to be a fix but that's good news.
Thanks for that info
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.
vjrx88 said:
Then what to do? I downgraded from Android 10 Stock to Android 9 Stock 3.13.0.PFQMIXM because I soft-bricked my phone. I Flashed the stock ROM using Mi Flash tool. It flashed OK but my MI A3 sensors are not working. Someone said Flash persist.img via TWRP but when I try to flash it asked me in which partition to flash.
Partitions available are:
bluetooth
modem
System Image
Dtbo
Vendor Image
splash
Boot
Install Recovery Ramdisk
I am confused where to flash. If this method isnt suitable as you said then guide me what to do. I have Global Fastboot ROM for Android 9 Version 3.16.0.PFQMIXM for Mi A3 available. Should I flash this using Mi Flash tool? Does it solve sensor issues or not? Please help.
Click to expand...
Click to collapse
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!
garylawwd said:
If you are on stock android 9 now then flash an android 10 custom rom and then downgrade to android 9 like you did. Downgrading from stock 10 to stock 9 causes big issues like you are having.
If you did flash persist.IMG you would have caused stuff in your device to break forever without any way of fixing it don't do it!!
Click to expand...
Click to collapse
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.
garylawwd said:
Don't tell him to downgrade. If you downgrade you will lose the use of all sensors or proximity sensor, compass etc and to fix this you need to flash persist.img which will cause you to lose widevine L1 so say goodbye to hd streaming and the like.
Be careful what information you give people if it will cause massive issues.
Its not that straightforward to just downgrade
Click to expand...
Click to collapse
No problem in downgrade ,, i Already downgraded. No bugs facing!
---------- Post added at 06:34 AM ---------- Previous post was at 06:32 AM ----------
vjrx88 said:
I updated it to Stock Android 10 OTA update using TWRP Recovery and re-flashed TWRP and Magisk ZIP using TWRP and now sensors and phone is working fine. I know Android 10 for Mi A3 have some bugs but I decided to live with it until Stable Android 10 update made available by Xiaomi. Flashing Custom Android 10 ROMs have mixed reviews and have bugs so I decided to stay on Stock.
I tried flashing persist.img by mounting Persist partition using TWRP before doing this but nothing happens and sensors didn't worked. Now they are working.
Click to expand...
Click to collapse
Lol i came back to 9 ,, untill stable comes or i will use pixel rom ?
Kaissner said:
I had this device for two days now, one of the first things that I tried was to install a custom ROM and I was surprised of how hard it was to do, so after a lot of trial and error I managed to install those two ROMs so I wanted to share how I did it so nobody has to suffer like I
Okay so I have tried two methods, one worked for Pixel Experience and the other for Lineage OS, there are probably better ways to do this so be sure to reply to this thread if you find another ways to accomplish this!
IMPORTANT!:
1. I did the two of this methods with the stock ROM with a minimal setup (skipping wifi, no google login, no fingerprint, etc).
2.You need to have the bootloader unlocked.
3. Im not responsable if you brick your phone or lose your data, do the following steps if you know what you're doing and always back-up your data!!!
Files used:
TWRP link (Download both the img and the zip)
Pixel Experience link
LineageOS link
Gapps link
Magisk 20.1 link
Encryption patch (patch_no_fde10) link
Method 1 (Tested succesfully with Pixel Experience):
Thanks to ElSuperFullHD for creating an awesome guide in how to install Pixel Experience!
How to install Pixel Experience in Xiaomi mi a3 (Spanish guide)
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay) and reboot into recovery again (Long press Vol + when the device starts until you boot into recovery).
6. Go to advanced wipe Dalvic cache, Data and System.
7. Install Pixel Experience ROM and TWRP zip again and restart to system.
8. You're done, enjoy!
Method 2 (Tested succesfully with LineageOS):
Thanks to suschmania for your extremely helpful comment, I wouldnt have figured how to install LineageOS without him!
1. Start your phone in fastboot mode.
2. use fastboot getvar current-slot (Check if phone is in slot a, if it isnt change it to a using fastboot set_active a)
3. Flash custom recovery (in this case I used TWRP) with fastboot flash boot twrp.img
4. reboot using fastboot reboot (NOTE : Before hitting "Enter", long press Vol + on your device until you see the Android One logo. By doing this your device will be forced to boot into Recovery and not into System).
5. Once in TWRP copy TWRP recovery zip into the phone and wipe Dalvic cache, Data, Vendor and System.
6. Install the ROM and TWRP recovery zip (This will make the recovery to stay).
7. Reboot into recovery (twrp shows the warning no os installed, continue anyway).
8. The filesystem will be decrypted (All folders corrupted) dont worries, just go to advanced wipe and wipe internal data, once that's done copy Gapps, magisk and the encryption patch into the phone).
9. Flash Gapps, magisk (Optional) and encryption patch.
10. Reboot to system (It may take up to 10 minutes to start so give it time, if more than 10 minutes passes see step 11).
11. In case of bootlop boot back into recovery and format data (its the one where you need to write yes to format), after its done reboot to system again.
12. You're done, enjoy!
I hope this guide was helpful to you, good luck!
Click to expand...
Click to collapse
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.
spring_roll said:
EDIT: Solved it by flashing this inofficial TWRP: https://forum.xda-developers.com/mi-a3/development/recovery-twrp-3-4-0-0-patched-boot-img-t4123287
I have a problem. I am stuck on fastboot. I followed the tutorial unto step 4:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot twrp.img
target reported max download size of 803475456 bytes
sending 'boot_a' (39892 KB)...
OKAY [ 0.910s]
writing 'boot_a'...
OKAY [ 0.197s]
finished. total time: 1.111s
But after this the phone always reboots to fastboot, I can't boot into TWRP or the system. Plz help.
Click to expand...
Click to collapse
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version
garylawwd said:
I know you solved it but the reason the other twrp wasn't working for you is because it is built only for Android pie and I'm assuming you have Android 10. That's why you always booted to fastboot. The installer.zip will work with any Android version but the twrp.img files are built using kernels of a specific Android version
Click to expand...
Click to collapse
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?
spring_roll said:
Ok thx for the info.
Another question. I didn't understand step 5:
"5. When TWRP starts, move and flash TWRP zip (This will make the recovery to stay)"
Where do I have to move and flash the ZIP? I just skipped this step and now I have the ROM installed which I wanted (PE Plus).
Do I have to do something now or is TWRP installed properly now? Can I fetch this step later?
Click to expand...
Click to collapse
For you I don't think twrp is installed now. Some ROMs have twrp built in but if not then you have to manually flash twrp every time you flash a ROM or it gets overwritten with stock recovery.
When you flash the twrp.img and boot twrp it isn't actually installed, you are running it in ram and when you reboot it goes out of ram and your left with an un-bootable slot due to your boot slot being messed up from flashing the twrp.img and twrp won't stay installed.
For it to be installed properly you need to flash twrp.zip which will patch your boot.img with twrp and install it.
But as I said everytime you flash a ROM this will overwrite twrp and it will be gone unless the twrp.zip is flashed in twrp before rebooting.
Not as easy as it used to be by just installing twrp once and it is there forever. The new era of Android
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