Related
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Install correct driveres or use another usb port. Device have to be adressed via "fastboot devices" or "adb devices".
It's probably a typing error ..Rename the twrp in whatever you want and then type " fastboot flash recovery " whatever you want".img
Rename file
Did you rename the file? You need to rename it before flashing.
IT WORKED
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I also experienced this thing this morning.
A simple unplug, re-plug solved for me
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Guiliang said:
Did you rename the file? You need to rename it before flashing.
Click to expand...
Click to collapse
no you don't.
Just type the first few letters and hit [tab]. Works on windows, linux, mac os and every other shell made within the last 40 years.
cerfeda.albert said:
I tried to install twrp on my OP3T but everytime i write "fastboot flash recovery trwp.img" it says "error: cannot load 'twrp.img'"
When I type "adb devices" my phone doesn't show up
I unlocked the bootloader
I activated USB debugging
I checked the OEM thing
I have put the twrp.img in the same Minimal ADB and Fastboot folder
What could it be?
Click to expand...
Click to collapse
The last parameter has to be the EXACT filename, that you are flashing, which is the TWRP image. It has to be in the same folder as your command prompt is or you need to include the path to the twrp file.
Try the last TWRP release, should work!
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
milanexplorer said:
Whenever i flash twrp through fastboot it just gets stuck on the twrp logo and doesn't go beyond it.
I've tried with 3.0.3.1, 3.0.3.0, 3.0.2.0 but still the same
can anyone help me with this?
Click to expand...
Click to collapse
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
After installing the twrp and then you type ... Fastboot boot twrp.img. Probably you are stuck on twrp splash screen...
Try to boot manually.to twrp by pressing power button and volume down button...Then you should be able to boot on twrp....
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
See this thread.
originalnabisco said:
Would like to express that I am also having the exact same issue. Any version of TWRP simply fails to load and stays on the TWRP logo.
I am on OxygenOS 3.5.3.
Anybody know a solution? I am currently running with no recovery now and I am quite worried.
Click to expand...
Click to collapse
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
jmazzamj said:
Did you try to fastboot TWRP after flashing it?
What I mean is, after you enter the command "fastboot flash recovery twrp.img", proceed with "fastboot boot twrp.img" and it will boot. Doing this you prevent Oxygen OS from overwriting TWRP. You should be able to boot normally after doing that.
Don't be worried and try to boot into recovery as described, that should work, if it doesn't I wonder if you flashed the right version of TWRP.
Try and let us know.
Click to expand...
Click to collapse
how long does it usually take? i've waited more than 10 minutes now.
Razoth said:
how long does it usually take? i've waited more than 10 minutes now.
Click to expand...
Click to collapse
Boot manually on it...
cultofluna said:
Boot manually on it...
Click to expand...
Click to collapse
apperantly i'm a retard, after i rebooted to recovery with hardware keys it shows the oneplus logo and i was like "this isnt twrp startup" and hardreset it... waiting boots into twrp just fine...
adb cannot locate file
cerfeda.albert said:
Everytime I was putting the phone into bootloader mode, the phone was already plugged in. Then I tried to put the phone to bootloader mode and THEN plugging it in my pc... and it worked ^^
Strange, right?
Click to expand...
Click to collapse
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
chizzwhizz said:
I'm having some difficulty getting past this step.
I've unlocked bootloader, enabled oem unlock and enabled usb debugging. I've added the PATH where my twrp.img file is located.
Whenever I input fastboot flash recovery twrp.img, it says error: cannot load twrp.img: no such file or directory.
I see the file in the correct location so i'm not sure what i'm doing wrong here.
Any ideas?
Click to expand...
Click to collapse
Reinstall your adb + fastboot drivers
Hello, I installed Havoc OS on my MI A2, but then an update was requested, I did the update, but when I rebooted the device, it did not start, I went into fastboot mode and I reinstalled the havoc. "androidOne" screen and nothing happens, now I have to enter fastboot mode with the command "fastboot boot twrp.img" and the error "failed to load / authentication boot image" appears, I tried flashing the rom stock using the MiFlash, and the cell phone persists with the same error, now my cell phone is with the bootloader locked and I do not know what to do
gmoura5010 said:
Hello, I installed Havoc OS on my MI A2, but then an update was requested, I did the update, but when I rebooted the device, it did not start, I went into fastboot mode and I reinstalled the havoc. "androidOne" screen and nothing happens, now I have to enter fastboot mode with the command "fastboot boot twrp.img" and the error "failed to load / authentication boot image" appears, I tried flashing the rom stock using the MiFlash, and the cell phone persists with the same error, now my cell phone is with the bootloader locked and I do not know what to do
Click to expand...
Click to collapse
Hi
Enter to fastboot and try this:
open a cmd
fastboot devices
fastboot -w
fastboot getvar current-slot ( you can see it a or b)
fasboot set_active b
Then
Try boot into twrp etc
Have luck pal !!
rodrimx4 said:
Hi
Enter to fastboot and try this:
open a cmd
fastboot devices
fastboot -w
fastboot getvar current-slot ( you can see it a or b)
fasboot set_active b
Then
Try boot into twrp etc
Have luck pal !!
Click to expand...
Click to collapse
Thanks, I was able to repair after unlocking the bootloader again and then unlocking the critical parts, so I flashed a stock rom from August 2018, however didn't block the bootloader again.
i was trying to install twrp in my rog 2 but while installing twrp from fastboot and adb i got stuck in fastboot mode and cannot boot into main OS PLEASE HELP ME
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse
Have the same problem. Did all that you say but keeps restarting.
ED_STUFF said:
Have the same problem. Did all that you say but keeps restarting.
Click to expand...
Click to collapse
I had this problem, and I had to download the RAW firmware files and run the "flashall.bat" file through fastboot.
ED_STUFF said:
Have the same problem. Did all that you say but keeps restarting.
Click to expand...
Click to collapse
Did you manage to solve this issue? I have the same problem.
rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse
I was in csc fastboot mode then i mistakenly did some fastboot adb commands from github rog phone 2(am having rog 3, works same) try those and you will get into fast boot mode from csc fastboot mode after than try above for any query contaact me on my mail [email protected]
Thanks xda love you
rabunz1105 said:
Check current slot and then switch to other slot and boot.
First try
fastboot devices (make sure your device is listed)
if it boots to fastboot again
fastboot getvar current-slot
fastboot --set-active=a or fastboot --set-active=b
fastboot reboot
Click to expand...
Click to collapse
Flash fastboot Raw firmware
My phone is stuck in a bootloop. Original firmware, rom, everything, not rooted, bootloader locked. It just restarted by itself randomly and has been stuck in a bootloop ever since. I've flashed raw firmware but it didn't help. Help please
shinnsan said:
My phone is stuck in a bootloop. Original firmware, rom, everything, not rooted, bootloader locked. It just restarted by itself randomly and has been stuck in a bootloop ever since. I've flashed raw firmware but it didn't help. Help please
Click to expand...
Click to collapse
Have you fixed your issue? if not, have you tried flashing both slots, _a and _b, using the same raw rom? use fastboot cmd's to set either slot_a or slot_b to active so you know you're flashing each slot
So I was going about rooting and all that, when I rebooted to check if i was successful and saw a few different things:
A. the battery icon showed that it was depleted when it wasn't
B. the screen was on, making that weirder
C. i didn't have service, when i did
D. the screen straight up didn't work, but the volume key shiz did
E. Windows didn't recognize my phone
Please help I got this phone 6 hours ago I'm breaking down
ah **** i posted this in the wrong place gimme a sec
You have to fastboot flash the modded boot image to slot a then slot b
JimmyJurner said:
You have to fastboot flash the modded boot image to slot a then slot b
Click to expand...
Click to collapse
Already did that, the problems started after that
I first screwed up like you did. Then used Lenovo software to rescue my phone...then one of two was the solution. I used Lenovo software to copy my rom to my computer and I opened the powershell in the rom files folder that came with the software instead of the original adb folder I had on my laptop and either "fastboot flash boot magisk_patched.img or fastboot flash magisk_patched.img" one of the commands screwed it and the other did it right. I just can't remember which one did what.
Cdbarron727 said:
I first screwed up like you did. Then used Lenovo software to rescue my phone...then one of two was the solution. I used Lenovo software to copy my rom to my computer and I opened the powershell in the rom files folder that came with the software instead of the original adb folder I had on my laptop and either "fastboot flash boot magisk_patched.img or fastboot flash magisk_patched.img" one of the commands screwed it and the other did it right. I just can't remember which one did what.
Click to expand...
Click to collapse
You'd want to run
Code:
fastboot flash boot magisk_patched.img
The other command should just fail to run since no valid partition was entered
You must flash patched boot in fastbootd
Source boot must match building number
I rooted many Moto phones and I never encountered problem you mentioned
2 days ago i woke up to my phone's screen already on, it had been frozen for 2 hours (woke up at 3:40pm but the phone lockscreen showed 1:14pm) so i held down the power button to soft reset it but when it turned itself back on the phone was now stuck in a bootloop. Been 2 days now of trial and error and a whole load of research which now leaves me here. I have unlocked the bootloader (also done critical unlock) but trying to flash stock rom (have tried multiple versions) through miflash gives me "Flash bluetooth_a error", trying to flash it manually through cmd on platform tools gives me the following:
fastboot flash bluetooth_a bluetooth.img
Sending 'bluetooth_a' (556 KB) OKAY [ 0.031s]
Writing 'bluetooth_a' FAILED (remote: 'Error flashing partition : Device Error')
fastboot: error: Command failed
Anyone know how i can fix this? It's not rooted and the bootloader had never been unlocked previously.
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
ricardohorta said:
Why are you trying to flash the bluetooth_a? Any reason for this?
Have you tried to: fastboot boot recovery_image_name.img ? And from there try to solve it?
Click to expand...
Click to collapse
"bluetoot_a" is the first thing it tries to flash through mi flash. Its also the first thing in the images.
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
ricardohorta said:
I´m a bit of a newbie, but i would try to boot into TWRP with fastboot command. From there do a full wipe on the phone and try again.
You might loose all your data.
Click to expand...
Click to collapse
Im not able to boot into twrp, it just hangs on the splash screen.
It should load directly from the bootloader.
Maybe you can try different TWRP versions, maybe it helps.
Xiaomi Mi A2
Disclaimer:Team Win strives to provide a quality product. However, it is your decision to install our software on your device. Team Win takes no ...
twrp.me
There are some instructions also.
rxsta said:
Im not able to boot into twrp, it just hangs on the splash screen.
Click to expand...
Click to collapse
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Sorry @User699 I was out of town, but I'm back now. What's your current status ?
User699 said:
I had that too. You can use this twrp https://androidfilehost.com/?fid=17248734326145702860 provided by @tecknight (here in post 2: https://forum.xda-developers.com/t/...lineageos-nightly-if-i-update-the-os.4240753/)
Click to expand...
Click to collapse
When i boot this version of twrp, the screen goes black for a bit but then just reboots itself.
Finally booted but still hanging on splash screen.
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
User699 said:
Well, that's odd. I tried this on LineageOS, maybe it doesn't work with another OS...
Did you do
Code:
fastboot boot twrpIMG.img
and NOT
Code:
fastboot flash boot twrpIMG.img
?
Click to expand...
Click to collapse
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
rxsta said:
Yes, think it's safe to assume it's a lost cause. Not sure if i want to buy from xiaomi again.
Click to expand...
Click to collapse
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
User699 said:
EDIT 2: Please try
Code:
fastboot getvar all
and look for
Code:
(bootloader) current-slot:a
first. It could also be slot b instead of slot a.
If it's slot a, change the slot using
Code:
fastboot set_active b
, else insert `a' instead.
Then reboot.
Maybe this helps to load your OS.
Well, if losing your data is an option, you could try to factory data reset your device via your recovery (the one that is already present, no need to boot one).
If that also doesn't help, you could try:
Code:
fastboot -w
to wipe your phone. I don't know, however, if you need to reflash everthing again after doing that fastboot wipe, but since you wanted to flash via miFlash either, it shouldn't be much of an issue.
EDIT: It should just wipe it:
Code:
-w Erase userdata and cache (and format if supported by partition type).
(from `fastboot --help')
Click to expand...
Click to collapse
Doubt there's anything else I can do.
Think it's important I also mention that I can't get into the phone's recovery.
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Changed slots but still won't boot, tried doing the "fastboot -w" but got this error
fastboot -w
Erasing 'userdata' FAILED (remote: 'Check device console.')
fastboot: error: Command failed
Click to expand...
Click to collapse
Does your device display anything on its screen?
User699 said:
I see.
I'm sorry, I don't have any ideas toward it right now...
The only thing I could think of is booting into edl (emergency donwload) and reflash your os that way.
But you would have to open your device to access its hardware and since I don't have any experience with it, I couldn't help with it.
Does your device display anything on its screen?
Click to expand...
Click to collapse
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
rxsta said:
nope, it stays on the fastboot screen with no change. Warranty ended few days before the phone died so may as well try it.
Click to expand...
Click to collapse
I wish you the best of luck!