I got my device stuck in a bootloop whilst trying to root it. Recovery mode doesn't work. In the magisk I clicked install and set the file to boot.img. I sent the file I got from magisk to my PC and I used in cmd fastboot flash boot "the name of the file I got from magisk" and then fastboot reboot and that's when it got stuck in a bootloop.
Device name: Alcatel Pixi 3 (10) 9010X
I have used the boot.img file from the folder I attached.
This is the source where I got the file: https://alcatelfirmware.com/alcatel-onetouch-pixi-3-9010x (It's the first file from this site)
I think I can get it into fastboot mode if that helps.
Does your device have a vbmeta partition?
Related
I am using TWRP to install a flash (Because the Phone is getting stuck a HTC's logo) and after I finished flashing it, I reboot and it gets me back to TWRP so it's not working. What to do?
How did you install TWRP on your device? it must be Fastboot-ADB folder where you have already copied the recovery .img file. Open the command window in this folder by Shift and Right click combo and type the following command with the part of command of your recovery image file:
fastboot flash recovery(yourRecoveryFileName) and then type .img at the end of the command – hit Enter
The process of installing of your chosen custom recovery will now start on HTC One Max.
Ok, I am new to this. My op3 was on oxygen os 5.0.8. I first unlocked my bootloader, then flashed twrp, and through twrp i have flashed Magisk 18.1. Then I cleared data, dalvik and cache and started a reboot. I am now in a bootloop, tried to uninstall Magisk through the uninstaller, but still i am in a bootloop. So please help me with the bootloop or guide me on how to get back to stock rom and recovery.
N1mbus17 said:
Ok, I am new to this. My op3 was on oxygen os 5.0.8.
Click to expand...
Click to collapse
Hello, have you tried flashing the stock boot image from fastboot?
I donno how to flash stock boot image with fastboot, can i flash that img with twrp?
N1mbus17 said:
I donno how to flash stock boot image with fastboot, can i flash that img with twrp?
Click to expand...
Click to collapse
What happens when you place your stock boot image somewhere you can access from TWRP and try?
If you want to try fastboot method:
Download the version of OxygenOS you’re currently on
Extract the contents of the ZIP file from Step 1
Copy/move the boot.img file to the same directory as your ADB/Fastboot tools
Launch a Command Prompt, Terminal or PowerShell in that directory
Boot the OnePlus 3 into Fastboot Mode
Connect the OnePlus 3 to the PC with a USB cable
Type the following into the Command Prompt, Terminal or PowerShell. . .
Code:
fastboot flash boot boot.img
. . .then press Enter on the keyboard
Wait for the boot IMG file to be sent and written
Then press the Power button on the OnePlus 3 to reboot back into Android
adapted from https://www.androidexplained.com/oneplus-5-stock-kernel/
united_we_stand said:
What happens when you place your stock boot image somewhere you can access from TWRP and try?
If you want to try fastboot method:
Download the version of OxygenOS you’re currently on
Extract the contents of the ZIP file from Step 1
Copy/move the boot.img file to the same directory as your ADB/Fastboot tools
Launch a Command Prompt, Terminal or PowerShell in that directory
Boot the OnePlus 3 into Fastboot Mode
Connect the OnePlus 3 to the PC with a USB cable
Type the following into the Command Prompt, Terminal or PowerShell. . .
Code:
fastboot flash boot boot.img
. . .then press Enter on the keyboard
Wait for the boot IMG file to be sent and written
Then press the Power button on the OnePlus 3 to reboot back into Android
adapted from Link
Click to expand...
Click to collapse
Ok I will try this method, but what will happen to twrp if I flash through fastboot, will it get removed and replaced by stock recovery?
N1mbus17 said:
Ok I will try this method, but what will happen to twrp if I flash through fastboot, will it get removed and replaced by stock recovery?
Click to expand...
Click to collapse
Hi! in the following command
Code:
fastboot flash boot boot.img
fastboot is the tool
flash is the operation
boot is the destination partition
and boot.img is the source
so to answer your question, TWRP should remain unaffected, as it should reside on your recovery partition
united_we_stand said:
Hi! in the following command
Code:
fastboot flash boot boot.img
fastboot is the tool
flash is the operation
boot is the destination partition
and boot.img is the source
so to answer your question, TWRP should remain unaffected, as it should reside on your recovery partition
Click to expand...
Click to collapse
Ok i did a wipe on cache, dalvik and system, flashed the official os zip file with TWRP and i am still stuck in a bootloop. I haven't tried your method yet where you flash the boot.img as it's just 15mb while the zip file is 1.5gb. What am i missing here? Is my TWRP recovery installing the os zip file correctly? I am stuck.
This is what i have done till now:
Unlocked my bootloader
Flashed official TWRP (twrp-3.2.3-1)
Then cleared data, cache, dalvik and flashed Magisk
Rebooted and got stuck in a bootloop
Used magisk uninstaller but didn't work
Downloaded official Oxygen OS 5.0.8 and then went to twrp, wiped dalvik, cache, data, system and then flashed the zip file.
Rebooted and still stuck in a bootloop
I am now scared that this phone won't startup. Please provide a solution.
Ok, i have followed the mega unbrick guide for oneplus 3 and it has finally come out of the bootloop, it's now updating to the latest oxygen os. Sadly i donno what went wrong the 1st time i tried to root with Magisk, maybe the oreo on the op3 doesn't support magisk. If it's possible can you guide me into rooting the phone with magisk, as most of the tutorials are old and for marshmallow rom and recovery. Thanks.
Why i can't flash TWRP even thought I unlock bootloader
When i boot into recovery it's say "No such file in directory"
I used to try rename recovery.img to twrp.img and run command on powershell
I was successfully to flash TWRP when i rename recovery to twrp. When i flash it's has error need password and i fix it by wide data
When i go to recovery mode, it's go to original recovery and i can't flash again
Hello everyone, I have a problem, maybe someone will be able to assist me.
I have a phone Samsung Galaxy A20e (SM-A202F) with unlocked bootloader (Yes, in developer settings it says "Bootloader already unlocked" and the "OEM unlocking" option is grayed out).
I am trying to root the device and for that I have modified boot.img that I repacked with Magisk Manager, and an empty vbmeta.img that makes the device ignore verify. So far no guides I found worked. When i try to flash modified AP (with the modified boot.img inside) with Odin (including the rest of the files) it flashes successfully but I get "Error verifying vbmeta image" on the device screen and device is stuck on Download mode. If I re-flash unmodified AP with Odin, it works and device is like new.
All the small details aside, the problem is that I can't boot the device into fastboot mode. Whenever I do "adb reboot fastboot" it always boots into Download mode and fastboot commands don't work. Same goes with stock recovery, when I click "Reboot to bootloader", device boots into Download mode.
On the Magisk website I read something about "VaultKeeper" but I was sure i connected to Wi-Fi during setup and then enabled Developer mode. Link What I might be missing here?
tomasxp said:
Hello everyone, I have a problem, maybe someone will be able to assist me.
I have a phone Samsung Galaxy A20e (SM-A202F) with unlocked bootloader (Yes, in developer settings it says "Bootloader already unlocked" and the "OEM unlocking" option is grayed out).
I am trying to root the device and for that I have modified boot.img that I repacked with Magisk Manager, and an empty vbmeta.img that makes the device ignore verify. So far no guides I found worked. When i try to flash modified AP (with the modified boot.img inside) with Odin (including the rest of the files) it flashes successfully but I get "Error verifying vbmeta image" on the device screen and device is stuck on Download mode. If I re-flash unmodified AP with Odin, it works and device is like new.
All the small details aside, the problem is that I can't boot the device into fastboot mode. Whenever I do "adb reboot fastboot" it always boots into Download mode and fastboot commands don't work. Same goes with stock recovery, when I click "Reboot to bootloader", device boots into Download mode.
On the Magisk website I read something about "VaultKeeper" but I was sure i connected to Wi-Fi during setup and then enabled Developer mode. Link What I might be missing here?
Click to expand...
Click to collapse
Samsung don't support fastboot as Odin mode is what is used. You'll need to edit the fstab under /vender/etc.. and no you can't replace it with fastboot because you'll hard brick the device
Unfortunately I'm unsure if what's going on so you may not be able to root your device
TheExploitedOne said:
Samsung don't support fastboot as Odin mode is what is used. You'll need to edit the fstab under /vender/etc.. and no you can't replace it with fastboot because you'll hard brick the device
Unfortunately I'm unsure if what's going on so you may not be able to root your device
Click to expand...
Click to collapse
Thank you, I didn't know new Samsung devices don't support fastboot (or at least this one specifically).
On the other hand, when you said it, I tried other thing. I repacked AP image with Magisk modified boot.img and empty vbmeta.img I had from other tutorial and after flashing with Odin and factory resetting it stopped showing the boot error and booted the Android up. Long 1st boot tho, about 6 minutes. So far the device appears to work fine, will update if I manage to complete the root process.
EDIT1: The phone appears to be working with patched boot.img and vbmeta.img but Magisk can't detect that boot.img is pached. It only gives me the option to download zip (which I can't install because I don't have TWRP installed) and patch the boot.img again. Well atleast we are getting somewhere with this, I'll try to figure it out later.
EDIT2: I successfully rooted the phone. I had once again to extract the modified boot.img from the AP, modify it the second time with Magisk. Then I put it back into the AP file, deleting all other images, leaving only boot.img and META-DATA folder. Flashed it through Odin once again and this time Magisk waited 30s at launch and showed that everything is ok. Root checker is also showing that device is rooted as superuser asks for permissions.
tomasxp said:
Thank you, I didn't know new Samsung devices don't support fastboot (or at least this one specifically).
On the other hand, when you said it, I tried other thing. I repacked AP image with Magisk modified boot.img and empty vbmeta.img I had from other tutorial and after flashing with Odin and factory resetting it stopped showing the boot error and booted the Android up. Long 1st boot tho, about 6 minutes. So far the device appears to work fine, will update if I manage to complete the root process.
EDIT1: The phone appears to be working with patched boot.img and vbmeta.img but Magisk can't detect that boot.img is pached. It only gives me the option to download zip (which I can't install because I don't have TWRP installed) and patch the boot.img again. Well atleast we are getting somewhere with this, I'll try to figure it out later.
EDIT2: I successfully rooted the phone. I had once again to extract the modified boot.img from the AP, modify it the second time with Magisk. Then I put it back into the AP file, deleting all other images, leaving only boot.img and META-DATA folder. Flashed it through Odin once again and this time Magisk waited 30s at launch and showed that everything is ok. Root checker is also showing that device is rooted as superuser asks for permissions.
Click to expand...
Click to collapse
That's good to hear that root was successful!
I'm having a hard time flashing the boot.img for the N10. I have the T-Mobile version BE2028. I got the latest Magisk patched boot. img from Andreas's rooting guide. I have the phones boot loader unlocked, network unlocked with automatic updates disabled and USB debugging enabled. Every time I try to flash the boot image I get the message Permission Denied. I have tried running the commands as administrator with no luck. I run the commands adb devices, fastboot.exe boot magisk_patched.img . I have also tried the commands; fastboot boot magisk_patched.img and fastboot flash boot magisk_patched.img . I extracted the patched boot.img file, renamed it magisk_patched.img, put that into the platform tools folder, and put a copy onto my phone. I have Magisk installed on my phone, but not fully installed. I use windows 10, any help, thoughts, ideas, hints and tips would be very appreciated.