I have used cynogenmod on my moto pure. After a while i have tried to turn it back to the stock rom following this thread: "https://forum.xda-developers.com/moto-x-style/development/firmware-moto-x-style-pure-stock-t3272486" and while doing so my phone has failed in the "fastboot flash bootloader bootloader.img" command. Now my device is soft bricked. It is stuck on boot loops.
I have tried going to fastboot by pressing the buttons but the phone only restarts, i have tried adb commands and fastboot commands but both don't recognize the device. my pc makes noise as it recognized my device yet i cant use adb nor fastboot. i suspect that while doing "fastboot flash bootloader bootloader.img" my bootloader was removed. how can i return it? please help.
I also read about using SP flash tool, but i'm having a hard time in getting the scatter loading file for the moto pure. I can't find it anywhere.
Thanks, Eden
What firmware did you use to flash your phone?
I always had good luck with Autoscript. Never failed me.
So your phone restarts, when you try to go on fastboot?
Sent from my Portable
PassatSport15 said:
What firmware did you use to flash your phone?
I always had good luck with Autoscript. Never failed me.
So your phone restarts, when you try to go on fastboot?
Sent from my Portable
Click to expand...
Click to collapse
Well i used Minimal ADB and Fastboot. which worked for me when i rooted the device and installed the cyno rom.
and yes. it just skips the fastboot. when i press vol down and power together my device shows the bootloader unlocked screen and then goes to the cyno loading screen and keeps there.
PassatSport15 said:
What firmware did you use to flash your phone?
I always had good luck with Autoscript. Never failed me.
So your phone restarts, when you try to go on fastboot?
Sent from my Portable
Click to expand...
Click to collapse
I just tried your autoscript and yet it is stuck on "waiting for device"
edenah said:
I just tried your autoscript and yet it is stuck on "waiting for device"
Click to expand...
Click to collapse
Can you send that script?
You should be able to see where the issue went wrong.
Is the bootloader unlocked? Take a shot of the phone, in fastboot mode.
Sent from my Portable
PassatSport15 said:
Can you send that script?
You should be able to see where the issue went wrong.
Is the bootloader unlocked? Take a shot of the phone, in fastboot mode.
Sent from my Portable
Click to expand...
Click to collapse
i must say. my device manager shows my android phone as a portable device "mtp usb device" and not as "other device" "android". so maybe thats why it cant find the device? Just to make you sure: i have installed the correct drivers for adb and fastboot, my brother's phone works with my pc.
and for the script you asked:
"@echo off
:WARNING
echo Created by ScardracS for the Moto X Pure.
echo I am not responsible for any damage, you're been warned!
echo You will be able to quit the installer simply press K on any question.
pause
:START
cls
echo Have You already installed ADB and Fastboot? (Yes/No/Kill the script)
set /p a=
if /i "%a%"=="Y" GOTO ROM
if /i "%a%"=="N" GOTO INSTALLER
if /i "%a%"=="K" GOTO END
echo Wrong Answer!
GOTO START
:INSTALLER
cls
echo This is the ADB and Fastboot's installer.
echo You have to install both ADB, Fastboot and Drivers.
echo It's better to install it System Wide.
pause
start adbinstaller.exe
pause
:ROM
cls
echo Have You already downloaded the Stock ROM? (Yes/No/Kill the script)
set /p b=
if /i "%b%"=="Y" GOTO STARTINSTALL
if /i "%b%"=="N" GOTO DOWNLOAD
if /i "%b%"=="K" GOTO END
echo Wrong answer!
GOTO ROM
OWNLOAD
cls
echo I'll open GitHub where You will be able to choose your preferred Stock version.
start https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/Stock/
echo WHEN THE DOWNLOAD IS FINISHED PLEASE UNZIP AND MOVE HERE ALL THE FILES.
pause
:STARTINSTALL
cls
echo Are You ready to intall STOCK ROM? (Yes/No/Kill the script)
set /p c=
if /i "%c%"=="Y" GOTO READY
if /i "%c%"=="N" GOTO START
if /i "%c%"=="K" GOTO END
echo Wrong answer!
GOTO STARTINSTALL
:READY
cls
echo Do you want to delete user data? (Yes/No/Kill the script)
set /p d=
if /i "%d%"=="Y" GOTO WIPE
if /i "%d%"=="N" GOTO NOWIPE
if /i "%d%"=="K" GOTO END
echo Wrong answer!
GOTO READY
:WIPE
cls
echo WIPE SUBSCRIPT
echo DO NOT STOP THE FLASHING PROCESS!!
adb reboot-bootloader
echo FOLLOW THE INSTRUCTIONS ON WATCH ME FOLDER AND THAN HIT ENTER
pause
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
GOTO LOOK
:NOWIPE
cls
echo NOWIPE SUBSCRIPT
echo DO NOT STOP THE FLASHING PROCESS!!
adb reboot-bootloader
echo FOLLOW THE INSTRUCTIONS ON WATCH ME FOLDER AND THAN HIT ENTER
pause
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase customize
fastboot erase clogo
fastboot oem fb_mode_clear
:LOOK
echo Do you want to lock your device? (Yes/No)
set /p e=
if /i "%d%"=="Y" GOTO LOCK
if /i "%d%"=="N" GOTO END
echo Wrong answer!
GOTO READY
:LOCK
echo Locking device
fastboot oem lock
echo Device locked
:END
fastboot reboot
cls
echo Enjoy!
pause
"
and for the logcat:
"@echo off
:WARNING
echo This script is made and tested by me (ScardracS).
echo You can use and/or modify it, but please give me proper credit.
:START
echo.
echo Have You installed ADB? (Yes/No/Kill the script)
set /p a=
if /i "%a%"=="Y" GOTO LOGCAT
if /i "%a%"=="N" GOTO INSTALLER
if /i "%a%"=="K" GOTO END
echo Wrong Answer!
GOTO START
:INSTALLER
cls
echo I'll install ADB
echo Please install both ADB, Fatsboot and Drivers.
start adbinstaller.exe
pause
:LOGCAT
cls
echo Do you want to overwrite previous file? (Yes/No/Kill the script)
set /p b=
if /i "%b%"=="Y" GOTO OVER
if /i "%b%"=="N" GOTO NOVER
if /i "%b%"=="K" GOTO END
echo Wrong Answer!
GOTO LOGCAT
VER
cls
adb logcat > logact.txt
GOTO END
:NOVER
cls
adb logcat >> logcat.txt
:END
cls
pause
"
Never use a script to flash Moto firmware... Period, don't do it.
OP... What state is you phone in now? Can you get to the fastboot/bootloader screen?
acejavelin said:
Never use a script to flash Moto firmware... Period, don't do it.
OP... What state is you phone in now? Can you get to the fastboot/bootloader screen?
Click to expand...
Click to collapse
idk then how to flash the moto frimware... that all the web is about.
and i cannot. i cant get to fastboot not by buttons not by adb not by fastboot command. That is my problem. dont have recovey no nothing. my device just skips it all and sticks to the os loading screen.
right now its out of power. if i charge it and turn it on it will get stuck on boot loop for the cynogen.
edenah said:
idk then how to flash the moto frimware... that all the web is about.
and i cannot. i cant get to fastboot not by buttons not by adb not by fastboot command. That is my problem. dont have recovey no nothing. my device just skips it all and sticks to the os loading screen.
right now its out of power. if i charge it and turn it on it will get stuck on boot loop for the cynogen.
Click to expand...
Click to collapse
Plug it in and let it charge a while, then disconnect cable from phone. Plug USB end of cable into computer and hold both Volume buttons... Continue to hold them and connect USB to phone, the bootloader should appear.
The bootloader has to be there or you would never get the OS to start loading.
acejavelin said:
Plug it in and let it charge a while, then disconnect cable from phone. Plug USB end of cable into computer and hold both Volume buttons... Continue to hold them and connect USB to phone, the bootloader should appear.
The bootloader has to be there or you would never get the OS to start loading.
Click to expand...
Click to collapse
ok i got it he might have not factory reset aka hard reset while coming to stock and now he has overwritten the both cyno and stock over... i also had done same thing but didn't made my bootloader vanished
ps: if there is no bootloader then u even can't see the offline charging happening
acejavelin said:
Plug it in and let it charge a while, then disconnect cable from phone. Plug USB end of cable into computer and hold both Volume buttons... Continue to hold them and connect USB to phone, the bootloader should appear.
The bootloader has to be there or you would never get the OS to start loading.
Click to expand...
Click to collapse
well the fact i still have a bootloader is comforting at least.
but i have tried what you said. but when i charge my device it does a charging screen, and it keeps stuck on this screen, so when i try the button series it doesn't work. wish i could remove the battery...
* Well i have played with it for a while and made the screen off after it is charged. when i do what you said. i see that charging screen and then it disappears as like i launched to bootloader, yet there is no bootloader, after a few seconds the charging screen comes back, and then again there is a loop between the black screen and the charging screen.
Sagar_1401 said:
ok i got it he might have not factory reset aka hard reset while coming to stock and now he has overwritten the both cyno and stock over... i also had done same thing but didn't made my bootloader vanished
ps: if there is no bootloader then u even can't see the offline charging happening
Click to expand...
Click to collapse
i see a charging screen but i cant see the precentage of the battery. and even when i remove the charging it still stuck on that screen.
as long as the phone has battery the screen will be kept on . i cant enter fastboot since its allways open. cant turn the phone on as fastboot as it cant be turned off before that! or the screen stuck on loading cynogen or the screen stuck on the charging screen. Please help!
Press and hold Vol Dn + Power for 15-30 seconds... Anything?
acejavelin said:
Press and hold Vol Dn + Power for 15-30 seconds... Anything?
Click to expand...
Click to collapse
phone restarts. skips the fastboot and goes to cynogen loading screen.
it shows the bootloader unlocked screen and the next thing i see is cynogen.
well as acejavelin said i have a bootloader so i guess i should make it an other post about the fact i can't get too fastboot. Thanks all!
edenah said:
well as acejavelin said i have a bootloader so i guess i should make it an other post about the fact i can't get too fastboot. Thanks all!
Click to expand...
Click to collapse
Don't make another post. Just keep this one up as your problem is being addressed. It is just not what you anticipated.
Jessooca said:
If possible, can you borrow another phone or a camera and make a video of the phone rebooting, as well as you holding the buttons etc etc.... Anything more you can do, can help us help you.
Upload the video to YouTube and share the link if you can do that
Click to expand...
Click to collapse
well i will upload the video soon.
But i think i should explain it more.
my device can't get now into fastboot! i have tried using adb commands but the adb doesn't recognize the device. I have tried fastboot commands but again it doesn't recognize the device. I also tried button combinations, but it didn't work.
Until the incidence i have used to press the power button+ vol down keys to get into fastboot mode, but now it doesn't work. I suspect that it doesn't work since in order to get into fastboot with the button combination i need to first get the device turned off. But when i connect my device to the charger it shows the battery charging screen and the device is stuck on that screen even if it has disconnected from the charger, and it will keep on that screen until the battery has depleted. I have tried shutting it down using the power button but then my phone gets into a loop with the cyanogenmod loading screen, and even if i turn it off it restarts instead.
Jessooca said:
Leave your phone out until it's fully dead, battery is dead dead dead.... then hold down the proper button combo to get into fastboot (hold VOLUME DOWN & Power button until it boots into fastboot) I know you said you've tried this however, I am suggesting you let the phone fully die, and while holding that button combo plug the phone in (just keep on holding those buttons until it at least powers up; you'll have to wait a couple minutes as it won't boot without at least 1% battery) however this suggestion may work, then again, it may keep rebooting as you've stated previously.
Let us know how this goes tomorrow.
Click to expand...
Click to collapse
well. when i do what you said my device instead of getting to fastboot it gets turned of while charging, its a step up. But when i try the button combination for fastboot it doesn't get into fastboot.
No vid yet, bud?
Sent from my Portable
Related
Nexus 7 was rooted,unlocked bootloader and was running paranoid anroid 3.90+ i think . i plugged it into the computer to get a new rom using nexus root toolkit v1.7.2. i was asked to update a few things, so i clicked yes. i then tried to flash stock + unroot and chose 4.3 cause i wanted to try the new OS. but i guess something happened because when i turned my nexus 7 back on i was stuck on the load screen (GOOGLE image with a unlocked lock) i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side. when trying to flash stock +unroot using NRT i get up to the sending "bootloader" part and my nexus 7 just freezes, how do i fix this. please and thanks
download the factory image from the google factory image and extract the archive.
try flashing the bootloader manualy with fastboot.
locate your fastboot binary and copy the bootloader image to that directory.
open a commandline in that directory and type
fastboot flash bootloader name-of-bootloader.img
after that you can try to flash the whole factory image with the flash-all.sh script.
Simple
dieselmonkeyy said:
i could cycle thru a few options using volume keys (start,recovery,power off) .all of them seemed useless as they would just bring me back to where i was.when clicking start "booting failed" come up on the upper left side.
Click to expand...
Click to collapse
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
MlucianoEze said:
Boot failed??? That's a bad flash of the stock ROM. I had the same problem at my first attempt trying to flash Stock ROM, but don't worry! Let's do this:
WARNING: Before you continue you are accepting that I'm not responsible of anything can happen to your Nexus and your battery is fully charged.
When you download the stock ROM you have to uncompress the zip file. You will find the bootloader and another zip.
Uncompress that zip file, put fastboot program, the bootloader and the files together.
Then start your Nexus into bootloader mode, connect it to your PC, open a console (cmd for Windows, Terminal for Linux and Mac OS X) and type this:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
WARNING: Your Nexus is FULLY EMPTY!!! Don't reboot it because it can get a full brick (It will not turn on any more).
Now type this:
fastboot flash bootloader bootloader-grouper-X.XX.img
NOTE: Replace X.XX with your version.
Now type:
fastboot reboot-bootloader
Your Nexus will reboot.
Type this:
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img #Will take a very long time. DON'T INTERRUPT THE PROCESS!!!!!
fastboot flash userdata userdata.img
Now reboot again with:
fastboot reboot-bootloader
Re-unlock bootloader to get a full wipe:
fastboot oem lock
Reboot again:
fastboot reboot-bootloader
And then unlock the bootloader:
fastboot oem unlock
Press "Yes" to the petition screen and reboot:
fastboot reboot
Ready the Nexus!
I had the same problem and I did this.
I hope I can help you.
Sorry for my bad English. I'm from Argentina and I'm learning.
Well,
Good luck!
Click to expand...
Click to collapse
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
You have to be in the folder with fastboot inside else those commands will not work.
It will be easier if you put the images extracted from the zip into the zip together with the fastboot program.
If you don't understand yet I'll try to be more specific.
Sent from my Nexus 7 using xda app-developers app
dieselmonkeyy said:
what do i type into cmd inorder to be able to type
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
and get it to work. im a noob . thanks in advance
Click to expand...
Click to collapse
It can be intimidating... and the so-called tool-kits don't help you learn
I assume you are using Windows.
follow the unzip instructions from the previous poster. (not quoted here). note the directory.
find the directory containing your android tools... ADB.exe and FASTBOOT.exe.
transfer your unzipped files to this directory. Open your CMD prompt window and change to this directory if necessary.
plug in your Nexus.
type fastboot device at the prompt. MAKE SURE YOUR NEXUS 7 is listed (serial number)
proceed with the complete instructions from the previous poster.
that should do it.
YES!!!
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
dieselmonkeyy said:
thanks alot for the instructions, it worked!!! i hope people use ur instructions as reference if they have the same problem. THANKS ALOT!!!
Click to expand...
Click to collapse
I'm glad the problem is solved. Do not forget to click the THANKS button.
Sent from my Nexus 7 using xda app-developers app
Hello. My brother's Nex 7 is also has this issue. I cannot follow any of the steps as it gets stuck on erasing any of the partitions. I tried erasing those partitions in any order and they still get stuck. His device was stock and bootloader locked too. When I try to unlock the bootloader, it gets stuck as well at the erasing userdata part. I suspect a bad memory chip. Anyone else experience this?
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
jophisdrazin said:
Yes, mine is sticking on the (bootloader) erasing userdata on bootloader unlock as well.
It also sticks on any fastboot ERASE command.
Factory reset had a bunch of errors and no longer comes up. none of the FLASH commands work because the BOOTLOADER is locked.
And since it freezes on the unlocking bootloader commands I believe I am screwed.
This was a factory installed, never flashed, unlocked or rooted Nexus 7 wifi 2nd gen. After installing the 4.4.2 that popped up it loaded once then crashed and never loaded again
I have tried every tool I can find. They all stick on the erase part.
Click to expand...
Click to collapse
Send your device for repair. My brother did so. My suspicions were correct. A faulty chip. They replaced the whole board, according to my brother.
Sent from my Nexus 7 using Tapatalk
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
jaed.43725 said:
So I moved my Android zips off of my phone to make some extra room for Firefox OS. And when I was done playing with it I found out that the USB connection to get into the SD card does not work (another reason to have removable storage). I have Google_Nexus_4_ToolKit_v2.0.0 and tried everything I could think of in there. I dont know how to ADB except to put the phone into sideload mode and you use command prompt. I have CWM recovery on it. So any help would be awesome. I will take a good link or some step by step stuff. Thank you.
Click to expand...
Click to collapse
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
luiseteyo said:
Calm down, there's solution.
1. Download Google Factory Image from here(4.3)
2. Extract it in your adb directory. You should see some files, but we oly need the radio.img, bootloader.img and image-occam-blabla.zip
3. Open a command window in your adb directory.
4. Reboot into bootloader and write the following code:
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-blablabla.img
> fastboot reboot-bootloader
> fastboot flash radio radio-blablabla.img
> fastboot reboot-bootloader
> fastboot -w update image-blablabla.zip
5. The phone will reboot. Now u can use the toolkit to flash a recovery again (select 4.2.2 firmware) and starting rooting and flashing roms again.
Good luck! If u need any help just quote my comment so I get notified
Click to expand...
Click to collapse
Ok. So what I did was kinda following your setup here. I had to get the Android SDK first. Then extract that into C:/. Then I got the 4.3 like you said and extracted that C:\adt-bundle-windows-x86_64-20130917\sdk\platform-tools. Then because of the new SDK I put the phone into the first 3-button mode. I then ran flash-all. And after a minute I had stock 4.3.
PROBLEM SOLVED! I used another pc, my usb ports were the problem! I recently got my Nexus 7 (2012), wi-fi only , I unlocked it's bootloader, installer TWRP recovery, and rooted it. For all these operations i used the N7 toolkit , because back then, I was a noob. The rooted tablet (4.2.2) worked Perfectly! But, after about 3 months, it's "volume down" button stopped working. I rebooted it, but it went in bootloader, instead of normal system. So I just select "Start" and it was in Safe Mode! OK, my "volume down" didn't work in Safe Mode (and bootloader mode) neither! And every time I reboot it, it goes to bootloader! I thought that it was a software problem confused , so I began flashing a new ROM. I didn't want to use the toolkit because everyone says that it's bad . I downloaded AndroidSDK, I re-downloaded the ADB and Fastboot drivers, and I downloaded the newer version of the bootloader (4.23, .img) . Tablet was already in bootloader and I connected it to the PC. In platform-tools folder I ran the "fastboot devices" command, and It was able to see it . So I copied the bootloader img to the same folder, and I ran "fastboot flash bootloader bootloader-grouper-4.23.img" . Then I rebooted it into bootloader again. IT WORKED! But, it didn't solve the "volume down" problem. My rooted 4.2.2 and TWRP were still on the system. Everytime I power off the tablet, and then hold the "Power" button, it goes into bootloader. It was that button issue causing that. Then I decided to take it to the service (same place where I bought iw the unloct) , but I couldn't because if they saked bootloader, non-stock recovery and the root, the wouldn't accept the warranty . I decided to download the latest 4.3 stock android, and stock recovery, flash them, and lock the bootloader. I downloaded 4.3 stock from google's official site, (nakasi-jwr66y) and I used the flash-all.bat command that came with it.
.bat command looks like this:
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot oem unlock
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
ping -n 10 127.0.0.1 >nul
fastboot -w update image-nakasi-jwr66y.zip
echo Press any key to exit...
pause >nul
exit
I ran it. It successfully did the oem unlock (it was already unlocked) , all the erase commands, and flash bootloader command. But it was stuck on
"fastboot -w update image-nakasi-jwr66y.zip" . It stays steady for about 30secs , and than it says
"sending 'system' (x-kb)"
After some time it just says Data transfer failure(too manly links) ...
I tried the same process billion more times, but same error :/
I tried
-Re-downloading and installing the drivers
-Changing the usb ports, and microUSB cables,
-Restarting the pc (of course)
-Re-downloading the nakasi-jwr66y
-Downloading the twrp recovery (it successfully flashes it)
-Re-downloading the whole SDK
But it DOESN'T WORK? What should I do? Is the volume-down issue hardware or software ?
Sorry for my bad English :////////
P.S. What is the difference between "fastboot flashall" and "fastboot update" ?
People need help. Sorry if'm posting in the wrong place, I'm new here.
I have a Moto X Play (XT1563) And after I flash it to the stock rom 6.0 he installed it right more at the time of restart he did not call more, no charges and no starts in fastboot.
The bootloader it was unlocked, and the battery was at 20% load.
When I plug it in the PC it is recognized as UNKNOWN DEVICE. What I do to try to recover it? as seen videos of people recovering MOTO G1 AND 2, MOTO X 1 and 2. Thank you in advance!
Rwaan said:
People need help. Sorry if'm posting in the wrong place, I'm new here.
I have a Moto X Play (XT1563) And after I flash it to the stock rom 6.0 he installed it right more at the time of restart he did not call more, no charges and no starts in fastboot.
The bootloader it was unlocked, and the battery was at 20% load.
When I plug it in the PC it is recognized as UNKNOWN DEVICE. What I do to try to recover it? as seen videos of people recovering MOTO G1 AND 2, MOTO X 1 and 2. Thank you in advance!
Click to expand...
Click to collapse
1st thing is please Charge your moto x play First ,it must be charged at least 50%
2nd I cant understand what u want to say .
So, Please calm Down and Explain It.
xpectedme094 said:
1st thing is please Charge your moto x play First ,it must be charged at least 50%
2nd I cant understand what u want to say .
So, Please calm Down and Explain It.
Click to expand...
Click to collapse
My bike x play does not turn over and not charge or enter the fastboot mode, I was in the custom rom RR 6.0 went back to the stock and the battery was only 20% used the following commands FlashFile file in cmd ...
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
* q in the last command is to restart it hung up and did not care anymore.
Rwaan said:
My bike x play does not turn over and not charge or enter the fastboot mode, I was in the custom rom RR 6.0 went back to the stock and the battery was only 20% used the following commands FlashFile file in cmd ...
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
fastboot reboot
* q in the last command is to restart it hung up and did not care anymore.
Click to expand...
Click to collapse
If its not charging then there might be problem in your Charging Jack.
First press power Button ( Around 10 sec ) When Screen Off Immediately press Power and Volume less Button.
Bootloader Mode opens .
Connect Your Charger and Check whether Charger Connected or Not ??
Now
I
Came To Your Question * q in the last command is to restart it hung up and did not care anymore. ??
When You Command " fastboot reboot " it hang up to " Bootloader unlock Screen" Its Because might be While Flashing TWRP You by mistakely Remove Your "Boot Image" and Thats Why your Mobile Hang Up.
You should Also Note That All Moto X Play dont have same Boot Image .
You First Need To Download Boot Image Flash It Then Your Problem will sohrtout For Sure.
xpectedme094 said:
If its not charging then there might be problem in your Charging Jack.
First press power Button ( Around 10 sec ) When Screen Off Immediately press Power and Volume less Button.
Bootloader Mode opens .
Connect Your Charger and Check whether Charger Connected or Not ??
Now
I
Came To Your Question * q in the last command is to restart it hung up and did not care anymore. ??
When You Command " fastboot reboot " it hang up to " Bootloader unlock Screen" Its Because might be While Flashing TWRP You by mistakely Remove Your "Boot Image" and Thats Why your Mobile Hang Up.
You should Also Note That All Moto X Play dont have same Boot Image .
You First Need To Download Boot Image Flash It Then Your Problem will sohrtout For Sure.
Click to expand...
Click to collapse
Yes, he hung up and did not care anymore. when I command "Fastboot reboot" he simply hung up and now does not care and neither starts in fastboot and also does not charge. It kind "put out the fastboot mode system" and is being recognized the computer as "unknown device" and has no way gives the flash rom stock because does not start in fastboot mode. He got hardbrick.
more where I download the boot image of it? 're Almost impossible to find a solution to this problem.
* Very need your help, Thank you!:crying:
Rwaan said:
Yes, he hung up and did not care anymore. when I command "Fastboot reboot" he simply hung up and now does not care and neither starts in fastboot and also does not charge. It kind "put out the fastboot mode system" and is being recognized the computer as "unknown device" and has no way gives the flash rom stock because does not start in fastboot mode. He got hardbrick.
more where I download the boot image of it? 're Almost impossible to find a solution to this problem.
* Very need your help, Thank you!:crying:
Click to expand...
Click to collapse
Try Flashing Firmware through RSD Lite ( Note RSD Lite Cant support Window 10)
and Please Give me Some more information .
1. Do Bootloader Mode Open or Not.
2. What Command You Exactly use when your cell Bricked .
and please reply fast.
xpectedme094 said:
Try Flashing Firmware through RSD Lite ( Note RSD Lite Cant support Window 10)
and Please Give me Some more information .
1. Do Bootloader Mode Open or Not.
2. What Command You Exactly use when your cell Bricked .
and please reply fast.
Click to expand...
Click to collapse
1. He does not enter the bootloader mode. You can not use RSD Lite to be able to give him the flash, the RSD does not recognize him because he does not enter the fastboot mode, moto x play he does nothing're completely off. when I connect the computer it is always recognized as "unknown device" so I can not give it flash or the cmd and not by RSD Lite.
2.I used all of the commands but did not pay attention had given error in any command more in the last it is simply reset the device he hung up and did not care anymore. Ai can not do anything it just know that he ta working as it appears on the computer when I connect it, the following NOTIFICATION ...
"USB Device Not Recognized,
* installing drivers ... failure.
* Unknown device. "
Every time I connect it to the computer appears such reports and have all the drivers installed and already uninstalled and installed back more not decided.
someone there gives me the file "bootloader singleimage.bin" Moto X Play (XT1563) and drivers "Qualcomm HS-USB qdloader 9008 (com12)" for me to recover my device a Hard Brick. Thanks in advance.
I have the same problem
Rwaan said:
someone there gives me the file "bootloader singleimage.bin" Moto X Play (XT1563) and drivers "Qualcomm HS-USB qdloader 9008 (com12)" for me to recover my device a Hard Brick. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem, Can you send me the files? please. do you advance with the thing? (sorry for my poor english)
laloraptor said:
I have the same problem, Can you send me the files? please. do you advance with the thing? (sorry for my poor english)
Click to expand...
Click to collapse
I have the files that can fix my machine, since'm two months without any solution. I need the files to resurrect my Moto X Play With HardBrick.
Who has the files please makes a uploud and I send. My Gmail is [email protected].
thank you!
I have same problem, my moto x play is hard bricked and gets only detected as qdloader Q9008. I am looking for the blank flash files, something like prog_emmc_firehose_8939.mbn
i also have hard bricked ( Qloader 9008 )
Did someone find a solution? Mine is also hard bricked the exact same way.
hi there I am in the same situation! any solution? any ideas?
gilbertoperezx1 said:
hi there I am in the same situation! any solution? any ideas?
Click to expand...
Click to collapse
It can be revived either by Blank flash files or by easy jtag emmc flash.. Unfortunately no one is having blank flash files.. Hopefully someone will come up with a blank flash file.. If you want to fix it quicky, then only way is flashing emmc by easy jtag box.. Like the video below..
https://www.youtube.com/watch?v=t7ZzeRGOoEw&feature=youtu.be
Moto x play hard brick
Moto x play turned off after an update and did not turn on nor does it give a precise signal of the files BlankFlash for XT1563
alexmota00 said:
Moto x play turned off after an update and did not turn on nor does it give a precise signal of the files BlankFlash for XT1563
Click to expand...
Click to collapse
Its hard bricked and no blank files aren't working as of now.. We have started a telegram group of those who got their MXp's hard bricked.. You can join too if like.. Here is the link : https://t.me/Unbrick_MXP
i have the same problem hardbrick please send me file. my mail [email protected]
david livingstone said:
i have the same problem hardbrick please send me file. my mail [email protected]
Click to expand...
Click to collapse
There is no working files available as of now..
share to me please have the same problem
Have the same problems please share to me this files
[email protected]
!Disclaimer! READ EVERYTHING... and then read everything again... If you do/don't follow everything and brick your phone oops, don't know what to tell you.
Started on Android 9.0 When building this guide.
1.) Make sure you have no SIM in your device
2.) Factory Reset your device
3.) In the setup wizard, skip !EVERYTHING!
4.) Enable Developer Options in settings and then enable USB debugging
5.) Connect your phone to PC
6.) Open Powershell in adb directory (shift right click) and type: .\adb shell pm uninstall --user 0 com.android.phone
7.) Restart your device
8.) Connect to WiFi, Open Chrome and go to google.com (or any other website)
9.) You can now Enable OEM unlocking in Developer Options
10.) Open Powershell in adb directory (shift right click) and type: .\adb reboot bootloader
11.) In Powershell type .\fastboot oem unlock
You are now ready to Push via adb
**Because of so many getting, .img Missing Errors" trying to install using the Flash-All Scripts**
The easiest way to move foward from here is to extract your Android OS image into a folder. Afterwards, extract your image zip within that folder. Rename any files that need to be Pushed to something simple without removing the file type .img. Open PowerShell in this folder containing ALL the files you need with (shift right click)
The order of installation is Important so please Read Carefully!
1.) .\fastboot flash bootloader <bootloader file name here>.img
2.) .\fastboot flash radio <radio file name here>.img
After flashing the Bootloader/Radio, you Need! to reboot the bootloader as shown below, Don't Skip This Step!
3.) .\fastboot reboot-bootloader
!Now! You can move on to the rest of the files
4.) .\fastboot flash recovery recovery.img (If Exists)
5.) .\fastboot flash boot boot.img
6.) .\fastboot flash system system.img
7.) .\fastboot flash system_other system_other.img (If Exists)
8.) .\fastboot flash vendor vendor.img (If Exists)
*****************SeeBelow*******************
9.) .\fastboot reboot
You Should now be running your choice of Android!!
**If you are installing 8.1 and older pls follow these additional steps**
8.5) .\fastboot reboot-bootloader
.\fastboot flash aboot aboot.img
.\fastboot flash apdp apdp.img
.\fastboot flash bootlocker bootlocker.img
.\fastboot flash cmnlib32 cmnlib32.img
.\fastboot flash cmnlib64 cmnlib64.img
.\fastboot flash devcfg devcfg.img
.\fastboot flash hosd hosd.img
.\fastboot flash hyp hyp.img
.\fastboot flash keymaster keymaster.img
.\fastboot flash modem modem.img
.\fastboot flash pmic pmic.img
.\fastboot flash rpm rpm.img
.\fastboot flash tz tz.img
.\fastboot flash xbl xbl.img
Side Notes:
Going from Android Q to 8.1 I got a Black Screen after the Non moving google logo screen on boot. Afterwards, the phone seemed completely dead and would not turn on. I held Volume Down+Power for almost a minute and it finally booted into Fastboot. I went through the steps again and this time I noticed the Non moving google logo screen had a lock at the bottom. I tapped it a few times and it then told me my install had an issue and I needed to do a factory reset. I chose to do so and it completed and rebooted with no issues.
I've just bought myself a brand new Pixel 1 XL - 128GB Factory Unlocked. Sadly I wasn't aware of all these issues with OEM unlocking via the Developer Menu. Not knowing the drawbacks, I casually breezed through all the upgrades and reached 10.0 (QP1A.191005.007.A3) state. It was then I realised I cocked up...:crying: because no matter what combination of instructions I try in this (and other) threads, I simply cannot get the greyed out menu to budge! I have tried at least a dozen factory resets, countless adb removals, with/without WiFi, with/without SIM, with/without Google sign in, with/without Safe Mode, with/without Guest User Profile delete and so on.... all to no avail:crying:
I am lost at the moment... I'm sure there's other in the same boat as me. I really do hope there is a solution for all of us out there.. any one have any ideas?
sidhaarthm said:
I've just bought myself a brand new Pixel 1 XL - 128GB Factory Unlocked. Sadly I wasn't aware of all these issues with OEM unlocking via the Developer Menu. Not knowing the drawbacks, I casually breezed through all the upgrades and reached 10.0 (QP1A.191005.007.A3) state. It was then I realised I cocked up...:crying: because no matter what combination of instructions I try in this (and other) threads, I simply cannot get the greyed out menu to budge! I have tried at least a dozen factory resets, countless adb removals, with/without WiFi, with/without SIM, with/without Google sign in, with/without Safe Mode, with/without Guest User Profile delete and so on.... all to no avail:crying:
I am lost at the moment... I'm sure there's other in the same boat as me. I really do hope there is a solution for all of us out there.. any one have any ideas?
Click to expand...
Click to collapse
Have you tried adb pm uninstall android.phone?
djared704 said:
Have you tried adb pm uninstall android.phone?
Click to expand...
Click to collapse
Yes, tried that method too - nothing works. I just sold my Pixel XL and bought a Pixel 2 instead
recently im using arrows os today im trying to flash stock rom and it fails then try to reset all from rcoververy and try again but the next time i try my phone trun of now my phone not even charging mybe bootloader also deleted ...anyone know? how to fix it
abir zzzz said:
recently im using arrows os today im trying to flash stock rom and it fails then try to reset all from rcoververy and try again but the next time i try my phone trun of now my phone not even charging mybe bootloader also deleted ...anyone know? how to fix it
Click to expand...
Click to collapse
please help mee