Hi there,
I ****ed up and I'm now stuck in bootloop with no access to a computer and was wondering if I could do anything to solve my issue.
I've been testing blu spark kernel for months and wanted to go back to stock kernel.
I flashed my backup from FKM (made it with FKM too) and now I'm in bootloop.
My backup was from january build and my phone has been updated to february build since. Is it the reason of the bootloop ?
Anyway, I'm in a bootloop now and I only have an other rooted Pixel 6.
Can I do anything with it ?
I tried Android Flash Tool from Google within Chrome but the download of the rom is always stucked at some point.
I tried magisk adb module but I'm afraid it's not up to date as I'm still in fastboot after I flashed the bootloader and update the image.
Any ideas ?
First try to turn off your phone and then reboot to bootloader. Download factory image and launch flash-all.bat.
Sorry for your datas.
I haven't been able to launch flash-all.sh with termux with the second Pixel 6 I have as the fastboot version from the magisk module is too old.
I don't have a computer to do it.
bobby8921 said:
I haven't been able to launch flash-all.sh with termux with the second Pixel 6 I have as the fastboot version from the magisk module is too old.
I don't have a computer to do it.
Click to expand...
Click to collapse
Get a computer, or at least borrow one so you can restore your device using Google's flash tool. You're not fixing your bootloop without one.
Related
Hello!
This is my first post. I've searched for hours. Visited over 200 sites and forums tried multiple things installed all available android tools you can find online and i am seriously stuck.
Setup before problem : One Plus X - Cm13 - Version 2016 - Oct - 10. This is updated from the cyanogen website and its treated as the stable version.
Downloaded the latest version which is the 15th and got stuck at bootloop. After some searching i discovered that i had to updated my bootloader as it was the same since November 2015. In the website that i got the new version i was also given the new TWRP version 3.0.2 . So i went into my recovery flashed the new bootloader , then the TWRP , then the new ROM. Mobile boots up shows completly empty fresh install CM 13 without gapps or any of my previously installed programs. Everything is still in the storage. All installation folders from the various programms i had.
My recovery mode refuses to Boot. It just stays on the one plus logo. Tried TWRP manager from the OS but the old version 2.8.7.0 refuses to be unistalled. Adb command lines : I've been trying on windows 10 , 8 , 7 with the appropriate drivers and the only thing that i can make the phone do is go to either FASTBOOT or normal boot. Flashed the TWRP multiple times and no changes what so ever. I can make the mobile show up with ADB device, Fastboot device it shows success and when i try to boot into recovery it just gets stuck. I also got the MTP package from Windows. Basically i bricked my phone within a glass. OS works but Recovery not. Fastboot is supposignly working but i see no changes.
Thank you in advance!
Install original stock recovery then 2.2.3. If you want to use ashwins cm13,cm14 from here on out and a couple other ROMs required updated bootloader. You achieve this by flashing 3.1.3 Oxygen OS. After you updated your bootloader only twrp you can use is blusparks latest v41 or Nichets twrp. On a side note 2.8.7 twrp is old 3.0.2 is latest.
Exodusche said:
Install original stock recovery then 2.2.3. If you want to use ashwins cm13,cm14 from here on out and a couple other ROMs required updated bootloader. You achieve this by flashing 3.1.3 Oxygen OS. After you updated your bootloader only twrp you can use is blusparks latest v41 or Nichets twrp. On a side note 2.8.7 twrp is old 3.0.2 is latest.
Click to expand...
Click to collapse
Thank you i managed yesterday from a program to flash twrp as kernel and was rebooted into a working twrp and fixed everything from there.
hi
i just update my mi a3 from June to October update (first updated to September and then notify me immediately for October update). now every time i turn WiFi or hotspot on it turn back off.
something that maybe cause the problem:
i use magisk tutorial for updating and then i realize it was bad decision and twrp is gone. installed twrp (via fastboot then twrp.zip) and magisk(via twrp) again and then face the problem. i don't check that it was there before reinstalling twrp or not.
how can i fix it?
update: it seems like twrp not working with October ota. i install alogcat and searched error. it lead me to this threat where twrp made this problem with same errors.
i reboot to twrp and now i stock in it. rebooting to system take me back to twrp. decryption isn't working anymore(no prompet for pattern).
i just can reboot to fastboot!!!
i managed to download 10.3.8.0 pfqmixm and extract images from it. flash all of them in slot a and b via fastboot. then flash twrp and it decrypt my data. phone boot to system now but wifi and hotspot problem exist. if i flash stock boot.img phone show a page that it coudn't load system and maybe my data was corrupted. it give me to option: 1. try again (reboot) 2. factory data reset.
any suggestion?
ghasemi.hussein said:
hi
i just update my mi a3 from June to October update (first updated to September and then notify me immediately for October update). now every time i turn WiFi or hotspot on it turn back off.
something that maybe cause the problem:
i use magisk tutorial for updating and then i realize it was bad decision and twrp is gone. installed twrp (via fastboot then twrp.zip) and magisk(via twrp) again and then face the problem. i don't check that it was there before reinstalling twrp or not.
how can i fix it?
update: it seems like twrp not working with October ota. i install alogcat and searched error. it lead me to this threat where twrp made this problem with same errors.
i reboot to twrp and now i stock in it. rebooting to system take me back to twrp. decryption isn't working anymore(no prompet for pattern).
i just can reboot to fastboot!!!
Click to expand...
Click to collapse
But it's working for me
At end i clean install v10.3.8.0. all data lost. it socks really.
again after installin twrp wifi and hotspot breaked.
Hey guys, so I had the forced update to Android 10 about 1 month ago, and I lost root, which I didn't found about until I tried installing something today.
As this isn't my first time losing root I just followed the steps I always do on this guide (https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509) and I managed to successfully install TWRP, but the phone is now stuck on the orange MI logo when I reboot to system. Someone pls help!
Edit: For anyone curious, I just used the Fix Recovery Bootloop inside TWRP and it worked! I still don't have root tho...
Edit 2: After trying to flash Magisk installer for the second time I determined it to be the problem. Can anyone help me with that?
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
garylawwd said:
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
Click to expand...
Click to collapse
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP
garylawwd said:
Use the magisk patched boot.img from here that corresponds with your firmware version and follow to guide to flash in fastboot https://forum.xda-developers.com/mi-a3/how-to/guide-how-to-root-mi-a3-magisk-t3958509/page40
Click to expand...
Click to collapse
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP.
Edit: I just flashed TWRP on flashboot and I was able to solve this. I can't still fond what's the issue with magisk tho.
SirAerion said:
Just tried that, the phone is stuck again on the orange MI logo and now when I try to boot into TWRP it shows an android laying down with the message "No command" PLEASE HELP.
Edit: I just flashed TWRP on flashboot and I was able to solve this. I can't still fond what's the issue with magisk tho.
Click to expand...
Click to collapse
What Magisk modules do you have installed? They might be preventing the phone to boot up.
_mysiak_ said:
What Magisk modules do you have installed? They might be preventing the phone to boot up.
Click to expand...
Click to collapse
Afaik the only module I HAD installed before the forced update was Smali patcher for POGO. But I can't check the modules now because the option isn't there in the manager.
SirAerion said:
Afaik the only module I HAD installed before the forced update was Smali patcher for POGO. But I can't check the modules now because the option isn't there in the manager.
Click to expand...
Click to collapse
Well, the module "only" patches framework from the phone, so you're trying to boot Android 10 system with Android 9 framework. It doesn't get uninstalled automatically even if you remove Magisk from boot image.
Either flash Magisk uninstaller from TWRP or flash correct patched boot file, connect phone to the PC, type in this command and reboot the phone.
adb wait-for-device shell magisk --remove-modules
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Yajirobai said:
Hi.
I´m interested. I´m not able to root the MI 8A MIUI 11 global 11.0.2.0 QCPMIXM. I achieved install TWRP . But I can´t install MAGISK . It don´t show me any error, but it isn´t installed. I ´ve tried many versions 20.0, 20.1, 20.2, 20.3 20.4 21.0 and 21.1. neither of them are successfull with TWRP.
Neither with magisk manager apk 7.5.1 and above. These are installed but then I download magisk 20.4 version, but this isn´t installed.
how did you it? please.
Click to expand...
Click to collapse
Your bootloader needs to be unlocked and USB debugging enabled first of course. TWRP Recovery should be installed.
To do this, you need the adb and fastboot binaries installed on a PC/Laptop. I use Ubuntu and installing these is trivial via apt package manager:
Debian based:
Code:
sudo apt install adb fastboot
RedHat based:
Code:
yum install adb fastboot
If you use Windows, the install and use of these binaries is a little different. I don't use Windows so you'll have to do a quick search to find out how to install and use these binaries. The commands listed below will work no matter what OS you use.
Connect your phone to your PC/Laptop via it's USB cable and reboot it to TWRP Recovery:
Power off the phone, then power on while holding the volume up button until you see the TWRP logo. Log into TWRP to decrypt.
Next, you need to pull the current boot.img from your ROM to patch it for root access:
Code:
adb shell dd if=/dev/block/by-name/boot of=/sdcard/boot.img
There should be a boot.img on your phone's internal storage, copy it to your PC/Laptop. From TWRP, reboot your phone to fastboot.
Now, we'll use this most excellent, free resource to patch the boot.img file which will give root access:
https://patcher.yaalex.xyz/
Check the 'Include Magisk' checkbox on the website before submitting image.
Important: After you upload your boot.img file to the website, be patient. This could take 10 minutes or more to complete, just wait until you get a prompt to download the patched image. You will be provided a patched_boot.img file from the website once it is finished.
Finally, all you need to do is flash the patched_boot.img to your phone:
Code:
fastboot flash boot patched_boot.img
Boot your phone to the ROM:
Code:
fastboot reboot
Install Magisk Manager if you haven't already, and enable Magisk Hide in the settings. Magisk Manager should report root access is available and SafetyNet test should pass.
I typed all this up from memory so if you run into trouble or are confused by any step, let me know and I will gladly clarify/fix the steps.
I hope this helps others achieve root on this phone. Let me know how it goes and happy de-bloating!
Rollback instructions:
If your phone fails to boot don't panic. You can restore your original boot.img if needed to regain access. Reboot your phone to fastboot:
Boot phone while holding the down volume button until you see the fastboot logo.
Next, flash the original boot.img to the boot partition:
Code:
fastboot flash boot boot.img
Now just reboot to ROM and all should be restored:
Code:
fastboot reboot
stvmnn said:
Hi all, my first post here.
I recently bought this phone thinking it was customizable. Every tutorial I have tried has failed and required a re-flash to stock ROM using MIFlash.
I have tried custom ROMs, GSI ROMs, 64 bit, 32 bit, etc. I tried using Magisk 21.0 to root, it appears to work, but I believe the boot.img patching isn't currently working on this particular phone.
Most tutorials I have tried are very simple and use TWRP to flash the OS img file, then reboot and enjoy. Some suggest flashing vbmeta.img to prevent boot loop, but, boot loop happens anyway. I have TWRP installed and working, so far, that is all I have had success with.
Can this phone still be customized at all?
Update: I achieved root on the stock ROM. If anyone is interested I'll post the exact instructions.
Click to expand...
Click to collapse
Iirc redmi 8a is an ab device, and yes this device is as customisable as any other Qualcomm. What gsi image are you flashing?
Actually he is not way off ..... i am NOT able to find a Custom Non MIUI ROM with full VoLTE support. VoLTE fix for GSI's ( if at all it worked ! ) does not work for Havoc. twrp root is all good. I want a NON MIUI ROM that can regional variants ( Europe and Asia ) and supports VoLTE
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
You have to be decrypted or flash DMverity for A12. I assume You mean Magisk 24.1 the current version is 24.3
Hi. This is what I did:
I downloaded and installed original firmware through fastboot (fastboot was still on).
I also installed original recovery through fastboot.
After that my oneplus 5t was in stock condition, apart from the bootloader, which was unlocked.
After that I managed to install TWRP through fastboot, and then lineage 19.
The thing is that TWRP doesn't support lineage 19, for one reason or another. Or it could be the other way around (lineage 19 doesn't support TWRP). In any case I had a phone which would only go in fastboot mode.
At least I knew what to do, as I did it already: reinstall stock firmware and recovery.
Long story short, I installed LOS recovery and lineage 19, and everything works fine.
Thanks everyone, and especially thaidroid, for the support.
Have a nice day.
miclombardo said:
Good evening dear members, I ask for your kind advice, as I have done something wrong to my Oneplus 5t.
I upgraded my Oneplus 5t with "lineage for microG" 19.1 (from lineage 18).
I had installed TWRP 3.5.0_9 (phone encrypted).
It booted fine the first time into system.
The problem arose after I tried to install Magisk 21.4 from TWRP.
Now the phone only boots in recovery, but it doesn't enter TWRP's menu. It stays on the first TWRP screen (where it shows the version number).
The good thing (I hope) is that I can enter fastboot mode.
I tried flashing TWRP again from fastboot to no avail.
I tried flashing boot.img from fastboot (taken from the original firmware), but still no luck.
Is there a way to install the original firmware from fastboot?
I think starting from scratch would be a step into the right direction.
Please give any suggestion which I fill follow to the letter.
Thank you, thank you, thank you!
Click to expand...
Click to collapse
Its not working cus you need to format data in recovery and then reboot it.
kirknado18 said:
Its not working cus you need to format data in recovery and then reboot it.
Click to expand...
Click to collapse
It wont boot cus your encrypted formatting data will allow op5t to boot.
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
paradoxiumwind said:
latest lineage + magisk = stuck on boot logo, I tried an older version of lineage + magisk (known to work), same thing.. what did I do?
Click to expand...
Click to collapse
What recovery are you on? TWRP?
I use the one posted alongside each version: https://download.lineageos.org/dumpling
can you help?
I need to root so I can titanium backup everything. but I can't root. I suspect I might need to fully format and wipe and start again, I tried wiping data and doing a fresh install, but after sideloading magisk it just fails to boot every time now.
Does it boot regularly BEFORE installing magisk? I am trying to define the source of the problem.
I have installed lineage 19 and magisk, and I confirm you that it's possible
Yes. It boots fine if I just install lineage then nevermindthegapps. problem only occurs if I flash magisk. I tried installing the .apk and patching the .boot image manually in it and then fastboot flashing that, but same thing.
oh - one possible thing that it may be - is that I had a couple of modules loaded (I think a gcam fix mod and something similar) in magisk, and I read somewhere about people having them stuck 'installed' despite demoving all traces of magisk app. whether that is the problem I don't know.
This is very strange. That's what I did:
Sideload lineage recovery
Sideload lineage 19
Download magisk apk
Patched boot image from lineage 19.zip
Sideload the patched boot image
And that's it it all worked
May I suggest you to start all over again?
is wiping system data sufficient or do I need to format it? I'd rather not lose my appdata- but I can't rescue it without root / titanium backup :/
Try first without formatting, and see how it goes
I wiped system/cache, installed lineage-19.1-20220719-nightly-dumpling-signed.zip / mindthegapps, phone booted up fine - rebooted fine.
ok, good. Now download latest magisk app and patch the boot img.
do I click patch vbmeta in image?
Yes.
First extract the file called boot.img from lineage.zip you just installed.
Then in magisk select "patch vbmeta in image".
Magisk should produce a file named something like " magisk_pached-24300_f41h3.img".
That patched file should be sideloaded.
Installation is explained really well by topjohnwu
it wouldn't flash without selecting vbmeta, so tried with, flashed it, now i'm sitting looking at the boot logo.