Database Users

Corrupted (most likely) bootloader

Hello,
Tried to update to lollipop like the rest of the world..well, i should have waited
At first i just ran the flash-all.bat (edited so it didn't include erase userdata and the -w option)
fastboot threw all sorts of errors, too many links, invalid argument
then i tried to run manually the commands, same thing. Not all of them "worked" at once.
Unfortunately I don't have a log.
So now i have a N7 that won't boot past the Google screen
I can get to bootloader but it shows on device manager as Unknown USB device, Device Descriptor Request Failed, so fastboot doesnt help.
I can also get to stock recovery and use adb just fine.
Is there anyway to fix this? sideloading anything?

No system, no recovery, bootloader unlocked, FRP locked

After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!

CanIHelp said:
After some problems (corrupted data partition and sticking in bootloop after reboot) on LineageOS 14.1 and PA 7.2.2, I decided to reflash the EMUI. That didn't work and through a series of my mistakes I have no recovery, no system and can't flash anything.
Fastboot gives me the "remote: command not allowed" error whatever I try to do except for "fastboot reboot" and "fastboot oem get-bootinfo" (which says the bootloader is unlocked). The fastboot screen says : Phone Unlocked, FRP Lock.
I can connect to adb after a few minutes of waiting at the "Your device is booting now..." screen that also shows 3 options. But I have nothing in /system/, which means /system/bin/sh doesn't exist so I can't get a shell into the phone. "adb ls" does work, though (don't know how).
I've also tried to push at least a shell into /system/ with "adb push", but it says that the partition is mounted read-only. Is there a way to mount it read-write without using "adb shell"?
Is my phone recoverable or is it bricked beyond repair? Any suggestions on how to repair it without changing the motherboard?
Thanks in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/huawei-p9lite/how-to/unified-help-thread-huawei-p9-lite-t3649152
Post 5. Unbricking EMUI 5. Don't take for granted it will work, but considering FRP is locked, this is the only way not needing a unlocked bootloader.

Doesn't work. It's still stuck at the "Your device is booting now..." under the vmall link screen.
Isn't the 3-button method counting on the original recovery being in the recovery partition?
I only have the second recovery working (that eRecovery which only lets you "download and install the latest recovery and system"...and doesn't do anything).
Is there a way to override the frp lock? I saw a couple of tools online claiming to do that, but none worked. I haven't tried DC-Unlocker. If I'm gonna pay for it, might as well go to a service

Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.

Plug your phone on computer.
You see yellow advice? Appears automatically.
Juste after this advice, tip "fastboot reboot bootloader".
After, unlock your bootloader again "fastboot oem unlock YOUR_OEM_CODE"
Ok now shutdown and hold buttons for boot to TWRP recovery, if not appears, flash it on "fastboot flash recovery recovery.img"
Warning command not allowed on fastboot is 90% time du at bootloader unlocked (even if he says it's good)

dariomrk said:
Dload method uses the secondary recovery, It should be there if you press all three buttons.
From what i have heard, DC-Unlocker works.
Click to expand...
Click to collapse
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!

CanIHelp said:
It did boot in the secondary recovery (had to hold onto the 3 button for 3-4 minutes continuously). But it said that "Software install failed/ Incompatibility with current version. Please download the correct update package."
I'm now trying the B160 image in that thread. Wish me luck!
EDIT: It worked. The B160 image flashed using the three button method. I'm now at the setup screen. And the keyboard is there. (Also had the problem where I'd only have the voice input keyboard)
Thank you very much!
Click to expand...
Click to collapse
No problem mate, nice to hear you did it without problems.

[Help] Stuck on Android One Logo [locked bootloader]

Its a 64 gb A1 variant. Everything was stock. It was on stock pie (update via OTA). I never tried unlocking bootloader as well as flashing custom rom.
3 day ago when i using it,suddenly it turn off and stuck at android one logo. I can go fastboot mode by pressing power+volume down.
I try to flash stock rom using mi flash tool,but as my bootloader is locked it show error. :crying:
Please help me out,it is my daily driver. :crying:

Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.

punktnet said:
Use the fastboot oem unlock command and see what it does.
If the command is succesfully will trigger the factory reset of devices, but maybe you`ll get it to work.\
If the above command not working, maybe you can try to factory reset from recovery if you can boot into it.
In the end maybe a fastboot flash will do the trick.
Click to expand...
Click to collapse
I found this thread after i post this. Hope this will help me, though i am not try yet. I will update what happen. https://forum.xda-developers.com/showpost.php?p=78378088&postcount=43

use miunlock tool to unlock bootloader if you're not familiar with fastboot commands and as punktnet said unlocking bootloader will reset your device and erase your userdata and internal storage then maybe your device works fine if not then reboot it again in fastboot mode and flash stock firmware.

Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?

WORKMEISTER said:
Facing similar issue. Am able to flash via test point method however still stuck when device is rebooted with this message;
Supported API: 3
E: Failed to clear BCB message: failed to FSync/dev/block/bootdevice/by-name/miscperation not permitted.
Any other solution?
Click to expand...
Click to collapse
This occurred to me today aswell :c I tried wiping all the data from recovery but the phone couldn't even end to wipe all. My phone went into a "erasing" screen for almost 1 hour when I decided trying to hold the power button, it rebooted but I still got into the bootloop :l my Xiaomi Mi A1 is not unlocked for bootloader so I can't flash it. I also tried with the mi unlocking but didn't go past 50% when it launched an error. Guess I'll die.

[SOLVED] Bricked ALE-L21 | Damaged fastboot partition

So, I've had an issue with fastboot mode for some time, it reacted to everything with a "remote: command not allowed". I tried an sdcard upgrade to stock which did nothing, ran the oem unlock again and that said unlocked succesfully (it was aleady unlocked but ok) then tried to relock, tried to flash every stock image from B896 I knew the partition of - everything returned "remote: command not allowed", also did a fastboot reboot - which worked, if I remember correctly, enabled usb debugging and saved my computers key just to be sure - still no difference.
Later on, I tried reinstalling the fastboot image from the phone itself using dd - that was pretty stupid, I know - especially since there were two files named fastboot and fastboot1 but only one fastboot partition (I don't even, just had to try) and after a reboot it shows no logo, doesn't vibrate, only thing it does is blink the led red-green-green for a minute and power off again. I have a raw backup of the original partition but no way to restore it.
Does anyone know how to repair a diskdestroyer'd fastboot partition? I'm willing to try any risky methods, including disassembly and reflashing of the memory chip. Does someone have a model number for the built in flash storage?
Any help is much appreciated.

Xiaomi Mi A1 Boot loop, locked bootloader, Stock ROM, fastboot/recovery/edl

Hi,
my MI A1 froze and after hard switch off (pressing Power button x seconds) it was in a boot loop.
ADB was enabled, OEM unlock not...
Boot into Recovery and Fastboot does work...
... but flashing latest stockware (10.0.24.0) will not work:
recovery shows an error message:
E: failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: Operation not permitted
What I did, so far (working on win10, vmware):
- doing a lot of reading here (tnx for all the info!)
- installed android ubs and qualcomm drivers, platform tools, Mi Tools, etc.
0. Recovery "Wipe data & factory reset" did not work (trying, but with not returning after 1 hour)
1. Fastboot: MiFlash Tool and Stockrom -> "Remote: not possible, because of locked mode)
2. Fastboot: MiUnlock-Tool (Created Mi-Account): -> "No Token found" , so no unlock.
3. Qualcomm edl mode (test point) & MiFlash Tool: --> not possible, because of locked (?).
4. Boot to recovery & image on SD card (flash from SD card):
after getting errors "images are too old", I got the latest image on sd card and recovery tries to start flashing.
but the following error message shows up:
E: Error in /sideload/package.zip (Status 1)
5. Switch active Slot A/B also did not work.
What I did not:
- trying with other flash tools (Qualcomm), because of "fear" to make things even worse, when flashing files into wrong memory areas.
- using another prog_emmc_firehose_8953_ddr for the MI A1 (what will happen, if I use another 8853 file?).
recovery log shows:
>> recovery filesystem table:...
>> 0 / ext4 /dev/block/blockdevice/by-name/system_b 0
error messages also show skipped entry for partition "system" and "vendor"
so I guess, I have to restore "system_b" to get the "/sideload/package.zip" working, at least to reflash the device in total.
Now the question to the experts here:
Any way/procedure to restore the system_b with a locked boot loader (edl mode, perhaps)?
And then reflash fastboot or recovery Stock Rom
Is there a good howto for using different flash tools and/or emmc_firehose files?
Any hint is apreciated!
Tnx a lot in advance!