Bootloop after reset what can i do - Xiaomi Mi A1 Questions & Answers

I have reset my a1 and now it stuck in bootloop on android one screen.
I can go into fastboot and recovery but the bootloader is locked.
When i reset again in recovery its the same.
Is there a way i can give the phone new life?

fellow this and flash the image http://en.miui.com/thread-807252-1-1.html
don't unlock just flash from fastboot

Error: "Erasing boot failed, maybe the device is locked"

Piti8576 said:
Error: "Erasing boot failed, maybe the device is locked"
Click to expand...
Click to collapse
Did you manage to do it?

Flash it through EDL, or unlock it again.

Related

Assistance Needed Nexus 1 not working after unlocking bootloader and rooting

I used the guide on this site,
I don't know what I did wrong, but now it just hangs on the screen shown below.
Any help, guidance, words of wisdom, or berating would be awesome.
Pull the battery. Hold the volume down button on the phone and put the battery back in and power it on (while still holding the button). Select recovery and see what happens. . . Cross your fingers, pray to Allah, etc.
how far did you get in the rooting process? were you able to install amon_ra's recovery image yet? also can you get into fastboot mode or recovery mode?
momohammed20 said:
how far did you get in the rooting process? were you able to install amon_ra's recovery image yet? also can you get into fastboot mode or recovery mode?
Click to expand...
Click to collapse
i got the bootloader unlocked.....not 100% sure that the root through fastboot was fully completed. Tried flashing amon_ra's recovery image and got the error message:
"downloading 'recovery.img'...failed <remote: not allow>"
byalansmithee said:
i got the bootloader unlocked.....not 100% sure that the root through fastboot was fully completed. Tried flashing amon_ra's recovery image and got the error message:
"downloading 'recovery.img'...failed <remote: not allow>"
Click to expand...
Click to collapse
It's the oem unlock that will allow you to flash the recovery image, not root.
Sounds like it's not quite unlocked although you have the unlock boot image (which is odd).
Have you tried doing the oem unlock again and then tried to reflash the recovery image?
SC
ScaredyCat said:
It's the oem unlock that will allow you to flash the recovery image, not root.
Sounds like it's not quite unlocked although you have the unlock boot image (which is odd).
Have you tried doing the oem unlock again and then tried to reflash the recovery image?
SC
Click to expand...
Click to collapse
Yeah, I tried the whole process (the oem unlock and superuser root) a second time and got the response: ... INFODevice was already unlocked!
OKAY
I can still boot to the bootloader and fastboot, but can do nothing more.

Help! "Your device is corrupt. It can't be trusted and may not work properly." (Red)

Help! "Your device is corrupt. It can't be trusted and may not work properly." (Red)
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
bb1981 said:
I've had that as well with mine before. The way I fixed mine was a somewhat tedious process but it did work for me. Start by downloading one of the angler images from Google, then with 7zip, decompress the .tgz which gives you a .tar. Once more will get you a folder named xxxxxx-angler. (I think it was that way but not 100% sure since I'm not at my laptop at the moment). With your phone (unlocked) in bootloader/fastboot mode, run flash-all.bat. this gets you back to a fully stock system but still has the corruption flag tripped. Run stock recovery and do a factory reset and the corruption warning should be gone and back to the "normal" screen saying please lock the bootloader.
Click to expand...
Click to collapse
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Moddy98 said:
thank you but i have already done all that, the problem is that i have flashed the angler image from google and did a factory reset,however, i am selling the phone soon and the warning message is still there even though the boot loader is locked and am not rooted
Click to expand...
Click to collapse
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
same prob in orange..plz help bro
TnT_ said:
Try doing this process manually, if you're selling it. I would infer the data doesn't matter on the device.
Depending on which OS you are on. Focus your command prompt with fast boot installed to your directory containing the stock files (unzip the image zip)
Now do the following process manually. Step by step
fastboot flash bootloader bootloader-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio radio-angler-angler-xx.xx.img
fastboot reboot-bootloader
fastboot flash vendor vendor.img
fastboot reboot-bootloader
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot format cache
fastboot flash cache cache.img
Now, if you still get the red warning. Repeat the process and add :
fastboot format userdata
DO NOT FLASH THE USERDATA IMAGE
If this does not work, I have other suggestions.
Click to expand...
Click to collapse
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
vigy321 said:
I flashed my nexus 5x with marshmallow from nougat...but at the end i didn't lock the oem bootloader...so now i am repeatedly getting an error message "your device software can't be checked for corruption.Please lock the bootloader nexus"(orange color)..i had downgraded my nexus to marshmallow because i was having a bootloader stuck up loop problem...
And to do any of the steps I have to switch on the usb debugging mode right ??? But the problem is this message is constantly coming and i am unable to do anything for the past 2 days
Click to expand...
Click to collapse
To flash back to stock, you have to boot into bootloader and using fastboot to flash factory image.
But hey, you're in the Nexus 6P forum, try following this guide in the Nexus 5X forum:
https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I just went through this. Just unlock your bootloader with the Nexus toolkit and it'll go away that's all i did
Sent from my Nexus 6P using Tapatalk
---------- Post added at 06:45 PM ---------- Previous post was at 06:42 PM ----------
Moddy98 said:
Hello,
just recently i rooted my Nexus 6p device and unlocked the bootloader, i noticed however, after rooting the device i received an error on boot up stating "Your device software can't be checked for corruption. Please lock the bootloader." (Orange), but after researching on the internet many people said that was normal due to the boot loader being unlocked...
however my concern for today is i have flashed back to the factory images of marshmallow, and am now experiencing an error on boot up that Your device is corrupt. It can't be trusted and may not work properly." i followed the exact step-by-step guide on how to unroot and lock the boot loader on the link below however am still experiencing the issue, please help it will be ever so much appreciated.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
(the error that i am receiving after flashing stock image)
https://lh3.googleusercontent.com/iGv9RPFbDSLec-4-cvsQNOh46pt5RhEvPy7EKKZXmbtjJ16P7d5EXOJHCIsR=w300
Click to expand...
Click to collapse
It happened to me just last week. Just unlock your bootloader with the Nexus toolkit and it'll go away. That's all i did and it went away i got it the same way you did and that's all I did
Sent from my Nexus 6P using Tapatalk

Asus Zenfone 2 Laser ZE500KL

Hi. I have soft-bricked my phone and when I turn it on it says "ERROR:Can't load invalid boot image!" then after finding some solutions here in xda, the fastboot boot boot.img method worked but whenever I restart my phone it keeps bringing the problem back to I need to fastboot boot it again.. Is it because my fastboot is not saving my work after restarting my phone? Any solutions for this please
So find true version boot fit ur version android firmeware then open cmd type
Fastboot flash boot boot.img
"Boot.img" is name of ur file boot....
Hope it work for u
binsz said:
Hi. I have soft-bricked my phone and when I turn it on it says "ERROR:Can't load invalid boot image!" then after finding some solutions here in xda, the fastboot boot boot.img method worked but whenever I restart my phone it keeps bringing the problem back to I need to fastboot boot it again.. Is it because my fastboot is not saving my work after restarting my phone? Any solutions for this please
Click to expand...
Click to collapse
You have bootloader unlocked??

Phone stuck on Essential Logo (Powered by Android) screen while trying Oreo B2 OTA

I have tried everything to get this phone to boot up. I was downloading the Oreo B2 via OTA, not sideloading. While the update was installing, I went about my business. I walked away for a few minutes and came back to a phone that just sat at the boot screen. I let it sit for about an hour, thinking that was some how normal. After an hour, I hard powered down and it came back to the same screen. I have rebooted at least 50 times now with no luck.
I can boot into fastboot, but not recovery. If I try to go into recovery, it goes to the boot screen and sits there. I have tried to switch partitions, it is stuck on A, without luck. The bootloader is locked and I can not remote unlock it via fastboot. Nor can I manually change the boot partition to B.
I have an open ticket with Essential, but they have been blowing me off and basically told me I'm out of luck since I was in their Beta program. They told me to go to XDA. A$$wipes! Any help you can offer is greatly appreciated since I'm stuck with a bricked phone and having to use an old iPhone since I cannot be without a phone.
Exact problem happened to me last week and a very helpful XDA member saved me.
Just hook up phone to pc by adb, type in 'fastboot devices' (while in fastboot mode) and install 7.1.1 os again. You'll lose everything but at least you won't be softbricked anymore.
Edit: sorry, just read you do not have unlock bootloader so this probably won't work.
Have you tried wiping data in while in fastboot? That might get it to boot.
Sent from my PH-1 using Tapatalk
You don't need an unlocked bootloader to sideload the install (following the BETA instructions: https://www.essential.com/developer/beta-builds
Since you can use fastboot, it looks like you have working ADB environment, so you should be able to follow those instructions. The STOCK recovery works very differently than TWRP, so make sure you follow those intructions, particularly the "Apply update from ADB" part. It took me a while to understand this, especially because the type on the screen is so tiny, I couldn't tell any words were changing.
I'm having the same issue (stuck on the boot logo "powered by android" screen) and I can get into fastboot mode, however if I try to go into recovery mode it just gets stuck on the boot screen again.
When in fastboot mode, the device state is "locked" is there any ways to get this fixed?
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
ilpolpi65 said:
You could try: (you will lose all your data)
fastboot -w
fastboot reboot
Click to expand...
Click to collapse
Here's what I've got
Code:
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: unknown command)
erasing 'userdata'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.002s
It's still having the same issue..
update im still stuckk
Have you tried booting to bootloader and mounting /system?
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
I also have my phone stuck The bot is closed and I can not do anything
V0idst4r said:
This is obviously corruption of the firmware, and has nothing to do with wiping userdata. Download the full firmware and flash all of it through fastboot.
Click to expand...
Click to collapse
I also have my phone stuck
The bot is closed and I can not do anything
Same here
It can't get passed the logo and I can't get any command in adb to go in fastboot. And recovery is a no go. Yay
Ph-1 stuck at boot, bootloader locked
kuyzz said:
update im still stuckk
Click to expand...
Click to collapse
We're able to fix the issue???

My PH-1 bricked ,I am so sad.What should I do?

question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]
[email protected] said:
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]
Click to expand...
Click to collapse
Can you boot to recovery and factory reset?
ktmom said:
Can you boot to recovery and factory reset?
Click to expand...
Click to collapse
no,the phone can't do this
[email protected] said:
no,the phone can't do this
Click to expand...
Click to collapse
Have you tried unlocking again in fastboot?
ktmom said:
Have you tried unlocking again in fastboot?
Click to expand...
Click to collapse
Yes,but it failed. remote is Flashing Unlock is not allowed .
[email protected] said:
Yes,but it failed. remote is Flashing Unlock is not allowed .
Click to expand...
Click to collapse
It sounds like the OEM unlock was turned off in developer settings.
If you can't get to recovery and you can't boot to be able to unlock again, you're stuck [emoji17]
This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader
HueyT said:
This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader
Click to expand...
Click to collapse
Exactly. This has been highlighted many times - relocking the BL after unlocking it once is a bad idea...
Shoot me a msg I May Be of help
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
Click to expand...
Click to collapse
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...
Aimless Rambler said:
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...
Click to expand...
Click to collapse
also failed……

Categories

Resources