Database Develop

Bricked razr i Hellp

(Before, sorry for my bad english, I'm Poland..)
I've receive my Razr i xt890 yesterday and today I have unlock the bootloader. i root.exe
Everything happen very good, my bootloader is unlock but when my phone reboot it'll go to fastboot over and over again.
In fastboot, I can see :
"AP fastboot flash moide (secure boot)
20.00 (sha - bdfb943)
IFWI info 42.21
eMMC info
battery (okay) 4.18v
connect USB data Cable
ROM-key : motorola -key
Boot mode selection menu:
- normale powerup FAILURE crashes
- recovery FAILURE crashes
- factory FAILURE crashes
- BP tools FAILURE crashes
- switch console [default: null] work
- power of " work
And, it's written in yellow :
dismatched partition entry array crc32
" fastboot reason : sticky bit fastboot
fastboot : max download size: 100MB
In addition, the vol down button work for scroll, but the vol up button work, so, I can't select boot mode selection.. crashes
Rsd lite USED to flash CFC_signed_customer_8.7.1I-110_IFW-DE-31_RTEU.xml
There is an error ---- fAILED FLASHING PROCESS . 3/11 FLASH MOTOBOOT "MOTOBOOT" - PHONE RETURNED FAIL
And, it's written in yellow ITS FHONE:
Getvar max-download -size
downloading...
Flashing gpt ...
OEM fb_mode_set
Getvar max-download -size
downloading...
E: Downgarded security version for logo
fastboot command failed
Is there a solution please?
Help me please!!!!!

Why have you copy this post?! : http://forum.xda-developers.com/showthread.php?t=1945176
Your phone isn't brick if you can go into fastboot mode.
To repair your phone you have to flash a homemade fastboot with a command on cmd, like that: fastboot flash boot "name of your boot".img
Go on the link and read the thread , all is explain.
Good luck and don't worry your phone isn't dead

PELLET Nolwenn said:
Why have you copy this post?! : http://forum.xda-developers.com/showthread.php?t=1945176
Your phone isn't brick if you can go into fastboot mode.
To repair your phone you have to flash a homemade fastboot with a command on cmd, like that: fastboot flash boot "name of your boot".img
Go on the link and read the thread , all is explain.
Good luck and don't worry your phone isn't dead
Click to expand...
Click to collapse
Do not look at this post I copied my description of a test in different ways. Compare that everything is copied.
FOR IN cmd fastboot me wondering. And nothing helps.

rymaz said:
Do not look at this post I copied my description of a test in different ways. Compare that everything is copied.
FOR IN cmd fastboot me wondering. And nothing helps.
Click to expand...
Click to collapse
if you still need help pm me. i speak polish

[Q] help bootloader & root

hello,
I buyed a moto g, it's my first smarthphone...
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...

RastaFATian said:
hello,
I buyed a moto g, it's my first smarthphone...
I followed this tuturial http://forum.xda-developers.com/moto-g-2014/development/guide-root-moto-g-2nd-gen-2014-t2874245,
I get to unlock the bootloader, but when I get to this point
4. Flash Recovery through fastboot mode/bootloader mode
and Go into your adb+fastboot folder and Type in CMD prompt
Command :
Code: fastboot flash recovery TWRP2801-titan-motog-2014.img
can't get the moto g in flash recovery mode, it appear a dead android with a RED ! TRIANGLE...
any idea to resolve this...
Click to expand...
Click to collapse
#If U Successfully unlocked ur Bootloader then,
place the recovery image in the same directory as fastboot.
Open a terminal on your PC and reboot the device into fastboot mode by typing
adb reboot bootloader
or by using the hardware key combination
(press & hold Volume down and power button When phone is off)
#Once the device is in fastboot mode, verify your PC sees the device by typing
fastboot devices
If you don't see your device serial number, and instead see "<waiting for device>", fastboot is not configured properly on your machine.
#Flash recovery onto your device by entering the following command:
fastboot flash recovery your_recovery_image.img
where the latter part is the filename of the recovery image.
Once the flash completes successfully, reboot the device into recovery to verify the installation. Boot to recovery instructions: Hold Volume Down & Power simultaneously. On the next screen use Volume Down to scroll to recovery and then use Volume Up to select.

I successfully installed twrp recovery system but I can't do any backup, the system reboot in the process...

flash the recovery again and try...

jbanti said:
flash the recovery again and try...
Click to expand...
Click to collapse
It's not my fault.... seems a bug of twrp
XT 1068 UK
TWRP 2.8.0.1 Back up fails to both internal and external SD.
When external selected, backup starts but after 10 to 30 seconds it reboots the device. It starts to back up files and then just reboots. If I don't select compress backup, then it starts to backup more files before it reboots. Seems to be time related. Also tried unplugging while backing up and same issue.
Folders get created in all cases for external SD but data files. Not sure where the log files would get stored. Suspect they don't get created as the system reboots during the backup

Trying to backup stock recovery and boot, then stuck in boot logo...

I need some urgent advice. I was following this guide https://forum.xda-developers.com/le-2/how-to/guide-unlocking-rooting-restoring-to-t3515555 to backup stock recovery and boot. I did not want to flash twrp and su, so I skipped to wipe Dalvik/Cache, did that, and reboot from twrp.
Then the phone stuck in boot logo, I've waited at least 12min, nothing. So I tried to restart from stock recovery as stated in the guide, no good.
Basically I skipped step 16-20:
Download and install Minimal ADB and Fastboot: http://forum.xda-developers.com/show....php?t=2317790
Download latest official TWRP, place file in ADB installation folder, and rename to "twrp.img": https://twrp.me/devices/leecole2.html
Download SuperSU 2.78 (stable): https://download.chainfire.eu/1001/
Boot up phone and plug into computer
Settings > scroll to bottom to "About phone" > touch "Build" 7 times to enable developer options
Developer options > toggle "OEM unlocking" and "USB debugging" so that they're both enabled
When "Allow USB debugging?" window pops up on phone, check "Always allow..." box and hit OK
In Minimal ADB installation folder, hold Shift and right-click "Open command window here", then type:
Code:
adb reboot bootloader
Once in fastboot:
Code:
fastboot oem unlock-go
fastboot boot twrp.img
If password screen comes up, tap "Cancel" button
If it asks, tap "Keep Read Only" button (probably doesn't matter, but whatever)
Wipe > Format Data
Make backups (I suggest boot, recovery, and system since this will allow you to return everything to stock later on)
Mount > Enable MTP
Copy entire TWRP folder from internal storage to your computer
Copy SuperSU zip from your computer to root of internal storage
Reboot > Bootloader
Code:
fastboot oem unlock-go
fastboot flash recovery twrp.img
Hold Vol+ and Pwr until boots into TWRP
Swipe to Allow Modifications
Install > select SuperSU zip > swipe to flash
Wipe Cache/Dalvik
Reboot (first boot will take a little while, so be patient)
Click to expand...
Click to collapse
Please help!

Hi, unfortunatelly I have the exactely same problem.
I boot to TRWP > wipe Format Data > did backup and restart.
Then my LeEco Le 2 X527 stuck on the booting LeEco logo. I've tried to Pwr+Vol Up and selected all the checkboxes to do stock factory reset but it didn't help.
Also, it seems I cannot use ADB, fastboot and TWRP any more, because after the Wipe the device is unauthorized
Did I brick the phone? Please help dear professionals!
Update:
I found that I can still boot to the bootloader by holding Pwr+Vol down. After that I was able to normally use "fastboot oem unlock-go" and
"fastboot flash recovery twrp.img" to flash the TWRP. After I installed the LineageOS and GAPPS and phone boot up successfully!

Mi A2 Can't flash anything via fastboot (bootloader unlocked, oem critical too)

When I flash TWRP
It shows me this
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
PS C:\adb>
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
Code:
PS C:\adb> fastboot boot recovery.img
downloading 'boot.img'...
FAILED (command write failed (Too many links))
finished. total time: 0.003s
PS C:\adb>
I try to use another way
Code:
PS C:\adb> fastboot devices
******** fastboot
PS C:\adb> fastboot getvar current-slot
getvar:current-slot FAILED (command write failed (No such file or directory))
finished. total time: 0.000s
PS C:\adb>
But without fastboot devices
Code:
PS C:\adb> fastboot getvar current-slot
current-slot: a
finished. total time: -0.000s
PS C:\adb> fastboot flash boot_b recovery.img
sending 'boot_b' (41314 KB)...
FAILED (remote: unknown command)
finished. total time: 0.000s
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
-------------------------------------------------------------
UPDATE!!
I just use a USB2.0 Port (USB HUB)
and I got the problem solved!!!!

You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......

bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(

same problem here , please help anyone

cs853120 said:
I'm using the TWRP For jasmine from this thread
also tried this too
I have my usb debugging on already and I also tried to lock my bootloader then unlock it again
the problem still there
(
Click to expand...
Click to collapse
reset your phone once then try........also try to unlock your boot loader & see if you can flash the stock rom from the official website......make sure that the entire rom file is in a folder on your desktop.......for some reason MI flash does not like long system paths.....

cs853120 said:
When I flash TWRP
It shows me this
and my mi a2 turned in to black screen and shows "press anything to shutdown" on the upper left corner
if I didn't use fastboot device first it shows me this
I try to use another way
But without fastboot devices
already changed 3 different cable and try 8 usb port on my computer
tried adb installer 1.3 and 1.4.3
updated my Mi Usb Driver
I have never flash any a/b slot device before I have no idea what's going on
any my mi a2 still can boot into system and stock recovery
any solution please
sorry for my bad English.
Click to expand...
Click to collapse
Hi there.
I have the same problem. Can't do anything with my phone on any USB 3.0/3.1-Port on my Ryzen desktop (works neither on Win10 nor Linux Mint). I have to use my old Win8.1 Intel laptop and there everything works flawlessly but only on the USB 2.0 port. I used the same tools/commands/Mi-drivers but it only works on the laptop. Tried different drivers for MB/USB-host controller and different cables but to no avail... Connecting the phone and mtp works but no adb/fastboot.
I read on different threads that other people have the same problem with other hardware setups but most of them were able to fix it with MB drivers from the manufacturer instead of the Windows ones. Maybe that could work for you.
For now I keep the laptop around for flashing my A2....

whenever you get "press any key to shutdown" on fastboot it's because of the usb port, use usb 2.0

I have the same problem , and change to 2.0 USB Ports works! Thanks!

Did you found a solution?

Please help. Facing exact same issue. Tried all USB ports on my PC. Switched between Ubuntu and Win10. All to no avail.

It's a USB 3 problem. I had it too in my laptop. You gotta find a USB 2 port, maybe in another PC. Good luck.
Sent from my Mi A2 using XDA Labs

i was also fasing same problem so what is did is
fastboot flashing unlock_critical
then
fastboot oem edl
and flashed stock

Mi A2 Boot loop
The first thing you'll want to do here is extract the factory images archive that you downloaded from your manufacturer's website. For that part, I'd recommend using 7-Zip, as it's free and works with most archive formats , move all of the contents of the archive to the platform-tools folder inside of your ADB installation directory, then open an ADB Shell window in this folder.
Flash the system images individually. This method takes some extra work, but it can be used to un-root, update, or un-brick your device without losing existing data.
Start by extracting any additional archives from the factory images package. Sometimes, factory images packages can contain a series of three or four nested archives, so make sure to unzip all of them. From there, copy all of the image files to the main platform-tools folder—in other words, don't leave them in any sub-folders.
there are two images that you can get rid of: cache.img and userdata.img. These are the images that will overwrite your data and cache with blank space, so if you don't flash them, your existing data will remain intact.
Of the remaining images, six make up the core elements of Android: boot, bootloader, radio, recovery, system, and vendor.
The boot image contains the kernel, so if you just want to get rid of a custom kernel that's causing issues with your device, you only have to flash this one. To do that, type the following command into the ADB shell window:
//
fastboot flash boot <boot image file name>.img
//
Next is the bootloader image—this is the the interface that you're using to flash images with Fastboot commands. So to update your bootloader, type:
fastboot flash bootloader <bootloader image file name>.img
//
Once you've done that, you should reload the bootloader so that you can continue flashing images on the newer version. To do that, type:
fastboot reboot-bootloader
//
After that, we have the radio image. This one controls connectivity on your device, so if you're having problems with Wi-Fi or mobile data, or if you just want to update your radio, type:
fastboot flash radio <radio image file name>.img
//
Then there's recovery. This is something you may or may not want to flash, depending on the modifications you've made. For example, if you've installed TWRP custom recovery, flashing this image will overwrite your modification and replace it with the stock recovery interface. So if you're just updating your modded device, you should skip this one. Otherwise, if you plan to keep your phone stock and want the newer version of stock recovery, type:
fastboot flash recovery <recovery file name>.img
//
Next up is the big one: The system image. This one contains all of the files that make up the actual Android OS. As such, it's the most essential part of any update.
However you may not be updating your phone. You may just be re-flashing the stock firmware to recover from a soft brick. If this is the case, the system image is often the only image you need to flash in order to fix everything, because it contains the entirety of Android. In other words, if you flash this image and nothing else, it will undo any changes you made with root access and put everything back the way it was.
So as a cure-all in most soft brick situations, or as a method for getting the core part of an Android update, type:
fastboot flash system <system file name>.img
//
Finally, there's the vendor image. This is only present on newer phones, so don't worry if it's not in your factory images package. But if it's there, it contains a few important files, so type the following line to get this partition updated:
fastboot flash vendor <vendor file name>.img
//
After you've sent any or all of the above commands, you'll be ready to restart your device and boot into Android. To do that, type:
fastboot reboot
/
Thanks to Android gadget hacks .
P.S : Including today , it was 22nd time that i rooted , enabled camera2api .. but i think till know its useless .

After dealing with this issue for a long time I found that using a USB hub solved it for me.
This is the one I'm using: https://es.aliexpress.com/item/USB-...342.html?spm=a2g0s.9042311.0.0.1d6e63c04tJJe6
Hope this helped!

the same problem
have tried all USB port, unfortunately, no success

Hi everyone,
Today I have a big problem
I install jasmine__V10.0.8.0.PDIMIXM and after I set "fastboot oem lock" but Now my MI A2 Can't enter in OS.
I have this message on screen
"Your device has loaded a different operation system"
and another page says
"Your device software can'tbe checked for corruption. Plese lock the bootlader.
But when I check in fastboot I have bootloader locked.
Any suggestion to unlock ? I can't enter in OS.
Thanks

HELP
bladehunter said:
You are using the wrong recovery....check if developer op is on & usb debugging is enabled....also try to unlock you bootloader again......
Click to expand...
Click to collapse
Can you help me with my thread?? Thank you!

Same error.

Download TWRP and TWRP installer
DONT CONNECT YOUR PHONE!!
Put your phone in Fastboot
in cmd type
fastboot boot twrp.img (twrp name instead of twrp.img)
Then when you see <Waiting for Device> connect your phone !
Check if it's working.
This was fix for me, when I was unable to even boot into recovery.
Once you boot into recovery, wipe everything, flash twrp zip, and error should be gone

Hey guys,
same issue here but i don't have any usb2.0 port on my laptop now. Any workaround? Totally sure that i used fastboot + usb3.0 on Sony, LG, Samsung ROMs with no hassles whatsoever. Is this only happening with Xiaomi?
Cheers

Help me recover my motorola g5s plus Android phone

Hi All,
I need help from you experts to recover my phone moto g5s plus
Type : M271C Model : XT1806
The phone was working without any issues but suddenly got restarted and now i's stuck in the "Fast Boot Flash" Mode.
It cannot boot and the "Boot Loader Log" screen says below.
"Start Up Failed:
Your Device did not startup successfully.
Use the software repair assistant on computer to repair your device.
Connect your device to your computer to get the software repair assistant.
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason : Fall Through from normal boot mode
USB Connected"
1. I installed the "Rescue and Smart Assistant" software and tried to recover from there but unfortunately it does not recognize my phone model.
2. Tried to install Install TWRP Custom Recovery tool. But I cannot do it because the "USB debugging " is not enabled on the phone.
3. 'USB debugging"and "OEM Unlock" on my Android device is not enabled so I cannot Unlock Bootloader
Is there any way that I can boot into recovery or install a custom ROM without having the "USB Debugging" and "OEM Unlock" Enabled in my phone?
Thanks

Are you using adb for recovery?

andres_vacal said:
Are you using adb for recovery?
Click to expand...
Click to collapse
No. ADB cannot be used since my device is not enabled "USB Debugging"

USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Try "fastboot reboot recovery"

andres_vacal said:
USB debugging should not be required to unlock the bootloader as you are using fastboot commands to unlock the bootloader rather than ADB commands.
Try "fastboot reboot recovery"
Click to expand...
Click to collapse
I get following error when I run that command.
Rebooting into recovery FAILED (remote: 'Unknown command')
fastboot: error: Command failed

dharshana1 said:
I get following error when I run that command.
Rebooting into recovery FAILED (remote: 'Unknown command')
fastboot: error: Command failed
Click to expand...
Click to collapse
Okay, I think I untherstand whats happening. Its probable that any way or another you deleted your recovery or directly your ROM.
So i´ll recommend you to download and run TWRP(You can look out on the internet for your specific device)
If it runs correctly, go to reboot and check out if in the top part says "No OS installed", if it says that, then you will have to lock out for a compatible ROM and instal it.
If you have any thoughts let me know how it goes..

andres_vacal said:
Okay, I think I untherstand whats happening. Its probable that any way or another you deleted your recovery or directly your ROM.
So i´ll recommend you to download and run TWRP(You can look out on the internet for your specific device)
If it runs correctly, go to reboot and check out if in the top part says "No OS installed", if it says that, then you will have to lock out for a compatible ROM and instal it.
If you have any thoughts let me know how it goes..
Click to expand...
Click to collapse
Hello,
Thanks for the reply, I tried to install the TWRP tool that is for my specific device, but it won't allow me to install since "USB debugging" is not enabled in my device.
Is there any other way to install that without USB debugging enabled?
Thanks

Okay, so i´ll try to explain in detail how to install TWRP via Fastboot commands (No usb debugging needed since you are using fastboot)
1. Make sure you have all the specific drivers for using fastboot.
2. Type "fastboot devices" and make sure your device appears on the command prompt
(it should apper something like "5f684fe2").
3. Type "fastboot erase recovery" to make sure the old recovery is no longer avaiable in your device.
4. Send the TWRP.img file that you already have to the adb folder you are using on the command prompt
5. Type "fastboot flash recovery TWRP.img" ("TWRP" is the recovery´s name you have saved)
6. Tyoe "fastboot reboot recovery" and see if TWRP is now installed.
Important note: Make sure you have saved all the important files from your phone.
If this doesn´t fuction, after you make step 2 succesfully:
Type these 3 commands:
"fastboot erase system"
"fastboot erase data"
"fastboot erase cache"
and "fastboot reboot"
Then repeat the instalation process.

andres_vacal said:
Okay, so i´ll try to explain in detail how to install TWRP via Fastboot commands (No usb debugging needed since you are using fastboot)
1. Make sure you have all the specific drivers for using fastboot.
2. Type "fastboot devices" and make sure your device appears on the command prompt
(it should apper something like "5f684fe2").
3. Type "fastboot erase recovery" to make sure the old recovery is no longer avaiable in your device.
4. Send the TWRP.img file that you already have to the adb folder you are using on the command prompt
5. Type "fastboot flash recovery TWRP.img" ("TWRP" is the recovery´s name you have saved)
6. Tyoe "fastboot reboot recovery" and see if TWRP is now installed.
Important note: Make sure you have saved all the important files from your phone.
If this doesn´t fuction, after you make step 2 succesfully:
Type these 3 commands:
"fastboot erase system"
"fastboot erase data"
"fastboot erase cache"
and "fastboot reboot"
Then repeat the instalation process.
Click to expand...
Click to collapse
Hi,
Thank you so much for the reply. I can see a device when I run the "fastboot devices" command. But when I tried above other commands (fastboot erase ...) they failed with below error.
Erasing 'recovery' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'system' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
Erasing 'data' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
when I run the fastboot erase cache command below error throws
Erasing 'cache' (bootloader) Failed to erase partition
FAILED (remote: '')
fastboot: error: Command failed
Thank you for your time helping me resolve this issue, anything else that I can try out?

Okay so I think your phone´s bootloader is locked.
So try this out: https://forum.xda-developers.com/t/...der-root-and-recovery-for-the-moto-g.3418432/ (Unloock bootloader section)
Hopefully it will get your bootloader unlocked and then you will be ready to do the process I posted before.
This is going harder than I thought.

dharshana1 said:
Hi All,
I need help from you experts to recover my phone moto g5s plus
Type : M271C Model : XT1806
The phone was working without any issues but suddenly got restarted and now i's stuck in the "Fast Boot Flash" Mode.
It cannot boot and the "Boot Loader Log" screen says below.
"Start Up Failed:
Your Device did not startup successfully.
Use the software repair assistant on computer to repair your device.
Connect your device to your computer to get the software repair assistant.
AP Fastboot Flash Mode (Secure)
failed to validate boot image
ERROR: Failed to pass validation, backup to fastboot
Fastboot reason : Fall Through from normal boot mode
USB Connected"
1. I installed the "Rescue and Smart Assistant" software and tried to recover from there but unfortunately it does not recognize my phone model.
2. Tried to install Install TWRP Custom Recovery tool. But I cannot do it because the "USB debugging " is not enabled on the phone.
3. 'USB debugging"and "OEM Unlock" on my Android device is not enabled so I cannot Unlock Bootloader
Is there any way that I can boot into recovery or install a custom ROM without having the "USB Debugging" and "OEM Unlock" Enabled in my phone?
Thanks
Click to expand...
Click to collapse
Just got the same issue..
Did you get it resolved?

andres_vacal said:
Okay so I think your phone´s bootloader is locked.
So try this out: https://forum.xda-developers.com/t/...der-root-and-recovery-for-the-moto-g.3418432/ (Unloock bootloader section)
Hopefully it will get your bootloader unlocked and then you will be ready to do the process I posted before.
This is going harder than I thought.
Click to expand...
Click to collapse
Well this guy has given same steps , but while unlocking bootloader
fastboot oem get_unlock_data
is not working at all, its giving same error which @dharshana1 has mentioned before.
I'm using this cell last three years, it started acting slow all of a sudden and then this thing has happened.

smandar said:
Well this guy has given same steps , but while unlocking bootloader
fastboot oem get_unlock_data
is not working at all, its giving same error which @dharshana1 has mentioned before.
I'm using this cell last three years, it started acting slow all of a sudden and then this thing has happened.
Click to expand...
Click to collapse
I worked with this model 3 weeks ago, and the thing is that in order to unlock bootloader you will need to go to motorola´s web page for getting a password. in this thread you will find how it goes. I untherstand that amazon's versions are unable to unlock bootloader so if you are into that version, bad luck.