Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Ye, great chance that the emmc is damaged. But it still looks to me as if it is software damaged, not hardware, because of the successful flash of recovery. And it is on the same memory module.
Just as in the other post of this phone can u try this and give me the output of especially the flash of gpt.bin (partition table file). I never got an exact answer to it, for my liking, maybe i read over it.
If that doesn't flash (give me the output then i know for sure ), try flashing the boot.img and see what happens. I assume nothing will change from flashing the boot.img, but u gotta try something.
Next we can do is have a look at that intel flashing file, it looks promising. I never had to go to this part so i am out of general ideas (think outside the box maybe?). Maybe we can fiddle something from here. It looks to me like it can flash more than fastboot can, u just need the right files and some we can make, hopefully if i read the sources available to us right.
Hazou
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash gpt gpt_s
igned
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'gpt' (32 KB)...
OKAY [ 0.358s]
writing 'gpt'...
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 1.094s]
finished. total time: 1.460s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motoboot
motoboot
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motoboot' (23273 KB)...
OKAY [ 2.635s]
writing 'motoboot'...
(bootloader) flashing image dnx...
(bootloader) flashing image ifwi...
(bootloader) flashing image bos...
(bootloader) flashing image logo...
(bootloader) flashing image ulogo...
OKAY [ 2.338s]
finished. total time: 4.981s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash boot boot
_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'boot' (11264 KB)...
OKAY [ 1.243s]
writing 'boot'...
OKAY [ 1.549s]
finished. total time: 2.799s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash recovery
recovery_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'recovery' (11264 KB)...
OKAY [ 1.338s]
writing 'recovery'...
OKAY [ 1.563s]
finished. total time: 2.907s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash motobp mo
tobp
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'motobp' (17091 KB)...
OKAY [ 1.714s]
writing 'motobp'...
OKAY [ 76.674s]
finished. total time: 78.396s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash system sy
stem_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
Multi-Flash is enabled!
sending 'system' (102400 KB)...
OKAY [ 9.377s]
writing 'system'...
OKAY [ 2.576s]
sending 'system' (102400 KB)...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
OKAY [ 11.154s]
writing 'system'...
FAILED (remote failure)
finished. total time: 25.509s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot flash cdrom cdr
om_signed
(bootloader) Variable not supported!
target max-download-size: 100MB
sending 'cdrom' (53258 KB)...
OKAY [ 4.891s]
writing 'cdrom'...
FAILED (remote: Preflash validation failed)
finished. total time: 6.273s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase cache
erasing 'cache'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase cache fail
FAILED (remote failure)
finished. total time: 1.897s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>mfastboot erase userdata
erasing 'userdata'...
(bootloader) BLKDISCARD ioctl /dev/block/mmcblk0 fail
(bootloader) Erase userdata fail
FAILED (remote failure)
finished. total time: 8.110s
T:\Motorola\Serwis\RAZR i (XT890)\Unbrick\mfastboot-v2>
So it looks like only few partitions are broken but how to repair it without unlocking bootloader??
Hmm, it does flash a part of the system if I read it correct. After the first one it gives errors to all partitions after it.
Can u reboot to recovery now, we finally flashed it right. Didn't work last time.
The things I wanted to do with the Intel thingy, are already done with flashing motoboot. So the things I had there are done.
Verstuurd van mijn GT-P5110
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Chamelleon said:
Nope, still red logo on recovery. The same was flashed by RSD and same errors appeared as on fastboot. Only different is after flashing RSD I can turn normal powerup and phone restarts to red logo from AP Fastboot but after flashing fastboot commands an error appeared.
Click to expand...
Click to collapse
Yep, this happens because it has nothing to start.
There is just 1 more think I can think off, because all others are closed (locked) or don't work. Or if unlocked we still don't have access.
Does the command "fastboot oem format" does something?
Verstuurd van mijn GT-P5110
Completely forgot about this command, I'll try it after work.
FAILED (remote: Restricted OEM command)
Then its over I think. We can't flash a custom recovery and fiddle around with it. Because maybe by not asking for system/data partition at start etc u can reformat the emmc with parted or other application.
Sorry, only Motorola can fix it. Or u need to replace the motherboard maybe? But that's something else.
Oh, try 1 more thing. Is it possible to load a custom boot image by the command "fastboot boot (image)"? Don't think so, but who knows. So u won't flash it.
Verstuurd van mijn XT890
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Chamelleon said:
creating boot image...
creating boot image - 11536384 bytes
downloading 'boot.img'...
OKAY [ 1.412s]
booting...
(bootloader) Command restricted
FAILED (remote failure)
finished. total time: 1.614s
Bootloader blocks it??
Click to expand...
Click to collapse
Yup, the defy could do it if i remember correctly. Hoped that this one would either. I am out of ideas now, but will have one more look. Don't expect anything, because we already tried most if not all the things we can do.
Edit:
All other things i can think of need to have adb access, and that can only be done by having an unlocked bootloader or root access. Because with root access u can flash a recovery even when u have a locked bootloader most of the time. But we don't have access to the system as well as the partitions, so we are stuck.
That Intel thingy can only flash the bootloader and the bootloader wont repartition the emmc. But we can try anyway if u want. Its a little bit different then the unbrick methode, just a little.
Verstuurd van mijn XT890
Today I flashed Samsung C3595 with partition table from S5610 and it's working well so "different" methods are not scary for me.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
Hi Chameleon.. i'm having a phone with similar issues (I created a post about it). I have tried steps one and two to no success. To unlock it do you do it via the official way (I ask because I don't know much, maybe there are other ways of doing it)
Yup, only official way.
Wysłane z Motorola RAZR i
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
hjahmetoglu said:
hey guys, i ve got the same problem. the phone stucks on the red M logo. i'm not familiar "aka" noob with this things. I wonder if anyone can give me a help?
I tried to wipe data and participation. the phone completes this commands but again stucks on the red logo.
Click to expand...
Click to collapse
Luckily, u don't have the same problem. U only have to search for a rsd lite flash guide. Flash your latest firmware that is available for your phone and country/brand. And all will most likely be good.
Hazou said:
here is the thing i talked about. Its just one more command with the unbrick method. But if u never try, u never know.
I assume u have all the files for the unbrick method still installed and on your PC. So u have the xFSTK driver and xfstk-dldr-solo.exe on your drive and working.
In the unbrick folder where the dnx and ifwi files are add the latest files from your latest firmware (dnx, ifwi and motoboot!).
Download the unbrick3.txt and rename to unbrick3.bat inside the folder with the original unbrick.bat
Now open a cmd shell inside the folder where the batch file is located. And then run unbrick3.bat.
After this try rsd lite again with the latest firmware u used.
Most likely it will not work... but ye, u gotta try.
I got this from an acer/asus device. It is the official unbrick methode from that device.
Click to expand...
Click to collapse
Yesterday I tried it and unfortunately nothing changed, still can't erase or write to those partitions.
XT890 Stuck on Red Logo. Probably damaged partitions
I woke up this morning to find that my Motorola XT890 is not working. I followed all the procedures for hard rest got the same result as listed below.
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
Contacted Motorola customer service, followed all the procedures as prescribed by Motorola customer service still stuck at Red Logo. Motorola has requested that I send it in for repair. The phone is 11 months old and under warranty. The unfortunate thing is that this is the second time I am sending the phone to Motorola for repair.
Chamelleon said:
Hi, yesterday I received XT890 from another user. Phone stuck on red Motorola logo, can enter fastboot and has locked bootloader.
Fastboot actions:
1. Normal Powerup - Freeze on Fastboot
2. Recovery - Freeze on Red Logo
3. Factory - Freeze on Red Logo
4. BP Tools - Freeze on Fastboot
5. Switch Console - Working
6. Power Off - Freeze on Fastboot
So first of all I tried to flash it by RSD with CFC_9.8.2I-50_SMI-26_S7_USASMIJBRTEU but on 4/12 it can't reboot phone so I did it manually and it goes to 8/12 and phone shows E:failed to erase partition system.
I also tried to skip system by deleting it from xml but on every other step it can't do anything with partitions (data, cache, cdrom).
I tried fastboot to erase partitions manually but no luck with locked bootloader. So I tried to unlock it but it can't be done cause data can't be erased.
I even tried unbrick script for modified and it passed but no changes.
So what I tried:
1. Format Data/Cache - Can't enter Recovery
2. Flash RSD - Can't flash system partition
3. Unlock Bootloader - Can't format data partition
4. Unbrick - No changes after that
5. Fastboot flash CWM - only stock recovery can be flashed on locked bootloader
6. Fastboot erase data / system/ cache partitions - error
After that I'm assuming that emmc is damaged. If it's software damage it should be way to resurrect it.
Any help is welcome.
Sorry for my nasty English.
Click to expand...
Click to collapse
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!
I tried to update my moto XT1097 AT&T locked version and it did not complete the update successfully. It goes until flashing the boot.img, failed and don't go any further. I supposed it is because it is a locked phone. After this, the phone went to a fastboot mod loop. Even If I tried to sideload the orignial rom or use the fsaboot comandts to restore the original rom it remains in this mode.
It generates a first error when I tried to issue the command "fastboot flash partition gpt.bin" returning this:
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.004s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.013s
And the phone display shows "hab check failed for primary_gpt"
I am issuing this command from the folder where the files of the original rom are located.
I tried to use a different gpt.bin file, from other ROMs and the same thing happen. I also tried another Lollipop ROM and not luck at all.
What I understand is that the gpt is the partion table that indicates where begins and where finish the diferent partitions into the phone, so I guess the problem could be resolve if I can change the gpt file into the phone for the original one.
I have tried to follow with the rest of the instalation but the motoboot and the boot files also are rejected and the system files are denied due an authentication problem.
The roms I have tried are:
ATT_XT1097_4.4.4_KXE21.187-38_cid1_CFC.xml
TMO_21.21.42.victara_tmo.tmo.en.US
4.4.4_to_5.0-11OTA
And the first one I used, which reach the same stage every time is:
RETBR_XT1097_5.0_LXE22.46-17_cid12_CFC.xml
I really appreciate any help and ideas you can give me to get my phne back to kitkat. I am not an expert but I am willing to do and learn what it takes
Did you solve this? How?
I am into this problem too. Any news?
hi,
can someone please help.. my phone stopped booting up all of a sudden. I am trying to install this CFC_9.8.2I-50_SMI-29_S7_USASMIJBRTGB.xml which i downloaded from a thread on this forum using rsd lite v6.1.5
I get the following error..
AP Fastboot Flash Mode (Secure boot)
20.25 (sh - dae73d6)
IFWI Info: 42.26
eMMC Info: Size 8GB
Barcode: TA32407FJN
Battery (OKay): 3.70v (temp 37)
Transfer mode : usb connected
Rom-Key: Motorola-Key
Modem Status: Secure
Boot Mode Selection menu
......
Fastboot Reason:
fastboot: max download size: 100MB
USB Connected
Getvar max-download-size
Downloading
downgraded security version
update gpt_main version failed
preflash validation failed for GPT
Fastboot command failed.
Can anybody help? not sure what i am doing wrong. I am a noob.
thanks.
I have a Moto G6 Forge Cricket that I forgot the password to. I have been trying to boot into another image without data loss in order to go in and delete the password config files, but have not been able to get anything to work. USB debugging doesn't seem to be on, the bootloader is locked, and I have no idea if it's possible. I can access fastboot and android recovery. Fastboot says the product variant is "jeter XT1922-9", leading me to believe that it's just a reskinned moto g6 Play.
I have tried recovery loading update aroma file manager from SD card, which failed signature check. Updating over adb doesn't work, as the phone doesn't show up in adb at all, only fastboot.
I tried flashing TWRP recovery for the moto g6, and got the following output on PC:
C:\Android\SDK\platform-tools>fastboot flash recovery twrp.img
(bootloader) is-logical:recovery: not found
Sending 'recovery' (17626 KB) OKAY [ 0.559s]
Writing 'recovery' (bootloader) Image recovery failed validation
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed
On the phone, I see a series of yellow cmd log lines leading up to "cmd: flash:recovery" followed by pink "Mismatched partition size (recovery)" Some posts said that this was an ignorable error and to just proceed into recovery, but when I did it just went to the normal android recovery.
I also tried just using fastboot boot, but that obviously didn't work due to the locked bootloader.
C:\Android\SDK\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (17626 KB) OKAY [ 0.563s]
Booting (bootloader) permission denied!
FAILED (remote: '')
fastboot: error: Command failed
I'm out of ideas and out of google search results that aren't SEO spam to read. If anyone knows something else I could try I would be happy to hear it. Thank you so much!
The only thing I can think of is using the factory recovery to erase the user partition / factory reset.