Related
My MT4GS is boot looping. I can get into the bootloader, but can't get into recovery and flashing a stock image doesn't do anything. I've unlocked the phone and achieved S-OFF using the j-bear wire trick. I've ran the phone for a few weeks after getting the s-off, so I don't think it's that. When I flash a stock image from the bootloader, the software/radio versions don't change and it still boot loops. I also have a faint red light in the notification and trackpad. I'm out of ideas. Anyone have any suggestions?
well first thing id attempt is to grab an image of a recovery and try and flash it through fastboot, image HERE
fastboot command
Code:
fastboot flash recovery recovery.img
if you need any further instruction on how to use fastboot you can get some info HERE
or if this dosent work or have more questions feel free to ask
its not a brick if you can get into hboot, you may have a tough time getting your phone working again but usually its doable.
good luck!
Thanks for the quick reply. I did a recovery flash through fastboot (CWM 5.0.2.7), but still couldn't get to recovery. I was able to update hboot to the jb_hboot. That allowed me to perform some more fastboot commands, such as: erase boot, recovery, system, userdata. I then tried to flashed a signed stock image, but still got stuck at boot loop and couldn't get into recovery. I might try TWRP recovery to see if it changes anything.
what all does it say on your bootloader screen now?
It says:
= Juopunut Bear =
DOUBLESHOT PVT SHIP S-OFF RL
HBOOT-1.45.1313
RADIO-11.16.3504.20_2
eMMC-boot
Nov 21 2011, 20:20:47
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
demkantor said:
Well it let you write to the emmc so that's a good sign. Did it give you an error in fastboot? Or did it say completed in .9 sec or something like that?
What happens when you choose recovery from the bootloader screen? Also have you tried adb reboot-recovery?
Sent from my Desire Z using Tapatalk 2
Click to expand...
Click to collapse
Riyal said:
when you say you cant get to recovery what's basically happening when you boot to recovery? Red triangle on screen? reboot loop? black screen? or what else.
Click to expand...
Click to collapse
I didn't get a fastboot error when I wrote to boot, it said completed and a time. When I choose recovery, I get a boot loop. I can't connect via adb. I don't think I have the right drivers setup for adb because when I type "adb remount" it says no device found.
Drivers taken from weekendsr2shorts mirror thread
it is strange that you can get fastboot working but not adb, but maybe more digging needs to be done to solve that. but it could just be from hboot screen there is no access to adb... come to think of it that sounds normal
try erasing recovery partition and flashing again, maybe there is some corruption there that stuck around even after the last flash
Code:
fastboot erase recovery
fastboot flash recovery recovery.img
fastboot reboot-bootloader
see if any of that works
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Not too sure a great way of telling, maybe try reformatting recovery? On a side note what exactly were the stock image you were trying to flash? I believe there is an issue when flashing certain stock setups after the radio s-off, being the way bootloader varifies the radio, recovery, Rom, etc. Sometimes things can go awry when doing this. I don't have a ds yet (still waiting on stupid parts from China) so I haven't done a whole lot of research on this phone. Maybe someone will chime in who knows more specifically what to be looking for
Sent from my Desire Z using xda premium
I tried to flash both "PG59IMG_Doubleshot_TMOUS_1.55.531.3_Radio_11.59.3504.00_11.16.3504.20_2_release_227956_signed" and "PG59IMG_Doubleshot_TMOUS_1.63.531.2_Radio_11.59.3504.00_11.16.3504.20_2_release_245247_signed". You think I should try a custom ROM instead? Is there one available to flash through the bootloader or fastboot? I tried to flash the signed stock image zips with fastboot, but it complained about not finding expected signature. Sorry to hear about your DS. Hope you get your parts soon.
rumi409 said:
Erasing and flashing recovery still resulted in a boot loop. How can I find out if there is a corruption in flash?
Click to expand...
Click to collapse
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Well you can flash roms through fastboot,
fastboot update.zip
Just change the name of the Rom to what's needed
Maybe try to format as many partitions as you can through fastboot first?
Sent from my Desire Z using xda premium
WeekendsR2Short said:
Here's a copy of my "platform-tools" files. They've always been flawless for me. You can also take the PG59IMG file and rename it to JUST PG59IMG.zip, put it in the root directory of your SD card and reboot and see if your bootloader will load it for you.
**you'll need to get a recovery operational before you can move on to custom ROMs. Edit: UNLESS you want to use Update.zip (See demkantor's post below.....)
This IS assuming that the main files you're running thru ADB have no corruption issues though.
Click to expand...
Click to collapse
I flashed this recovery image via the bootloader and fastboot. Still no luck. Is erase and format the same thing? I've erased boot, recovery and system. I checked that they were erased by doing a Image CRC, which resulted in a 0 value. Then flashed the signed DS ROMs. It still resulted in the same, boot loop.
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
demkantor said:
erasing will wipe out whats in the partition, formatting will get rid of the partition and replace it with a new one. so think of it as a super eraser sorta
fastboot format recovery
but you can also see if any of this helps but im not too sure it would
fastboot format system
fastboot fromat boot
fastboot format userdata
fastboot format cache
also you can do a fastboot oem format, never done this but my understanding is it will reformat most partitions for you, and something is nagging me about this one and i just cant remember, ill do some googleing and get back on that, although im not sure if any of this will help too much in your situation
Click to expand...
Click to collapse
I can't seem to get any of the format commands to work. It just displays the fastboot commands and options, as if I typed something it can't understand.
Have you tried a different SD card?
mattlowry said:
Have you tried a different SD card?
Click to expand...
Click to collapse
I'm not using a micro sd card. Have been flashing through the computer.
rumi409 said:
I'm not using a micro sd card. Have been flashing through the computer.
Click to expand...
Click to collapse
have you tried placing the pg file on your sd card and let the bootloder load it itself?
Hello everyone,
I am asking for help because my Nexus 5 stuck into bootloop suddenly. My phone is unrooted, bootloader in locked state, as I have never flashed any ROM in my phone. I am not keen on getting the files in my phone back but just want to use the phone again. I have tried many methods to restore my phone but still, I failed. I can go to fastboot and recovery mode. However, my phone is still in locked state, I could not flash any factory image into it using Nexus root toolkit nor put any rom files to sdcard. and I couldn't unlock the boot loader as it is in a boot loop. Do anyone got any ideas to save my phone, please help me.
P.s. I have already tried the following methods:
Method1 ( Failed because my phone is in locked state, cannot push any ROMs into it.)
-setup ADB, connect phone while its in recovery to adb.
-Download a rom for your phone (you can head over to XDA to look for rom and download one you like). Just download it to your pc.
-Connect your phone to pc using USB.
-Open cmd and enter the command adb push PathAndNameOfROMFile.zip /sdcard/. This will push the rom file you downloaded above to sdcard.
-Wipe your system, dalvic cache, cache and data (recommended, but not necessary if you downloaded same rom as previously installed on your phone).
-Reboot.
Method2 ( Failed because my phone is in locked state)l, cannot write any ROMs into my phone)
Semi-Case 2:
-There is some problem flashing some specific part.
-In this case, you can try flashing manually.
-Run these commands One by One in cmd/terminal (replace C:/ with path to where you extracted the official factory ROM archive):
fastboot flash bootloader C:/image-hammerhead-xxxx/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-xxxx/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-xxxxx/system.img
fastboot flash userdata C:/image-hammerhead-xxxxx/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-xxxx/boot.img
fastboot flash recovery C:/image-hammerhead-xxxx/recovery.img
(Skip the above command if you dont want to flash stock recovery and are sure that your current recovery is not corrupt).
Fastboot erase cache
-This will manually flash everything. Hopefully this time it should be fine.
If you can get into recovery try wiping your cache from there. Try more than once if it doesn't work the first time.
Sent from my SHIELD Tablet using Tapatalk
frenziedfemale said:
If you can get into recovery try wiping your cache from there. Try more than once if it doesn't work the first time.
Sent from my SHIELD Tablet using Tapatalk
Click to expand...
Click to collapse
I have tried that for a few times, but a flashing recovery mode android logo appears after I wiped the cache.
Unfortunately you may have to unlock your bootloder and reflash the firmware. Not that difficult but will wipe your phone so you will lose any photos or data that you may have on it.
frenziedfemale said:
Unfortunately you may have to unlock your bootloder and reflash the firmware. Not that difficult but will wipe your phone so you will lose any photos or data that you may have on it.
Click to expand...
Click to collapse
Thank you for your advice, I don't mind losing the data. I have tried unlocking the bootloader but when my phone is unlocked using Nexus Root Toolkit, it goes into boot loop and become locked again when I goes into fastboot mode.
Hello everyone,
I have accidentally messed up a TF700 device that my grandma received from a friend. Now I am stuck in a loop, when the device boots up directly into recovery. In recovery, I can connect with adb and reboot to bootloader with fastboot mode, where I see the three icons and I can connect with fastboot, I can even boot the stock ROM, which works fine now, because /data has been wiped.
I have been looking for recovery blob on Asus website, but it looks like Asus has totally cut off the device support, I can not find anything.
Because I have been doing lots of nasty things to the tablet, by following a guide for flashing the TF201 (long story including wrong model name on the device sticker ) the easiest solution is probably to flash the original recovery, bootloader and ROM. Does anyone has by accident the recovery blob for Bootloader 1.00e ww_epad-10.6.1.14.10-20130801 a03 ?
Or is there any other solution for the loop? The problem is that in the recovery, I can not do almost anything, no partition can be mounted, I have probably flashed recovery for TF201.
Thank you.
Yes, best would be if you reflash the Asus firmware, then start from scratch.
Geab the zip here https://www.androidfilehost.com/?fid=817550096634791660
Extract it until you see the system blob (called simply "blob"), move it to your fastboot directory and flash it in fastboot:
fastboot flash system blob
Reboot
That returns you to a stock system.
Then flash the latest TWRP, format /data, then flash your Katkiss rom of choice
Good luck
Sent from my Pixel 2 using Tapatalk
This is awesome, thank you for such quick reply. Just one more question, is it OK to flash US recovery if there is WW version bootloader? Just to be sure not to scew it even more
Yes, flash away. The bootloader is the same for WW and US, just some wifi modules are different, I think.
That firmware is US anyway and it includes the bootloader, so you'll have a US BL afterwards
Sent from my Pixel 2 using Tapatalk
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
hornmich19 said:
OK, sounds good then
I have tried downloading the archive now several times and no matter what program I use for unpacking, I always get error. May I ask you please to verify that the file is alright?
Click to expand...
Click to collapse
Works fine for me. Downloaded it and it opened without problem. Try this link, uploaded the same file here: https://www.dropbox.com/s/tz1lcspqayhs7ug/US_epad-user-10.6.1.14.10.zip?dl=0
No I just can not extract it
7-zip, winrar, gzip tried and I always get CRC error. I can however open it to see what files are inside, but not extract the blob to flash it. So maybe there was a little misunderstanding.
So Good news (partially), I have managed to find on the Internet similar package with WW. Extracted the blob and flashed to system partition. But nothing has changed, it is still booting right to recovery (FlatLine CWM)
Strange thing is, in recovery, I can not mount any partition.
Another strange thing is that in the fastboot mode, there is no blue progress bar as it used to be before I damaged it. Also it does not respond to any reboot commands. I have to do hard reset.
Any idea to try out, please?
Mhhh, maybe you have to go the super clean route.
Run these commands one after the other, letting every single one finish. Some are very fast, some take a bit longer
fastboot erase misc
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase boot
fastboot erase userdata
fastboot flash system blob
fastboot reboot
If it hangs at any of the commands (30 min or more does not return to prompt) just reboot with the buttons and continue with the next command.
Good luck
Awesome, I have some progress here, thanks to you. After formating the other partitions, the fastboot screen finally started to react and the blue progressbar appeared and the blob has been flashed.
After that, I have rebooted the tablet and it was stuck on the ASUS splash screen. When I rebooted to fastboot again, and tried recovery, I got Dead Android image instead. So there was no recovery image on the partition. When I tried to select cold boot to Android, I gets stuck again. So I have at least flashed TWRP recovery back again and I can boot to that recovery.
Also it looks like, despite of what was the archive name, I have now US bootloader and not WW anymore
So how to ged rid of the ASUS splash screen now? I suspect there is no kernel and RAMdisk on the boot partition now, since I have formated it, right?
I have tried flashing the JB kernel linked in the thread here https://forum.xda-developers.com/showthread.php?t=1919961 but without any result. However I am not 100% sure about the android version.
Or maybe this is a good time to flash completely different ROM?
Ok, step-by-step...
Strange though that it did not boot after flashing the blob... hope you do not have something else going on.
The Asus blob contains everything: Every partition is reflashed with stock software so everything should be in place. The dead Android is the stock recovery showing that it cannot find anything to flash. That is perfectly normal and healthy.
Yes, do not try to piece the system together, flash a full rom now (after formatting /data in TWRP).
https://forum.xda-developers.com/tr.../guide-convert-data-to-f2fs-twrp-2-8-t3073471
I would recommend one of the KatKiss roms, the latest is here:
https://forum.xda-developers.com/transformer-tf700/development/rom-t3457417
Hello and sorry for not replying long. The baby at home was sick so I didn't have time to play with the tablet.
I have flashed the ROM you linked and the tablet finally is booting and working :victory: Or so far it looks like that
Thank you so much for your asistance here, I learned a lot on this journey.
For whatever it is worth, I just had a sudden occurrence of a similar problem. Im still using this tablet on an almost daily basis and one day it started a boot loop. When I tried the RCK it would show TWRP and then bootloop again. Followed the 'simple clean' steps and reflashed twrp and clean version of KatKiss and now good to go! Thanks @berndblb for the refresher course in fastboot commands.....
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Benfran said:
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Click to expand...
Click to collapse
You can copy the full ota.zip into the root of your storage and can manually install it with system updater.
This update works pretty good here for me. Do you use any magisk modules? Themes for example? Deactivate all and try to install latest ota again.
Benfran said:
Hi,
I just updated to the latest version for my EU op8t (11.0.6.9) , and since the update System settings have completely disappeared !! There's no settings icon anymore !!
Also, whenever i try to check "app info" for any app, nothing happens, and i get an error saying "services keeps stopping" .
I'm rooted with magisk, but that is working fine after the update.
Please someone give me any type of solution, as the phone is pretty much useless, without being able to change any kind of Setting (wifi, bluetooth, info, etc).
How can i manually reflash this the previous version from fastboot ? I have downloaded the full OTA, but i don't know the command, and also if it's possible to go to a previous version without losing data ?
Or maybe it's better if i reflash it from stock recovery (if possible) , or any app, if there's any ?
Thanks in advance
Click to expand...
Click to collapse
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Kollachi said:
You can copy the full ota.zip into the root of your storage and can manually install it with system updater.
This update works pretty good here for me. Do you use any magisk modules? Themes for example? Deactivate all and try to install latest ota again.
Click to expand...
Click to collapse
Thanks but I can't do this, as i can't access system settings. Will it work with Oxygen updater app ?
EDIT: Oxygeon updater, also uses system settings...
Qnorsten said:
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Click to expand...
Click to collapse
Thanks. Will try this if the above method doesn't work first.
Qnorsten said:
Use payload dumper to extract all the images from payload.bin in the ota.
Use fastbootd (reached by doing reboot fastboot from the bootloader)
Flash each of the extracted partition with the command
fastboot flash boot boot.img and so on
Click to expand...
Click to collapse
Before reflashing i tried to wipe cache from stock recovery, like you mentioned in my other post, but now i'm really screwed i think.
It started correctly the first time, but was stuck on start screen on "starting system" or something like that.... But then suddenly rebooted itself and is now stuck in the boot logo....nothing happening, and unresponsive to my forced restart with keys.
What can i do ?
Thanks
EDIT: Managed to get in fastboot, and started flashing all the .img
But i'm getting some errors with some of them:
Either FAILED (remote: 'Value too large for defined data type') or fastboot: error: boot partition is smaller than boot image (with modem and others)
Benfran said:
Before reflashing i tried to wipe cache from stock recovery, like you mentioned in my other post, but now i'm really screwed i think.
It started correctly the first time, but was stuck on start screen on "starting system" or something like that.... But then suddenly rebooted itself and is now stuck in the boot logo....nothing happening, and unresponsive to my forced restart with keys.
What can i do ?
Thanks
EDIT: Managed to get in fastboot, and started flashing all the .img
But i'm getting some errors with some of them:
Either FAILED (remote: 'Value too large for defined data type') or fastboot: error: boot partition is smaller than boot image (with modem and others)
Click to expand...
Click to collapse
Your command should be something like this
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
and so on
Sorry if I wasn't clear enough about that in my previous post
Qnorsten said:
Your command should be something like this
fastboot flash product product.img
fastboot flash abl abl.img
fastboot flash aop aop.img
fastboot flash bluetooth bluetooth.img
and so on
Sorry if I wasn't clear enough about that in my previous post
Click to expand...
Click to collapse
Oh ok !
I was doing fastboot flash BOOT .... with all of them.
I'll try again now.
Thanks
Benfran said:
Oh ok !
I was doing fastboot flash BOOT .... with all of them.
I'll try again now.
Thanks
Click to expand...
Click to collapse
Any luck?
If not the unbrick msm tools will definitely restore the phone. But also wipe the whole phone
Qnorsten said:
Any luck?
If not the unbrick msm tools will definitely restore the phone. But also wipe the whole phone
Click to expand...
Click to collapse
No luck.
I flashed all the .img and rebooted correctly. As before, everything works fine , except System settings (icon doesn't even appear). So i can't even check what version i have installed...
There was one issue flashing in fastboot though...only with 3 of the .img files :
reserve.img
xbl_config_lp5.img
xbl_lp5.img
With these 3 i got an error, the same one for all 3:
Writing 'reserve' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Any idea as to why i'm getting this error and do you think this is related to the settings error ?
Thank you for all the help !
It finally worked !
I disabled the only magisk module i had active, and again flashed all the .img (still got the same 3 errors as above) and rebooted, and the system settings finally appear.... Although under a weird name.
The settings app is now called "Set data limit".
Also the characters of the clock app name are in Chinese now...
Besides these 2 things, the rest seems to be working fine now with 11.0.6.9
Thanks Qnorsten !
Hi! My old phone is booting into fastboot mode, when I try to boot normally I get a black screen, the "Power off" button appears when I hold the power button. The bootloader is not unlocked and the phone was never rooted. Wiping the user partition does not help. It is visible in fastboot mode and I can enter stock recovery, though trying to adb sideload a stock rom returns an error (footer is wrong; signature verification failed). Trying to fastboot boot twrp or recovery.img doesn't work either. I've ran out of ideas, what should I do to get this phone to work?
Try flashing the stock ROM with fastboot. I'm pretty sure ADB doesn't let you flash onto your phone because using your phone with ADB means that it's still powered on - which can cause some issues. You can also try and unlock your bootloader through fastboot, and then flash a recovery and custom ROM.
Both failed. I attached the errors I recieved.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try "fastboot bootloader unlock", maybe. Also: Is there a flashall.bat in the stock ROM folder? If there is: Connect your device while in fastboot, and double-click it.
crepper4454 said:
Both failed. I attached the errors I recieved.
Click to expand...
Click to collapse
Try this maybe. I know you can't wipe through the stock ROM, so, try the command: "fastboot -w". That'll wipe everything off the device.
[INDEX][Osprey][Merlin] Moto G Factory Firmware Images
Disclaimer: I am not responsible for anything that happens as a result of flashing these files. Your destiny is your own. Moto G (3rd Gen) Factory Firmware Images - Provided by Firmware TEAM - Please report broken links. New Mirrors welcome...
forum.xda-developers.com
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
crepper4454 said:
I can wipe through stock recovery. I did fastboot -w and it cleared the cache and userdata partitions, they were already clean afaik. Typing fastboot bootloader unlock returns unknown command. There are no .bat files in my firmware. I can try downloading one from the site you linked, but I don't know what to do with it if fastboot flash does not work.
Click to expand...
Click to collapse
Try this: https://forum.xda-developers.com/t/guide-osprey-fastboot-flashing-factory-firmware-images.3187750/
It says there that the "preflash validation failed" error occurs when the firmware being flashed is older than the one already installed. I will try downloading a newer version and flashing it. Will update here.
Update: I have dowloaded a newer rom and tried to flash it. This time got different errors (picture attached, this went for every sparsechunk). I think I know the reason but I do not know how to solve it. This might not be the exact stock rom of this phone so I cannot flash it with a locked bootloader. Could someone help me finding the correct rom or suggest a different solution?
Yooooo. I have the Moto e5 Cruise and so does my wife. We bought them in 2018 from Cricket and last night hers went to emmc failure, also known scientifically as 'no worky' mode.
The phone would only load in fastboot and had tried to use my Moto RSD tool to reflash but the phone would not detect in anything but fastboot mode.. Here's where it gets interesting....
There is a piece of software called the Lenovo (which now owns Moto) Rescue and Smart Assistant that can reflash your phone back to factory, no matter your sub-variant (cricket, metro, etc). Without having a fresh backup on hand, you're going to be beholden to the last cloud sync or manual backup you have because all data will be wiped in the below process.
BTW: Just run the assistant as it seems to be the easiest 'back-to-stock/working' tool I can find. Going to fastboot alone yielded weird errors since i didn't have the unlock code for the 'fastboot oem unlock [code goes here]' command.
**RESTORATION PROCESS**
This will apply to multiple Lenovo/Moto Mobility devices. Unknown at this time how many have been impacted by this seemingly pre-planned failure on Lenovo's part.
If your phone is stuck in fastboot mode where MTK download mode does not load, nor does adb, follow these simple steps:
(NOTE: BACKUP YOUR FILES IF POSSIBLE)
1. Click the link above to be directed to the Lenovo software download page and run the installer on your PC (Sorry Mac users :'().
2. The software, once installed, will require you to sign up for OR link a google, fb, g+, etc account to it for purposes of creating a Lenovo ID. Once signed in, click on 'Rescue Now'.
3. With your phone in fastboot mode, allow the software to download the firmware for your phone.
4. Once the firmware has finished downloading and validating, click on 'Rescue Now' once again. Your phone will begin the reflashing process.
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
crepper4454 said:
That... actually worked. The program found the required ROM and flashing went without problems. Thank you very much @kmt5150 .
Click to expand...
Click to collapse
No problemo! Glad it worked!