(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
Okay, I know this question has been asked quite a few times, but I'm really stuck here.
I was running CM10.2 on my KFHD, when I wanted to revert back to Stock OS for a while so I could test something I was working on. I created a full backup in TWRP so that once I was done I could go back. I then proceeded to wipe (factory reset) and flash the 7.4.3. I then rebooted. My Kindle won't get past the 2nd bootloader. It only show's the blue logo. I thought, "Okay, something's not right, I'll just restore from a backup. So I rebooted into TWRP, and proceeded to restore, only to be graced by big red letters that said, "Restore Failed." I rebooted the bootloader, putting it into fastboot mode, and tried to restore from some boot, recovery, and system images I had lying around on my hard drive somewhere. Still no dice. My Kindle just sits there, refusing to boot past the 2nd boot loader.
Any ideas out there?
Ph0enix_216 said:
Okay, I know this question has been asked quite a few times, but I'm really stuck here.
I was running CM10.2 on my KFHD, when I wanted to revert back to Stock OS for a while so I could test something I was working on. I created a full backup in TWRP so that once I was done I could go back. I then proceeded to wipe (factory reset) and flash the 7.4.3. I then rebooted. My Kindle won't get past the 2nd bootloader. It only show's the blue logo. I thought, "Okay, something's not right, I'll just restore from a backup. So I rebooted into TWRP, and proceeded to restore, only to be graced by big red letters that said, "Restore Failed." I rebooted the bootloader, putting it into fastboot mode, and tried to restore from some boot, recovery, and system images I had lying around on my hard drive somewhere. Still no dice. My Kindle just sits there, refusing to boot past the 2nd boot loader.
Any ideas out there?
Click to expand...
Click to collapse
You can try to adb sideload a factory image in TWRP if you have not tried that. Otherwise it's a factory reset.
Seems the flashing of the images did not take or you would not have the 2nd bootloader anymore. So first, check your drivers and make sure they are installed right. Also make sure you have adb.exe and fastboot.exe in the folder you are CD'ing from.
What I would do is download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and CD from inside that folder and push those images. I know that process will/should work.
Double check and make sure you have fastboot communication with your computer fastboot -i 0x1949 getvar
then from inside the folder hold shift and right click on mouse choosing open a command prompt here
Then type these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
LinearEquation said:
You can try to adb sideload a factory image in TWRP if you have not tried that. Otherwise it's a factory reset.
Seems the flashing of the images did not take or you would not have the 2nd bootloader anymore. So first, check your drivers and make sure they are installed right. Also make sure you have adb.exe and fastboot.exe in the folder you are CD'ing from.
What I would do is download this tool http://forum.xda-developers.com/showthread.php?t=1951254 and CD from inside that folder and push those images. I know that process will/should work.
Double check and make sure you have fastboot communication with your computer fastboot -i 0x1949 getvar
then from inside the folder hold shift and right click on mouse choosing open a command prompt here
Then type these commands
fastboot -i 0x1949 flash boot "image name here" include .img at end"
fastboot -i 0x1949 flash recovery "recovery name here" include .img at end
fastboot -i 0x1949 flash system "system image name here" include .img at end
Now give some time as the system image is quite large
when done, type fastboot -i 0x1949 reboot
Profit
Click to expand...
Click to collapse
I've got the correct drivers. I've had them for a couple of months--they're the ones from @stunts513. And Windows driver enforcement has been disabled for a while now, because signature enforcement is pretty annoying.
And I can't use the system restore tool. The download is just too big. My internet is just one step above dialup, just enough to watch videos on YouTube and "Doctor Who." A 1.1 GB file is just too big, and the script without the images is no longer available.
Still, thank you for responding.
Ok, so I was running a custom ROM (I don't even recall which specific one at the moment....one of the Cromi ROMs). I tried to wipe it and install a new version, and the install didn't go as smoothly as planned. I can still load the TWRP recovery system, and begin attempting to install any ROM, but when it gets to the point where it says it's installing, the bar across the bottom that should show progress disappears almost instantly and the next button becomes available. When I go to reboot, it warns that there is no OS installed. Of course if I continue anyway, it won't boot beyond the Asus splash screen. There are errors in multiple places saying that it can't mount /system. I saw this error in the log file generated, I saw it during reboot, and there was some point in the TWRP screens where I saw it, but can't recall where at this moment. If I go into the Mounts section, System is not checked and I cannot check it.
I tried following the instructions on the unbricking thread and got stuck. I fear this has likely only made matters worse.
Following these steps:
Code:
fastboot erase boot
fastboot erase staging
fastboot format system
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery.img
fastboot reboot-bootloader
I was able to successfully erase the partitions mentioned, then when I tried to flash the first time, I actually screwed up and didn't have the blob file I needed, so now I go back, and obviously I can't re-erase the other files, but formatting system still works, so I know I'm getting good communication with the device. Then trying to flash the blob to staging, I get:
sending 'staging' (1379 KB)...
FAILED (command write failed (No such device or address))
Any thoughts or suggestions would be greatly appreciated. I've currently got an expensive paperweight.
Hello guys, ive been generally lucky in the sense that i have had no issues...until now.
I have tried installing the most recent updates (7.0, and now 7.1.1) and i continue to get this error through cmd. It does not seem to want to flash anything, and i have gotten it to flash, root, and twrp, but it still acted funky. Today, trying to remedy the situation, i attempted to flash the new 7.1.1 update, and return to stock (to later return to power user) but it is still doing it.
It says Bootloader: has-slot (not found), and a couple other things. When i try to flash individual pieces, it does not retain it. when i try to flash the flashall.bat, it flashes but does not flash everything, it will say the stuff has transferred 0 and skips it as it looks like. I cannot get my bootloader off the october one, and i have looked everywhere i can to try to fix this.. please help, its driving me mad. I will be happy to provide any information needed.
Thanks Community! You rock!
Have you tried a different USB cable? A different computer? How about a different USB AND a different computer? I think this would be a good place to start.
Can i ask you why this would matter? My usb seems to work fine, and my computer had no issues before this... i can still perform different actions, and my phone is showing up as ADB and Fastboot.
If it's not pc or usb cable related you can try to flash latest factory image step by step via fastboot without your simcard
Well, you might want to post the complete output of your flashing attempt, but if the bootloader slot isn't found, that's usually a sign of a hardware problem. Hopefully I'm wrong, but until we see more from you, I simply don't have an answer for you.
Ive tried to fastboot everything individually, and it refuses to take. I tried the flashall, same thing. I used NRT and it partially worked, but has sorta the same error. I will be flashing again and providing screenshots right now. I was able to get into a rom, root, twrp but i still cannot update all of those core things (bootloader, radio, and such) Thank you guys for the help. Much needed.
Here is the attempt to just flash the bootloader, i have tried from a different location but this is directly in Platform-Tools of the SDK. As you can also see, it does register under fastboot...
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
yes i have, i only do it with the simcard removed. Now whats weird is it says my bootloader is on 72.01, but my cmd clearly tells me its not working correctly...
coremania said:
Try to flash radio and bootloader via twrp
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052
Did you try without simcard?
Click to expand...
Click to collapse
I just tried what you suggest, and im not sure if it worked. It said everything wrote (on twrp) but it was very quickly done. I feel it did the same thing as CMD did.
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
hahahaha well that could surely be the issue :silly:, but the one thing im wondering is why it wouldnt work through NRT, and i also "successfully" sideloaded the ota... Gonna try this now and hopefully it works! I shall report back when finished
dahawthorne said:
You could try using the correct Fastboot command...
fastboot flash bootloader bootloader.img
The command is fastboot flash <partition> <image>
Your screenshot says only "fastboot flash image" but doesn't state the partition you're trying to load, hence "unknown partition".
And since we're on the subject, perhaps a repetition of the procedure I used to use before the full OTA days might be useful to you and other people.
Preparation.
- Take a TWRP backup and save it on your PC.
- Download factory image (https://developers.google.com/android/nexus/images#shamu) and unzip all files, including the zip within the zip. Rename the *.img files to the names below. Copy all of them to the same folder as your ADB/fastboot executables.
- Download the relevant TWRP and rename to twrp.img - also put in ADB/fastboot folder.
- Copy SuperSU to device (if root wanted).
- Set USB debugging in Developer options & attach to your PC.
- Open a CMD window, navigate to your ADB folder, and check connectivity with "adb devices". If it's ok, copy & paste each command below into the CMD window and run them - the only lengthy one is the system.img.
1. adb reboot bootloader
2. fastboot flash bootloader bootloader.img
3. fastboot reboot-bootloader
4. fastboot flash radio radio.img
5. fastboot reboot-bootloader
6. fastboot erase system
7. fastboot flash system system.img
8. fastboot erase boot
9. fastboot flash boot boot.img
10. fastboot erase cache
11. fastboot flash cache cache.img
12. fastboot reboot-bootloader
13. fastboot flash recovery twrp.img
14. From bootloader boot to TWRP and reflash superSu
Click to expand...
Click to collapse
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Calko2882 said:
Unfortunately, it did not work. Now google app keeps crashing. Phone is extremely buggy.
Click to expand...
Click to collapse
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
dahawthorne said:
Can you give a bit more detail? So the phone is crashing, but is it now on the version that you wanted to have (7.0, 7.1.1)? There is rarely such a thing as "too much information".
Click to expand...
Click to collapse
Ok, so what happens is that it says i am on 7.1.1 with i guess the related info, but it does not load in properly as you can see with the screenshots. I start up the initial setup, and i can get through most of it fine, but some areas *permissions* are all blotchy. like i can toggle them on to submit data but i cant see what it is exactly im agreeing to. Then i start the phone, Google App automatically crashes, along side system ui. When i updated them, it seemed to fix the problem. But the issue is, i am not receiving phone calls and texts until possibly days later, and when i send texts it says "sending" and proceeds to spam the hell outta whoever its going to (sends literally 30+ texts). When i call someone, my phones Do Not Disturb mode gets enabled, and then nicely cuts out my audio. I can turn this feature off when im in the call, but sometimes it will then glitch the phone app, and i cannot essentially "hangup". My phone also now dies at 9%, where it had not previously (when i was on other rom / older stock) This all started after i updated to the october patch, and i noticed in december that i didnt have the december patch / update. I went to install it, and the same exact thing occurred. Ive attempted a rescue ota, and a sideload ota, and now this stuff as well, but i fear the worst for my phone. Let me know if i need to add anything else
Strephon may be right in suggesting a hardware fault, but equally it may just be that your phone is now somehow corrupted. My only suggestion is that you nuke it - factory reset, TWRP, wipe everything again in TWRP, and then try installing from fresh using the 7.1.1 full (not OTA) image and the instructions I posted earlier. If it still doesn't work I'm out of ideas, but there are people with far greater experience here than I have, so don't give up. It's too nice a device to just write off.
Calko2882 said:
When i call someone, my phones Do Not Disturb mode gets enabled
Click to expand...
Click to collapse
That's a new feature of 7.1.1. So you won't have to listen to notifications while on the phone. It's disabled as soon as the phone call is over.
dahawthorne said:
Strephon may be right in suggesting a hardware fault...
Click to expand...
Click to collapse
I hope I'm wrong.
I have unlocked my bootloader and when I try to install TWRP recovery and open a cmd write the commands 'adb devices' and "fastboot devices" to check whether connected or not it shows connected then reboot to to bootloader but when I put command "fastboot flash recovery recovery. img" I get " cannot load recovery. Img" . I also downloaded the latest TWRP victara and adb, fastboot aswell but can't get what problem is please Help guys!!!
Vedang V said:
I have unlocked my bootloader and when I try to install TWRP recovery and open a cmd write the commands 'adb devices' and "fastboot devices" to check whether connected or not it shows connected then reboot to to bootloader but when I put command "fastboot flash recovery recovery. img" I get " cannot load recovery. Img" . I also downloaded the latest TWRP victara and adb, fastboot aswell but can't get what problem is please Help guys!!!
Click to expand...
Click to collapse
So you got the latest ADB and Fastboot:
https://developer.android.com/studio/releases/platform-tools.html
You got the latest TWRP Victara:
https://twrp.me/motorola/motorolamotox2014.html
Extract ADB and Fastboot, and put the TWRP img file in the same folder, start command prompt as Admin and Change Directory to where the files are:
cd C:\Users\User\Downloads\platform-tools (this is just an example)
fastboot flash recovery twrp-3.2.1-0-victara.img
Boot into recovery immediately.
Vedang V said:
I have unlocked my bootloader and when I try to install TWRP recovery and open a cmd write the commands 'adb devices' and "fastboot devices" to check whether connected or not it shows connected then reboot to to bootloader but when I put command "fastboot flash recovery recovery. img" I get " cannot load recovery. Img" . I also downloaded the latest TWRP victara and adb, fastboot aswell but can't get what problem is please Help guys!!!
Click to expand...
Click to collapse
Did you install the Motorola USB Drivers?
https://motorola-global-portal.custhelp.com/app/answers/prod_detail/a_id/79106/p/30,75,27,
Did you type the full name of the img file, including .img
You must write fasstboot flash recovery (full name of the file ot rename it).img.
When is finished not take off the cable and run recovery from device bootloader.
Thats it.