Related
My current situation:
Recovery does not work, when I try to enter it it gets frozen on the Google screen with the lock at the bottom.
When I try to go into the phone normally I receive an infinite error "Unfortunately, Setup Wizard has stopped".
My device is not being recognized as an ADB device so i cannot reinstall recovery (possibly USB debugging is disabled and cannot get to it).
How I got here, Used the Nexus RootToolkit v1.5 to unlock the bootloader/root the phone which worked fine except recovery was not working and the play market was gone for some reason. Did a variety of things to get it back with no avail and eventually got frustrated and tried a factory reset. Now I am in this perdicament :crying:
I came from a Samsung Galaxy and Odin was the universal tool to get the phone back even if it could not enter recovery or the phone, Is there anything like that that can fix the phone without entering recovery or the phone itself?
If you can get the device to recognize in fastboot you can flash the factory image for nakasi from here
How do you flash without entering recovery though?
Can you enter the bootloader? While the tablet is off, hold both volume buttons and the power button, and let go of only power after you see the Google logo. You should enter the bootloader. Download and decompress the factory image from the aforementioned link and open the flash-all file in Notepad to see the required fastboot commands. Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue. If your computer isn't recognizing your Nexus, install the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1766220. Good luck!
Sent from my Nexus 7
slifer315 said:
Can you enter the bootloader? While the tablet is off, hold both volume buttons and the power button, and let go of only power after you see the Google logo. You should enter the bootloader. Download and decompress the factory image from the aforementioned link and open the flash-all file in Notepad to see the required fastboot commands. Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue. If your computer isn't recognizing your Nexus, install the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=1766220. Good luck!
Sent from my Nexus 7
Click to expand...
Click to collapse
Yeah I can get into the boot-loader. I'll give this a shot and see if it works. thanks!
slifer315 said:
Use the corresponding command to flash the stock recovery back to your Nexus 7 and see if that fixes your issue.
Click to expand...
Click to collapse
I installed the universal naked drivers with no problem. Sorry for the noob question but where do I input the commands in the flash-all file for the fastboot?
Use my video guide to help you out. http://www.youtube.com/watch?v=-E-EF0QC0Gc
l0aded said:
I installed the universal naked drivers with no problem. Sorry for the noob question but where do I input the commands in the flash-all file for the fastboot?
Click to expand...
Click to collapse
You need to have the Android SDK installed, open a command prompt, and cd to its directory and the tools folder. In there is the fastboot binary that allows you to run fastboot commands. For ease of execution, you can just install the SDK on the root of your C: drive or just copy the tools folder to wherever it was installed by default (/Program Files/Android/).
Sent from my Nexus 7
Thanks guys! Restored to factory stock and am back from the brick.
l0aded said:
Thanks guys! Restored to factory stock and am back from the brick.
Click to expand...
Click to collapse
Great!
Sent from my Nexus 7
For what its worth-
I can boot into Android system recovery <3e> for Android 5.1.1 build # A1PV1.0.0B17 by powering off and pressing power and volume up at the same time then releasing when the Android appears. Pressing the volume key down instead takes you to Factory Test Mode. The following options are available in recovery:
reboot system now
apply update from ADB
wipe data/factory reset
wipe cache partition
reboot to bootloader
power down
view recovery logs
apply update from cache.
Unfortunately there seems to be no way to get into the bootloader. Hitting "reboot to bootloader" just reboots the phone back to android. One of these days someone will crack this phone. Just hoping we get some people with some development experience on board with this phone.
There was a post that I saw that said that ZTE phones come with the bootloader already unlocked, but I haven't found a way to check it. Has anyone tried to see if the Factory Test is just their fancy way of saying that it's in bootloader mode?
For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:
Code:
adb devices
Code:
adb reboot bootloader
Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.
http://forum.xda-developers.com/showpost.php?p=48319535&postcount=29
http://forum.xda-developers.com/showthread.php?t=2520309
http://cellphonetipsandtrickss.blogspot.com/2013/10/the-super-secret-codes-fr-zte.html
Sebring5 said:
For fastboot: If you have ADB you have fastboot, even if you don't know it yet. Make sure adb sees you device by running the following:
Code:
adb devices
Code:
adb reboot bootloader
Your device will have a RED light at the top, and your screen will be black. Make sure Windows Update can get drivers for you, and it'll install it.
Click to expand...
Click to collapse
I've tried this and it simply reboots my Axon Pro (model A1P). Where are you getting the drivers from? (Besides windows update and Install mode when you connect the Axon to your PC.)
I use a Mac. No drivers needed.
Sebring5 said:
I use a Mac. No drivers needed.
Click to expand...
Click to collapse
That..doesn't exactly help..
Archfeind2 said:
That..doesn't exactly help..
Click to expand...
Click to collapse
http://forum.xda-developers.com/zte-axon/help/zte-axon-drivers-adb-t3173020
Sebring5 said:
http://forum.xda-developers.com/zte-axon/help/zte-axon-drivers-adb-t3173020
Click to expand...
Click to collapse
Already checked that thread out and the ZTE or the google drivers doesn't allow me to get to fastboot. After putting in "adb reboot bootloader" it just reboots the phone.
I also see that whenever you install the drivers from the phone, it installs only adb with a bunch of other ZTE programs for adb with no fastboot in sight.
Archfeind2 said:
Already checked that thread out and the ZTE or the google drivers doesn't allow me to get to fastboot. After putting in "adb reboot bootloader" it just reboots the phone.
I also see that whenever you install the drivers from the phone, it installs only adb with a bunch of other ZTE programs for adb with no fastboot in sight.
Click to expand...
Click to collapse
Try this: http://www.downloads.techdiscussion.in/smartphones/zte-axon-pro-pc-suite-and-usb-driver/
Okay cool. I'll check it out in a couple of minutes.
Edit:
It didn't work it was the same as the axon installer unfortunately. Maybe I'll have to virtual machine either mac or Linux, again >.<
I really want this phone's bootloader unlocked xD
Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA!
Do you know if you had amazon FireOS version 5.0.1 or 5.1.1?
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
drillster said:
I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
Click to expand...
Click to collapse
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
hAtE NeVeR dIeS said:
Just use this method: http://forum.xda-developers.com/ama...howto-how-to-restore-frimware-device-t3238740
Click to expand...
Click to collapse
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
blueberry.sky said:
Do not follow the instructions in that thread! It will permanently brick you if you're have the FireOS 5.1.1 bootloader. The OP of that thread finds it too hard to add a note that it's outdated. See the page 4, post #36
Click to expand...
Click to collapse
I have 5.1.1... yeah, thanks.
blueberry.sky said:
Do you know if you had amazon FireOS ve wrsion 5.0.1 or 5.1.1?
Click to expand...
Click to collapse
I have 5.1.1.
blueberry.sky said:
Just to be clear, you have actually selected the adb sideload option on your Fire when you try to connect with adb on you pc, correct? ADB is not even active until the adb sideload option has been selected.
Click to expand...
Click to collapse
Yeah I selected apply update from adb, adb devices was blank, didn't work.
blueberry.sky said:
We can not "install" twrp. The bootloader is locked & won't allow it. We can only temporarily load twrp into memory. Each time we want to use twrp, we must connect usb to a pc, enter fastboot mode & load twrp. But this can only been done on 5.0.1 Fires. It's been blocked on 5.1.1. No way to load twrp at all on 5.1.1.
Click to expand...
Click to collapse
I went into fastboot mode, installed twrp, and nothing happened because yes, its 5.1.1.
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
blueberry.sky said:
I've seen some other people who also have been unable to get adb to work (in custom recovery). I don't recall a solution.
There is an option in fastboot to flash firmware, I haven't seen anyone try that yet..
Click to expand...
Click to collapse
Do you have any ideas on how to do this? I would greatly appreciate it.
Thank you!
Since I haven't read anyone try it before, there would be some risk. I suppose you are already bricked, seemingly without a way to fix it, but you could brick it harder. You might be able to get adb working. I may not have any ideas on how to get adb working for you, but someone else might know. If you try flashing the stock OS via fastboot, there is a chance you could brick it in a different way.
The command would be
Code:
fastboot update <filename-of-stock-firmware.zip>
But we don't have a .zip stock firmware file. In twrp recovery you can just rename the .bin file to .zip & it works. Not sure if that will also work for fastboot. My guess is it won't work & might brick you.
Also be aware, on Fires that self-updated to FireOS 5.1.1 (or came with 5.1.1 new) you must only flash 5.1.1. Attempting to flash 5.0.1 will brick it 100% of the time & it's unrecoverable.
drillster said:
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
. . .
Click to expand...
Click to collapse
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
I have same issue.
[QUOTE=drillster;64617577]Hey everybody!
This is my first time posting something on XDA. This is really cool.
So I just bricked my fire, hard. Let's start from the top:
- I used the super tools rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool to get the google play store.
- Using the google play store, I got flashfire.
- Using flashfire, I flashed SlimLP onto my tablet successfully and quickly.
- I got a little cocky, and based on the comments on the youtube.com/watch?v=NaCBSuUuhRE video that I used to flash SlimLP I decided to try the flashfire technique with CM since it is my favorite ROM.
- I did everything properly and the same, but... it got stuck here... for about an hour...
imgur.com/QJvmRz3
So I decided to do the smartest thing ever and cancel it myself by turning it off, I wasn't able to do anything else anyway. Either way, my tablet is now stuck in the cyanogen 12 boot load animation, the one of the cute blue head with the radar effect.
I would of fixed this a long time ago, but for some reason I'm not able to adb sideload.
I go into fastboot, I can detect the device, but not adb sideload.
I go into adb sideload mode, I can't detect the device, so definitely not sideload. :/
I've tried updating my drivers, I don't know if I'm doing it right, but while it was in fastboot mode, I changed it to Android Composite ADB Interface, and that didn't change anything.
No matter what I'm doing, whenever I do adb devices, I always get:
List of devices attached
Blank. Nothing. Only when I'm in fastboot mode do I get:
fastboot devices
G0K0H40454261ARU fastboot
Something, but still no ADB. I can't even load TWRP here, tried that, I just install it and it just sits there dumbly saying it's installed.
I'm bricked just like my tablet. Could I please get some help here? I'm very desperate to get this tablet back up and running, and I feel so stupid for not having stuck with Slim and trying to install CM. I really don't want it to stay bricked like this.
Thank you, XDA![/QUOTE]
I did the same thing. Slim worked great, tried to flashfire CM12, ot bricked. Can get fastboot, but nothing else. Afraid to try update from fastboot.
I just want to say thanks to everybody who contributed, I'm really appreciative of the support, especially because I didn't expect it, haha! Listening to blueberry.sky I'm going to try the flashboot update, because it's either that or a bricked device. School just started so I got busy with that.
DoLooper said:
Just a shot in the dark here, but have you gone into device manager while in sideload mode and updated drivers for KFFOWI under Other devices? Windows needs drivers for every mode.
Click to expand...
Click to collapse
So when I have it in adb mode, the fire doesn't seem to show up anywhere in any of my devices, and I can only find it when it's in fastboot mode. So when it's in that mode, I've tried Android ADB Interface, Android ADB Composite Interface, and when I go back to adb sideload, it's just not there in device manager. I don't know what this means, so any speculation? But no matter what mode I'm in or what driver I'm using, I can't seem to get it to show up in adb when in sideload mode.
Again, thanks everybody, and I hope anybody else in the future with this issue can refer to this thread for a lead!
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I didn't rename the Slim and this is what I get:
C:\path\to\SuperTool>fastboot update Slim-ford-5.1.1.build.2.2b-20151210.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
drillster said:
So I just tried to flash update the firmware from Amazon amazon.com/gp/help/customer/display.html?nodeId=201830180 which I renamed from .bin to .zip:
Is there anyway I can resolve this, so I can do SOMETHING?
Thank you!
Click to expand...
Click to collapse
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
thekrakah said:
To be clear, you were able to, "adb sideload update-kindle-global-37.5.4.1_user_541112720.bin". To restore your Fire OS 5.1.1?
Click to expand...
Click to collapse
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
drillster said:
No, I did fastboot update in fastboot mode as suggested by blueberry.sky since ADB isn't working for reasons I stated before.
C:\path\to\SuperTool>fastboot update update-kindle-global-37.5.4.1_user_541112720.zip
Click to expand...
Click to collapse
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
thekrakah said:
So when you say you go into "adb sideload mode. You selected "apply update from adb", and the Fire device is actively waiting for the sideload command, but you got nothing showing up in your device manager at that point?
I'm just clarifying because until the "apply update from adb" is activated, windows doesn't get a communication from the Fire device.
Click to expand...
Click to collapse
On my device, I can get fastboot, but not adb. if I reboot from fastboot, I only get the
CM logo and it sticks there permanently until I power off. When I boot to fastboot, the screen is blank but my Windows PC can see the device and return the SN. I can issue the command to reboot to bootloader, but reboots to fastboot with "fastboot" in small letters at the bottom of the screen. What else can I try? Thanks for all the help offered so far.
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
blueberry.sky said:
What happens when you try to get into recovery mode?
To get into recovery you start with the Fire off. Turn off by holding power button until it goes off (might take awhile). I just tried turning off from fastboot mode. Took only about 14 seconds of holding power.
To enter recovery: hold volume down button + hold power button.
Click to expand...
Click to collapse
When I try to get into recovery, it boots with a blank screen. At that point, I can connect to my PC, type fastboot devices, and it will show me device. Then I try to reboot-bootloader, and it reboots to fastboot, but this time it says fastboot on the screen. I can't seem to get to recovery
watch this video to see if it helps.
https://www.youtube.com/watch?v=RQLoH-ahjy4
Hello everyone, i got rooted Rog Phone 2 and after rooting my rog phone 2 i dont have wifi signal anymore. i unroot my phone by flashing stock + tried flashing stock boot.img but wifi is still not working, what happened and how can i fix it?
@Barcovn Would you like to share how to deal with this?
https://m.facebook.com/groups/2059277157699287?view=permalink&id=2106812296279106
From my friend. He share the Tut for fixing it. Basically we upgraded new fw after open the phone so the boot.img extracted from the website will be difference with newest ota upgrade. Lost wifi. You have to manual flash the phone again
Barcovn said:
https://m.facebook.com/groups/2059277157699287?view=permalink&id=2106812296279106
From my friend. He share the Tut for fixing it. Basically we upgraded new fw after open the phone so the boot.img extracted from the website will be difference with newest ota upgrade. Lost wifi. You have to manual flash the phone again
Click to expand...
Click to collapse
Right! As I haven't got the phone yet, didn't find out that new OTA have different boot.img. So as for now, rooting means just firmware on website is usable.
In the future if there is an update you will need to unroot, flash the original boot. Flash the rom update and then extract the new boot, patch it with magisk and flash the new patched boot to enjoy root again.
Personally I would rather stay on stock enjoy the timely OTA updates and keep my warranty.
dungnghien said:
Hello everyone, i got rooted Rog Phone 2 and after rooting my rog phone 2 i dont have wifi signal anymore. i unroot my phone by flashing stock + tried flashing stock boot.img but wifi is still not working, what happened and how can i fix it?
Click to expand...
Click to collapse
Hello dungnghien,
Could you please share the steps to root it? Also, where can I find the stock firmware in case things don't go well and I need to rom it.
Would appreciate your help.
So I unlocked bootloader using apk from asus site and patched boot.img using magisk. Now how to flash "magisk_patched.img"?
Can someone help please?
havork said:
So I unlocked bootloader using apk from asus site and patched boot.img using magisk. Now how to flash "magisk_patched.img"?
Can someone help please?
Click to expand...
Click to collapse
Follow the same procedure done for the ROG phone.
https://forum.xda-developers.com/rog-phone/how-to/guide-root-t3865490
Rashad83 said:
Follow the same procedure done for the ROG phone.
https://forum.xda-developers.com/rog-phone/how-to/guide-root-t3865490
Click to expand...
Click to collapse
Tried that already. No luck.
Is the phone supposed to go into some special download mode screen like on Samsung?
havork said:
Tried that already. No luck.
Is the phone supposed to go into some special download mode screen like on Samsung?
Click to expand...
Click to collapse
After patching the boot.img did you boot into fastboot mode and runned the command for flashing the patched boot.img.
Was the flash successfull or not?
Please be specific in what step you are having issues with and what actions you took.
Rashad83 said:
After patching the boot.img did you boot into fastboot mode and runned the command for flashing the patched boot.img.
Was the flash successfull or not?
Please be specific in what step you are having issues with and what actions you took.
Click to expand...
Click to collapse
I'm trying to follow steps from the tutorial.
Device is on, USB debugging on
adb devices list my device
adb reboot recovery reboots into recovery, but I don't see "Select ADB on phone" option antwhere in recovery.
havork said:
I'm trying to follow steps from the tutorial.
Device is on, USB debugging on
adb devices list my device
adb reboot recovery reboots into recovery, but I don't see "Select ADB on phone" option antwhere in recovery.
Click to expand...
Click to collapse
There is no such option with the stock recovery. Any way why do you need that. You don't need to use ADB commands to flash the patched boot.img.
Rashad83 said:
There is no such option with the stock recovery. Any way why do you need that. You don't need to use ADB commands to flash the patched boot.img.
Click to expand...
Click to collapse
So how do I flash the patched image? I really need to root this thing and would appreciate the help.
In Samsung phones it's pretty easy, boot into download mode and flash using odin, how to do that on this phone?
Anyone wanna report if there's any issues after rooting the device?
havork said:
So how do I flash the patched image? I really need to root this thing and would appreciate the help.
In Samsung phones it's pretty easy, boot into download mode and flash using odin, how to do that on this phone?
Click to expand...
Click to collapse
Follow step 8 in the tutorial, are you following the steps in the first page of the link i gave?, because the steps are straight forward.
Step 8
Rashad83 said:
Follow step 8 in the tutorial, are you following the steps in the first page of the link i gave?, because the steps are straight forward.
Click to expand...
Click to collapse
Turn device off.
hold down volume up and power button.
I get these three options you see in screenshot.
No download mode option.
havork said:
Turn device off.
hold down volume up and power button.
I get these three options you see in screenshot.
No download mode option.
Click to expand...
Click to collapse
There used to be a fastboot mode on the ROG phone on Android Oreo, i am not sure if things changed with Android Pie.
Anyway try the hardware method to connect, turn your phone off and connect it to the PC using the side port make sure to hold the low volume key when connecting the phone to the PC. See if a fastboot mode black screen shows up.
If not:
On the bootloader screan the second one you showed. On your PC after going to your platform tools and running the cmd window from there type the command:
Fastboot devices
Does it recognize your device?, if it does run the 2 commands stated in step 8. But do it on your own risk if something goes wrong you might brick the device and if you are not able to flash back the stock boot i am afraid you will end up with a bricked device until a solution is suggested.
I can't get into fast boot mode. Tried all options, volume up, volume down, usb, no usb, debugging on, debugging off...
No luck.
$20 for whoever helps me get this thing rooted.
havork said:
I can't get into fast boot mode. Tried all options, volume up, volume down, usb, no usb, debugging on, debugging off...
No luck.
$20 for whoever helps me get this thing rooted.
Click to expand...
Click to collapse
Maybe @Barcovn can help since he got root.
Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.
Bump.
Bump.
Bump.
Xenomorphs said:
Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.
Click to expand...
Click to collapse
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot
qwertz512 said:
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot
Click to expand...
Click to collapse
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.
Xenomorphs said:
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.
Click to expand...
Click to collapse
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.
hakudayo said:
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.
Click to expand...
Click to collapse
Thank you so much. I'm going to try.
Xenomorphs said:
Thank you so much. I'm going to try.
Click to expand...
Click to collapse
No problem if you have any questions just ask me
Now I'm stuck with this same issue.,
Got into this while trying to boot TWRP OrangeFox-R12.1_3_A12_FBEv2-Unofficial-lime.zip on xiaomi A12 ROM