Database Develop

[Q] Not quite Bricked, but can't get anything but Fastboot

Ok, so I'll be the first to admit, I'm a bit new to all this.... I figured I was following directions, but something went amiss...
I was working through the process to put CM11 on my Razr i (which had the soak of 4.4.2 from Motorola on it...).
I unlocked the bootloader, rooted it, (but of course never made a back-up). I was able to put in TWRP into the recovery partition and attempt to flash the OS zip image - which failed.
In that thread, there were many options to try, which I did, and eventually my phone will either get stuck at the "Warning - Bootloader Unlocked" screen, or if I reboot with Power/VolDown I can get into Fastboot. But every option in Fastboot menu just reboots the phone.
I can get to the phone with Fastboot from the PC through USB - and it *looks* like I can re-flash different recovery images, but nothing seems to change. The Lebobo flasher will not flash to the device at all - keeps saying "waiting for device" with any option. I have the Motorola USB drivers loaded.
Not sure what else to try.....

Check your drivers again and even reinstall them. U will need the Motorola ones and maybe even the Google ones.
The lebobo flasher uses the 'fastboot' executable to interact with the phone in fastboot. Get a copy off the fastboot exe from the Index thread in the general section. If u have the fastboot.exe or 'fastboot' binary if u are on linux then reboot your phone in bootloader mode. Open a commandprompt in the directory where u have the fastboot executable (shift+right mouse button). Now do the command "fastboot devices" if your device shows up in it the drivers are correctly installed. If it doesn't it not. If it does, install a recovery by using the command "fastboot flash recovery recovery.img" assuming u renamed the recovery image to recovery.img.

i have the same probleme , my motorola razr i is stuck on warning ......... help me pleas:crying:

Verified Moto driver installed (reinstalled).
fastboot.exe is latest from Android SDK - api 21 version
fastboot devices shows "TA237059P0 fastboot"
fastboot flash recovery recovery.img looks like it works. on the PC says "OKAY" and finished. On the phone says Downloading.... then Flashing recovery ... but just sits there. Tried with 2 different Recovery images.
Forgot to mention - in command window on PC, when I use above commend - first thing that comes back "(bootloader) Variable not supported!"
If I use fastboot menu on the phone to then go to Recovery, the phone reboots and sits at the Warning screen again.
Lelobo still says "waiting for device" even though command line fastboot seems to connect to the device.

Wipe cache through fastboot and try again. It van help

fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s​
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)

ccallana said:
fastboot -w give the following....
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
(bootloader) Variable not supported!
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote failure)
erasing 'userdata'...
(bootloader) Creating EXT4 FileSystem for userdata
OKAY [ 13.707s]
erasing 'cache'...
(bootloader) Creating EXT4 FileSystem for cache
OKAY [ 2.902s]
finished. total time: 16.614s​
Then flashing recovery behaves same as above, except when I select it in the Fastboot menu, the phone just shuts off now (tried different recovery, now it reboots, stuck at Warning)
Click to expand...
Click to collapse
Success!! used "fastboot erase cache" instead.... then flashed in the suggested Newbie recovery on page 1 of the CM11 thread. adb wouldn't sideload the modded image, so I stuck it on an sd card and loaded it from there... and voila, it is booting!

Failed to flash TWRP.

Hi,
I tried to flash TWRP to my phone using the command: "fastboot flash recovery twrp-3.0.2-0-titan.img"
This failed and gave me a message saying "mismatched partition size (recovery)"
What can I do?

Deleted boot.img

I accidently deleted my boot.img on mi Mi 9 Lite (Mi CC9) by doing: fastboot boot "random file". What can I do now?

Can Someone please send me their boot.img or a link?
..

realseal3 said:
..
Click to expand...
Click to collapse
https://www.sendspace.com/file/nddami
:fingers-crossed:

Thank you very much but I get an error message:
Sending 'boot.img' (15360 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed

realseal3 said:
Sending 'boot.img' (15360 KB) OKAY [ 0.332s]
Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')
fastboot: error: Command failed
Click to expand...
Click to collapse
What's the rom you have, miui version?

miui_PYXISGlobal_V11.3.3.0.PFCMIXM_6a3205a4b8_9.0
I have this one but it didn't boot before I did anything.
lmt399 said:
What's the rom you have, miui version?
Click to expand...
Click to collapse

realseal3 said:
miui_PYXISGlobal_V11.3.3.0.PFCMIXM_6a3205a4b8_9.0
I have this one but it didn't boot before I did anything.
Click to expand...
Click to collapse
Bootloader unlocked/locked?
Maybe it is better to flash the whole system through fastboot or mi flash tool.

..

It didn't work with the tool but I reflashed twrp and flashed the stock miui rom from there and it worked. Thank you anyway.

Download Fastboot rom and extract, then copy system.img to fastboot folder and also recovery, boot.img too...
Open fastboot:
Type: fastboot format system
Type: Fastboot flash boot boot.img version that you have when you brick device
Type: Fastboot flash system system.img
Type: Fastboot flash recovery recovery.img use wzsx1050 3.3.1-0709 version
Type :Fastboot boot recovery.img and device should reboot in recovery, without Booting FAILED (remote: 'Failed to load/authenticate boot image: Load Error')

Problem with on-boot password led to partial brick, need help [r13]

Hey guys,
I dun goofed when trying to do a routine backup.
First off, I'm trying to recover this without wiping, as I have some 2FA apps and other things that have secret keys that can't be recovered unless I can decrypt the darned thing
Rebooted into TWRP in order to do an image backup before I upgrade from arter97's kernel r13 to r14.
When TWRP comes up, it surprises me with a password prompt (instead of pattern unlock which is what it should be)
Reboot to system to remove encryption and then fix the password issue, greeted by "To start Android, enter your password" prompt, again instead of pattern unlock
Tried the numbers-to-pattern trick, no luck. Basically locked out of the phone now
Booted back into TWRP, while looking around for other options, accidentally chose "Slot A" which has gotten me stuck back on the old recovery
fastboot commands no longer work properly (see below)
Sometimes the commands hang, and I need to ctrl+c and re-run. I get very inconsistent results, as you'll see below
Code:
D:\adb>fastboot.exe boot twrp-3.2.1-0-cheryl.img
Sending 'boot.img' (23120 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
Trying to re-flash the kernel just hangs:
Code:
D:\adb>fastboot.exe flash boot arter97-kernel-r14-20200428.img
Tried switching to Windows Terminal/Powershell and got slightly different error:
Code:
PS D:\adb> .\fastboot.exe boot .\twrp-3.2.1-0-cheryl.img
Sending 'boot.img' (23120 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe flash boot .\arter97-kernel-r14-20200428.img
Sending 'boot' (30176 KB) FAILED (Write to device failed (Unknown error))
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe getvar all
getvar:all FAILED (Write to device failed (Unknown error))
Finished. Total time: 5.004s
PS D:\adb> .\fastboot.exe --set-active=a
PS D:\adb> .\fastboot.exe --set-active=b
fastboot: error: Device does not support slots
PS D:\adb> .\fastboot.exe --set-active=q
Slot q does not exist. supported slots are:
a
b
PS D:\adb> .\fastboot.exe --set-active=a
Setting current slot to 'a' FAILED (remote: 'Invalid Slot')
fastboot: error: Command failed
PS D:\adb> .\fastboot.exe --set-active=b
Setting current slot to 'b' FAILED (remote: 'unknown command')
fastboot: error: Command failed
I'm sure the TWRP image is still there in slot b, but I can't get it to switch back.

Update:
I tried running the `fastboot --set-active=b` on a different (older) system which did finally work and allowed me to switch back over to TWRP, but I'm still having that decryption issue.
Anyone know why the encryption would suddenly switch from pattern unlock to "password" and how I could fix it?
Edit: After doing some more research on here, it sounds like my phone may have OTA'd itself to MR3 which may be the cause for the password issue.
Got an idea that I hope will work, which is to use the factory MR2 image, and comment out the lines for wiping data. Maybe that will bring it back?

Question NE2217 Can't unlock my bootloader

I got my token, hit oem unlocking. Rebooted to fastbootd mode, then I use fastboot flash cust-unlock. Which returns,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock_code.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
If I try it without cust-unlock I get,
C:\Users\James>fastboot flash C:\Users\James\Desktop\10pro\unlock_code.bin
unknown partition 'C:\Users\James\Desktop\10pro\unlock_code.bin'
fastboot: error: cannot determine image filename for 'C:\Users\James\Desktop\10pro\unlock_code.bin'
If I fastboot reboot to bootloader and do the same command I get,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock_code.bin
Sending 'cust-unlock' (0 KB) OKAY [ 0.002s]
Writing 'cust-unlock' (bootloader) Device is unlocked.
OKAY [ 0.004s]
Finished. Total time: 0.099s
But, that doesn't actually unlock my bootloader. Can someone please help?

Here's some more I have tried
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock C:\Users\James\Desktop\10pro\unlock_code.bin
fastboot: usage: unknown 'flashing' command unlock
C:\Users\James>fastboot unlock C:\Users\James\Desktop\10pro\unlock_code.bin
fastboot: usage: unknown command unlock

Edit:
Sequence of commands
Code:
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock

centifanto said:
Edit:
Sequence of commands
Code:
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock
Click to expand...
Click to collapse
I even renamed the file but here's what I got,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Then I moved the unlock.bin and same results.
I was able to hit oem unlock so it shouldn't be sim related, but thanks for helping

Grin59 said:
I even renamed the file but here's what I got,
C:\Users\James>fastboot flash cust-unlock C:\Users\James\Desktop\10pro\unlock.bin
Sending 'cust-unlock' (0 KB) FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed
C:\Users\James>fastboot flashing unlock
FAILED (remote: 'Unrecognized command flashing unlock')
fastboot: error: Command failed
Then I moved the unlock.bin and same results.
I was able to hit oem unlock so it shouldn't be sim related, but thanks for helping
Click to expand...
Click to collapse
Four things:
Name of file doesn't matter
SIM unlock and bootloader unlock are separate things
Move the unlock.bin to the same folder as your platform tools so you don't have to put the entire the path. Or put it in quotation marks
Is fastboot in your system PATH? If not, prefix fastboot to look like this
Code:
./fastboot.exe

Also, what does the following command return?
Code:
fastboot devices

centifanto said:
Also, what does the following command return?
Code:
fastboot devices
Click to expand...
Click to collapse
C:\>fastboot devices
*serial number* fastboot
Also not too sure what you mean, "Is fastboot in your system PATH? If not, prefix fastboot to look like this"
But it is installed to my system drive. Even tried downloading new platform tools and trying it in my root drive of C:\

No worries. If you got the "5497b039" returned it means fastboot is working for you and your device is in the correct bootloader mode.
Does your device display "locked" in red letters?
Are you sure that "OEM unlock" is still toggled in the developer settings?

centifanto said:
No worries. If you got the "5497b039" returned it means fastboot is working for you and your device is in the correct bootloader mode.
Does your device display "locked" in red letters?
Are you sure that "OEM unlock" is still toggled in the developer settings?
Click to expand...
Click to collapse
Okay so I got it, thank you for the help.
Did the commands you sent in the bootloader menu, guess I missed the second.
For anyone who can't unlock the bootloader I'll post simple instructions, on the NE2217
OEM unlock - on
adb reboot bootloader
fastboot devices
fastboot flash cust-unlock unlock.bin
fastboot flashing unlock
anyone can add anything else