After some time of sitting on ColorOS 6.1 I decided it was time to move to a Custom Rom.
I watched some tutorials and managed to unlock my bootloader and flash twrp recovery version 3.4.
Following the steps from the Evolution X guide I wiped cache/system/vendor/data/internal storage. Then copied over the rom via the "mount" option, after successfully copying the rom I went to install and flashed the rom with no issues. However, once I go to reboot I boot strait into fastboot mode (which keeps restarting until I select 'restart bootloader').
I have tried other Roms such as Covus and the pixel experience rom that was posted here and have the same issue.
Finally I tried 'fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img' with vbmeta provided in root tutorial...still nothing
As it stands I can still boot into twrp without issue so I wouldn't call the device bricked just a victim of (likely) user error.
Oh and I also tried different versions of twrp...3.3-19 and that also did not work.
Is it possible that trying to flash to an android 10 rom from android 9 is the issue?
Please let me know if you guys or girls have any ideas because I can't think of anything else
Finally thank you in advance all those who respond!
Edit: So uhhh yeah y'all make sure you update to android 10 before trying to flash an android 10 rom lol
update: I followed this guide if anyone has issues and booted successfully after a couple attempts into RealmeUI
https://forum.xda-developers.com/realme-x2/help/how-to-flash-q-firmware-based-roms-t4115987
Related
So I recently updated my op3 to 3.5.2 Community Build of oxygen OS. It was working well with a few changes from the official builds but a little time passed and the 3.5.3 Community Build was released. Of course I wanted to update so I downloaded it and tried to update but when it booted into the recovery it froze on the logo. So I downloaded the update on the computer and flashed twrp to the recovery and booted into the recovery and it froze again. Currently i have no Recovery and no access to adb.
*When trying to flash a recovery it says it was done successfully but freezes when trying to boot into it.
Normal OS booting is unaffected.
When executing the command "fastboot boot recovery.img", to boot into the recovery without flashing it i get "(remote dtb not found)"
When trying to manually update the OS through "fastboot zip Update.zip", I get "(remote: data too large)".
I also tried to do "fastboot erase recovery" before issuing the flash command.
*In trying to fix this i flashed the boot image of 3.5.3 onto the boot partition but nothing happened and now the phone reads as 3.5.3 on 3.5.2 firmware :crying:
I tried to use SkipSoft ToolKit,custom and official twrp, and recoveries such as CWM.
This would probably be better placed into the, ONEPLUS 3 ROMS, KERNELS, RECOVERIES, & OTHER DEVELOPMENT, section but I can not post there yet. If anyone can help me or find a mod that knows about this problem it would be much appreciated.
Found a Solution
http://forum.xda-developers.com/showpost.php?p=68691560&postcount=56
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Bijiont said:
Hello Everyone I am hoping there is a solution to this however I have been unable to find anything.
I flashed the latest OTA image via sideload and everything was fine until I tried to install TWRP. When trying to install the latest TWRP I could find ( 3.1.0-0RC2 ) my phone would then boot loop. I tried this process several times and each time after installing my phone would boot loop for 10 minutes until I forced it into fastboot, fast booted the TWRP image, and finally sideload the OTA once again.
I have seen a couple threads which I believe indicate that May update changed/broke something with the bootloader but I will be honest I
haven't read into it much.
This is on a Google version of the device with the bootloader unlocked. (failed to mention that).
Thanks in advance.
Click to expand...
Click to collapse
Please read the other Posts about this
Flash the bootloader from april.
****************************
Download last months 7.1.2 factory image.
Extract it and find "bootloader-marlin-xxxxblahblah.img".
Rename it to "bootloader.img" for simplicity's sake, then move it to the side.
:Flash-all" the latest factory image, after its done stay in fastboot.
Run "fastboot flash bootloader_a bootloader.img" from wherever you moved the file to
Disregard if "partition_a" isnt your primary, once the command is ran it will auto flash to the primary partition.
Boot and setup, reboot back to bootloader.
Boot and install twrp, then reboot to recovery.
Delete fstab.marlin in main directory, then flash preferred supersu (i use 2.79 sr3).
Reboot to system and your done. from here reboot to recovery or bootloader to flash your preferred kernel and mods.
Was able to get this all sorted out.
If anyone else happens to see this thread with the same issues and missed the April bootloader deal you can find a good overview Here
To get the April bootloader image which is something I have never loaded myself you need to download the Factory Image from April then extract it. Inside there you will see the bootloader image.
Hope this helps anyone else who didn't read far enough into this issue.
Hi, I flashed the FOTA Kernel with TWRP 2.8.7 onto my phone and inside TWRP I flashed the recovery with the 3.0.2 TWRP image (telling me "Successfully flashed")
But after rebooting I still have TWRP 2.8.7
Using windows command line and "fastboot flash recovery "TWRP.....img" I get this "FAILED" message.
What am I doing wrong?
I even flashed the phone back to stock and then followed these instructions but same result.
Is my phone broken or sth?
Hi H4NNE5, the Xperia M does not have a recovery partition. The TWRP recovery is included in the boot partition when flashing the kernel. Try to upgrade with the TWRP-Manager if your phone is rooted.
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
H4NNE5 said:
Hi Lightningsfire, Thanks for you answer.
Ok, that's weird because I read a lot of threads but none said anything like that. I'm more confused right now.
Anyhow the LineageOS is not properly working on my phone anyhow so I set it back to Stock Rom and check back in a few months if it improved
One more question:
So if I flash the whole software package the boot partition is overwritten then, right? Because I noticed that the Recovery was a different one, after I flashed the system.
Click to expand...
Click to collapse
Try this command
fastboot flash boot twrp_name.img
This is my first thread, I apologize for any mistakes or core aspects left out.
Intro/Formatting KeyBefore I start, I want to give a quick thanks to those contributing to these forums/threads, as it got me through my first custom ROM install ever! Knowing too much information is better than too little, and my want to not waste anyone's time, I'm going to share most of my experience installing the custom recovery and ROM. I will explain what I mean by custom recovery dying at The Dead Recovery. Italics will be used as commands entered in SDK tools. Bold will be used as outputs from cmd.
Phone SpecsPhone: Oneplus 7T HD1905 running Android 11 OOS
Custom Recovery: Chinese TWRP from this youtube video
Custom ROM: Derpfest R for hotdogb found here
My Install ProcessBesides needing to turning off driver signature reinforcement, the bootloader unlock was a normal process. Issues started occurring when I wanted to flash the custom recovery. fastboot reboot fastboot would not give me any feedback on the cmd prompt as it would say <waiting for devices> even though my phone was in fastbootd mode. After reading another thread, I hail married the flash using fastboot flash recovery twrp_best.img. All was great! My phone booted into TWRP, wiped the old stuff, flashed Derpfest, and rebooted. Derpfest works pretty well! (a little buggy but what do you expect from a beta build?).
The Dead RecoveryI notice the safety net with this ROM was broken, so I wanted to install Magisk to fix that issue (I wanted to use Gpay). I download the apk, do my renames for .zip and unintall.zip, and attempt to boot to recovery, but I just get a black screen! Using PWR+VOLUP allows me to reboot into the ROM just fine at least, so I didn't brick my phone. From here, I don't know what I should do to mitigate this issue. Here are my main concerns/questions.
Questions/Concerns1. Will flashing a new recovery allow me to still boot into my phone?
2. Should I use a different image?
3. Should I maybe use flashboot flash recovery_a twrp_best.img flashboot flash recovery_b twrp_best.img to flash the recovery?
Thank you in advance!
Hi everyone,
I'm writing this blog post to ask for some help from the XDA community. I have a Samsung A22 SM-A225F and I want to install a custom ROM on it, preferably an Android 12 GSI. However, I'm having some trouble getting it to boot properly.
I'm following the directions on this blog post which claims to have successfully installed Android 12 GSI on the same device. The steps I'm following are as follows:
Use Odin tool to flash the stock verified ROMs on my phone to start from zero.
Flash the (magisk patched.tar) file on AP
Boot to Android and set it up then install Magisk app to check for root (I'm doing this because it doesn't work otherwise)
Flash TWRP and run multidisabler then boot again to check if everything is working.
Finally flash the system.img, I'm not sure about vbmeta so I'm skipping it.
But I keep getting a bootloop no matter what I try, I've tried wiping cache and everything.
Weirdly enough I have flashed stock Android like two days ago except that it actually booted to set up but it didn't detect the network and kept mini rebooting from time to time.
I've tried the steps in that blog for Android 11 to flash crDroid but that also didn't work, I've also tried flashing crDroid even when following the steps for Android 12. Still no success.
I'm wondering if anyone has any idea what I'm doing wrong or what I can do to fix this issue. I've read some other guides on how to install custom ROMs and GSIs on Samsung devices without TWRP but they seem too complicated for me.
If anyone can help me out or point me in the right direction, I would really appreciate it. Thanks in advance! and i'll gladly provide any information required when i have time as it's currenlty night time
what twrp u using also where u flashing it using fastboot or from TWRP ?
i recommend u using fastboot to flash GSI