Hi guys,
After I had serious problems with the latest MIUI 12 (freezes, slow, high battery drain, reading mode goes on-off at random, write keyboard delay, countless other bugs)... I unlocked the bootloader and installed Lineage 17.1 and gapps via ADB sideload. All OK for a week of intensive use.
Then I decided to backup all, copy backup on the PC, wipe all and try EvolutionX 4.5 via sideload.
It stuck on boot animation.
I reboot in recovery, wiped, installed EvolutionX via recovery, same problem.
Then I wiped all and try to restore the LOS 17.1 backup, but the restore freezes at 19% (restoring system image).
So I re-wiped all and tried pixel experience 10, but after install, it stuck on "MI" screen and then reboot on recovery again.
Same for ALL the android 10 roms I tried then.
The only ROM that work now, is Evolution X 5.3; if I wipe and install LOS17 or any other ROM based on android 10, It reboots to recovery again, except EvolutionX 4.5 that stucks on boot animation.
How can I go back to lineage 17.1 or make EvolutionX 4.5 works?
I want to remain in the android 10 system that drain less battery and I see more smooth in performance, thanks.
Format your data partition
Formatted 1000 times, no way to boot LOS 17.1 again...
I tried this also, but no luck https://forum.xda-developers.com/t/fix-for-recovery-loop-twrp-etc-no-computer-needed.2873386/
SOLVED!!!
I always tried to format the partitions via recovery but (who knows why) this phone likes more from fastboot.
My obvious question could be "what is the format command in recovery for, if it doesn't work well? ", but let's go further...
So I backup all, reboot in fastloop and give the commands:
fastloop erase system
fastloop erase userdata
fastloop erase boot
fastboot erase recovery
fastboot format system
fastboot format userdata
I downloaded the new version to be sure
twrp-3.5.1_9-0-dipper.img
fastboot flash recovery twrp-3.5.1_9-0-dipper.img
fastboot boot twrp-3.5.1_9-0-dipper.img
adb start-server
adb sideload "name of lineage OS image and gapps"
BOOM, worked at first try.
ANOTHER IMPORTANT THING I NOTICED:
I don't know why even about this, I have 2 laptops with the exactly same configurations (2 SSDs cloned + driver update of course).
On Intel one, always OK.
Every time I try to use adb or fastboot commands with the AMD laptop, it takes me half... for example gived me unknown errors at the "fastloop erase system" command and the phone rebooted.
This is not the first time I notice to have troubles unlocking android devices with AMD PCs; the same happened to me with a S4 years ago through my old AMD desktop, no way to solve trying 1000 drivers versions and cofigurations.
So, I recommend to who have these problems, use an INTEL machine to work with fastboot.
Related
Hello All,
I was on Stock MIUI 9 Global ROM (rooted with TWRP 3.2.1.0 OFFICAL) which was getting slower by the day. One day all of a sudden, I started getting ads on my lockscreen which was the final straw. So I installed dot OS 7.1.1 for Mi Max2. When setting up dot OS, I setup the lock screen pattern without knowing that it was turning ENCRYPTION ON.
I got bad sound in dot OS 7.1.1 ROM (tinny sound with echo), I was not happy so I did a full wipe of all partitions EXCEPT internal storage. and then installed Xiaomi EU ROM 9.5 Stable.
The issue:
TWRP and Normal Android BootUp on Xioami EU asks me for entering pattern every single boot. It asks for: Enter pattern to start android. On TWRP recovery boot: TWRP asks me to enter pattern and then decrypts phone.
How can I DISABLE Encryption without doing a full wipe + format of data partion?
Just to confirm: I remember the pattern, my phone works perfectly in Xiaomi EU ROM, I just want to disable encryption without doing a full WIPE+FORMAT+SETUP of my phone.
Thanks.
sk280 said:
Hello All,
I was on Stock MIUI 9 Global ROM (rooted with TWRP 3.2.1.0 OFFICAL) which was getting slower by the day. One day all of a sudden, I started getting ads on my lockscreen which was the final straw. So I installed dot OS 7.1.1 for Mi Max2. When setting up dot OS, I setup the lock screen pattern without knowing that it was turning ENCRYPTION ON.
I got bad sound in dot OS 7.1.1 ROM (tinny sound with echo), I was not happy so I did a full wipe of all partitions EXCEPT internal storage. and then installed Xiaomi EU ROM 9.5 Stable.
The issue:
TWRP and Normal Android BootUp on Xioami EU asks me for entering pattern every single boot. It asks for: Enter pattern to start android. On TWRP recovery boot: TWRP asks me to enter pattern and then decrypts phone.
How can I DISABLE Encryption without doing a full wipe + format of data partion?
Just to confirm: I remember the pattern, my phone works perfectly in Xiaomi EU ROM, I just want to disable encryption without doing a full WIPE+FORMAT+SETUP of my phone.
Thanks.
Click to expand...
Click to collapse
Honestly I didn't find any OTHER WAY without a Full Wipe!
TBH.. I'm kinda glad that someone else had this scenario.. :cyclops:
(Cause I had)
Here's how I overcame this issue..
1. First I Cleared everything on my phone using twrp and wiped everything **literally everything**
2. Then using fastboot on my PC I did this:
fastboot boot -recovery-( fastboot boot twrp.img)
[This will temporarily boot into TWRP]
3. And I wiped everything all over again
[Don't ask me why I did that but it worked for me]:silly:
4. Installed TWRP again using fastboot
5. Flashed a new ROM!
Hope this helps you!
Cheers mate!:fingers-crossed:
Thanks for that. I do NOT want to do a full wipe as I don't have access to Windows PC to do this (I'm on a MAC and don't have adb and drivers for MI MAX2).
TBH, the pattern is very annoying especially on restart as I have to wait for it and then wait some more for restart.
Worse case scenario, I'll a full backup of /data internal storage to an SD CARD, WIPE ALL Parittions and try again.
I'm almost tempted to reinstall dotOS and then NOT select a pattern when setting it up, you think that'll work?
the_phantom_97 said:
Honestly I didn't find any OTHER WAY without a Full Wipe!
TBH.. I'm kinda glad that someone else had this scenario.. :cyclops:
(Cause I had)
Here's how I overcame this issue..
1. First I Cleared everything on my phone using twrp and wiped everything **literally everything**
2. Then using fastboot on my PC I did this:
fastboot boot -recovery-( fastboot boot twrp.img)
[This will temporarily boot into TWRP]
3. And I wiped everything all over again
[Don't ask me why I did that but it worked for me]:silly:
4. Installed TWRP again using fastboot
5. Flashed a new ROM!
Hope this helps you!
Cheers mate!:fingers-crossed:
Click to expand...
Click to collapse
the_phantom_97 said:
Honestly I didn't find any OTHER WAY without a Full Wipe!
TBH.. I'm kinda glad that someone else had this scenario.. :cyclops:
(Cause I had)
Here's how I overcame this issue..
1. First I Cleared everything on my phone using twrp and wiped everything **literally everything**
2. Then using fastboot on my PC I did this:
fastboot boot -recovery-( fastboot boot twrp.img)
[This will temporarily boot into TWRP]
3. And I wiped everything all over again
[Don't ask me why I did that but it worked for me]:silly:
4. Installed TWRP again using fastboot
5. Flashed a new ROM!
Hope this helps you!
Cheers mate!:fingers-crossed:
Click to expand...
Click to collapse
Thanks a lot!
I was having a problem installing couple of ROMs with hanging on logo screen.
I was wiping everything and nothing was helping until I formatted data partition in twrp, it is not only wipe, it is format where you have to confirm writing 'yes' if you really want to.
Then everything started to work!
Thanks again!
Hi Guys
I tried an update to Mirza's ROM but after it caused more issues, I tried restoring from full Orangefox backup in recovery; only to find the phone stuck at Fastboot mode. It appeared strange, so I tried it again to end up with same fate. I tried installing Xiaomi.EU ROM, but after installation it got into a boot loop alternating between Recovery logo and MIUI startup logo. I got into fastboot again and flashed TWRP trying the same, but without joy. Tried another recovery and multiple versions of Xioami.EU ROM all with same fate. Finally got hold of an old fastboot ROM from Xioami.EU and flashed with MiFlash tool and it flashed successfully without issues. Assuming all was well, I tried flashing ROM via recovery which either gets stuck at MIUI logo or recovery. Boot loader in unlocked and decrypted. I tried flashing SHRP recovery, Magisk, wiping data etc as well to rule out any issues, but the problems remain.
Any ideas as to what's happening?
If I understood right, recovery ofox is working.
So reboot to it
Format data with yes
Reboot ofox
Flash ROM
Flash magisk recommend
Format data again with yes
Reboot system and give time to boot, could be more than some minutes but I think not more than 20
For those who might face similar issues.
According to Orangefox website, 'note that you should not restore a backup of the persist image, unless it proves absolutely necessary'. I may have checked it in recovery during restoration which probably destroyed the partition.
Fix:Installed TWRP via flashboot, formatted all data(not wiped) and installed ROM then formatted again and it booted.
Hi,
I have C11 RMX2185, unlocked bootloader, installed TWRP and then some roms (pixel experience, next stock android 11, next CipherOS-2.0-KNIGHT)
everything worked fine and I was preparing to try some other ROMS
But now I am unable to enter TWRP (I was, I flashed roms with TWRP before)
In fastboot I do fastboot reboot recovery and TWRP started to load (blue TWRP logo), and it blink and logo, blink - logo,.... forever
I tried to flash boot.img, flash TWRP again, tried another release of TWRP for RMX2185, flashing vbmeta, format userdata, ..... all kind of posibilities without any error but stil unable to run TWRP
I can boot into system (CipherOS-2.0), I can do things in fastboot, when it loops in starting TWRP it is able to react to adb reboot
I run out of ideas.
Thanks in advance for some kicks in the back
All,
I'm attempting to figure out whether something in my flashing process broke down for one Zenfone 8 in particular that results in an unusable LineageOS 18.1 OS. This one particular phone was in a fastboot cycle that would not load the LineageOS Recovery mode or OS until I flashed the `dtbo.img` file. That fixed the fastboot and I was able to then sideload the OS.
However, the OS comes up with a white screen and extreme unresponsiveness. It's unusable. Other phones whereby I followed the same process (but did NOT need to flash `dtbo.img`) are working just fine.
I've run through the flashing process multiple times on the problem phone w/ no luck. Any thoughts appreciated. Should I get the phone back to complete stock and try again?
Flashing Process
-------------------------------
1. Unlock tool APK, unlock, etc.
2. fastboot flash vendor_boot sake_vendor_boot.img
3. fastboot flash boot recovery.img
a. When in fastboot cycle, I then flash `dtbo.img`, but I've only done this on the problematic phone
4. Factory reset
5. Restart, Recovery Mode, Update via ADB
6. adb sideload lineage.zip
chingtastical said:
All,
I'm attempting to figure out whether something in my flashing process broke down for one Zenfone 8 in particular that results in an unusable LineageOS 18.1 OS. This one particular phone was in a fastboot cycle that would not load the LineageOS Recovery mode or OS until I flashed the `dtbo.img` file. That fixed the fastboot and I was able to then sideload the OS.
However, the OS comes up with a white screen and extreme unresponsiveness. It's unusable. Other phones whereby I followed the same process (but did NOT need to flash `dtbo.img`) are working just fine.
I've run through the flashing process multiple times on the problem phone w/ no luck. Any thoughts appreciated. Should I get the phone back to complete stock and try again?
Flashing Process
-------------------------------
1. Unlock tool APK, unlock, etc.
2. fastboot flash vendor_boot sake_vendor_boot.img
3. fastboot flash boot recovery.img
a. When in fastboot cycle, I then flash `dtbo.img`, but I've only done this on the problematic phone
4. Factory reset
5. Restart, Recovery Mode, Update via ADB
6. adb sideload lineage.zip
Click to expand...
Click to collapse
HI
Lineage OS 18.x is based on Android 11 as far as I know so I suggest to install the original ASUS Android 11 raw image and then reinstall the LineageOS using the install instructions from LineageOS.
The raw image for Android 11 on the ASUS Zenfone 8 is available on this Website:
https://www.asus.com/Content/Android-12-Beta/
in the section
How to opt-out and revert back to Android 11
at the end of the page
That's how I reinstall my development Zenfone 8 from 12 to 11 or vice versa.
regards
Bernd
Just wanted to thank you for the information you posted; the re-flash to stock download worked perfectly for what I needed.
Hello,
This won't work for some reason. I flash spesn_global_images_V13.0.5.0.SGKMIXM_20221020.0000.00_12.0_global with fastboot.
Then I boot TWRP with fastboot boot twrp.img. I then install xiaomi.eu_multi_HMNote11_V13.0.5.0.SGKMIXM_v13-12.zip in twrp.
But then it just keeps booting to recovery.
Did anybody try this or have tips?
Thanks.
I don't remember exactly what I did, but I think I flashed the fastboot version and then updated
Be sure to get the version of recovery for the android version you want to flash. Or that was the case back then.
Be sure to format /data as well, not just wipe
Okay, I got it working like this:
1. Flash xiaomi.eu_multi_HMNote11_V13.0.10.0.RGKMIXM_v13-11-fastboot
2. Fastboot boot into OrangeFox-R11.1_A12.1-Unofficial-spes
3. Push xiaomi.eu_multi_HMNote11_V13.0.5.0.SGKMIXM_v13-12.zip via adb to /data/
4. reboot to bootloader
5. fastboot boot into twrp-3.6.1_11-0-spes
6. install xiaomi.eu_multi_HMNote11_V13.0.5.0.SGKMIXM_v13-12.zip and format data
7. reboot
Very annoying it doesn't work by just flashing the xiaomi eu zip on anything.
Strange, I got mine working first time flashing using TWRP 3.6.1
A bit of a messy procedure is required because of several technical changes from Android 11 to Android 12.
Plus, Xiaomi's messy encryption makes things worse.
Use TWRP 3.7.0