Hello. Out of nowhere, phone throws the "Cant load Android system. Your data may be corrupt" error everytime it tries to boot. The only choices are to retry (that obviously doesn't fix everything) or perform a factory reset. The problem is that i need to try to recover the data from the phone. It can boot to fastboot mode and is detected by the pc, but the bl is locked. Is it possible to do anything without an edl cable?
Related
Hi, I need help with my huawei p9, when I power up and the system start, a screen says Encryption Unsuccessful, and that I should do a factory reset for resume using the phone. I do the cleaning in TWRP and I install fRomFuture - NewWorld V4.1, the installation is performed without errors, but the message remains.
How could resolve this situation?
PS: sorry for my English
I have similar problem
Hi, I have the same thing here, but it has stock recovery, which I can't boot into. I can get to Encryption unsuccessful screen and to fastboot. It is customers phone, he was messing around with SW, and I think he didn't allow oem unlocking, debbugging is disabled aswell I think. I can't flash anything to it, whatever I try I get 'FAILED (remote: command not allowed). Tried force-flashing it via SD card, it gets stuck at Huawei logo. Any thoughts? Or to tell him to use it for smashing nuts?
Hello everyone, it's my first time writing here, but I’ve tried everything, searched everywhere, and am desperate for help.
I screwed up big time while trying to flash a custom rom on my nem-l21, as I successfully did before with my xiaomi... So what I did:
I managed to unlock bootloader with dc unlocker. Then I got stucked flashing twrp with adb tools. Everything was looking to be fine, no error messages, “flashing successful”… But, I was never able to boot into flashed twrp. Always got stuck on “your phone has been unlocked blah blah. Your device is booting.” It never booted, not in twrp, nor in stock recovery. I tried different versions of twrp from different sources, always same result (flashing successful, booting into recovery not). Booting into the system was fine. And then I made that horrible mistake. Oh, how I wish I didn’t!!
I read on some website, that you are supposed to flash the twrp as boot.img, not as recovery.img. Seemed illogical and stupid to me, but in the end I tried it. Of course, this just bricked my phone, with no possibility to boot. After hours of googling, installing, trying and crying, I managed in the end to flash back stock boot.img. But at that time, I didn’t know my build number (b359), and I flashed boot.img b351. So now I have a phone which boots into the system b359 with boot.img b351, but with lot of errors.
- developer options, security options, display and factory reset option doesn’t work and just crashes. Therefore I am not able to flash the correct boot.img b359 or anything else at all from pc, no way to enable usb debugging and oem unlocking. Adb devices → nothing. I am able to use fastboot (fastboot devices sees the phone), but when try to flash something, I get error “command not allowed”. Also I can’t enable unknown sources installation, which bothers me a lot. And I can’t make factory reset to restore the crashing settings. Also I can’t change display timeout, and original 30 secs is super annoying.
- I am not able to uninstall even apps installed by me, always just restarts system UI and app stays.
What I tried so far:
- flashing correct boot.img from pc, not working because of dev options crashing
- go into recovery, but stock one is overwritten with unfunctioning twrp, always just get stuck on “your phone was unlocked blah blah… your device is booting now”, but it never does, have to hard reboot
- go into huawei erecovery, which is working, but when I try to resolve problem from there, always ends up with errors and crashes
- connect to pc and use HiSuite, system recovery tool here always says “no problem detected”
- updating to b361 through system update settings, always crashes on 5% and sends phone into “your phone was unlocked blah blah… your device is booting now” error
- downloading the proper b359 as and update.app file, put it in dload internal storage → same error during update, put it in dload sdcard → same error, no matter which way I use to start the update
- boot into twrp or stock recovery.img through fastboot without actually flashing it, anyway error “command not allowed”
- do factory reset or update through dial codes (i.e. *#*#123456#*#* …), nothing worked
My pc is windows 10, all drivers up to date. Using powershell as an admin. Am an idiot for not making backup of the phone before I started...
So, now I have more or less functioning phone, but I can’t uninstall any apps at all, can’t install from unknown sources, can’t do nothing from pc, can’t make any update, and lot of important settings keep crashing.
I can use the phone like this, but if somebody could think about some solution for this ****ed up situation I got myself into, I would be grateful to him/her for the rest of my life.
Sorry for a long post.
Thank you in advance and have a nice day
I think using Hisuit will help. Enter Fastboot and connect ur phone to ur computer and use system recovery toll
Hi,
so i got a situation here that xiaomi mi a2 (6x) out of nowhere rebooted to factory recovery with message "cant load android system. your data may be corrupt. If you continue to get this message you may need to perform factory reset deleting all data stored on this device"
Now after turning it off and on, it shows black screen "failed to boot" with option to power off or restart.
When restarting it goes to factory recovery again with that message and option to factory reset or try again (restart)
Now i cant perform factory reset before backing up the data, but i cant find the way to backup.
There is no custom recovery to download files from phone. When tried to flash custom recovery found out i cant because bootloader locked. And when found the way (dont know i it works) to unlock it without loosing data - cant do even that because developer options must be enabled to allow unlocking and debugging, so i get message in adb console FAILED (remote: Flashing Unlock is not allowed.
Is there any other way to keep the data before doing factory reset ?
Maybe try to flash with miflash keeping the data
blazessdd said:
Maybe try to flash with miflash keeping the data
Click to expand...
Click to collapse
unfortunately miflash cant do anything with locked bootloader as well. Just when starts to flash, gets error with bluetoth_a.
After research i noticed that miflash does nothing special at all just automated flash commands. In rom directory you can find flashing .bat files and run them in adb console.
When did that got all the data log, that bluetooth a is the first file that is tried to flash and stuck on locked bootloader.
Hello. Did you manage to solve your problem?
I have the same saituation.
Hi, unfortunately the only way i found is EDL mode.
https://youtu.be/i3OU4DOd7aY
When you keep those pins shorted, plug usb to your pc, and then , simply said, pc sees it as another device that can be flashed with everything locked.
So i flashed with miflash with keeping files option, but all that was saved is locking pattern. All media files lost.
Anyway, now i rooted and installed custom recovery to avoid any incident like this.
andjar said:
Hi, unfortunately the only way i found is EDL mode.
https://youtu.be/i3OU4DOd7aY
When you keep those pins shorted, plug usb to your pc, and then , simply said, pc sees it as another device that can be flashed with everything locked.
So i flashed with miflash with keeping files option, but all that was saved is locking pattern. All media files lost.
Anyway, now i rooted and installed custom recovery to avoid any incident like this.
Click to expand...
Click to collapse
you should edited rawprogram0.xml to not flash userdata (for saving your data)
Well if i only had this info 2 moths ago...
At leats others with this problem can find solution here now.
So here's the thing. The phone was kinda fuzzy, cause it didn't load an App. So I tried to turn it off and on again.
Aaand then it was kinda bricked. The phone is starting but it just flashes the Mi Logo. Afterwards it shows black Screen.
I can't boot up into my recovery. i tried it via fastboot reboot recovery. i also can't boot into an twrp-santoni.img because the Bootloader is locked. i can get fastboot running but i'm not allowed to do anything.
Is the only way to get my phone up and running again to flash it via PIN forced EDL?
Is there another way to access the Data on my Phone?
Can I still access the Data or at least clone the partition? I want to keep the files!
Does any1 know a lil?
Best Regards
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Is it a Guide?
Oh, now, its a Great News!
Please delete this post from this forum.
As I have already wrote to you, questions should go to "Questions and Answers" forum.
And as I have already wrote to you, Search works here, and if you've used it, you'd get answers (in mentioned above forum):
1. MiA2 having A/B slots architecture, - is supposed to recover to the other slot X when OTA corrupts ROM is slot Y, - after numerous boot attempts.
2. In case you have tampered phone with try-and-see operations without knowing what you were doing - the only way to recover phone is: TEST Point / EDL. Search these keywords in this forum for appropriate Guide.
try the "fastboot continue" command
dillu12 said:
Hi Guys,
My MI-A2 is stuck in bootloop ( When I turn on my phone it shows its Android One logo and then it shutdown itself ).
In my phone, I didn't turn on any USB Debugging or and OEM unlocking. and now it is possible as the phone is not starting.
I am able to access fastboot and recovery options
I tried to do factoryReset the device from the recovery option but it is just wiping the data.
here are the following things which I have tried with fastboot.
- I tried to unlock the fastboot with MiFlashUnlock but it stops at 99% and gives me the error of unable to verify the device,
- flashing the Stock ROM isn't working with MiFlashTool. giving random errors.
- tried changing the drive partition. it gives error to unlock the device first.
- tried tried to flash TWRP but it also gives me the error of unlocking the device first.
Almost every command of Fastboot is giving me some kind of error
But I am able to access the ADB Sideload from the recovery option.
- I tried to load the April OTA update from ADB Sidelode. The update is Successfully installed. But the device is still in bootloop.
Saving User data is not my priority. I just want the device to be working anyhow. As per my assumption, Fastboot is not an option for me unless it unlocked. I think something from the ADB sideload can be done.
Any help will be appreciated.
Click to expand...
Click to collapse
you need to flash the phone in edl mode
**just be careful there is a timeout ..when you put it into edl you need miflash and rom.loaded
*** download a stock fastboot stable pie for jasmine
**** unzip amd select revelant xml from within miflash
*****on phone manually boot to fastboot mode with buttons
****** run command "fastboot oem.edl"
*******device will boot to black screen ... immediately go to miflash and press the button to start flashing
___BE CAREFUL__ select clear all tick box at bottom of miflash screen
this should be enough to rescue your device regardless of what you've done or whether you unlocked bootloader or not