I was running the November version version on Pie with Magisk working just fine. I saw that there was an update available so I did a complete uninstall of Magisk from the app. My phone rebooted to the screen that shows "No Command". At this point, I figure worst case I can just reflash and start over no biggie. It has happened before. I reboot my phone to fastboot but if I try to push any command to the device whether it be to boot into twrp or even run the MiFlash tool it fails. All that pops up is the a very small message that says press and key to turn off. I'm at the end of my knowledge and I'm hoping someone can help me to get my phone back up and running. Thanks in advance to anyone that tries to help.
You're using a USB 3.0 port, use a USB 2.0 port, also you just need to flash stock boot
Nebrassy said:
You're using a USB 3.0 port, use a USB 2.0 port, also you just need to flash stock boot
Click to expand...
Click to collapse
I can try that but i have flashed quite a few images using the exact same USB port and cable previously. I'll let you know though. Thanks.
I got my phone back thank you. I never realized adb and fastboot got cranky with usb 3.0. Thanks again. Now off to try and break it again haha.
bobomonkey00 said:
I got my phone back thank you. I never realized adb and fastboot got cranky with usb 3.0. Thanks again. Now off to try and break it again haha.
Click to expand...
Click to collapse
Hi man. Sorry this could be in wrong forum,
But seems like you are quite familiar with Mi Flash.
Can I update December patch with Mi Flash.
I keep getting "system update failed".
Appreciate all the help.
Qyfaruxx said:
Hi man. Sorry this could be in wrong forum,
But seems like you are quite familiar with Mi Flash.
Can I update December patch with Mi Flash.
I keep getting "system update failed".
Appreciate all the help.
Click to expand...
Click to collapse
Are you trying to use an OTA image or a FASTBOOT image? MiFlash only supports fastboot images.
bobomonkey00 said:
Are you trying to use an OTA image or a FASTBOOT image? MiFlash only supports fastboot images.
Click to expand...
Click to collapse
It's OTA image.
I see...so I can't flash OTA image in Mi Flash.
But is it possible for me to Flash Oreo official Room if I'm in Pie?
Qyfaruxx said:
It's OTA image.
I see...so I can't flash OTA image in Mi Flash.
But is it possible for me to Flash Oreo official Room if I'm in Pie?
Click to expand...
Click to collapse
There are a few guides that explain how to unpack an OTA and then flash the images individually. I personally got tired of working around all the OTA nonsense. I installed TWRP persistently and then installed crDroid.
Not sure if you can downgrade to Oreo then update back to Pie. I would assume you can based on the fact that last I checked Xiaomi only has one MiFlash compatible image Oreo image on their support page.
bobomonkey00 said:
There are a few guides that explain how to unpack an OTA and then flash the images individually. I personally got tired of working around all the OTA nonsense. I installed TWRP persistently and then installed crDroid.
I see.
Im interested with these method.
May i know in details how you do it?
Click to expand...
Click to collapse
Solved !!!! worked for me.
guys, try the following threads, it worked for me.
https://forum.xda-developers.com/mi-a2/help/soft-bricked-a2-urgent-help-t3834188
https://forum.xda-developers.com/showpost.php?p=77302899&postcount=4
Related
bootloop. & bootloader is locked. And I do not have usb debugging enabled. Any way to get around this?
Depends... You're quite sparse with information about what you've done to get to where you are and about your setup.
A few options come to mind. If you have TWRP you can try flashing a custom rom zip and that could fix it. You could also try the special N preview OTA that google provided to fix phones that got screwed up by an N OTA. http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Yeah sorry about that. While updating to 6.0 the phone died. And is now stuck in a bootloop (stuck at the google logo screen). I was trying to use nexus root toolkit to flash stuck android back onto it, however my bootloader is locked. And I did not have usb debugging enabled either. So I am trying to find a way to unlock my bootloader. If that makes any sense
Use the second method I suggested. Should work.
Can you get in bootloader or recovery mode?
http://forum.xda-developers.com/nexus-6/general/to-save-bricked-nexus-device-t3334660
Try to sideload shamu-ota-npc91k-201dd8d1.zip. (This upgrades to Android N Preview.)
Since the OTA is a complete image, it should restore the device to working condition. Then you should be able to enable USB debugging and OEM unlock so the bootloader can be unlocked through fastboot.
Sorry for the late replies. I am attempting the second method & I am able to boot into recovery mode. However I keep getting "adb server is out of date" so I am trying to work it out at the moment
This worked for me! Locked bootloader, no usb debugging, no custom recovery, stuck in bootloop due to software issues.
Bootloader showing engineering
Hi,
I-ve attempted to do the manual upgrade from Android 5.0 to 6.0.1, when running the restart on my Motorola Nexus 6. the screen is showing Bootloader status> Engineering mode.
Somebody told me I would not be able to update this phone because is a prototype or something like that, I need help with this.... thank you!!
Warhammer143 said:
Hi,
I-ve attempted to do the manual upgrade from Android 5.0 to 6.0.1, when running the restart on my Motorola Nexus 6. the screen is showing Bootloader status> Engineering mode.
Somebody told me I would not be able to update this phone because is a prototype or something like that, I need help with this.... thank you!!
Click to expand...
Click to collapse
have you tried manually flashing/updating your bootloader, via fastboot or flashable zip?
simms22 said:
have you tried manually flashing/updating your bootloader, via fastboot or flashable zip?
Click to expand...
Click to collapse
tried many things but not sure..
Is there any thread where I can find the instructions???
Warhammer143 said:
tried many things but not sure..
Is there any thread where I can find the instructions???
Click to expand...
Click to collapse
well, instructions, probably not. if its a flashable zip, that means that you can use twrp recovery to flash it. fastboot flashing has to be done while youre in the bootloader, using fastboot. the command is.. fastboot flash bootloader zipname.img
right now am using nexus root toolkit V 2.1.6.....
look. I am really a noob on this topic .... don't know what to do....
Warhammer143 said:
right now am using nexus root toolkit V 2.1.6.....
look. I am really a noob on this topic .... don't know what to do....
Click to expand...
Click to collapse
well, being a noobie, use google to find out about twrp recovery and about fastboot flashing. fastboot flashing would be more important to you, as twrp recovery use is simple when you already have it installed. unfortunately, im at work at the moment, so cant really help out to much.
simms22 said:
well, being a noobie, use google to find out about twrp recovery and about fastboot flashing. fastboot flashing would be more important to you, as twrp recovery use is simple when you already have it installed. unfortunately, im at work at the moment, so cant really help out to much.
Click to expand...
Click to collapse
Well, I will be searching on google, but thanks a lot!
Hi, I am new to this forum but old on android. My oneplus 3t brick yesterday and i don't know why. I never rooted phone and always update phone via OTA. I contacted Oneplus support yesterday and they arrange a remote session where they are unable to install anything via msmdownload tool. I download msmdownload tool yesterday from this forum and my phone works but there is no modem in it. I am unable to connect to wifi and SIM internet. Oxygen OS version install at the moment is 3.5.1 and android version is 6.0.1. Need help from some seniors.
Update by using on the of the official "full zips"? These include the modem, so I would think that would fix the problem, unless there is a more serious issue (hardware failure, etc.):
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
redpoint73 said:
Update by using on the of the official "full zips"? These include the modem, so I would think that would fix the problem, unless there is a more serious issue (hardware failure, etc.):
https://forum.xda-developers.com/oneplus-3t/how-to/rom-oxygenos-3-5-4-mm-ota-update-t3519074
Click to expand...
Click to collapse
I tried multiple time but device stuck in boot loop. Downloaded ROM from Oneplus official site.
xusmanmalik said:
I tried multiple time but device stuck in boot loop. Downloaded ROM from Oneplus official site.
Click to expand...
Click to collapse
The full zip or the OTA?
Is your phone rooted/TWRP installed, or is it stock?
redpoint73 said:
The full zip or the OTA?
Is your phone rooted/TWRP installed, or is it stock?
Click to expand...
Click to collapse
Phone is stock not rooted. When i upgrade locally or through adb process phone stuck in bootloop.
xusmanmalik said:
Phone is stock not rooted. When i upgrade locally or through adb process phone stuck in bootloop.
Click to expand...
Click to collapse
Now i updated from 3.5.1 to 3.5.4 but issue still exist
xusmanmalik said:
Now i updated from 3.5.1 to 3.5.4 but issue still exist
Click to expand...
Click to collapse
Upgrading from 3.5.4 to 4.0.2 phone again stuck at boot screen. I don't know what to do know. Should i go for warranty claim or try something else. Need HELP!!!!
Thanks in Advance.
Are you able to go to fastboot mode? If yes, go for it:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Install TWRP too. Now you're able to wipe everything and upload a full ROM to your device (Thanks to MTP-mode via TWRP, so handy!). Flash the full ROM and have a try .
MickyFoley said:
Are you able to go to fastboot mode? If yes, go for it:
https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
Install TWRP too. Now you're able to wipe everything and upload a full ROM to your device (Thanks to MTP-mode via TWRP, so handy!). Flash the full ROM and have a try .
Click to expand...
Click to collapse
Micky Thanks for the help. I will give a try and will inform further.
I ****ed up somewhere. Encryption unsuccessful Error.
xusmanmalik said:
I ****ed up somewhere. Encryption unsuccessful Error.
Click to expand...
Click to collapse
Do you have TWRP installed? Just wipe your phone, get an otg cable and a flash drive, you can flash everything from the flash drive
I revert back trying again now.
xusmanmalik said:
Micky Thanks for the help. I will give a try and will inform further.
Click to expand...
Click to collapse
Hi Micky Foley, I successfully followed all steps and now i am on twrp and su installed.
But still i am unable to install other ROM than 3.5.*
Your last option is the warranty then mate
Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,
aliensk said:
Hey guys,
I am having issues updating to February update. I already tried all the guides on how to uninstall the patched boot through Magisk as well as manually trying to flash through fastboot 10.03 (January update) boot.img but everytime i end up in bootloop which i resolve after flashing 10.03 patched img. Uninstalling it through Magisk managers shows that I do not have root but the update still fails.
Any one has a link for the full 10.0.03 boot.img as I have a suspicion that the ones I am using might be partial from the ota and that is why they fail to boot.
Or let me know if you have any other idea how to fix this without wiping the data or restoring through mi tool
If someone from xiaomi read this "fix your s...t "
Thank you in advance,
Click to expand...
Click to collapse
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12
lept_2014 said:
Try with this:
https://forum.xda-developers.com/showpost.php?p=78757162&postcount=12
Click to expand...
Click to collapse
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.
Hey guys,
I managed to resolve the bootloop issue. If anyone has the same issue use the following untouched boot.img
https://xiaomifirmware.com/download/11657/
As I was suspecting, the ones I was using the from the links provided in the forum were too small and this one is 64 mb. After flashing it boots perfectly.
However, unfortunately again I get errors during the update. At least no bootloop
aliensk said:
Thank you but that one didnt work I already tried it. Bootloop when using that one. I have not done any mods to system files except using e patched boot to get root.
Click to expand...
Click to collapse
That Stock BOOT works fine for me. Remember flash it into the right slot for you.
I did flash to to slot B as the getvar current-slot was B but it was still bootlooping until i tried the last one from the link I provided. However, since I am still unable to update, is there a link to download the system.img for 10.0.3.0 just in case i have somehow modified my system? I dont remember to have done anything but just in case.
Thank you.
How will you solve it
Plz...tell me with boot file how fill solve your problem
Varshithpoudala said:
Plz...tell me with boot file how fill solve your problem
Click to expand...
Click to collapse
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful
aliensk said:
have not resolved it yet. In fact after trying to fix now it went into full brick mode no button reactions and nothing on the screen must have done something really wrong so be careful
Click to expand...
Click to collapse
Did you find any way to fix it?
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
features99 said:
I tried re-rooting after updating and now it says Your device is corrupt. It cant be trusted and may not work properly.
It freezes on the Google if I continue. Not sure what happened.
Any remedy for this?
Click to expand...
Click to collapse
Need more specific details, like specific method of rooting, version of Magisk, updating to what?, etc...
Unfortunately you may have to flash the factory image and start all over again if no one else can help you with it. At least you have the option. Sucks when that happens.
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
jljtgr said:
I mean... the first message just sounds like the bootloader unlocked message which would show up even if you could fully boot in.
I wouldn't factory reset over just this though. Flash the factory image without the -w parameter in flash-all.bat
Click to expand...
Click to collapse
I agree. Flashing the factory image without the -w would likely allow him to boot up again. But it would be helpful for that person to tell us exactly what they did so we can help them avoid it in the future, e.g. maybe they flashed the stable version of Magisk instead of Beta or Canary, or maybe they tried a direct install instead of patching the boot image, etc...
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
Also I didnt modify my own boot image, but one I downloaded from a matching build.
I really appreciate the help
features99 said:
Ok guys sorry for not giving more details.
So I rooted awhile back when I got the phone, havent updated in a long time so I thought it was time.
I updated to Android 11 with the latest security updates and tried to re-root.
I updated Magisk to the latest version and patched the matching boot image, but Im pretty sure I used the stable version.
I should of researched it more as Im reading the beta method is the way to go.
I opened the command prompt with the following commands:
cd Downloads
cd fastboot
fastboot flash boot magisk_patched.img
fastboot reboot
Seems like everything went ok...
Then afterwards got the corrupted message and Google hang.
I can still load to fastboot but recovery or rescue doesnt work.
So where can I go from here? I only rooted a few phones in the past so Im still learning and reading lots of posts.
I really appreciate the help
Click to expand...
Click to collapse
I would try fastboot flashing the stock boot image first.
If Magisk says you're on a version before 21.0, the patched image won't work for Android 11. Stable is currently 20.4 released in March.
Lughnasadh said:
I would try fastboot flashing the stock boot image first.
Click to expand...
Click to collapse
tried that..it didnt work
features99 said:
tried that..it didnt work
Click to expand...
Click to collapse
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Lughnasadh said:
Then I would flash the December factory image using fastboot but with the -w removed from the flash-all.bat file so it won't erase your data.
Click to expand...
Click to collapse
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
features99 said:
Yes that worked, didn't know about edited the .bat to remove the the -w and saving all data. Back in business for now...
Thank you all for expertise, much appreciated!
Click to expand...
Click to collapse
No problem. Glad you got it going. As I see you've already found out, Magisk Beta 21.1 is a good way to go. Canary as well but then you may run into problems in the future when Canary gets updated since those are "cutting edge" builds.
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/rosemary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
OK nevermind I successfully got the phone booting again with miflash tool by reflashing an official firmware...
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/t/twrp-on-android-12.4522273/), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Click to expand...
Click to collapse
Hope it helps! ; D
dona3000 said:
Hey everyone
I recently got this phone and went through the bootloader unlock process.
I then tried to follow the instructions on this page https://wiki.pixelexperience.org/devices/ros mary/install/ to get this rom installed but somehow ****ed it up.
Everything went well until I tried to flash the recovery img from this page: https://get.pixelexperience.org/rosemary (i downloaded the 13 plus recovery img).
I flashed the img via fastboot but after that I got stuck in fastboot. The phone is stuck in a bootloop when I try to reboot into recovery or normal boot. The only thing I can get back into is fastboot.
Would really appreciate any help to get the phone working again. Im not new to android custom roms but Im new to xiaomi phones and Im a little lost
Thanks.
Click to expand...
Click to collapse
Did u make sure ur on Miui 12.5.16.0.RKLMIXM?
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
fol!s said:
I'm also having similar problem and circumstance, may I ask where did you find the official firmware and/or recovery img for the Redmi note 10s
Click to expand...
Click to collapse
Greetings!
As this phone has an MTK processor, we don't really have a recovery image, it's stored in the boot img I suppose. That link, you can download the official rom to this. DISCLAIMER: There are two types of ROMs listed here, one type is fastboot, that you need now in order to flash it through a computer for example. The another type is the recovery rom, that you can flash from recovery like a magisk package, or anything flashable zip, or with adb sideload.
https://mifirm.net
You should choose global if you are in Europe, but it's suitable for devices in the US or USA probably, ony feature differences are here between an EEA and Global rom.
Also, if you install pixel experience recovery, you can install the firmware by going into recovery, and do it via sideload. Or, you can try flashing the rom with TWRP (tutorial linked below), but then you won't able to install updates automatically.
One question: Did you checked in OEM unlocking in developer options before flashed PE?
Hope it helps!
Yeah, I did checked the oem unlocking. I think the reason why i failed because my bootloader probably updated and I forgot to check. You need bootloader version 12.5.16.0.RKLMIXM to install the pixel experience. Also thank for help
Greetings!
You can install the rom via adb sideload too. Put on some random recovery (see my tutorial here: https://forum.xda-developers.com/members/gurtnyi.11842195), and start adb sideload.
Then,
adb sideload insert_package_name.zip
Hope it helps! ; D
Click to expand...
Click to collapse
Can I do that on newer firmware or should I roll back to version 12.5.16.0.RKLMIXM? And if I roll back then I need to unlock device again?
I think you can. I've flashed it successfully on the latest version too. Currently I don't use PE but it was good for me.
Well, regarding to the unlock, it's not a big deal, you don't have to wait 168h again, once you've firstly unlocked your device, you can re-unlock it again, and again, no matter how many times, you don't have to wait a lot again.
But depending on how you rollback it,
I mean, with xiaomi flasher (i think that's its name) you can choose between clean all and lock, save userdata, and clean all, but in the first case, it'll lock back the bootloader. With SP flash tool (if you need, I can provide a link for the modified version of it, that doesn't require an auth file, but if fails, you need a python script, I can link that too), as I remember it won't lock back the device, but I'm not a 100% sure
Hope it helps!
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
raven17a said:
Can you repair link to totorial https://forum.xda-developers.com/members/gurtnyi.11842195 doesn't seem to work.
Click to expand...
Click to collapse
Corrected, thank you!
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
raven17a said:
Thank you! I managed to install PE by rolling back to MIUI 12.5. Sideload unfortunatly not working on stock recovery.
Click to expand...
Click to collapse
Happy to hear that!
By the way, yes, pe recovery is better for sideloading, or eventually any not stock recovery. Also, if you install PE recovery, you can apply updates automatically, and in the future you won't need to flash it manually.